Hi, I have looked into this further. It appears that I only get the TS continuity errors when using my budget DVB-T card to view live TV.. They do not appear when using my FF DVB-S card.
Does this shed any light on things? The DVB-T stream is less robust that DVB-S, but the picture does not generally break up regularly or appear to suffer any major problems. Could it be a problem with my Hauppauge budget DVB-T card? SWITCH TO SATELLITE CHANNEL: - Feb 9 10:42:08 morfsta vdr: [25446] switching to channel 166 Feb 9 10:42:08 morfsta vdr: [25446] retuning due to modification of channel 166 Feb 9 10:42:08 morfsta vdr: [25446] switching to channel 166 Feb 9 10:44:47 morfsta vdr: [25446] cleaning up schedules data Feb 9 10:45:00 morfsta vdr: [25540] EPGSearch: timer conflict check started Feb 9 10:45:00 morfsta vdr: [25540] EPGSearch: timer conflict check finished Feb 9 10:51:01 morfsta vdr: [25536] channel 27 (CBeebies) event Fri 09.02.2007 10:50-11:00 'Boo!' status 4 Feb 9 11:02:12 morfsta vdr: [25536] channel 27 (CBeebies) event Fri 09.02.2007 11:00-11:15 'SMarteenies' status 4 Feb 9 11:09:19 morfsta vdr: [25446] cleaning up id3 cache Feb 9 11:15:00 morfsta vdr: [25540] EPGSearch: timer conflict check started Feb 9 11:15:00 morfsta vdr: [25540] EPGSearch: timer conflict check finished Feb 9 11:17:32 morfsta vdr: [25536] channel 27 (CBeebies) event Fri 09.02.2007 11:15-11:45 'Teletubbies' status 4 SWITCH TO FREEVIEW DVB-T CHANNEL: - Feb 9 11:35:55 morfsta vdr: [25446] switching to channel 1 Feb 9 11:35:57 morfsta vdr: [25536] channel 2 (BBC TWO) event Fri 09.02.2007 11:20-11:40 'Schools: Focus' status 4 Feb 9 11:35:57 morfsta vdr: [25536] channel 1 (BBC ONE) event Fri 09.02.2007 11:00-11:45 'To Buy or Not to Buy' status 4 Feb 9 11:38:12 morfsta vdr: [12243] TS continuity error (15) Feb 9 11:38:12 morfsta vdr: [12243] TS continuity error (1) Feb 9 11:38:12 morfsta vdr: [12243] TS continuity error (9) I generally only get sync problems on live DVB-T broadcasts (as well as all recordings). Hope this helps, Regards, Morfsta On 2/5/07, Morfsta <[EMAIL PROTECTED]> wrote:
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 <[EMAIL PROTECTED]> 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:[EMAIL PROTECTED] > > _______________________________________________ > vdr mailing list > vdr@linuxtv.org > http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr >
_______________________________________________ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
