[vdr] changing transponder data of channel

Klaus Schmidinger Klaus.Schmidinger at cadsoft.de
Wed Apr 12 17:50:01 CEST 2006


Richard Lithvall wrote:
> Hi VDR-gurus.
> 
> I get repeatedly annoying syslog messages from vdr stating transponder 
> data change. I randomly grep'ed after one of many channels this happens 
> to in the log:
> 
> # grep "changing transponder data of channel 205" /var/log/syslog|tail -4
> 
> Apr 12 15:55:54 localhost vdr: [29208] changing transponder data of 
> channel 205 from S1.0W:12303:v:27800:3 to S1.0W:12303:v:27799:3
> Apr 12 15:57:41 localhost vdr: [29208] changing transponder data of 
> channel 205 from S1.0W:12303:v:27799:3 to S1.0W:12303:v:27800:3
> Apr 12 16:00:46 localhost vdr: [29208] changing transponder data of 
> channel 205 from S1.0W:12303:v:27800:3 to S1.0W:12303:v:27799:3
> Apr 12 16:02:34 localhost vdr: [29208] changing transponder data of 
> channel 205 from S1.0W:12303:v:27799:3 to S1.0W:12303:v:27800:3
> 
> As you see it changes the freq from 27800 to 27799 and back again so I 
> started to dig into the source and immediately found this:
> 
> bool cChannel::SetSatTransponderData(int Source, int Frequency, char 
> Polarization, int Srate, int CoderateH)
> {
>   // Workarounds for broadcaster stupidity:
>   // Some providers broadcast the transponder frequency of their 
> channels with two different
>   // values (like 12551 and 12552), so we need to allow for a little 
> tolerance here
>   if (abs(frequency - Frequency) <= 1)
>      Frequency = frequency;
> 
> 
> As one can see, there is already a workaround for this behavior but it 
> seems that it doesn't work.
> 
> Any idea of what could be wrong?

It's not the frequency that's changing here, but the symbol rate.
Maybe we should add another "broadcaster stupidity" workaround for this?

Klaus



More information about the vdr mailing list