TVHeadend issues after LE8 Alpha 10

newkind · January 9, 2017 at 1:24 PM

Hi,

I started to have issues with TVHeadend (HTS Tvheadend 4.1.2401 ~ LibreELEC Tvh-addon v8.1.108) from LE repo after updating to the Alpha 10 of LE 8.0. Every 10 - 20 seconds there's a freeze of screen and sound and it rebuffers from TVHeadend. Not sure what's going on but this was not an issue with 009. Right now I'm getting tons of Subscription errors in TVH and such messages in log :

Code

2017-01-09 14:16:38.427 TS: DVB-S 130E/****/****/****: MPEG2AUDIO @ #850 Continuity counter error (total 13)


2017-01-09 14:16:47.702 TS: DVB-S 130E/****/****: H264 @ #535 Continuity counter error (total 14)


2017-01-09 14:16:47.726 tsfix: transport stream H264, DTS discontinuity. DTS = 26532922, last = 25694122


2017-01-09 14:16:47.980 tsfix: transport stream MPEG2AUDIO, DTS discontinuity. DTS = 26499600, last = 25644240


2017-01-09 14:16:48.005 tsfix: transport stream MPEG2AUDIO, DTS discontinuity. DTS = 26503200, last = 25647840


2017-01-09 14:17:28.415 descrambler: ECM - key late (24537 ms) for service "****"


2017-01-09 14:17:28.416 TS: DVB-S 130E/****/****: H264 @ #535 Continuity counter error (total 16)


2017-01-09 14:17:28.416 TS: DVB-S 130E/****/****: MPEG2AUDIO @ #851 Continuity counter error (total 10)


2017-01-09 14:18:03.824 TS: DVB-S 130E/****/****: MPEG2AUDIO @ #851 Continuity counter error (total 11)


2017-01-09 14:18:03.848 TS: DVB-S 130E/****/****: H264 @ #535 Continuity counter error (total 17)


2017-01-09 14:18:03.879 tsfix: transport stream H264, DTS discontinuity. DTS = 33385522, last = 30183322


2017-01-09 14:18:04.001 tsfix: transport stream MPEG2AUDIO, DTS discontinuity. DTS = 33339600, last = 30140640


2017-01-09 14:18:04.050 tsfix: transport stream MPEG2AUDIO, DTS discontinuity. DTS = 33346800, last = 30147840


2017-01-09 14:18:55.908 descrambler: ECM - key late (24437 ms) for service "****"


2017-01-09 14:18:55.908 TS: DVB-S 130E/****/****: H264 @ #535 Continuity counter error (total 18)


2017-01-09 14:18:55.908 TS: DVB-S 130E/****/****: MPEG2AUDIO @ #851 Continuity counter error (total 13)


2017-01-09 14:18:55.908 TS: DVB-S 130E/****/****: MPEG2AUDIO @ #850 Continuity counter error (total 16)


2017-01-09 14:19:07.276 TS: DVB-S 130E/****/****: H264 @ #535 Continuity counter error (total 19)


2017-01-09 14:19:07.278 TS: DVB-S 130E/****/****: MPEG2AUDIO @ #851 Continuity counter error (total 14)


2017-01-09 14:19:07.279 TS: DVB-S 130E/****/****: MPEG2AUDIO @ #850 Continuity counter error (total 17)


2017-01-09 14:19:07.338 tsfix: transport stream H264, DTS discontinuity. DTS = 39100522, last = 38090722


2017-01-09 14:19:07.467 tsfix: transport stream MPEG2AUDIO, DTS discontinuity. DTS = 39052800, last = 38013840


2017-01-09 14:19:07.534 tsfix: transport stream MPEG2AUDIO, DTS discontinuity. DTS = 39060000, last = 38021040


2017-01-09 14:19:09.240 descrambler: ECM - key late (294 ms) for service "****"

Display More

I replaced the channel name and frequency with **** as I don't think it matters.

My OSCam configuration in TVH :

Just like I mentioned before, everything started to be broken since Alpha 10. Before that everything was working like a charm.
Is there any possible fix ?

Thanks,

jahutchi · February 22, 2017 at 12:14 PM

I am experiencing this exact same issue on my x86_64 Generic HTPC (Acer Revo 3700) which has 4x 1.8GHz CPU Cores, 4GB RAM & 1TB SATAIII HDD.
I'm running the latest HTS Tvheadend 4.1.2415 ~ LibreELEC Tvh-addon v8.1.109, with 2x DVBSky S960 USB DVB-S2 adapters.

If I upgrade to one of the latest beta releases 7.95.1, 7.95.2, 7.95.3 then the picture breaks up (i.e. goes blocky for a second or so) every couple of minutes when watching either Live TV or recording. The issue is worse for HD channels but does also occur on SD Channels.

When the picture goes blocky I receive Continuity Counter errors in the logfile for example:

Code

2017-02-06 21:01:51.469 [WARNING] TS: Freesat/11097V/ITV HD: H264 @ #2310 Continuity counter error (total 16)
2017-02-06 21:01:51.469 [WARNING] TS: Freesat/11097V/ITV HD: MPEG2AUDIO @ #2313 Continuity counter error (total 2)
2017-02-06 21:06:03.462 [WARNING] TS: Freesat/11097V/ITV HD: H264 @ #2310 Continuity counter error (total 17)
2017-02-06 21:06:19.164 [WARNING] TS: Freesat/11097V/ITV HD: H264 @ #2310 Continuity counter error (total 18)
2017-02-06 21:06:19.164 [WARNING] TS: Freesat/11097V/ITV HD: AC3 @ #2311 Continuity counter error (total 5)
2017-02-06 21:06:19.164 [WARNING] TS: Freesat/11097V/ITV HD: MPEG2AUDIO @ #2313 Continuity counter error (total 3)
2017-02-06 21:06:50.707 [WARNING] TS: Freesat/11097V/ITV HD: H264 @ #2310 Continuity counter error (total 21)
2017-02-06 21:07:40.201 [WARNING] TS: Freesat/11097V/ITV HD: H264 @ #2310 Continuity counter error (total 23)
2017-02-06 21:09:05.369 [WARNING] TS: Freesat/11097V/ITV HD: H264 @ #2310 Continuity counter error (total 24)
2017-02-06 21:09:05.369 [WARNING] TS: Freesat/11097V/ITV HD: MPEG2AUDIO @ #2313 Continuity counter error (total 4)

If I downgrade to LE 7.90.009 alpha as stipulated by newkind then I do not have any problems whatsoever.

I wonder whether it relates to the move from a 4.8.12 kernel to 4.9.x since the problem ONLY occurs when I upgrade to anything later than 7.90.009

I was previously running Ubuntu 14.04 on this very same machine (i.e. same hardware & DVB Cards) and never had any disturbances in the picture quality, or Continuity Counter errors in the logfile... I know that because I took a full backup before moving away from Ubuntu. So was able to go back and examine my previous /var/log/syslog.x files - not a single Continuity Counter Error whatsoever!

I hope this will be fixed before the production release as I'd rather not stay on the alpha release forever.

I wonder whether it's possible to swap in the 4.8.12 kernel and run this against the latest 7.95.3 beta release to identify whether the kernel is indeed the point at issue. Could that be done by simply swapping the KERNEL & KERNEL.md5 files in from the alpha 9 release into the /flash folder (after mounting the vfat partition r/w). I'd be happy to give that a go if someone could confirm it won't break my system. If not, maybe there are other things I could try to help debug the issue?