|
SageTV Software Discussion related to the SageTV application produced by SageTV. Questions, issues, problems, suggestions, etc. relating to the SageTV software application should be posted here. (Check the descriptions of the other forums; all hardware related questions go in the Hardware Support forum, etc. And, post in the customizations forum instead if any customizations are active.) |
|
Thread Tools | Search this Thread | Display Modes |
#1
|
||||
|
||||
Halt Detected in Recording - iptv
From some sources (e.g. iptv), when I get the "Halt Detected in Recording" error from the tuner I want Sage to retry the stream straight away, say a 5-second wait at most. However, it seems to wait around 6 minutes before restarting the stream.
Is this intentional? And is it configurable?
__________________
unRAID Server: Intel Core i5 7600K, 48GB DDR4, 2x512GB PCIe M.2 Cache Pool, 2x10TB SATA3 Parity Drive, 3x8TB SATA Array, 1x hdHomeRun DVB-T2 Quattro, IPTV via xTeVe, unRAID 6.8.3, tvHeadEnd for recording back end, Emby Clients: 3 Nvidia Shields, 3 FireTV, 3 Win10 Pro PC Clients |
#2
|
|||
|
|||
My tuners detect halts every minute. The setting is seeker/duration_for_halt_detection in the properties file and defaults to 60000 (ms) which is 1 minute. Maybe yours was changed?
|
#3
|
||||
|
||||
Thanks for that, mine is the same. Does that mean check the stream every 60 seconds, or when checking, only act after 60 seconds of no data?
Seeker is only woken every 5 minutes though from what I see, I wonder if that could be the delay? I'll need to try to grab logs quickly when it happens and see if I can work it out.
__________________
unRAID Server: Intel Core i5 7600K, 48GB DDR4, 2x512GB PCIe M.2 Cache Pool, 2x10TB SATA3 Parity Drive, 3x8TB SATA Array, 1x hdHomeRun DVB-T2 Quattro, IPTV via xTeVe, unRAID 6.8.3, tvHeadEnd for recording back end, Emby Clients: 3 Nvidia Shields, 3 FireTV, 3 Win10 Pro PC Clients |
#4
|
|||
|
|||
You could be right that it’s the act after missing data for 1 minute. I do get stacks of warnings every minute when a recording fails but perhaps a halt detection keeps Seeker awake. I never paid attention to how mich delay there was before the first detection.
|
Currently Active Users Viewing This Thread: 1 (0 members and 1 guests) | |
|
|
Similar Threads | ||||
Thread | Thread Starter | Forum | Replies | Last Post |
Halt detected in recording, end up with mpg and ts | gprichardson1 | Hardware Support | 1 | 06-17-2014 07:58 AM |
Halt Detected in recording with SageDCT? | MickBurke | Hardware Support | 9 | 07-16-2011 10:12 AM |
Halt Detected in recording | PiX64 | SageMC Custom Interface | 18 | 04-13-2010 06:03 PM |
Halt Detected In Recording | vrscdx | Hardware Support | 43 | 03-05-2010 09:14 AM |
Halt detected in recording | loonsailor | SageTV Software | 0 | 08-12-2009 12:14 PM |