Synology - DVR Crashing after 2021.04.14.1420 Update/Tuning to FS1/FS2 on TVE

shnorgleton · April 14, 2021, 4:20pm

Hello!

Thanks for the update to address the TVE issue, however it's caused a different problem with my DVR it seems.

First, playing back FS1/FS2 (TVE feeds) in the browser had audio glitches throughout and would slide more and more out of sync. Playing it on the app on the phone resulted in a very strange stuttering/echo scenario, and the logs contained a lot of audio related looking errors.

I went back to see if these entries were present when viewing from the browser, but now when I try to play either, the DVR panics and shuts off. Here's a snippet of the log entry because it's mostly the same:

2021/04/14 12:12:36.488524 [HLS] ffmpeg: ch6197-dANY-fbf6e08f0dd8-remux:  [hls @ 0x75400c0] Non-monotonous DTS in output stream 0:1; previous: 2442240, current: 2438400; changing to 2442241. This may result in incorrect timestamps in the output file.
2021/04/14 12:12:36.490754 [HLS] ffmpeg: ch6197-dANY-fbf6e08f0dd8-remux:  [hls @ 0x75400c0] Non-monotonous DTS in output stream 0:1; previous: 2446080, current: 2442240; changing to 2446081. This may result in incorrect timestamps in the output file.
2021/04/14 12:12:36.490779 [HLS] ffmpeg: ch6197-dANY-fbf6e08f0dd8-remux:  [hls @ 0x75400c0] Non-monotonous DTS in output stream 0:1; previous: 2449920, current: 2446080; changing to 2449921. This may result in incorrect timestamps in the output file.
2021/04/14 12:12:36.490789 [HLS] ffmpeg: ch6197-dANY-fbf6e08f0dd8-remux:  [hls @ 0x75400c0] Non-monotonous DTS in output stream 0:1; previous: 2453760, current: 2449920; changing to 2453761. This may result in incorrect timestamps in the output file.
2021/04/14 12:12:36.490801 [HLS] ffmpeg: ch6197-dANY-fbf6e08f0dd8-remux:  [hls @ 0x75400c0] Non-monotonous DTS in output stream 0:1; previous: 2457600, current: 2453760; changing to 2457601. This may result in incorrect timestamps in the output file.
2021/04/14 12:12:36.492688 [HLS] ffmpeg: ch6197-dANY-fbf6e08f0dd8-remux:  [hls @ 0x75400c0] Non-monotonous DTS in output stream 0:1; previous: 2461440, current: 2457600; changing to 2461441. This may result in incorrect timestamps in the output file.
2021/04/14 12:12:36.492742 [HLS] ffmpeg: ch6197-dANY-fbf6e08f0dd8-remux:  [hls @ 0x75400c0] Non-monotonous DTS in output stream 0:1; previous: 2465280, current: 2461440; changing to 2465281. This may result in incorrect timestamps in the output file.
2021/04/14 12:12:36.494054 [HLS] ffmpeg: ch6197-dANY-fbf6e08f0dd8-remux:  [hls @ 0x75400c0] Non-monotonous DTS in output stream 0:1; previous: 2469120, current: 2465280; changing to 2469121. This may result in incorrect timestamps in the output file.
2021/04/14 12:12:36.494075 [HLS] ffmpeg: ch6197-dANY-fbf6e08f0dd8-remux:  [hls @ 0x75400c0] Non-monotonous DTS in output stream 0:1; previous: 2472960, current: 2469120; changing to 2472961. This may result in incorrect timestamps in the output file.
2021/04/14 12:12:36.495395 [HLS] ffmpeg: ch6197-dANY-fbf6e08f0dd8-remux:  [hls @ 0x75400c0] Non-monotonous DTS in output stream 0:1; previous: 2476800, current: 2472960; changing to 2476801. This may result in incorrect timestamps in the output file.
2021/04/14 12:12:36.495414 [HLS] ffmpeg: ch6197-dANY-fbf6e08f0dd8-remux:  [hls @ 0x75400c0] Non-monotonous DTS in output stream 0:1; previous: 2480640, current: 2476800; changing to 2480641. This may result in incorrect timestamps in the output file.
2021/04/14 12:12:36.497594 [HLS] ffmpeg: ch6197-dANY-fbf6e08f0dd8-remux:  [hls @ 0x75400c0] Non-monotonous DTS in output stream 0:1; previous: 2484480, current: 2480640; changing to 2484481. This may result in incorrect timestamps in the output file.
2021/04/14 12:12:36.497616 [HLS] ffmpeg: ch6197-dANY-fbf6e08f0dd8-remux:  [hls @ 0x75400c0] Non-monotonous DTS in output stream 0:1; previous: 2488320, current: 2484480; changing to 2488321. This may result in incorrect timestamps in the output file.
2021/04/14 12:12:36.497626 [HLS] ffmpeg: ch6197-dANY-fbf6e08f0dd8-remux:  [hls @ 0x75400c0] Non-monotonous DTS in output stream 0:1; previous: 2492160, current: 2488320; changing to 2492161. This may result in incorrect timestamps in the output file.
2021/04/14 12:12:36.497662 [HLS] ffmpeg: ch6197-dANY-fbf6e08f0dd8-remux:  [hls @ 0x75400c0] Non-monotonous DTS in output stream 0:1; previous: 2496000, current: 2492160; changing to 2496001. This may result in incorrect timestamps in the output file.
panic: runtime error: integer divide by zero

Thanks!

racameron · April 14, 2021, 4:34pm

Just a cursory look over those logs looks to me that there is a problem with the audio stream in the source, and when Channels tried to remux the stream to serve it, the incoming stream was so bad, that it crashed the program.

Assuming when you tried to watch it via the Channels app that it didn't crash but just had bad audio, it sounds like the app's streaming quality was set to Original. If that's the case, this points more to issues with the source, not Channels.

shnorgleton · April 14, 2021, 4:47pm

The only thing I can go off of is if I access FS1 or FS2 from their websites, they play back just fine. I figure that always doesn't necessarily translate into that it then should work here the same, but maybe someone who knows what to look for under the hood can see what's up! Who knows if they changed something, too!

It was indeed on Original quality on the iOS App (I'm outside the home right now so I can't view it on my ATV4K), but threw up the same logs when I moved it to 6Mbps (saying remux in the log but Transcode in activity). At least the last couple of attempts at viewing the channel didn't result in crashes, but did still result in the App audio stuttering/echoing like crazy, and the browser plays with audio hiccups every maybe 8-10 seconds and it slipping out of sync, along with similar corresponding log entries.

tmm1 · April 14, 2021, 4:52pm

Fixed in next prerelease

tmm1 · April 14, 2021, 5:00pm

Can you submit diagnostics from your dvr web UI under Support > Troubleshooting

shnorgleton · April 14, 2021, 5:04pm

Sent!

Logs have been submitted as 9ce3e76c-6c06-4131-a59f-e2c61ad65b78 .

shnorgleton · April 14, 2021, 5:12pm

Submitted logs were from 2021.04.14.1420. Was just able to upgrade to 2021.04.14.1650 and they seem to play just fine now on both Browser and Mobile with no audio errors reported in the logs. Thank you!!