DVB-T scan: duplicate muxes created for MPEG channels

[Nick Morrott <knowledgejunkie (at) gmail (dot) com>]

Using the same configuration as reported in #8726.

Scan details: full UK scan using Sutton Coldfield transmitter with 6 available muxes. Signal/tuning timeouts raised to 2000/6000ms. ALL services (DVB+MPEG) scanned, with decryption testing disabled.

During a successful DVB-T scan, all DVB channels are eventually discovered (although only 1 mux was successfully tuned during the initial scan phase and the remaining 5 muxes were found in the Network Information Table of the successfully scanned mux.)

However, although there are only 6 available muxes, 9 muxes are created in the database at the end of the scan.

Further checking reveals that the creation/configuration of the 4 MPEG channels found during the scan creates 3 new mux entries in the database, rather than configuring them with one of the existing mux entries used for the DVB channels on those muxes. Additionally, networkid is set to 0 on the additional muxes.

Full log output is attached to #8731

[stuartm]

I don't think this is going to get looked at for 0.25, not without a patch at least however it should be dealt with early in 0.26.

[Stuart Auchterlonie]

Milestone renamed

[Stuart Auchterlonie]

Moving remaining open tickets to 0.28.2 milestone

[Stuart Auchterlonie]

Moving remaining open tickets to 29.2 milestone

[Klaas de Waal]

Is there still a problem when you make a scan with the current pre-v31 master?

[Klaas de Waal]

No information is given and also the channel scanner code has been improved a lot in the last few years, therefore closing this ticket now. If the problem still persists then please re-open this ticket or create a new one.