I use Channels DVR on my Unraid server to stream and record channels from a custom M3U list that is routed through DIspatcharr. It mostly works fine but in the last few days I have scheduled some long recordings of approximately 3-4 hours in length and each time the recorded file is just the first 30 mins or so. This happened last night and here are the logs:
025/09/08 01:09:02.941388 [TNR] Opened connection to M3U-Dispatcharrr for ch11
2025/09/08 01:09:02.941744 [DVR] Recording for job 1757290140-ch11 from M3U-Dispatcharrr ch11 into "TV/Live NFL Football/Live NFL Football Baltimore Ravens at Buffa 2025-09-08-0109.mpg" for 4h35m59.998571766s
2025/09/08 01:09:02.976597 [IDX] Generating video index for job 1757290140-ch11
2025/09/08 05:45:00.001388 [TNR] Closed connection to M3U-Dispatcharrr for ch11
2025/09/08 05:45:00.013565 [SNR] Buffer statistics for "TV/Live NFL Football/Live NFL Football Baltimore Ravens at Buffa 2025-09-08-0109.mpg": buf=0% drop=0%
2025/09/08 05:45:00.022263 [DVR] Finished job 1757290140-ch11 Live: NFL Football
2025/09/08 05:45:00.038250 [DVR] Processing file-565: TV/Live NFL Football/Live NFL Football Baltimore Ravens at Buffa 2025-09-08-0109.mpg
2025/09/08 05:45:02.160452 [DVR] Running commercial detection on file 565 (TV/Live NFL Football/Live NFL Football Baltimore Ravens at Buffa 2025-09-08-0109.mpg)
2025/09/08 07:44:12.023641 [DVR] Commercial detection for Live NFL Football Baltimore Ravens at Buffa 2025-09-08-0109.mpg finished with 22 markers in 1h59m9.863240127s (4 threads).
From those logs, it looks like the recording started at 01:09 as scheduled and that it ended at 05:45 as scheduled but yet the recorded video file is only the first 34 mins of the recording. The same thing also happened on Friday morning with a similar operation.
Is it possible to get any more detailed logs to understand what happened? I understand that there are a lot of moving parts that could be causing the issue but I am finding it very difficult to understand what is happening.



