[vdr] VDSB Video Data Stream Broken

Klaus Schmidinger Klaus.Schmidinger at cadsoft.de
Fri Jan 6 19:07:21 CET 2006

Udo Richter wrote:
> Klaus Schmidinger wrote:
>>I have attached a slightly modified version of the patch, which
>>avoids error messages like
>>  ERROR (dvbdevice.c,157): Value too large for defined data type
>>when clearing the event queue. It also returns the current frontend status
>>even if there was no event, and logs the channel number and transponder
>>in case of a timeout. As far as I can see the timeouts always happen
>>on transponders that are currently not broadcasting, or use very low
>>symbol rates, which my full featured second device can't handle.
> For me, I'm currently getting errors for tp 10773h, 10832h, 10861h,
> 10920h, 11479v, 11914h, 12441v and 12522v. The four low-band
> transponders are known PITA of my card, and the four high-band
> transponders are empty according to lyngsat.
> One case looks like the lost lock state needs additional resetting on
> transponder change:
> 18:22:09 vdr[]: ERROR: frontend 1 lost lock on channel 705, tp 110920
> 18:22:11 vdr[]: frontend 1 regained lock on channel 347, tp 111720
> There were no other messages between these two.
> Cheers,
> Udo

Incidently I had already added the necessary source line, but
then I thought it might not be that bad to have that "regained"
message, because otherwise there would be a "lost lock" message
in the log without any "regained lock", even if in fact the lock was
actually regained.


More information about the vdr mailing list