Dolby Vision Issue in Infuse (support in dvhe.05.06 only but not dvhe.04.06 or dvhe.06.06)

Not all because 07 is double layer.

At least MrMC is proper support all Single Layer Dolby Vision Profile, include Profile 6 where seems Dolby itself taken out.

I am getting a profile 7 video now, later will test out, I don’t put high hope on it, but hope miracle appear. Haha!

james
I found dvhe.04.06 and 06.06 file on makemkv forum you can check uploaded to dropbox done.

I dont have TV w DV and I cant confirm this file but Andrewtst niteflyr can test it in MrMC.

Just to provide some clarity here.

The Apple TV supports Dolby Vision Profile 5, but unfortunately does not support other profiles.

What this other app is doing here is simply switching the output to Dolby Vision and playing the HDR10 content. None of the extra DV info is actually making it to the TV.

You can get the same effect in Infuse by following these steps.

  1. Manually switch output to Dolby Vision via Settings > Video and Audio
  2. Disable Dynamic Range matching via Settings > Video and Audio > Match Content
  3. Play these Dolby Vision files

The result is the Apple TV will stay in Dolby Vision mode while the HDR10 content is played, and tvOS will scale the HDR10 data to the DV range. This method can be used for these videos as well as normal (non-DV) HDR10 videos to achieve the same result.

2 Likes

Hmm interesting so Andrewtst and niteflyr the must compared colors :slight_smile:

My default setting is 4K SDR RGB High and match content on.

If you said MrMC simply switch, at least MrMC switch correctly Dolby Vision to Dolby Vision, HDR10 to HDR10 and it playback correctly.

When the film play at HDR10 using Infuse, the output is not better than MrMC playing at Dolby Vision. This show MrMC didn’t simply switch as you said.

2nd I try your method set default as Dolby Vision and match content off, in this case off course it will playback as Dolby Vision as SDR will also playback as Dolby Vision but the output from Infuse by doing this make the film look not correct with a bit over contrast and too dark.

I believe It is not good you said people work simply switch when you un-manage to make it.

I make a report here to let you all know the issue and hope you all can study and fixed it not simply ping point others people work. I not asking you must fix now and not forcing you to fix it, if unable to fix, it was ok, but it is not ok you point other people work simply switch.

I am truly disappointed, this is not a good developer attitude.

This is 2nd not good behavior already. 1st is white cover issue, your site just switch cover to black and make the white cover issue behave like solved. Now happen black cover issue and your site keep denying even though have some people submit the report to you, I also submit and I didn’t get any feedback on that as well except you point to TMDb that is causing issues. I mostly use self upload cover and this is happening to me using self upload cover.

Stop pointing fault to others as it wasn’t.

The Black Cover issue - Black Covers for movies are back!

Before this, similar issue but is in White Cover - Poster Art Turned White

Are you calling this solve? Changing blank cover from white to black doesn’t look solved to me.

Thanks for clearing this up James.

I’m simply providing some background on what is actually going on with these particular videos.

I’m not sure if the behavior you are seeing in this other app is a feature or a bug, but switching to DV when playing HDR10 video is generally not consider a best practice for video playback.

I guess we can consider this thread a feature request to enable DV output for HDR10 videos. Thanks!

Did you check my file info screenshot? It is Dolby Vision format.
Please check again my screenshot post previously.

It is label as

HDR format: Dolby Vision, Version 1.0, dvhe.06.06, BL+EL+RPU / SMPTE ST 2086, HDR10 compatible

or

HDR format: Dolby Vision, Version 1.0, dvhe.05.06, BL+EL+RPU / SMPTE ST 2086, HDR10 compatible

This one is the only detect as Dolby Vision in Infuse. Unless you also said your Infuse apps is detected it wrongly and also switch it wrongly to Dolby Vision as well because the file is HDR10. Stop being silly talking nonsense.

or

HDR format: Dolby Vision, Version 1.0, dvhe.04.06, BL+EL+RPU / SMPTE ST 2086, HDR10 compatible

Who need HDR10 playback in Dolby Vision. Nobody need this. You the one asking me try force method and disable Match Content which make all HDR10 and SDR play as Dolby Vision and said people apps - MrMC is cheating using this switching method. Don’t know whose the one talking lie here.

All the files I post here is Dolby Vision format not HDR10. From the place I get, Nvidia Shield 2019 user is success playback all as Dolby Vision in MrMC or KODI. Are you saying all those apps or the Device also detected it wrongly?

James is not clearing up but instead talk lie, if you believe him then I got nothing to said.

james You no need reply anymore.

You more feedback more lie.

I know Infuse was once great, but don’t be too arrogant.
Lie won’t make the apps better and they is no things always No. 1

I am enough with your lie

  • Blank Cover Issue (white or black or future you may consider red, blue, green, orange, yellow, purple or even rainbow cover).
  • Dolby Vision Support Issue

It looks like you have 3 samples.

The Apple TV will be able to support the Profile 5 sample (#2 in the list), but not the other 2.

Since all 3 have an HDR10 fallback layer, this is what can be played when the DV portion of the video isn’t supported.

So, for Profile 5 you will get true Dolby Vision.

For Profile 4 and Profile 6 Infuse will play the HDR10 portion and output HDR10 video.

What the other app is doing for these Profile 4 and Profile 6 video is playing the HDR10 video but outputting Dolby Vision.

We could of course enable this same behavior in Infuse, but it would be technically incorrect as the video output mode should always match the video being played.

All the files you post here, also have HDR. The Nvidia Shield 2019 is indeed capable of playing most or all DV profiles. Don’t confuse the two completely different devices. Apple’s Technical Specifications for the ATV4K specifically say Dolby Vision profile 5 only. See for yourself here under video formats. I, as yourself, was hoping for a miracle. What I would like to know is, could the current Apple TV4K support other profiles with a software update, or if we are going to have to wait for the next gen device?

1 Like

Thanks for the reply.

It is time for me considering Nvidia Shield TV 2019 already, will check more to see whether it fully support all profile or not.

I just get another profile movie, this time is Dual Layer dvhe.07.06
As predicted none apps in Apple TV 4K manage to playback as Dolby Vision.

But surprising me, my LG C9 internal player manage to playback as Dolby Vision by direct connect the HDD to the TV. The playback is no error so far. So seems LG C9 only support dual layer dvhe.07.06 as dvhe.05.06 came with double image, another two profile is not playable.

Dual layer is only supported directly on some TVs and the Oppo (and clone) media players. No other media player is licensed or supports dual layer Dolby Vision.

Thanks for the information, in this case no need think about Nvidia Shield TV 2019 already. Haha!

Will by pass dual layer copy in future.

I have a shield 2019 it’s not perfect either. It won’t have dual layer as it’s a feature that requires a paid license/proprietary codec. From what I’ve heard Dolby is pretty picky on who gets it (unless it’s pirated via firmware like the Oppo clones).

Appreciate much for your information, in this case I think no point to get Nvidia Shield TV 2019 for this moment.

I only had 1 title in dual layer, it simply can ignore.

I not interesting with Oppo media player, haha.

This is interesting with 1.15.2 we can create MKV backup with DV
https://www.makemkv.com/forum/viewtopic.php?f=12&t=22513

and play in shield tv using custom player “ExoPlayer”
https://www.makemkv.com/forum/viewtopic.php?f=12&t=21937&start=990#p93672

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