I bought the Tube a few months ago and returned it because it was not able to play high bitrate videos. A week ago I bought the Pro and it works like a charm with any bitrate.
Appreciate the feedback guys… I ordered the Pro a few days ago and just waiting for it to arrive.
I’ve updated my tubes to pros and the stuttering has stopped.
Now I need to work out why some of my 4k files play with a purple/green tint!!!
are they Dolby Vision?
I have a similar problem.
Plex struggles to play 4K HDR with high bitrate while Kodi plays them smoothly (including files with >100Gb and ~65K birate).
Whether the hardware should be improved it’s a completely separate question. The reality is that using the same hardware, network configuration and setup Kodi is able to playback flawlessly these files while Plex drives you mad until you decide to stop watching. This cannot be expected, and no matter how much love you have for Plex (as I do) we need to acknowledge that this should be working better. I’ll still invest in a Pro but I feel that Plex could be better optimized.
EDIT/PS: thank you Binson_Buzz (and others) for confirming that migrating to the Pro version of the Nvidia Shield solved your issue.
Yes. I have the same problem across Shield Pros connected to LG, Samsung and Tosh TVs that support HDR, and PMP connected to a 4K LG monitor where I’m not sure.
I hear certain movie rips only include the dolby vision profile (no backwards profile included). So if you are using a non dolby vision monitor/tv then you see that.
I can’t remember what Dolby profile it is that causes that issue, but it is a well known issue. It is because the particular profile is for streaming and does not contain the proper fallback layers. Plex has been looking at figuring out how to bring compatibility but I imagine it is proving to be difficult since those profiles were really never meant to be used outside of the streaming services they were designed for. Someone else will hopefully be able to provide more information about what exact profile it is that causes the issue, but there isn’t really any way to fix it without grabbing a new file.
2 Likes
Its profile 5
Thanks. That’s what I’ve been doing - just grabbing another file.
This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.
