<div>Hi,</div>
<div> </div>
<div>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.</div>
<div> </div>
<div>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?
</div>
<div> </div>
<div>SWITCH TO SATELLITE CHANNEL: -</div>
<div> </div>
<div>Feb 9 10:42:08 morfsta vdr: [25446] switching to channel 166<br>Feb 9 10:42:08 morfsta vdr: [25446] retuning due to modification of channel 166<br>Feb 9 10:42:08 morfsta vdr: [25446] switching to channel 166<br>Feb 9 10:44:47 morfsta vdr: [25446] cleaning up schedules data
<br>Feb 9 10:45:00 morfsta vdr: [25540] EPGSearch: timer conflict check started<br>Feb 9 10:45:00 morfsta vdr: [25540] EPGSearch: timer conflict check finished<br>Feb 9 10:51:01 morfsta vdr: [25536] channel 27 (CBeebies) event Fri
09.02.2007 10:50-11:00 'Boo!' status 4<br>Feb 9 11:02:12 morfsta vdr: [25536] channel 27 (CBeebies) event Fri 09.02.2007 11:00-11:15 'SMarteenies' status 4<br>Feb 9 11:09:19 morfsta vdr: [25446] cleaning up id3 cache
<br>Feb 9 11:15:00 morfsta vdr: [25540] EPGSearch: timer conflict check started<br>Feb 9 11:15:00 morfsta vdr: [25540] EPGSearch: timer conflict check finished<br>Feb 9 11:17:32 morfsta vdr: [25536] channel 27 (CBeebies) event Fri
09.02.2007 11:15-11:45 'Teletubbies' status 4</div>
<div> </div>
<div>SWITCH TO FREEVIEW DVB-T CHANNEL: -</div>
<div><br>Feb 9 11:35:55 morfsta vdr: [25446] switching to channel 1<br>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<br>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<br>Feb 9 11:38:12 morfsta vdr: [12243] TS continuity error (15)<br>Feb 9 11:38:12 morfsta vdr: [12243] TS continuity error (1)<br>Feb 9 11:38:12 morfsta vdr: [12243] TS continuity error (9)
<br> </div>
<div>I generally only get sync problems on live DVB-T broadcasts (as well as all recordings).</div>
<div> </div>
<div>Hope this helps,</div>
<div> </div>
<div>Regards,</div>
<div> </div>
<div>Morfsta<br><br> </div>
<div><span class="gmail_quote">On 2/5/07, <b class="gmail_sendername">Morfsta</b> <<a href="mailto:morfsta@gmail.com">morfsta@gmail.com</a>> wrote:</span>
<blockquote class="gmail_quote" style="PADDING-LEFT: 1ex; MARGIN: 0px 0px 0px 0.8ex; BORDER-LEFT: #ccc 1px solid">
<div>Reinhard,</div>
<div> </div>
<div>Thanks for your help and description.</div>
<div> </div>
<div>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?
</div>
<div> </div>
<div>Cheers,</div><span class="sg">
<div> </div>
<div>Morfsta<br><br> </div></span>
<div><span class="e" id="q_11093ecbb7c06220_2">
<div><span class="gmail_quote">On 2/5/07, <b class="gmail_sendername">Reinhard Nissl</b> <<a onclick="return top.js.OpenExtLink(window,event,this)" href="mailto:rnissl@gmx.de" target="_blank">rnissl@gmx.de</a>> wrote:
</span>
<blockquote class="gmail_quote" style="PADDING-LEFT: 1ex; MARGIN: 0px 0px 0px 0.8ex; BORDER-LEFT: #ccc 1px solid">Hi,<br><br>Morfsta wrote:<br><br>> Lots of TS Continuity Errors in the messages file.<br>><br>> Feb 5 08:25:00 morfsta vdr: [19772] TS continuity error (11)
<br>> Feb 5 08:25:01 morfsta vdr: [19772] cAudioRepacker(0xC0): skipped 588<br>> bytes to sync on next audio frame<br><br>Sad to say, I'm happy that this is not a bug in cAudioRepacker.<br><br>So what can you do about this TS continuity errors? First of all, this
<br>error means that at least one TS packet got lost, most likely by the<br>fact that the card's hardware buffers where overrun. A overrun can<br>happen when for example the kernel is busy with other things and doesn't
<br>react to the cards signalling (e. g. IRQ) in time.<br><br>Several months ago, I had my PATA harddrive sent in for repair and<br>substituted it by a SATA model. The result was, that I wasn't able to<br>take a single VDR recording on my P4
2.8 GHz without TS continuity<br>errors. When I got the PATA drive back and removed the SATA model, the<br>TS errors were gone.<br><br>So I'd say this is a hardware/driver/configuration issue -- but not<br>necessarily in the DVB area. I hope, someone else can give you further
<br>hints.<br><br>Bye.<br>--<br>Dipl.-Inform. (FH) Reinhard Nissl<br>mailto:<a onclick="return top.js.OpenExtLink(window,event,this)" href="mailto:rnissl@gmx.de" target="_blank">rnissl@gmx.de</a><br><br>_______________________________________________
<br>vdr mailing list<br><a onclick="return top.js.OpenExtLink(window,event,this)" href="mailto:vdr@linuxtv.org" target="_blank">vdr@linuxtv.org</a><br><a onclick="return top.js.OpenExtLink(window,event,this)" href="http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr" target="_blank">
http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr</a><br></blockquote></div><br></span></div></blockquote></div><br>