single transponder scan on Astra 19.2E triggers the scanning of all existing transponders

[pik]

This happens only with Astra 19.2 E, not with hotbird 13.0 E. The only way out is to interrupt the scanning mlanually otherwise it scans all existing transponders defined for Astra 19.2 E in my database ( Astra 19.2E is defined asa source in my setup -

[pik]

tested with svn 21583, kernel 2.6.30 and s2-liplianin drivers

[pik]

This problem can be reproduced by scanning the following transponders on Astra with mythtv-setup:

( Astra 1L (19.2E) - 12581.00 V - Txp: 110 - Faisceau: Astra 1L DVB-S2 (8PSK) - 22000 2/3 - NID:1 - TID:1110)

Please note that it also happens with a fresh database, so it looks like that the single transponder scanning function of mythtv-setup is exploiting the info in provided in the signal tuned to scan all the other Astra 19.2E transponders ( since the database is empty and fresh at that time )

[pik]

mythtv-setup log

[Janne Grunau]

This is not a bug. The scan type is "Full Scan (Tuned)" and it scans all transports it finds in the NIT. It looks like the transport you scanned on Hotbird doesn't have a NIT or just a single transport in it.