I had the prime time theory as well but havet proven it yet…
Ive had a couple of recordings complete this morning with no errors, and i think that commercial detection is non optimized in this version of the pre-release. i.e. comskip is being used.
Those two recordings looked great, and comskip worked as expected.
Another just completed with an error, but not the audio segment error?
However, the time duration was only 5 minutes. This is similar to a couple of recordings from earlier in the week. No error on the client, just a recording with wrong duration.
I did notice that a breakpoint was triggered in the logs @eric , but the recording didnt have the same audio segment error text . Seemed to be a different error.?
2022/10/18 07:01:10.122996 [DVR] Running commercial detection on file 3283 (TV/Alaska The Last Frontier/Alaska The Last Frontier S05E03 2015-10-18 Fear and Floating 2022-10-18-0559.mpg)
2022/10/18 07:29:41.796855 [DVR] Commercial detection for Alaska The Last Frontier S05E03 2015-10-18 Fear and Floating 2022-10-18-0559.mpg finished with 12 markers in 28m31.750759174s.
2022/10/18 07:48:00.635454 [NAT] Successfully mapped port 8089 using upnp
2022/10/18 07:58:59.960726 [DVR] Waiting 39.284ms until next job 1666097940-ch6101 Alaska: The Last Frontier
channels-dvr(12072,0x70000c4c7000) malloc: *** error for object 0x103045600: incorrect checksum for freed object - object was probably modified after being freed.
*** set a breakpoint in malloc_error_break to debug
SIGABRT: abort
PC=0x7fff50d9fb66 m=3 sigcode=0
Ive just submitted diagnostics from the DVR web interface:
fcdc42f3-2139-4cb4-aa24-09555ac65436
In the meantime ive got deadliest catch scheduled for primetime this evening, and several others scheduled during the day. Ill scheduke a couple more on food channel and hgtv for primetime as well @scottuf