Multiple DVB channelscanner issues

[anonymous]

1. Full Scan only scans the transport entered, not others
   
2. Other transports found are stored incorrectly and/or bogus non-existant transports are stored (see attached file)
   
3. Channels found in the transport scanned get stored with a mplexid of one of these invalid/bogus transports, not with the correct transport, often also stored.

Library API version : 0.20.20070821-1 Source code version : 14972 SVN Branch : branches/release-0-20-fixes Options compiled in :

linux release using_xvmcw using_v4l using_oss using_alsa using_jack using_ivtv using_dvb using_x11 using_xv using_xrandr using_xvmc using_xvmc_vld using_opengl_vsync using_opengl using_frontend using_backend using_bindings_perl

And yes, I know that it is strange for a DVB-C network to be using QAM 64, but they do that here. They also broadcast DVB-T to the same network. No need to remind me of how obscure that is.

[danielk]

These issues have channelscanning component tickets.