Newest Beta Dolby Vision Issue

I believe it should, as Kodi does this with the SL/Profile 5 DV .mp4’s it currently supports. Now i’m no programmer, but i guess what happens is something like this:

  1. I initiate a playback of a DV file while in 60hz mode.
  2. Plex sees this is a DV file and asks the Shield/TV if it currently supports DV.
  3. Shield/TV says “no”.
  4. Plex says “OK then, ill play it in HDR 10 then”
  5. Plex sees it is a 23.976hz file, and switches to 23.976 and starts playback.

maybe if it switched to 23.976hz BEFORE “asking” the Shield/TV if it is DV capable (step 3) it would work? I suspect this is what Kodi does. (#NotAProgrammer) :slight_smile:

Should happen automatically. My Shield is defaulted to 50hz, and switches to 23.976hz as needed, and triggers DV :thinking: Provided Refresh Rate Switching is enabled, of course

Your TV probably supports DV at 50/60 hz over HDMI, which i believe was implemented in the 2017 models, as opposed to my 2016 model which is capped at 30hz for DV over HDMI. (which ends up being irrellevant anyway, disregarding that ONE movie actually in 60hz DV)

I have a Sony TV, but it still switches to 23.976hz (though it does support DV at 50hz and 59.94hz)

The more I read on this thread, the more I am convinced that the experience for those of us with DV @ 30Hz limited TVs is not the same for those with newer TVs that support DV @ 60Hz.

Is there a list of devices with known/confirmed support of mkv files with Dolby Vision. I’ve a Sony AG9 TV and I’m running Plex as an app in Android TV. I can playback mp4 files with Dolby Vision, but haven’t been able to play any mkv file with Dolby Vision. The playback always fallback to HDR10.

Is this a known issue or am I doing something wrong?

My TV is from 2016 :sweat_smile:

Though I was wrong earlier, we should not do refresh rate switching when using DOVI, as we can’t tell which modes support DV, and which don’t, unfortunately :disappointed:

IMO it would seem to make most sense to force (or always attempt) refresh rate switching to the native file rate, before attempting to request DV mode ?

1 Like

Just an update. I tried a relatively low bitrate DV file on my Shield (non pro, Tube). DV triggers perfectly fine but then it exhibits the same issue as playing high bitrate files. The shield freezes up and although playback seems fine the remote is unresponsive and it requires a hard boot to get out.

can we have a flag to disable DV playback? it doesn’t work well on sony TVs (ie. via plex on the sony tv, not via shield), so would be better to just have normal HDR playback with the possibility of future DV playback if the situation ever improves.

So that means it will never be solved for us LG 2016 users? :confused:

Hang on a minute… if the Shield knows which modes support DV from the connected television, why can’t Plex query the same information?

Doesn’t mean the OS gives us that information, unfortunately (we had the same conversation internally) :sweat_smile:

Have you spoken to Nvidia to see if they can expose the relevant information to apps?

I like to keep a backup MKV of physical media. Before MakeMKV 1.5.3. I was preserving the 1080P Dolby Vision EL inside my 4k UHD MKVs. I noticed in some testing that the new MakeMKV files with the Dolby Vision converted to a Single layer have 45-50% less “Dolby Data” than the original Dual Layer MKV. So clearly something is being lost in this process. Does anyone especially the Plex Devs think it is feasible that sometime even way down the road that PMS would be able to combine Dual Layer DV into Single Layer DV/HDR10 on the fly? As fast as it runs in MakeMKV it seems more like a muxing process as opposed to a CPU intensive process?

I have a 2020 TCL Roku TV that supports DoVi. I’d very much appreciate Plex on Roku would be updated to support DoVi soon. :blush:

That’s a pretty big claim to say that makemkv is losing data. There have been lots of test to suggest otherwise. To get a 50% smaller file I would say there’s something else wrong somewhere.

You can, using other tools, demux the single layer back into dual layer too and these have been compared to the raw files.

Just received my 2019 shield pro today after a torrid time with the non pro tube version and Plex (Stuttering and freezing on high bitrate content and DV titles). It’s night and day in difference. Everything on Plex is playing smooth for me so far including Dolby Vision titles.

1 Like

Sorry I was tired when I wrote the post let me explain my numbers:

Using older version of MakeMKV a Disc rip to MKV with only HDR10 video track and audio track is 42.5gb. A version then created with MakeMKV 1.5.3 is 44.2gb and difference of 1.7gb for the integrated DV information. But if I use MKVToolnix to create a MKV with 3 tracks, 4k video, 1080P DV-EL and audio and then extract only the 1080P DV-EL track it is 3.7gb of just Dolby Vision data.

If all 3.7gb of this DV-EL is really being integrated into a single layer why is it only1.7gb larger? I clearly don’t understand how it works from a technical standpoint but the numbers seem odd. I have 6 titles I tested and all had 45-50% less Dolby data in the single layer DV/HDR10 layer.

Algorithm doesn’t not merge BL and EL streams “as is” by simpe summation. It rebuild two hevc raw streams into one. General idea is described here https://www.makemkv.com/forum/viewtopic.php?p=85231#p85231

1 Like