Recording stopped part-way through and rebooting caused "waiting for stream" error
Recording stopped part-way through and rebooting caused "waiting for stream" errorAdded by Martin Underwood about 6 years ago
Tvheadend 4.2.6-65 on Raspberry Pi
I had set a programme to be recorded as an Autorec. I noticed that the file stopped growing in size and its modification time didn't update, after the recoding had been running for about 30 minutes of a 1-hour programme.
After trying various other things, I rebooted the Pi, and I found that I couldn't then schedule any recording on either of my tuners to take place from "now" to some time in the future (to resume the recording that had been interrupted). The error was "Waiting for Stream".
I also noticed that the Status | Stream page showed that both tuners were busy, although I didn't notice what frequency (ie which multiplex) each was tuned to, and at the time I didn't know about the Status | Subscriptions page. I now know to check those things if it happens again!
Is there any debug info that might help to identify what went wrong.
TVHeadend is configured to start the EPG Grabber on both tuners when I reboot (the default state), I'm wondering if this somehow took precedence over the scheduled recording. I presume that by default EPG updates are assigned a lower priority than scheduled recordings so a recording is never blocked by an EPG update. Is there any rule about what Priority I should set on Configuration | DVB Inputs | <adaptor> | Priority for the two tuners? I've given them values of 1 and 2, with the higher number being the tuner that is used in preference.
I've now set Configuration | Channel/EPG | EPG Grabber | Periodically save EPG to disk to 1 hour (changed from the default of 0 = never save). How does this field work? Does it save the EPG to disk immediately it has been updated by cron job or "Trigger OTA EPG Grabber" and then re-save it the stated number of hours later, or does it only save it after the stated number of hours, and not immediately? The former would seem to be the most sensible, as you don't want to lose updates that you've just acquired manually if you then need to reboot within the minimum configurable time of 1 hour.
For UK DVB-T and DVB-T2 broadcasts, what is a sensible "EPG scan timeout"? When I triggered a manual scan, I noticed that it was taking 10 minutes (600 seconds - the default) to scan each multiplex, rather than finishing sooner if possible. How long does it normally take to extract the EPG from a UK multiplex?