Reinhard,

 

Thanks for your help and description.

 

Can anyone help me track down what might be the problem? I built my own kernel could a setting there be a problem? What settings are recommended for type of IO scheduler, timer frequency, etc? Anyone else have a similar problem and can recommend a fix?

 

Cheers,

 

Morfsta

 

On 2/5/07, Reinhard Nissl <rnissl@gmx.de> wrote:

Hi,

Morfsta wrote:

> Lots of TS Continuity Errors in the messages file.
>
> Feb  5 08:25:00 morfsta vdr: [19772] TS continuity error (11)
> Feb  5 08:25:01 morfsta vdr: [19772] cAudioRepacker(0xC0): skipped 588
> bytes to sync on next audio frame

Sad to say, I'm happy that this is not a bug in cAudioRepacker.

So what can you do about this TS continuity errors? First of all, this
error means that at least one TS packet got lost, most likely by the
fact that the card's hardware buffers where overrun. A overrun can
happen when for example the kernel is busy with other things and doesn't
react to the cards signalling (e. g. IRQ) in time.

Several months ago, I had my PATA harddrive sent in for repair and
substituted it by a SATA model. The result was, that I wasn't able to
take a single VDR recording on my P4 2.8 GHz without TS continuity
errors. When I got the PATA drive back and removed the SATA model, the
TS errors were gone.

So I'd say this is a hardware/driver/configuration issue -- but not
necessarily in the DVB area. I hope, someone else can give you further
hints.

Bye.
--
Dipl.-Inform. (FH) Reinhard Nissl
mailto:rnissl@gmx.de

_______________________________________________
vdr mailing list
vdr@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr