[mythtv] [mythtv-commits] Ticket #1049: DVBSignalMonitor thread exits before correct transponder is locked while using a rotor
danielk at cuymedia.net
Tue Jan 17 22:16:32 UTC 2006
On Tue, 2006-01-17 at 15:31 -0500, Buechler, Mark R wrote:
> Not without DiSEqC 2.0 and cards to support it. Unfortunately, using a rotor
> is sort of a guessing game.
> After thinking about this, maybe the signal monitor should be kept on at all
Nope, lots of DVB cards have problems with that.
> Where do the individual L A M values come from which determine a full
> lock? I know L is for signal lock. The others I'm not sure.
I believe this is in the documentation in SVN. 'A' means a valid looking
PAT has been seen and 'M' means a valid looking PMT has been seen.
> Maybe if all those methods were combined into a single class which stays
> running at all times and emits (sudo-)signals on changes to the
> signal/stream to DVBRecorder then it really doesn't matter if adjacent
> satellites have identical transponder frequencies/SIDs since DVBRecorder
> would simply stop/start recording based on signals from the signal monitor.
> When it doesn't have full lock (LAM) it could send dummy frames.
Except for the 'running at all times' part, that sounds like what the
signal monitor does. It sounds like simply using the NDT and SDT tables
like we use the ATSC MGT and VCT tables would solve the problem you
have described in the ticket.
More information about the mythtv-dev