Tvheadend

It seems like 'no key' issue. --trace descrambler,cwc : https://tvheadend.org/projects/tvheadend/wiki/Traces

yes, obviously a key was missing/late, but I think the reason for that might be the sequencing error or the maybe the dts discontinuity?
Where do I put the traces, here?(they tend to become large)

actually it is not a sequencing error. its just that two ecms are sent in rapid succession 471,472 and then the response for 471 triggers a 'unexpected..." before getting the response to 472. Imho a pretty typical async sequencing issue.
Also I keep seeing these DTS discontinuities. I don't know if it is a coincidence that this also is logged when I get a descrambling error, or which one of those two errors is causal to the other.

Show traces. The first problem was 'no key': [ DEBUG]:descrambler: no key for service='Fox HD', all other issues depend on this. If you don't have key in time, tvh cannot do much.

The ECM sequencing issue is another thing: from the log - tvh tries to ask for the previous ECM, but there's immediate ECM change, so two ECM requests are sent to the server. First reply (key for the old ECM) is correctly ignored, the newer ECM key is accepted. All is fine in my eyes.

I finally found the time to let tvh run for more than ca. 30mins.
As it turns out, the glitches I have been observing stop after some time. To be precise, they stop, when there is no tuning going on on other tuners.
Explanation:
I have 4 tuners pointed to Hotbird/astra (disecq).
Whenever I start tvh and start watching a stream, the other 3 tuners start doing a eit grabbing. Whenever one of the other three tuners tune to a new mux, chances are, I get discontinuities and subsequent glitches , maybe even descrambling issues. To verify, I started multiple recordings on all 4 tuners. Sure enough upon start of a new recording I almost always got a discontinuity on one or all of the other streams already running. But after that, I had no errors for a long time (until I decided to stop the streams).

To cross check, I waited again for the system to settle down. Started watching one stream, verified that that there no errors. Then I started a network scan, which uses the the other three tuners.
Sure enough, whenever a new mux is tuned to, I get a discontinuity and the one stream that I was watching became unwatchable to the point that the accumulated errors closed the client connection (Kodi).

I have a rather large log of today, where all this happened. It still has cwc/descrambler traces in it, which I think are important.
Is there some drop site you prefer me to put them in?
Maybe change the subject of this issue, I'm pretty sure descrambling is not the cause, since it works if there are no discontinuities.

correction to above:
...
.. traces in it, which I think are NOT important.
...

It seems that you have some issues with your DVB-S equipment/hardware or drivers.

not in the last 5 years or so,
ivy bridge 4-core 1225 on a intel dq77 board with dd cines2 v6 + duoflex s2

This machine has been running without these issues on windows/dvblink, and I believe also in earlier versions of tvheadend (4.0 or 4.1, or 4.2 timeframe, on ubuntu 1404/1604).
I understand that the linux media drivers for digital devices cards are whimsy, but starting with kernel 4.14 they should be ok (apart from the snr/signal strength issues)
Also if I use dddvb-dkms i have the same issues.

I'm not sure when these issues under linux started, maybe when I switched to ubuntu 1804.

I have been trying to ditch windows for tv for quite some time now, but it just doesn't seem to work. Something is always missing.
I guess I'll have to try vdr then (i know my config works there)

I took the time to install a fresh ubuntu 1804 on another disk.
Here I nstalled the released version of tvh 4.2.81...
Unfortunately the the current config from 4.3 was not usable in 4.2, it caused a crash on startup.
So I set up all channels again.

I can confirm that
- the released version of 4.2.81 has none of the problems mentioned here.
- background EIT grabbers using 3 of tuners is a lot faster (I mean a lot, just a few minutes compared to > 1.5h on 4.3)
- while background EIT grabber no glitches whatsoever
- I can even run network scans on 3 tuners in the background while watching a stream on 1 tuner without any glitches.
- Network scan is also a LOT faster than in 4.3

Some change in 4.3 compared to 4.2 has introduced these glitches. Since the configuration backup seems incompatible it difficult to switch back and forth to find out where the change was introduced.

Any ideas?
Should I create a new issue, since this one has a misleading title?

Why is the grabber/scanner so slow compared to 4.2.81?
I have only enabled the dvb eit grabber, all others are disabled. I still seem to see some traces of uk_skyview etc..

No idea, pls, provide the log only for one tuner as requested. Add 'tbl-eit' to traces.

It's not trace log. https://tvheadend.org/projects/tvheadend/wiki/Traces

sir I have same problem plz tell me how can solve I have ubuntu in 4.2.38v

Naeem Ahmad wrote:

sir I have same problem plz tell me how can solve I have ubuntu in 4.2.38v

By switching to a version that contains the fix linked above.