What I see happening is that when a channel does not tune 'startchan' is set blank. The next time you try to watch TV it can't tune since 'startchan' is blank. I tried a quick hack in the code that sets startchan in the database so it wouldn't write a blank field but I view this as a hack. The right solution would be to not update 'startchan' when tuning fails.

I'm away from my system right now and I won't be able to track this down any further until next weekend but I hope this information helps.

Mino


On Mar 5, 2005, at 3:48 AM, Leandro Dardini wrote:


----- Original Message ----- From: "Ed Wildgoose" <[EMAIL PROTECTED]> To: "Development of mythtv" <[email protected]> Sent: Saturday, March 05, 2005 11:32 AM Subject: Re: [mythtv] DVB lockup - a possible solution?


Leandro Dardini wrote:

I was thinking about possibile solution to lockup in tuning a dvb channel
not broadcasting



Are you using 0.17? This all seems to be fixed in the latest version?
No?

Ed W

A better response:
The lockup I am referring is a "logical" lockup. When you tune a
not-broadcasting channel, the mythfrontend returns to the main screen with
the following message on stdout:
Waited 14 seconds for data to become available, aborting
The mythtv system is fully functional, but you cannot tune another channel
and so you cannot watch livetv. If you retry livetv, the not-broadcasting
channel is again tuned and frontend exits again. The only way to exit this
loop is to access settings via mysql and change the startchan/tunechan in
videosource and restart mythtvbackend.


Leandro

_______________________________________________
mythtv-dev mailing list
[email protected]
http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-dev


_______________________________________________
mythtv-dev mailing list
[email protected]
http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-dev

Reply via email to