[mythtv] Ticket #1049: DVBSignalMonitor needs to be able to monitor NIT/SDT

[Yeasah Pell]

(see bottom)

Mark Buechler wrote:

> I would highly disagree with you here. From my experience, many cards 
> tend to wander too far when tuning takes too long (especially when 
> using a rotor). Often times the DVB card will lock onto a nearby 
> frequency and never lock onto the requested one. Retuning the card is 
> the only way to fix this. The only card I've found to NOT need this is 
> the Nexus-S. I've tested the SkyStar2, Twinhan 102G, Twinhan 1020a, 
> Nexus-S and the Genpix 8psk.
>
> - Mark.
>
> On 6/6/06, *MythTV* <mythtv at cvs.mythtv.org 
> <mailto:mythtv at cvs.mythtv.org>> wrote:
>
>     #1049: DVBSignalMonitor needs to be able to monitor NIT/SDT
>     -------------------------------------+--------------------------------------
>     Reporter:  Mark.Buechler at gmail.com
>     <mailto:Mark.Buechler at gmail.com>   |        Owner:  danielk
>          Type:  enhancement              |       Status:  closed
>     Priority:  minor                    |    Milestone:  0.20
>     Component:  dvb                      |      Version:  head
>     Severity:  low                      |   Resolution:  fixed
>     -------------------------------------+--------------------------------------
>     Comment (by danielk):
>
>     (In [10132]) Refs #1552. Refs #1049. Removes DVB retuning hack
>     from SVN
>     head.
>
>     This should no longer be needed now that #1049 has been fixed.
>
>     --
>     Ticket URL: <http://cvs.mythtv.org/trac/ticket/1049>
>     MythTV <http://www.mythtv.org/>
>     MythTV
>
When the diseqc stuff I'm working on is ready (it's getting close), that 
will help with the rotor issue, since the code will know approximately 
when the rotor is done rotating, and can issue another tune request at 
that point. I think that's a better way to handle the need for 
subsequent tuning commands than the retuning hack.

There may be other reasons to do retuning besides rotors though -- for 
example, the retuning code itself talked about some buggy DVB-C hardware.