Comment 7 for bug 434994
Revision history for this message
| Michael Lamothe (lamothe-deactivatedaccount-deactivatedaccount) wrote | #7 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
bbfa235
(Get the code!)
> Wouldn't reducing the timeout just be a workaround instead of a solution?
That depends on the "solution" that Me TV is trying to solve. But your point is valid.
> Would it be possible to load the channel first, and then load the EPG data?
You misunderstood my statements earlier, the issue is not on "channel load", it's on "channel unload". I assume that the first channels starts up quickly right? It's when you exit the channel that it takes 10 seconds while it waits for the EPG read from the demuxer to timeout.
I'm not sure if there's a way to know if there's EPG data available but there's only one quick solution that I can see. Reduce the timeout period to 2 seconds (currently 10) and terminate the thread if the demuxers don't return data. My concern is when the broadcasters stop transmitting temporarily (for whatever reason maintenance, fault, loading new EPG data) and then start again. In this scenario the EPG events will not be read again until you change channel. I guess I could make it automatically start the EPG thread every minute if it's not running, this is what other applications do.