Project

General

Profile

mpeg2 continuity errors

Added by ben barker over 11 years ago

Hello

Any ideas what could cause tvheadend to be running fine, then to start spewing "mpeg2 continuity" errors?

"
TurboSight TBS 62x0 2/London: 506,000 kHz/ITV3: MPEG2VIDEO @ #6881: Continuity counter error, 89 duplicate log lines suppressed
"

When this happens, channel playback stalls, or rather proceeds with massive breakout, but a restart of the machine reliably fixes the problem.

Could this be the memory leak discussed earlier in this forum? I have tried both stable and latest releases with same occsassional symptoms...


Replies (4)

RE: mpeg2 continuity errors - Added by ben barker over 11 years ago

Ah...disabling idle scanning seems to have helped :-)

RE: mpeg2 continuity errors - Added by Adam Sutton over 11 years ago

Is that a dual tuner setup. Maybe the idle scanning on the 2nd tuner is
causing problems due to cross interference.

Adam
On May 25, 2013 12:19 PM, wrote:

Tvheadend - General: RE: mpeg2 continuity errors
ben barker

Ah...disabling idle scanning seems to have helped :-)
------------------------------

You have received this notification because you have either subscribed to
it, or are involved in it.
To change your notification preferences, please click here:
https://tvheadend.org/my/account

RE: mpeg2 continuity errors - Added by ben barker over 11 years ago

I think you may be right - yes it is a dual TBS 6280 dual DVB-T2

I can watch two channels at once OK, or record one and watch one. With idle scanning turned on everything would be fine...until all of a sudden the erro log would start surting mpeg2 errors.

Since disabling idle scaning, touch wood, all is fine :-)

RE: mpeg2 continuity errors - Added by Scott Ware over 11 years ago

I have exactly the same card running in Ubuntu and have been experiencing the same issue for a few months now which is very frustrating. Disabling idle scanning helps but after a few days of tuning I have to remove and reload the tuner modules and restart TVHeadend (I run Tvheadend on a server which stays on 24/7). If I go back to the last stable build or a commit back as far as January the issue goes away. If I get a chance I will try and find the commit where the issue starts, however, it can take a few hours with 'idle scanning' enabled for the issue to occur. I should check the log when the issue occurs too which I haven't done yet. The tuner doesn't completely fail, it just doesn't tune correctly (bandwidth drops to < 200 kbps and lots of continuity errors.

    (1-4/4)