All videos experience a delay when starting on the Shield - some more than others.
What happens now is that when I start a movie, the video will “skip” ahead about 10 seconds and be frozen there. The video progress bar shows 0, 1, 2, etc… Audio plays in the background, but the video is frozen for about 10 seconds.
I’m seeing the same thing on my Shield. It usually starts correctly when I back out then start again, but I didn’t have this issue until I updated to v8.20.
I don’t know if this was happening prior to 8.20 for me, personally. But backing out/starting over does not seem to resolve it for me. Even exited the Plex app entirely.
I’m having this problem too, as described by the title. I also have a Shield TV, and both it and Plex are updated to whatever is currently latest. The video is “frozen” for the first few seconds while audio plays. Both are Direct Play. For me, stopping and playing again works, and the video plays normally. I don’t have a solution to offer, but I am putting my 2 cents in here, just to add another voice to this topic.
@anon18523487 - What do I need to do to help you guys track this down & resolve? I posted logs in this thread from when this happened (server & client logs.) This is fairly re-producible and as you can see, I am not the only one affected.
Can you generate a 30s sample of that file? My guess is that it’s missing a keyframe at the beginning of the file so the app is waiting for the next one. If the file was encoded using 10s intervals for the keyframes, that would explain the 10s delay you are seeing. If you see different delays, it could be those files have other keyframe intervals.
I am on version 8.20.1.26670 now and I feel like the issue happens less frequently now, although it does still happen and the delay varies from play-to-play, etc.
I will try to spend some time today testing and grabbing sample files for you.
In the meantime, @anon18523487 - are you able to have a look at any of the other bugs I have posted about recently? I’m having difficulty gaining traction on a lot of these. Thanks for your time & support.
I have the same issue. My workaround is to just hit the rewind button to go back 10 seconds/to the start of the video.
It’s not exactly a solution, but is possibly slightly quicker than stopping and starting the video again.
I no longer plan to generate sample files, @anon18523487. This happens on all of my media, randomly, only on Android TV/Shield.
Much more interested in resolutions/responses to my other bug reports, but I’m not holding my breath. I’m sure they will be auto-closed after 90 days with no response.
I have given up on Plex and am just using Emby at this point.
The logs you provided show some network weirdness; all connections from your client appear to be remote. As a result, due to bandwidth restrictions, all media playback is forced to be transcoded. So, is your Shield TV remote to the server?
Here’s the relevant logging (with some information redacted):
Jul 16, 2021 13:59:46.342 [0x80983f000] DEBUG - HTTP requesting GET https://redacted-public-ip-address.redacted-certificate-uuid.plex.direct:32400/library/media/68010/chapterImages/1?X-Plex-Token=xxxxxxxxxxxxxxxxxxxx
Jul 16, 2021 13:59:46.355 [0x80749e800] DEBUG - Request came in with unrecognized domain / IP 'redacted-public-ip-address' in header Host; treating as non-local
When the client is local, and seen as remote by the server, the most common cause is DNS rebinding protection. When the client performs the DNS lookup for the server’s local *.plex.direct FQDN, DNS rebinding protection can prevent it from being resolved correctly. So, the client falls back to the server’s public *.plex.direct address. There’s some additional information here and here.
There are some suggestions in that second article for troubleshoot DNS rebinding issues. You could also try enabling Treat WAN IP As LAN Bandwidth under Settings -> Network to cause the server to treat connections from your own WAN IP address as local (and thus bypass bandwidth restrictions and transcoding).
But you should probably try to find why the local client is attempting to access the server’s WAN IP address.
So it would make sense for those logs to show indications of a remote server. However, this is a local server. A force quit of the Plex app on that day fixed my “remote server” issue and it hasn’t occurred since (to my knowledge.)
Unfortunately these new logs don’t have debug logging enabled. So, they don’t show anything useful. There are a ton of failed database queries, but I don’t think those are relevant (at least not to this issue).
