Buffering on Nvidia Shield Pro while Direct Play

Plex Players Streaming Devices
1

Server Version: 1.24.5.5173
Player Version: 9.4.1.33413

Hi there,

I have noticed a problem with the Plex client on the Nvidia Shield Pro 2019. When I start a video file, the video plays nicely for about 1min40s. Then it starts buffering, always at the same point. Playback only restart after 10+ seconds and only for a very short time before buffering again.

The file direct playing (both video and audio) from my local server. Moreover, when I play the file with another player on the same device, everything works perfectly.

For now, I have only noticed this behaviour with a single file. The video is Dolby Vision with HEVC encoding.

Do you have an idea of what is causing the problem and how I can fix it? I am happy to provide logs if needed.

Best,

P.S. Noticed this thread. Not sure whether it is the same issue or not. Feel free to merge if you think it’s best.

2

I’d need to see debug logs to know if you have the same issue.
The issue I was running into was the buffering would start in random places, anywhere from 30 seconds in to 1hr20min. For me, the fix was using the correct HDMI port on my TV. HDMI 2.1 cable from Shield to TV HDMI 2.1 port, then HDMI 2.1 cable from earc on TV to arc on soundbar (my TV only has 2 HDMI 2.1 ports). Sound on TV set to passthrough, same with audio in Plex add, set to HDMI passthrough.

I don’t get the actual Atmos logo popping up on the TV anymore, but the sound is there and I get the DV logo.

For me the crux was using the wrong HDMI port on my TV for the Shield.

3

I suddenly started having this issue as well . Also on the nvidia shield with latest versions.

A Dolby vision file will start playing and about 2 minutes in the playback will stop with a yellow spinner. After about 15 seconds playback will resume for about 20 seconds before doing the same thing again. If I try to resume playing the playback gets stuck.

I have reproduced this with two different Dolby vision files, hevc.
I’ve also successfully played other hevc content, and h264 content with much higher bitrates.

4

Looking at the logs there is repeated connection dropping by the shield.

Here’s a snippet, these 4 lines happen consistently every second or more. Tested watching other non Dolby vision content and these logs do not appear.


Jul 10, 2022 17:18:44.431 [7200] Debug — Failed to stream media, client probably disconnected after 2097152 bytes: 10054 - An existing connection was forcibly closed by the remote host
Jul 10, 2022 17:18:44.431 [7200] Debug — Completed after connection close: [192.168.20.10:50018] 206 GET /library/parts/43615/1655037769/file.mp4?autoAdjustQuality=0&hasMDE=1&location=lan&mediaBufferSize=209664 (10 live) TLS 130ms 2097152 bytes (pipelined: 1) (range: bytes=2623218-) 
Jul 10, 2022 17:18:44.459 [13508] Debug — Request: [192.168.20.10:50020 (Subnet)] GET /library/parts/43615/1655037769/file.mp4?autoAdjustQuality=0&hasMDE=1&location=lan&mediaBufferSize=209664 (10 live) #36003 TLS Signed-in Token (bzmwillemsen) (SHIELD Android TV) (range: bytes=29217847-) 
Jul 10, 2022 17:18:44.468 [13508] Debug — Content-Length of D:\NVIDIA_SHIELD\redacted.2160p.ATVP.WEB-DL.DDP5.1.Atmos.DV.MP4.x265-DVSUX.mp4 is 10848547438 (of total: 10877765285).
5

If you remux the video to mkv (with MKVToolnix) does it still have problems? There have been issues reported with mp4 DoVi playback on Android clients recently.

6

Hi there,

In my case at least, the file was a .mkv.

7

Switching from an MKV to an MP4 container solved the issue for me.

To summarize: There exists an issue playing dolby vision content that is in an mp4 container. Temporary workaround is to remux to an mkv container.

8

This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.