Johannes Stezenbach wrote: > > [EMAIL PROTECTED] wrote: > > status 1f | signal a9b8 | snr e12d | ber 00000000 | unc 00000000 | > > FE_HAS_LOCK > > > > This was done @22:24. Is there any documentation other than the C source > > file to explain what the above values show? > > linux-dvb archives > Anyway, ber = bit-error-rate, unc = uncorrectable-errors > -> signal is good > > > RTL was recorded without any errors. > > > > SAT1 was recorded with these errors: > > > > Oct 13 21:00:00 tvt1 vdr[795]: cTS2PES got 1403 TS errors, 9577 TS continuity > > errors > > Oct 13 21:00:00 tvt1 vdr[795]: cTS2PES got 83 TS errors, 3768 TS continuity errors > > Oct 13 21:00:00 tvt1 vdr[795]: buffer stats: 143068 (0%) used > > If you get this errors with the signal from above, the frontend > is not the problem. It could be a DMA problem. > But since the card of the same making seems to work for other people, > it is possible that your card or your motherboard is subtly broken. > > Why does VDR report two different error counts in the same second?
The first one is for the video, the second one for the audio data. > What exactly are continuity errors and TS errors in VDRs view? "TS errors" counts the TS packets where the TS_ERROR flag is set. "TS continuity errors" counts the packets where the continuity counter is not consistent. See VDR/remux.c, cTS2PES::ts_to_pes(). With that many errors I guess there must be something fundamentally wrong with the incoming data. Klaus -- Info: To unsubscribe send a mail to [EMAIL PROTECTED] with "unsubscribe linux-dvb" as subject.
