2012-12-31, 03:27
When I start xbmc, this message appears at the top right corner. It takes ~5 minutes for it to finish. During the 5 minutes, it looks like it is hung on the first channel in the list. After ~5 minutes, the progress bar moves and it progresses through all of the channels. It doesn't take very long for the progress bar to complete once it gets going. I've also seen the same behavior on Raspbmc and Android (both using Frodo RC2). Is this a problem with the MythTV backend or with the MythTV add-on?
xbmc version 2:12.0~git20121230.0200-3a3e082-0precise
Athlon II X4 630
4GB RAM
Ubuntu 12.04
MythTV 0.25 backend is on the same machine as xbmc
Here is xbmc.log: http://paste.ubuntu.com/1481069/
The first channel is shown by this log entry:
19:10:36 T:140462180484864 INFO: EPG - UpdateFromScraper - updating EPG for channel 'EPG Local Sports 3 Hrs.' from client '1'
followed by the rest of them starting at:
19:14:59 T:140462180484864 INFO: EPG - UpdateFromScraper - updating EPG for channel 'KDTN' from client '1'
19:14:59 T:140462180484864 INFO: EPG - UpdateFromScraper - updating EPG for channel 'KAZDDT (KAZD-DT)' from client '1'
19:14:59 T:140462180484864 INFO: EPG - UpdateFromScraper - updating EPG for channel 'KDFW' from client '1'
.
.
What's up with the 4+ minute delay?
xbmc version 2:12.0~git20121230.0200-3a3e082-0precise
Athlon II X4 630
4GB RAM
Ubuntu 12.04
MythTV 0.25 backend is on the same machine as xbmc
Here is xbmc.log: http://paste.ubuntu.com/1481069/
The first channel is shown by this log entry:
19:10:36 T:140462180484864 INFO: EPG - UpdateFromScraper - updating EPG for channel 'EPG Local Sports 3 Hrs.' from client '1'
followed by the rest of them starting at:
19:14:59 T:140462180484864 INFO: EPG - UpdateFromScraper - updating EPG for channel 'KDTN' from client '1'
19:14:59 T:140462180484864 INFO: EPG - UpdateFromScraper - updating EPG for channel 'KAZDDT (KAZD-DT)' from client '1'
19:14:59 T:140462180484864 INFO: EPG - UpdateFromScraper - updating EPG for channel 'KDFW' from client '1'
.
.
What's up with the 4+ minute delay?