[mythtv] [mythtv-commits] Ticket #1866: DVB Scanning - Remaining Issues

Janne Grunau janne-mythtv at grunau.be
Sun Aug 20 21:53:35 UTC 2006

On Saturday 19 August 2006 12:27, MythTV wrote:
> #1866: DVB Scanning - Remaining Issues
>   * status:  assigned => closed
>   * resolution:  => fixed
> Comment:
>  The behaviour of tuned scan as it now exists is to
>  tune to the given transport and just scan that. ie.
>  It's the same as transport scan just with a user
>  defined tranport.
>  Previously (mythtv <= 0.19) the information received
>  in the NIT would be used to add other transports to
>  the list to be scanned.
>  The current behaviour is more logical from a users
>  point of view, since they asked it to scan the
>  given transport, and are not expecting it to go
>  wandering off scanning other transports.

I disagree. The scan is called "Full scan (tuned)". I would expect that 
something called full scan will find all or almost availabe channels. 

>  The old behaviour can be acheived by doing the
>  tuned scan, and then existing transport scan,
>  as the tuned scan will populate dtv_multiplex
>  from the NIT found on the first transport.

This is for a first time user confusing and for anyone else impractical. 
Most users of Full scan (tuned) use it since there is no full scan for 
DVB-S and DVB-C.

I looked into this 2 weeks ago and agree that it can't fixed easily. We 
are probably not able to have the old behaviour in 0.20 but it should 
be fixed sometime.

>  Alternatively, full scan is available to find
>  all the transports being broadcast, which will
>  work even if the transports do not provide any
>  information about other transports, as happens
>  in certain countries.

There is no full scan for DVB-S and DVB-C. I don't think that an 
equivalent to the DVB-T full scan is practical for DVB-S and DVB-C. 
Astra 19.2E has about 100 transponders and I don't think it's a good 
idea to maintain for several orbital positions lists of transponders in 
the MythTV source code. For DVB-C we could scan the appropiate frecency 
tables we have already. Although it is most of the time more effort 
than needed.


More information about the mythtv-dev mailing list