[mythtv-users] Dvb-s: handling of bad channel entries

[Eyal Lebedinsky]

Martin Bene wrote:
> Hi,
> 
> Mythtv 0.16 seemingly can't gracefully handle it if playback for an
> encrypted channel is requested while zapping in "watch tv" mode.
> Obviosuly the channel can't be displayed, but what happens is rather
> unexpected:
> 
>  - backend message:
> 2004-11-06 01:12:19 DVB#0 WARNING - Status: NO LOCK!
> 2004-11-06 01:12:19 DVB#0 Successfully tuned to channel 52.
> 2004-11-06 01:12:19 DVB#0 CAM - PMT cache updated.
> 2004-11-06 01:12:34 Couldn't read data from the capture card in 15
> seconds.  Game over, man.
> 
> - Frontend is frozen on last frame from previous program; console for
> frontend shows:
> 
> 2004-11-06 01:12:24 taking too long to be allowed to read..
> 2004-11-06 01:12:29 taking too long to be allowed to read..
> 2004-11-06 01:12:34 taking too long to be allowed to read..
> 2004-11-06 01:12:36 Waited 2 seconds for data to become available,
> waiting again...
> 
> - Default channel for watching tv gets set to the bad channel, so it's
> rather difficult to get away from the bad channel.
> 
> Is there any wayto make mythtv handle this more gracefully?

No help from me beyond saying that I see the same thing with
any bad channel on DVB-T too. Sometimes hitting ESC will
recover the frontend, but you must then run mythbackend-setup
to change the starting channel for the input.

This last bit is terrible, there must be a way to select a
viewing channel rather than drop into a channel by default
when you "Watch TV".

Anyway, is the starting channel in the "Input" definition a
per-user field? If not then it has no business changing as
a frontend changes channel.

I reported this before but saw no reply. I am now trying to
build from cvs to see if it is any better (especially as .16
is crashing so often).

-- 
Eyal Lebedinsky (eyal at eyal.emu.id.au) <http://samba.org/eyal/>