Project

General

Profile

Bug #2194

Continuity counter errors back again in release 3.9.1133

Added by Crazy Fin over 10 years ago. Updated about 10 years ago.

Status:
Invalid
Priority:
Normal
Assignee:
-
Category:
DVB
Target version:
-
Start date:
2014-08-02
Due date:
% Done:

0%

Estimated time:
Found in version:
3.9.1133
Affected Versions:

Description

Release 3.9.1133 fixed quite many bugs and other things and I am ni fact very happy with this realease so far after few hours of testing.

However, the dreaded "continuity counter errors" that were gone in the release i tested before 3.9.1133 has come back now. Worked fine in release 3.9.1095.

The continuity counter errors do not show up on all channels but exactly on the same channels as before (like TV3 HD on Canal Digital Sweden).

Looking at the channels you can clearly show disruptions in the live stream and as soon as I switch back to for example 3.9.1095 it works fine.


Files

TVH_errors.png (569 KB) TVH_errors.png Alfred Zastrow, 2014-08-03 15:36
TVH_no_errors.png (855 KB) TVH_no_errors.png Alfred Zastrow, 2014-08-03 15:36

History

#1

Updated by Alfred Zastrow over 10 years ago

Same here with my digital devices cine S2 (10 tuners, 3 active atm).

It looks like, that the problem is triggered by background searching and switching becaues if I use the 3 active tuners to receive 3 different sat streams, there are no disruptions. Maybe this information can help.

br
Alfred

#2

Updated by Alfred Zastrow over 10 years ago

Attached are two pictures:

TVH_no_errors is showing ten minutes of serving four xbmc-clients with tree different sat streams - no errors

TVH_errors is showing ten minutes of serving two xbmc-clients with one sat stream, the two free tuners are in background searching.

#3

Updated by Alfred Zastrow over 10 years ago

Another info: setting "idle scan muxes" to "false" eliminates the disruptions.

br
Alfred

#4

Updated by Crazy Fin over 10 years ago

Thx for the input.

I looked in the webgui of TVH and I already had the Idle Scan Muxes under DVB Inputs->Networks set to "False".

This seems to happen for me too only when background searching or background EPG updating is going on and TVH therefore uses more tuners.

I have also Digital Device Cine S2 (two cards with 4 tuners so totally 8 tuners).
My tuners shows 80-85% SNR and 70-80% signal strength which is very identical with the actual measurements I get when I measure with a DVB-S tool (SatLink WS-6926) so it should not be that I have bad signal or cables.

I am now running with two computers connected to TVH and watching 2 channels and recording 2 other at the same time and no continuity counter errors at the moment (however, no EPG updating going on either in the background)

I have also Disabled the "Force initial EPG scan at startup" that can be found under Configuration->Channel/EPG->EPG Grabber

#5

Updated by Rob vh over 10 years ago

I had the same issue when (OTA) EPG scanning was active on a free adapter: missing packets disrupting the HD stream I was watching. I am currently not sure if the issue was caused by tuning of the other adapter, or the EPG scanner, but when I selected "skip idle scanning" the disruptions disappeared.
Ubuntu 12.04, DD Octopus with 3x DuoFlex-S2.

#6

Updated by Jaroslav Kysela about 10 years ago

  • Status changed from New to Invalid

It seems like a driver / hardware issue.

#7

Updated by Crazy Fin about 10 years ago

Hi

I just wanted to clarify that I have found the (possible) reason for my continuity counter errors that I see on some of my DVB-S2 channels on the THOR satellite for Canal Digital Nordic channels.
I have mostly seen these CC errors on for example channel "TV3 HD (S)", "BBC HD" and I would probably have seen similar CC errors on other channels as well.

My tuner setup is 2 times of the Digital Devices Cine S2 cards with DuoFlex S2 added to the expansion port, i.e. 4 tuners per card, totally 8 tuners into TVH.The cards are all of the latest version 6.5 with the latest firmware (NOT the ngene-based cards that were version 5 and 6, my version 6.5 cards are displayed as "ddbridge" in the kernel)

(Card info at http://www.digitaldevices.de/english/Cine_S2.html)

I am using the latest driver from http://linuxtv.org/hg/~endriss/media_build_experimental.

The reason for these CC errors are NOT driver based and NOT caused by TVH as far as I can see now after extensive testing of both TVH and checking ALL my eight incoming DVB-S cables from my 8 port LNB.

I have checked all signal cables at the connector end that goes into my tuner cards with a SatLink WS-6926 satfinder/meter tool (http://www.satlink.de/satlink-ws-6926-hd-second-edition.html).
I get signal strength around 89% according to my meter WS-6926 and signal quality 80 to 81% continously on all channels and ALL 8 tuner cables. I have even logged each cable for approx 5-10 minutes and no signal or quality drops what so ever.

I was really wondering why I would get these CC errors.Suddenly while I was watching the TVH GUI under "Status" and being confused about these errors, I could see that when TVH started to use my tuner number 6 I would get CC errors?!

I checked the cable again and signal was as good as previously. I switched signal cables between tuner 5 and tuner 6, still CC errors as soon as TVH started to use tuner no 6?!

So it definately looks like a hardware error on one of my tuner cards!

The quick solution was to just disable that tuner from TVH under the configuration tab for tuners and I haven't had those CC error problems since then. :-) (Of course, I get small CC errors sometimes when switching channels but I consider that as fully normal. I get also CC errors if there is VERY heavy rain and I consider this also normal since I am not at a 90-98% signal/quality strength during normal weather.)

I will try to replace the tuner card that seems to have one of the two tuners broken/bad shape and see if a new tuner card will work better. I think I am still under warranty. :-)

#8

Updated by Crazy Fin about 10 years ago

I´ve found out that it is NOT the tuner cards that are broken (at least what I think)!

Have a look in my separate thread at https://tvheadend.org/boards/5/topics/12963.

Also available in: Atom PDF