Tvheadend

Are there any transport errors or continuity errors?

Flole Systems wrote:

Are there any transport errors or continuity errors?

Errors are neglectible: only a few every two hours

Flole Systems wrote:
Detect that the frequency is unavailable and disable it. Not a Tvheadend bug most likely, unless you can show that the data is actually sent to Tvheadend and it doesn't pick it up (which is possible but unlikely).

I think, SAT>IP-client of Tvheadend behaves buggy, because other SAT>IP-client (other E2-Box) is able to find all channels and receive streams without errors from SAT>IP-server.

To proof that behaviour, I would like to publish here detailed log of SAT>IP-server (SatPI) and at the same time (same time slot) detailed log of tvheadend. Please tell me which debug parameters to choose in order to catch precious information. Thank you

Logs alone won't help, what would be needed is a capture of the traffic with the log, if there's no traffic after Tvheadend sent a request then it's not a Tvheadend issue.

Flole Systems wrote:

what would be needed is a capture of the traffic with the log

Wireshark?

Yes, Wireshark could be used for that.

@Ernie Bert

Did you ever get to the cause of 'Parent disabled' ?

Probably you need to increase the adapter parameters 'Tuning Timeout' in Tvheadend

Ernie Bert wrote:

Manufacturer

Hi,
Yes that's me.

Well I have a Vu+ FBC dvb-s2 and C tuners. I have tried first the S2 variant which has this option in Tvheadend but for some reason for the C variant this option is not present.

The strange thing is older version of Tvheadend is working which I used initially.

The problem is the Vu is taking more time to produce the PID data used for initial scanning. So Tvheadend times out before data is available on the subsequent PID request.

I am trying to figure out what is going wrong.

During scanning lowering the PID max to the minimum as PMT PIDS that are in the PAT, will not be scanned.

So in other words: I have a PAT with 38 PMT PIDs and need to set the 'Maximum PIDs' amount to 20. Now for some reason the last are never requested. So my understanding is that the PID split-up is not working correctly?

Marc Postema wrote:

The strange thing is older version of Tvheadend is working which I used initially.

This is not try what I wrote, because the 'Parent disable' is added at some point after my build version.

The PMT PIDs are initially never read correctly in this version as well, but it lets you map them and add first tune it will read the PMT and update the data.

This is my understanding at the moment.

On my site all problems were solved by setting 'Grace period' to 50. (thanks to Marc Postema) All missing muxes can be scanned now and services are mapable afterwards. But I've heared already that I must be almost the only one being lucky in scanning dvb-c channels with SatPI.
My equipment is SatPI 1.6.2.26~g3730645 and TVheadend Version 4.3-2010~g3b1d7a928

It is not only that SatPI is affected see #6041. And that it is more luck that it works out. The "Grace period" is (mostly) only needed for FBC tuners as it takes longer time to produce data from the drivers.

I have added a tcpdump showing that Tvheadend receives the PMT but discards them.

It has something to do with the version in the mpegts table (PMT) that it is discarded by Tvheadend. This problem is introduced when "parent disable" is "turned on" in the code. Before it was possible to map services without correct PMT parsing. Makes you think why this "parent disable" was put in comment, because it did not work correctly.

Sorry, I think I made a mistake here with testing. During testing I changed a lot of things. But now with a clean setup I can not see the behavior that I show before and is described in this issue.

I will keep my I on this, one big problem with Vu+ FBC tuners is that it takes some time with 'low' bitrate PID (mostly during scanning) to receive data from the driver. That is why the 'Grace period' etc. should be increased.

Hey, I opened #6041....Still having the issue having come back after many months.

How do I go about increasing the 'Grace Period' I can't find that setting on DVB-T

Hi @ D B

You are only using TvHeadend with your setup?

There were some changes made to TvHeadend in the past. That I found a bit strange and to comment in the code was saying: to prevent 'Parent Disabled' Services this...and this.. (not sure what it was exactly)

I am not complexly convinced it is not a TvHeadend issue. But in my case I did not observe this at the moment I last checked this.

Well. I'm currently using NextPVR, without issues.

I run in a docker, so I kill one docker and boot up the TVHeadEnd docker. I'm able to do the scans etc but with 'parent disabled'

Where is the 'Grace Period' setting...?

My comments were more related to SatPI in combination with Tvheadend.

I am not very sure we're this 'Grace Period' is for dvb-t tuners. But dvb-s2 it is somewhere in the frontend config page in tvheadend.