Richard Lithvall wrote:
Hi,
While trying to track down what causes problem with a (probably crappy but very useful) patch/plugin to VDR I noticed this odd behaviour when zapping through channels: Aug 25 23:21:51 localhost vdr[3206]: status: cStatusTest::ChannelSwitch 0 0 Aug 25 23:21:51 localhost vdr[3206]: status: cStatusTest::ChannelSwitch 1 0 Aug 25 23:21:51 localhost vdr[3206]: status: cStatusTest::ChannelSwitch 1 4 Aug 25 23:21:51 localhost vdr[3206]: status: cStatusTest::ChannelSwitch 0 4
My primary card is an TT DVB-S 1.6 FF and my secondary card is an TT DVB-T 1.2 FF. Channel 4 is DVB-T. Why are my primary DVB-S card trying to tune this channel?
With the patch applied and plugin enabled it causes several more errors such as "ERROR: no DiSEqC parameters found for channel 4" looping over and over until VDR restarts.
I've tried with patched/unpatched VDR 1.3.22, 1.3.23 and 1.3.30 and all behave the same.
Your primary device isn't actually trying to tune to that channel. The first line (0 0) comes from the primary device switching away from the current channel (this may not have any physical implications if the primary device isn't actually receiving this channel directly). The second line (1 0) is the secondary device switching away from its current channel (whatever it may have been). Line three (1 4) is the secondary device actually tuning to the channel, and line four (0 4) is the primary device finishing the channel switch.
So the last line is more like a "virtual" switch, since the primary device is actually getting the channel from the secondary device.
In no case does a DVB-S card try to actually tune to a DVB-T channel.
Klaus