[mythtv] [mythtv-commits] Ticket #1049: DVBSignalMonitor thre ad exits before correct transponder is locked while using a rotor

Buechler, Mark R Mark_R_Buechler at bausch.com
Tue Jan 17 23:08:19 UTC 2006

Ah, yes.. excuse me while I smack myself.. That makes sense, look for a
matching NID before exiting.

- Mark.

-----Original Message-----
From: Daniel Kristjansson [mailto:danielk at cuymedia.net] 
Sent: Tuesday, January 17, 2006 5:17 PM
To: Development of mythtv
Subject: Re: [mythtv] [mythtv-commits] Ticket #1049: DVBSignalMonitor thread
exits before correct transponder is locked while using a rotor

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
> is sort of a guessing game.

> After thinking about this, maybe the signal monitor should be kept on at
> times?
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
> 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.

-- Daniel

mythtv-dev mailing list
mythtv-dev at mythtv.org


Please Note: The information contained in this message may be privileged and
confidential, protected from disclosure, and/or intended only for the use of
the individual or entity named above. If the reader of this message is not
the intended recipient, or an employee or agent responsible for delivering
this message to the intended recipient, you are hereby notified that any
disclosure, distribution, copying or other dissemination of this
communication is strictly prohibited. If you received this communication in
error, please immediately reply to the sender, delete the message and
destroy all copies of it.

Thank You

More information about the mythtv-dev mailing list