Project

General

Profile

One channel frequently experiences "Continuity counter error"

Added by M J over 2 years ago

For a couple of years now I've had this problem I can't fix w/one channel only. If I watch it live, sometimes the video just freezes for a few seconds, then comes back. If recording, it skips ahead several seconds (obviously from the same effect). It only happens on 1 channel. I've considered and eliminated these possibilities:
1. Weak signal: actually, this signal is the strongest one I receive. Even if I used rabbit ears it's hard not to get the signal and I use an outdoor antenna.
2. Required more throughput than my system can handle: that seems unlikely, because it is the only channel that is 720p. I often record from several 1080i channels and never have this problem.
3. Hardware: I've connected the tuner to my Linux computer and watched for a long time. Never had a problem.

All I can say about the channel is:
  • ATSC
  • On the web interface's Services tab has it as 539.028MHz
  • Real channel 25, virtual channel 4.1
  • The attached screen caps for the Muxes tab and Services tab on the web interface.

I've also tried the syslogs while I was recording:

Mar  7 14:14:10 dospace tvheadend[764]: TS: ATSC-T Network/539.028MHz/OTTAWA CBOT-DT Transport error indicator (total 1)
Mar  7 14:14:10 dospace tvheadend[764]: TS: ATSC-T Network/539.028MHz/OTTAWA CBOT-DT: MPEG2VIDEO @ #49 Continuity counter error (total 1)
Mar  7 14:14:10 dospace tvheadend[764]: TS: ATSC-T Network/539.028MHz/OTTAWA CBOT-DT: MPEG2VIDEO @ #49: Invalid start code 0d:98:83
Mar  7 14:14:10 dospace tvheadend[764]: TS: ATSC-T Network/539.028MHz/OTTAWA CBOT-DT: AC3 @ #53 Continuity counter error (total 1)
Mar  7 14:14:10 dospace tvheadend[764]: TS: ATSC-T Network/539.028MHz/OTTAWA CBOT-DT: AC3 @ #53: Invalid start code 03:35:e7
Mar  7 14:14:10 dospace tvheadend[764]: TS: ATSC-T Network/539.028MHz/OTTAWA CBOT-DT: AC3 @ #52 Continuity counter error (total 1)
Mar  7 14:15:55 dospace tvheadend[764]: TS: ATSC-T Network/539.028MHz/OTTAWA CBOT-DT: MPEG2VIDEO @ #49 Continuity counter error (total 14)
Mar  7 14:15:55 dospace tvheadend[764]: TS: ATSC-T Network/539.028MHz/OTTAWA CBOT-DT: AC3 @ #52 Continuity counter error (total 3)
Mar  7 14:15:55 dospace tvheadend[764]: TS: ATSC-T Network/539.028MHz/OTTAWA CBOT-DT: AC3 @ #53 Continuity counter error (total 4)
Mar  7 14:15:55 dospace tvheadend[764]: tsfix: transport stream MPEG2VIDEO, DTS discontinuity. DTS = 41487499, last = 41209721
Mar  7 14:15:56 dospace tvheadend[764]: tsfix: transport stream AC3, DTS discontinuity. DTS = 41448754, last = 41157874
Mar  7 14:15:56 dospace tvheadend[764]: tsfix: transport stream AC3, DTS discontinuity. DTS = 41448960, last = 41158080
Mar  7 14:16:32 dospace tvheadend[764]: TS: ATSC-T Network/539.028MHz/OTTAWA CBOT-DT: MPEG2VIDEO @ #49 Continuity counter error (total 15)
Mar  7 14:16:32 dospace tvheadend[764]: TS: ATSC-T Network/539.028MHz/OTTAWA CBOT-DT: AC3 @ #52 Continuity counter error (total 4)
Mar  7 14:16:32 dospace tvheadend[764]: TS: ATSC-T Network/539.028MHz/OTTAWA CBOT-DT: AC3 @ #53 Continuity counter error (total 5)
Mar  7 14:16:32 dospace tvheadend[764]: tsfix: transport stream MPEG2VIDEO, DTS discontinuity. DTS = 44787796, last = 43442452
Mar  7 14:16:32 dospace tvheadend[764]: tsfix: transport stream AC3, DTS discontinuity. DTS = 44743474, last = 43369714
Mar  7 14:16:32 dospace tvheadend[764]: tsfix: transport stream AC3, DTS discontinuity. DTS = 44743680, last = 43369920
Mar  7 14:16:52 dospace tvheadend[764]: subscription: 0016: "127.0.0.1 [ angus | Kodi Media Center ]" unsubscribing from "CBOT-DT", hostname="127.0.0.1", username="127.0.0.1", client="Kodi Media Center" 

The tuner is a Hauppauge WinTV-HVR 955Q. I'm running Kodi 18.7 on Raspbian 10 and Tvheadend 4.2.8-34.

CBOT.png (102 KB) CBOT.png
muxes.png (91.1 KB) muxes.png

Replies (3)

RE: One channel frequently experiences "Continuity counter error" - Added by clint jones almost 2 years ago

I've had a similar issue

The channel on my setup ran 15meg and was a 1080p channel, A year or so ago I switched to a usb adapter on a raspberry 4 and the channel would hang Tvheadend when conditions were poor.

Messed around with it for several months, even built my own antennae (was trying to get a VHF low channel) finally ran a cable to the TV directly both the VHF channel and the "strong" channel played well enough

Switched to a TBS 6704 on an x86 machine and the "strong channel works fine when it "pixelates" it still just keeps going and doesn't hang Tvheadend

As far as the VHF Low channel (2, 57mhz) neither adapter will get it with tvheadend although the adapters will get it directly through VLC just fine, running through tvheadend as a mux the channel will play but the bandwidth will go up and down until the channel disconnects.

in order to fix that I just tapped the channel directly off of another adapter with VLC and made an IPTV link on the main machine works fine

I suspect the "strong" channel on the usb stick was to much bandwidth for the usb to handle, and the PCI adapter will take it fine

Long story possible your channel is the problem and your adapter may be the issue.

as far as channel 2 goes who knows and there are not many channels on 2 thru 6 any more anyways it is a channel called Quest and has some old history channel shows on it.

Clint

    (1-3/3)