Using EITp/f for accurate recording

space_cadet

Hi, first of all thanks for TVHeadend! The more I do with it, the more I like it 😊 Great work!

I managed to set up a WinTV soloHD usb stick on a Raspberry Pi 4 and it works nicely with TVHeadend here in Germany. I am getting all the Channels / EPG info I need. Now I'd like to record the world cup football games that are deep in the night here in EU.

My question is, does anyone here have experience with the "accurate recording" feature? Does it work reliably in practice? I've tried it, and it started correctly. But then something happened at the end. The file was missing, the TVHeadend entry was now in the "Removed recordings" tab with status "file missing", and I got this message in the TVHeadend log:

Jun 13 12:50:00 raspberrypi tvheadend[578300]: subscription: 0098: "DVR: Lenas Ranch" unsubscribing from "KiKA", username=""
Jun 13 12:50:00 raspberrypi tvheadend[578300]: dvr: "Lenas Ranch" on "KiKA": End of program: Time missed

What happened? BTW 12:50 was the "official" end time of the program.

davep

space_cadet I have tried it (in UK) and also found it unreliable.

Your experience with the file display is expected. At the expected start time (less any warm-up) Tvheadend starts a thread to carry out the recording; this thread waits for the EIT p/f 'start' signal which for some reason never arrives. At the expected end time of the recording the thread exits. Tvheadend sees that the recording thread has finished but there is no file in the Completed Recordings directory, so the timer appears in "Removed Recordings" with status "file missing" as you have seen.

I have tried to work out why the recordings fail but without success.

All I can suggest is to add lots of pre- and post- recording padding to your timers.

space_cadet

You're right. I left out the beginning, but I had another look at it (see below) and it's clearly missing parts compared to successful recordings. So I agree with you that most probably, the EIT p/f start signal didn't arrive.

All I can suggest is to add lots of pre- and post- recording padding to your timers.

And disable "accurate recording". For football, that would mean a additional hour each time, to be safe. I guess that's really the most reliable option.

Jun 13 12:29:30 raspberrypi tvheadend[578300]: dvr: "Lenas Ranch" on "KiKA" recorder starting
Jun 13 12:29:30 raspberrypi tvheadend[578300]: mpegts: 570MHz in DVB-T2 (Germany) - tuning on Silicon Labs Si2168 #0 : DVB-T #0
Jun 13 12:29:30 raspberrypi tvheadend[578300]: subscription: 0098: "DVR: Lenas Ranch" subscribing on channel "KiKA", weight: 500, adapter: "Silicon Labs Si2168 #0 : DVB-T #0", network: "DVB-T2 (Germany)", mux: "570MHz", provider: "ZDFmobil", service: "KiKA HD", profile="recording", usernam>
Jun 13 12:29:30 raspberrypi tvheadend[578300]: transcode: 0006: 01:HEVC: ==> Copy
Jun 13 12:29:30 raspberrypi tvheadend[578300]: transcode: 0006: 02:EAC3: ==> Copy
Jun 13 12:29:30 raspberrypi tvheadend[578300]: transcode: 0006: 03:EAC3: ==> Copy
Jun 13 12:29:30 raspberrypi tvheadend[578300]: transcode: 0006: 04:EAC3: ==> Copy
Jun 13 12:29:30 raspberrypi tvheadend[578300]: transcode: 0006: 06:DVBSUB: ==> Filtered out
Jun 13 12:50:00 raspberrypi tvheadend[578300]: subscription: 0098: "DVR: Lenas Ranch" unsubscribing from "KiKA", username=""
Jun 13 12:50:00 raspberrypi tvheadend[578300]: dvr: "Lenas Ranch" on "KiKA": End of program: Time missed