2014-11-20, 06:10
I'm loving this plugin on my RaspBMC. I'm having a bit of trouble though with autotune. I'm using entirely offline content at the moment so I've disabled any internet-based sources for autotune. The first half of autotune on startup works fine, but when it finishes building the channel list and starts to populate the channels with content before the first run, the first couple channels proceed to have 25 videos added, but when it gets to channel 3, I get..
PseudoTV Live - 3%
Updating channel 3
adding Videos
added 2 entries
And it gets stuck there. Hitting cancel does not seem to work, or at least not within 30-60 minutes. A reboot is required. Eventually I worked out that I could disable or remove channel 3 and the process continued up to channel 18 (Nickelodeon). It got stuck again, so after that I removed channel 18 and up just to get things working and after that it worked fine. If I try to leave it to finish scanning on its own over night, it doesn't make any progress.
I don't have the debug logs on me now, but I couldn't really see anything super interesting. script.pseudotv.live-master/config.py logged periodic "waiting for thread..." and "FileLock: refreshLocks entries were all I could really see in there.
Happy to post logs later, just wondering if this is a really common issue and I just need to flip a setting somewhere?
PseudoTV Live - 3%
Updating channel 3
adding Videos
added 2 entries
And it gets stuck there. Hitting cancel does not seem to work, or at least not within 30-60 minutes. A reboot is required. Eventually I worked out that I could disable or remove channel 3 and the process continued up to channel 18 (Nickelodeon). It got stuck again, so after that I removed channel 18 and up just to get things working and after that it worked fine. If I try to leave it to finish scanning on its own over night, it doesn't make any progress.
I don't have the debug logs on me now, but I couldn't really see anything super interesting. script.pseudotv.live-master/config.py logged periodic "waiting for thread..." and "FileLock: refreshLocks entries were all I could really see in there.
Happy to post logs later, just wondering if this is a really common issue and I just need to flip a setting somewhere?