I should have been more specific, I was only referring to the server logs . The client logs should be fine as-is.
Ok yeah, didn’t think I could increase logging any further on the Shield. I’ll get a new set of logs.
Here’s a new set of logs with DEBUG enabled on the server.
Happened again with The Avengers, and with Captain America - activities started around 14:44.
Plex Media Server Logs_2021-08-17_14-46-58.zip (6.9 MB)
shield_logs_v5.txt (4.8 MB)
Having looked at your logs, nothing really jumps out at me. From the Shield’s perspective, it looks like the playback was requested around 14:44:01.035 and that it actually entered the playing state at around 14:44:04.641. It looks like playback was stopped around 14:44:21.464.
There’s no obvious buffering/freezing during this timeframe, at least not that the client is reporting. It just appears to be regularly fetching stream data and performing its timeline reporting to the server every ~10 seconds. (For what it’s worth, the server’s logs are roughly 6 seconds “behind,” so the sequence above starts at 14:44:06.045 in them).
I tested a playback on my Fire TV client to compare the generated logs and they were substantially similar to yours.
Thanks for having a look.
I agree with @pshanew that there is nothing in your logs to indicate any freezing of the video. I do think it’s a keyframe issue.
Your Shield is set to output at 1920x0180 @ 59.94 fps. The video itself is 23.976 fps. So the Shield has to pulldown the framerates to get them to match. It’s possible your TV doesn’t like this and is causing the delay waiting for the Shield to match up. This would explain why the delays are different depending on the video and why some videos may not exhibit this issue, it all depends on the framerate of the video.
In the Plex app setting, turn on Refresh Rate Switching and see if that helps.
I have tried Refresh Rate switching in the past and it really jacked stuff up - blank screen for a number of seconds, etc. But I am willing to give it another try.
I am not convinced it is a key frame issue, because I can play the same video file repeatedly - sometimes it will be delayed - other times it won’t. If it was a key frame issue, wouldn’t the behavior be the same every time I played a problem file?
I can play the same file 10 times in a row and a few of those times it will be delayed, other times it will play successfully.
I am experiencing the same issue, with all kinds of videos (4K HDR, 1080 SDR, etc). I also don’t think it is a 3:2 pull down issue, as I have refresh rate matching turned on.
it appears to have started after the last update, but all different types of media:
- click play or resume
- spinning load icon sits on screen for 5-10s, sometimes I have to back out and then retry. within 5-10 resumes, can get it to play.
- other times same file will play no issues instantly upon clicking play.
no other changes for the past 9 months to server side or should pro.
have tried variety of things, no luck.
Exact same issue. Never had issue before. This is a new bug.
Same issue here for months now. If I turn on subtitles immediately the issue goes away and does not return if I exit then restart the video. Rarely does a video start properly and play immediately.
I have this exact same issue on my Shield Pro.
This same issue was prevalent on older Android devices up until roughly a year ago, give or take. Pixel phones (1&3), Nexus tablets, etc.
It was definitely not an encoding issue. It happened with any file in a library of h.264 MP4, even happened with Synced files downloaded to the device locally.
Same issue here. Willing to try things and provide logs, but not a serious enough issue for me to investigate at length.
exact same problem, on all videos i have.
just started after last update.
Pilling on. Same here. Been happening for a long time now. Happens with my friend’s Shield Pro too.
I have seen this issue on my Firestick that I pretty much gave up on.
Same issue here. OG Shield Console w. local server, wired gigabit connection.
Same issue, NVIDIA Shield Pro as my client.
Having the same issue after the last update. This was not a problem previously and I have tested with media I have watched before where this wasn’t an issue. Using 2017 Nvidia shield TV.
