After playing a virtual channel for an extended period of time, the video starts to stutter

[YetiMan]

Client is an Nvidia Shield, server is running on a Synology DS1819+. Full 1 gig network and a speed test confirms good speeds to the server.

After playing a virtual channel for an extended period of time, the video starts to stutter. Audio is fine, just the video.

I've only see this happen when I leave a virtual channel playing and I switch to another input on my AVR to do something else (watch a movie on a different device for instance). It's when I come back to the Channels input that I see this issue and the only fix seems to be a reboot. When I am actively watching a virtual channel I've never seen this issue, but so far the longest I've watched is probably 1.5-2 hours.

Maybe an HDMI handshake issue...?

[YetiMan]

Okay, this stuttering issue popped up again and it doesn't seem to be only virtual channels. I was watching an OTA recording this time. While watching, all of a sudden I notice the frame rate dropped, like it was missing frames. If I back out of the recording and re-start it, it does this weird pause/speed up thing that you can see in the video. The video shows me hitting "previous channel" between a live OTA channel and one of my virtual channels.

Channels frame rate issue

This issue seems to pop up every few days. Killing the app and clearing the cache does not fix the issue, a reboot seems to be the only way to fix it.

As soon as I noticed it last night I tried to submit diagnostics but the log file says:
[ERR] Diagnostics submission failed: Put "https://s3.us-west-2.amazonaws.com/diagnostics.channelsdvr.cloud/ae5c4927-7d34-4cec-be53-cd553b799fa4/dvr.hdhr.10B15329.log?X-Amz-Algorithm=AWS4-HMAC-SHA256&X-Amz-Credential=AKIA5BWMCXPFMBVC3OPV%2F20250418%2Fus-west-2%2Fs3%2Faws4_request&X-Amz-Date=20250418T235713Z&X-Amz-Expires=900&X-Amz-SignedHeaders=content-encoding%3Bcontent-type%3Bhost&X-Amz-Signature=8a7900fc61043205c0183847fb59f7f005dbdaccd5425a0a222772a144ade15d": dial tcp: lookup s3.us-west-2.amazonaws.com: i/o timeout

[YetiMan]

And here is everything else from the log file immediately after I hit submit diagnostics:

2025/04/18 17:57:00.057500 [TRS] DNS: OK: Resolved host via system DNS
2025/04/18 17:57:00.070584 [TRS] DBG: Provider: "Midcontinent Communications" (MIDCO-1) from 24.124.25.109
2025/04/18 17:57:05.071944 [TRS] Cloud Reachable: ERROR: Could not connect to community.getchannels.com: Get "https://community.getchannels.com/": Timeout after 5 seconds
2025/04/18 17:57:05.185965 [TRS] Local Time: OK: Local clock is accurate
2025/04/18 17:57:05.251181 [TVE] Couldn't get Chrome User Agent: fork/exec ./chromedp-shell: no such file or directory
2025/04/18 17:57:05.251244 [TRS] TV Everywhere: OK
2025/04/18 17:57:05.266716 [TRS] TV Everywhere DNS: OK: Resolved TVE authenticator via system DNS
2025/04/18 17:57:05.279272 [TRS] ad-dns: Resolved adservice.google.com: 142.250.69.226, 2607:f8b0:4009:81b::2002
2025/04/18 17:57:05.294655 [TRS] ad-dns: Resolved googleads.g.doubleclick.net: 142.250.72.2, 2607:f8b0:4009:807::2002
2025/04/18 17:57:05.307173 [TRS] ad-dns: Resolved assets.adobedtm.com: 23.217.77.90, 2600:1405:6400:18e::1e80, 2600:1405:6400:186::1e80
2025/04/18 17:57:05.319569 [TRS] ad-dns: Resolved d.adroll.com: 54.208.71.193, 52.44.39.244, 34.233.92.72, 18.214.82.138, 54.160.38.89, 52.87.98.154, 23.21.242.181, 3.218.149.164, 2600:1f18:61c0:2205:3afc:4f47:5e5:e52c, 2600:1f18:61c0:2205:d65f:54c:fd21:bcbb, 2600:1f18:61c0:2204:6152:ba31:f24f:2785, 2600:1f18:61c0:2204:2238:4615:c0d0:9277, 2600:1f18:61c0:2205:4b61:501a:6448:2905, 2600:1f18:61c0:2204:ca15:2040:9163:aa1c, 2600:1f18:61c0:2205:ad51:1040:c402:6f26, 2600:1f18:61c0:2204:ba25:9f07:8bb0:a5d3
2025/04/18 17:57:05.334272 [TRS] ad-dns: Resolved bat.bing.com: 150.171.27.10, 150.171.28.10, 2620:1ec:33:1::10, 2620:1ec:33::10
2025/04/18 17:57:05.351300 [TRS] ad-dns: Resolved pubads.g.doubleclick.net: 142.250.72.34, 2607:f8b0:4009:817::2002
2025/04/18 17:57:05.374743 [TRS] ad-dns: Resolved edge.api.brightcove.com: 199.232.66.27
2025/04/18 17:57:05.389292 [TRS] ad-dns: Resolved medium.ngtv.io: 23.11.12.210, 2600:1405:6400:18d::3134, 2600:1405:6400:180::3134
2025/04/18 17:57:05.389318 [TRS] DNS Ad Blocking: OK
2025/04/18 17:57:05.830195 [TRS] Guide Provider: OK: Connected to guide provider
2025/04/18 17:57:06.150108 [TRS] Device Lineups: OK: All devices have guide data mapped
2025/04/18 17:57:06.150166 [TRS] Operating System: OK
2025/04/18 17:57:06.150685 [TRS] Network Interfaces: OK
2025/04/18 17:57:06.150733 [TRS] Remote Access: OK: Remote access not configured
2025/04/18 17:57:06.150797 [TRS] Recording Directory: OK
2025/04/18 17:57:06.156660 [TRS] Disk Permissions: OK
2025/04/18 17:57:06.156720 [TRS] Disk Space: OK: DVR directory '/volume1/@appdata/ContainerManager/all_shares/ChannelsDVR' has 20.6T free
2025/04/18 17:57:06.369164 [TRS] DVR Version: OK: DVR is up to date
2025/04/18 17:57:06.369196 [TRS] DBG: Version info: &{2025.04.17.1651 https://cdn.channelsdvr.net/dvr false}
2025/04/18 17:57:06.369232 [TRS] DVR Status: OK: DVR is enabled
2025/04/18 17:57:06.405337 [DIAG] Could not find file: hls.log: open hls.log: no such file or directory

[YetiMan]

Can anybody offer any advice on my issue??

[tmm1]

Did you try software mode under advanced playback settings

[YetiMan]

Hey tmm1, thank you for the reply!

Yes, I have tried all three (hardware, hybrid, software) and no matter the setting it doesn't seem to effect my issue.

However, I have been able to cut down on how frequently this happens by doing a nightly reboot of the Shield. Not an ideal solution, but it works for now.