Help with "Accurate Recordings"

Nick Sillito

I've just updated to version 4.2.2-32 (running on Ubuntu Server 16.04 64 bit). This all worked really smoothly -- thank you!

I am trying to use "Accurate Recordings", however, the recordings simply appear to start at the time specified in the EPG.

I have the following in my configuration:

Default (and only) profile
Extra warmup time (seconds): 120
Pre & Post recording padding: Not set (none or channel configuration)

Use EPG running state: (SET)

For the channel:
Channel: BBC1 HD
Pre & Post padding: 0

Use EPG Running state: Enabled

Below, I've pasted from my syslog, and you can see that the example recording starts exactly at 10:00 (with 120 second warmup starting at 9:58). Any ideas what I am doing wrong?

Thanks

May 29 09:58:00 serv2 tvheadend[1595]: dvr: "Countryfile Spring Diaries" on "BBC One HD" recorder starting May 29 09:58:00 serv2 tvheadend[1595]: mpegts: 10847V in UK - tuning on Montage RS6000(DVBSky) : DVB-S #1 May 29 09:58:00 serv2 tvheadend[1595]: subscription: 00F5: "DVR: Countryfile Spring Diaries" subscribing on channel "BBC One HD", weight: 300, adapter: "Montage RS6000(DVBSky) : DVB-S #1", network: "UK", mux: "10847V", provider: "BSkyB", May 29 10:00:00 serv2 tvheadend[1595]: dvr: /mnt/pvr/recordings/Countryfile Spring Diaries/Countryfile Spring Diaries.ts from adapter: "Montage RS6000(DVBSky) : DVB-S #1", network: "UK", mux: "10847V", provider: "BSkyB", service: "BBC One May 29 10:00:00 serv2 tvheadend[1595]: dvr: # type lang resolution aspect ratio sample rate channels May 29 10:00:00 serv2 tvheadend[1595]: dvr: 1 H264 1920x1080 ? May 29 10:00:00 serv2 tvheadend[1595]: dvr: 2 MPEG2AUDIO nar ? ? May 29 10:00:00 serv2 tvheadend[1595]: dvr: 3 TELETEXT May 29 10:00:00 serv2 tvheadend[1595]: dvr: 4 DVBSUB eng May 29 10:00:00 serv2 tvheadend[1595]: dvr: 5 AC3 eng ? ? May 29 10:00:00 serv2 tvheadend[1595]: dvr: 6 TEXTSUB eng

mpmc

The EITp/f comes from the EIT data & not the Freesat EPG data. You need to enable and give the EIT grabber a higher priority.

Nick Sillito

Thanks Mark (is still not working)

On the "EPG Grabber Modules" tab, the only module I have enabled is "EIT: DVB Grabber" (is this what you meant)?

The tab "EPG Grabber Channels" is blank (is this correct). For every channel, the tick box "automatically map epg source) is set, and the field "EPG source" is blank (again it this correct?)

The actual EPG is populating fine.

mpmc

With the EIT grabber enabled, you'll more than likely only have Now and Next, nothing else.

EPG grabber channels won't show EIT/FV/FS grabber info.

Nick Sillito

Thanks for your ongoing help -- its very much appreciated.

I now have the following EPG modules enabled (priority):

OTA: EIT: DVB Grabber (1)
OTA: PSIP: ATSC Grabber (2)

OTA: UK: Freesat (5)

I'm still just getting recordings starting on the scheduled time (no variation for Accurate Recordings).

Further suggestions are very welcome

Eric Valette

I will not help just mention that it does not work for me either and I've lost several end of recording due to this (more than 20 min lateness). I also use 4.2.x

-- eric

Eric Valette

Side comment : If you use accurate recordings, given that the EIT is the only mean to really dynamically match what is broadcasted, it should immediately be given precedence compared to all other grabbers...

-- eric

Nick Sillito

Thanks Eric (at least I am not missing something too obvious!)

Eric Valette

More details : I also have -2mins +15mins set by default for all recordings and I get this exact recording time slots compared to xmltv grabber data whatever the eit says. Not at home, so I cannot check the priorities among grabbers but I think I gave the EIT precedence (although as said, it should be automatic when precise recording is selected).

If I can help debugging, send me command, request logs, request traces but outside of french working hours...

mpmc

Nick Sillito wrote:
> Thanks for your ongoing help -- its very much appreciated.
> I now have the following EPG modules enabled (priority):
>
> OTA: EIT: DVB Grabber (1)

> OTA: PSIP: ATSC Grabber (2)

You don't need PSIP enabled, it's for ATSC signals only.

> OTA: UK: Freesat (5)
>

> I'm still just getting recordings starting on the scheduled time (no variation for Accurate Recordings).

You have no pre-post padding, try setting them to 5 mins. and if you could provide a trace log, that would help :). You can do this by going into the debugging tab, and where it says filename enter something like /tmp/dvr.txt. And for the trace/debug subsystems enter "dvr". Hit save. Then try and do a recording & post the logs here.

> Further suggestions are very welcome

Nick Sillito

I think I have created a debug log as requested (5 minute padding added) -- attached.

Just noticing Eric's comment about French working hours. I am in Germany, and therefore using the Berlin timezone. I was wondering if its a timezone issue between the EPG and the system clock?

mpmc

Nick Sillito wrote:
> I think I have created a debug log as requested (5 minute padding added) -- attached.
>

> Just noticing Eric's comment about French working hours. I am in Germany, and therefore using the Berlin timezone. I was wondering if its a timezone issue between the EPG and the system clock?

Have you set the EIT time offset for the Network? Here in the UK I have this set to UTC. You need to use UTC+1.

Additionally, I don't see the eitp/f log messages.

Nick Sillito

Thanks Mark

> Have you set the EIT time offset for the Network? Here in the UK I have this set to UTC. You need to use UTC+1.

I haven't changed the EIT offset. I had understood that it all worked in UTC. In the EPG guide, the time of all the programmes shows correctly in local time, and times recordings work correctly. I will test using UTC+1 (I am afraid that I will be away for a bit so I can't test for a while)

> Additionally, I don't see the eitp/f log messages

I have turned on the "Use EPG running state". Is there something else I should do?

mpmc

Nick Sillito wrote:
> Thanks Mark
>
> > Have you set the EIT time offset for the Network? Here in the UK I have this set to UTC. You need to use UTC+1.
>
> I haven't changed the EIT offset. I had understood that it all worked in UTC. In the EPG guide, the time of all the programmes shows correctly in local time, and times recordings work correctly. I will test using UTC+1 (I am afraid that I will be away for a bit so I can't test for a while)
>
> > Additionally, I don't see the eitp/f log messages
>

>I have turned on the "Use EPG running state". Is there something else I should do?

Sorry I should've been a bit clearer with my last message. You won't see them unless they're correctly detected by TVHeadend. And by correctly, I mean the times match up.

Nick Sillito

Many thanks for the guidance -- I will try out your proposals in a couple of weeks when I am back

Eric Valette

Note that, because I found someone else with the same problem and I recently missed too much recording ends, I opened bug 4401 <https://tvheadend.org/issues/4401> and already gave the requested debugging output with a non working example.

Wim K

Guys,

I've been reading this thread and bug 4401.

I don't understand completely, so I could use your help.

I'm in the Netherlands, using Ziggo.
I have just 1 epg grabber module (EIT DVB grabber)

The over-the-air grabber fetches data at 2.00 and 14.00. So if Ziggo changes data, I might miss it (it's not continuously grabbing).

If I have epg running state off, it works like I expect it to. Just follow the guide info and use pre- and post-padding times.

If I have epg running state on, it looks like the only difference is that's it not using padding times anymore, the rest seems the same. I mean, I'm not sure it uses eitp/f (now/next data).

In the logs I see (for example):

2017-09-08 12:36:40.818 dvr: "NOS Journaal" on "NPO 1 HD": End of program: Completed OK

Not something like:

2017-05-31 12:02:57.894 [ DEBUG]:tbl-eit: eit: completed pid 18 table 00000000 / 00000000

I have "Loglevel debug: enabled".

I'm still on 4.1-2309~g0736ebc and maybe things have changed since, but how can I tell if Ziggo is sending the eitp/f data and it's sending it correct (not stopping recording 1 minute before the end of the show).

Thanks,

Wim

Wim K

Okay guys,

I've installed 4.2.3. Set in epg running state in recording profile AND in all channels.

I now get these entries in the debug log

2017-09-09 12:30:59.325 [ TRACE]:dvr: dvr event running check for Trips & Travel on RTL 4 running 0
2017-09-09 12:30:59.326 [ DEBUG]:dvr: dvr entry 70cba2bb54baa52e5cbcb1eaad2a3c36 event Trips & Travel on RTL 4 - EPG marking stop
2017-09-09 12:30:59.332 [ INFO]:subscription: 010C: "DVR: Trips & Travel" unsubscribing from "RTL 4"
2017-09-09 12:31:00.000 [ DEBUG]:epg: expire event 72479461 (Trips & Travel) from RTL 4
2017-09-09 12:31:00.000 [ TRACE]:dvr: entry 70cba2bb54baa52e5cbcb1eaad2a3c36 - unassign broadcast 72479461
2017-09-09 12:31:00.000 [ TRACE]:dvr: entry 70cba2bb54baa52e5cbcb1eaad2a3c36 start 2017-09-09;11:58:30(+0200) stop 2017-09-09;12:36:00(+0200) - set timer
2017-09-09 12:31:00.000 [ TRACE]:dvr: entry 70cba2bb54baa52e5cbcb1eaad2a3c36 when 1970-01-01;01:00:00(+0100) - retention arm
2017-09-09 12:31:00.000 [ DEBUG]:epg: now/next 72479463/72479465 set on RTL 4

2017-09-09 12:31:00.000 [ DEBUG]:epg: inform HTSP of now event change on RTL 4

Guess it works now.

Could it be I have to set epg running state in recording profile AND channels?

And I noticed, the recording still ended a bit too soon. I set post-recording to 5 mins, to be sure it's the eitp/f ending the recording and not the epg-data. But this also means I can't set any post-padding with EITP/f?

That would solve my problem.

Wim