Continuity counter error // descrambler: cannot decode packets for service
|Found in version:||HTS Tvheadend 4.3-1148~gd3fc96962||Affected Versions:|
I am using 3 satipaxe's as source of my tvheadend and i can say they are very stable @ moment (thanks perexg).
Even with they working well i get a lot of messages like this:
2018-03-06 09:19:40.517 TS: DVB-S 30/12206.98H/CMTV: H264
#6129 Continuity counter error (total 28478) #6130 Continuity counter error (total 4145)
2018-03-06 09:19:40.517 TS: DVB-S 30/12206.98H/CMTV: MPEG2AUDIO
2018-03-06 09:19:40.517 descrambler: cannot decode packets for service "CMTV"
2018-03-06 09:19:50.704 TS: DVB-S 30/12206.98H/CMTV: H264
#6129 Continuity counter error (total 33396) #6130 Continuity counter error (total 4842)
2018-03-06 09:19:50.704 TS: DVB-S 30/12206.98H/CMTV: MPEG2AUDIO
2018-03-06 09:19:50.705 descrambler: cannot decode packets for service "CMTV"
2018-03-06 09:19:56.653 parser: DVB-S 30/12206.98H/CMTV: H264 @ #6129: DTS and PCR diff is very big (1441331)
2018-03-06 09:19:56.654 tsfix: transport stream H264, DTS discontinuity. DTS = 553772160, last = 552380760
2018-03-06 09:19:56.658 tsfix: transport stream MPEG2AUDIO, DTS discontinuity. DTS = 553741920, last = 552340080
i don't see CC errors increasing on satipaxe's so i guess its not a hardware or reception problem!
i also checked my oscam and tvheadend dvbapi user is 100% OK not even a single NOK, so i guess there be a problem with key exchange between tvheadend and oscam!
#2 Updated by Pablo Rodríguez 8 days ago
I'm investigating more deeply about the problem you're reporting here, I'm experiencing something similar. It seems that sometimes descrambler does not accept the key and gives errors about 1 second (and continues?).
I have to investigate further if it is a key failure (incorrect) or really a problem of tvheadend.
#4 Updated by Pablo Rodríguez 8 days ago
Ricardo Rocha wrote:
i changed from capmt to newcamd and i have like 1/10 of the problems i have before... running it for some days now... however with newcamd still same message time to time. Oscam reports no NOK'S on the user!
Have you tried the latest version of tvheadend with oscam? I think the initial key error that does not work is fixed.
Now I have to check the change of key that sometimes does strange things (very occasionally).