That’s kinda helpful, but when I play a UHD movie (Aquaman) on my 2019 Nvidia Shield Pro, when you select the movie for the basic info (what kind of HDR or sound formats), it shows only regular HDR, whilst on my computer server side, it shows DoVi, but I can’t seem to get Dolby Vision to show up on the client side on the Shield. Is it supposed to show up or just stay HDR?
I ask because it doesn’t exactly say Dolby Atmos, just TrueHD 7.1, so not sure. I even tried asking at Nvidia forums for what they do, but nothing has come to light as of yet, that allows DV to show.
On another note: when I press the info button on my receiver, it does say DV, but in 8-bit & I thought DV is supposed to be 12-bit, correct? I can show images if you need to see those.
Ah, so it’s on the client side for TV’s that DoVi cannot be shown then. Is that when using the 2019 Nvidia Shield Pro as well? I ask because that’s where the PLEX client app I’m using. I am using the PLEX server from my PC, which shows DoVi.
Is there a reason why the Web App does not always accurately pull the Audio data correctly? I have many movies that show as having "DD+7.1 " audio in the MediaInfo App, but it only shows in the Web App as “EAC3 5.1” audio?
Is this simply a case of adding a few more codecs into the Plex app your side at the next upgrade? Or can it be added to the fix, with the Atmos issue please?
I believe there is some licensing involved (at least that was the case a few years back when I asked). I will see if anything has changed on that front to allow us to probe for 7.1 channels. No promises, but I will ask internally.
Just like other little things that are actually self-evident… you still don’t recognize Dolby Digital 7.1 correctly, Atmos in TrueHD and DD+ or DTSX is not displayed as 3D audio, HDR10+ is not displayed correctly… The backgrounds when switching to the next episode in series are still ugly, just like in the end credits of films when the image becomes small and the extras are suggested… And this has been the case for many years.
I have now finished with the topic and no longer believe there will be any change. It’s apparently rocket science.
There may be internal and external reasons which we are not privy to, for example Dolby being touchy about their IP/tech being called out in this way. More than likely though, it is just stuck in the basement of low priority issues on the internal git. Hoping for a miracle at this point.
This is, frankly, one of the easiest things for Plex to implement and is clearly wanted by a great many of their fee-paying customers and yet their belligerent behaviour continues unabated. It’s actually amazing they are still afloat!
Could we add Dolby vision as a sort feature just like HDR? I have a folder of just remux rips and some are dolby vision and some are HDR 10. I would like to organize/sort by this. Thank you.
No idea if there are some license issue of using Dolby Vision wording. Frankly, I don’t even care if it specifically use those words. Just want to be able to filtering option. It could be called something generic like Dynamic HDR and be distinguished from regular HDR 10.
Certainly, there is no licensing problem since plex already shows Dolby Vision in mediainfo, but only on the web-based client what is obviously senseless.
So what we dont get here is, why not just implement this feature on basis of an existing framework (web-based client is implemented → device client not).
Its also sad that noone of the devs just gives a short explanation… i gave up asking for ETAs… but an explanation why this seems to be so complicated would help to understand. Maybe this is just not part of their strategy any longer, or significant changes in the framework would have to be implemented etc
@chrisallen once said that he would ask for it, but never heard from him after that
