Dolby Vision Profile 7 & 8 support (.ts/.mkv files)

I’ve always done these steps. Only sometimes it doesn’t create the mkv container and leaves me the file in .hevc. But there is something wrong with these P8 DV in this 7.5 version.

The EL in a P7 MEL is blank; it contains nothing. P7 MEL is still 10bit just like P8.1, it’s just there for compatibility purposes. So when you convert P7 MEL to P8.1, you lose nothing.

On the other hand, converting P7 FEL to P8 means discarding the 2-bit Enhancement Layer, so you end up with the 10-bit Base Layer + the dynamic metadata (RPU), instead of the original 12-bit.

Could you describe the steps you followed?

On version 7.4 I converted all my 4k remuxes by the method provided here by @everest with dovi_tool and for the first time they trigger the DV logo on my tv . And saddly after v 7.5 all of them play with a black screen after taking much more time to work.
If v7.4 was working perfectly that means it can be fixed on future updates right?
Apple tv 4k 2017

I’m using dovi_tool v 0.52

  1. Drag original MKV file into DDVT_DEMUXER
  2. Drag original MKV file into DDVT_REMOVER
  3. Move RPU file created in step 1 into the folder with the No DV file created in step 2.
  4. Drag the No DV file into DDVT_INJECTOR
1 Like

5 posts were split to a new topic: DoVi P5 playing as HDR in 7.5+

can confirm that wiping out the existing DV metadata and sliding the RPU back in totally takes care of those pesky files

HDR files, with P5 injected to make P8 DV, seems to initiate DV just fine in Infuse’s limited mode on my tv. The Last of Us for instance.

1 Like

It sounds like you’re using dovi_tool via DDVT. Why are you using the REMOVER in Step 2 instead of just using the option in DEMUXER to save the BL (Base Layer)? They accomplish the same thing with 1 less step. The BL is demuxed anyways by the DEMUXER, but is deleted by default… you can just choose to retain it.

This didn’t work for me for files that are showing a black screen. I have been able to fix some files with that issue though by converting them from CMv4 to CMv2.9.

I’ve always used the dovitool tool (now I’m using 0.51) saving the rpu file, removing the metadata (hdr+ and DV) from the original and with the file without DV I inject the previously saved rpu file, so they all go to infuse 7.5 .

Previously I had problems with version 0.52. it didn’t create the mkv file for me.

Late to the party :tada: On my 1st test I ended up with a P8.1 from my UHD MEL (sample) that shows as DoVi with Infuse 7.5/Auto, ATK4K 2022, LG 2017 E7.

I can’t compare (nor do I have tools) to my Oppo UDP-203 streaming or playing the same disc but the convenience of Infuse and this recent P8 support is :+1:

ffmpeg -i bluray:/MOVIE
-map 0:0 -ss 01:06:00 -to 01:06:20 -c copy vBL.hevc
-map 0:1 -ss 01:06:00 -to 01:06:20 -c copy vEL.hevc

dovi_tool -m 2 mux --bl vBL.hevc --el vEL.hevc --discard -o vBL+RPU.hevc

MP4Box -add vBL+RPU.hevc:hdr=none:dv-profile=8.1:xps_inband -no-iod -enable 1 vP8-010600.mp4

Looking for some help… I am on the latest - Infuse 7.5 - and not seeing DV enable on the TV. I only see HDR.

Apple TV 4K - older model (2017)

Here’s the MediaInfo - I see it says DV, but I’m not sure which number is the profile:
HDR format : Dolby Vision, Version 1.0, dvhe.07.06, BL+EL+RPU, Blu-ray compatible / SMPTE ST 2086, HDR10 compatible

That’s profile 7

Hi James can’t you just have 2 options “Auto” or “Off” because having 3 options is confusing.

Why would “Limited” be more accurate as you described in settings?

So your saying in “Auto” P8 files which can’t be played as P5 will still play as DV files. But I can choose “Limited” to make it play as HDR as this is supposedly more accurate? I’m really confused.

Please only have 2 options “Auto” or “Off” as it doesn’t make sense and I don’t know what to choose between “Auto” or “Limited”

An absolutely awful idea. It needs setting once for your own preference and then you can forget about it.

If you want only true Dolby Vision set it to limited.
For files that cannot truly play back as Dolby Vision it will play as HDR.

If you want to see that Dolby Vision logo on your tv even if it’s actually playing fake Dolby Vision then set it to auto.

I do get your confusion however. For me Auto in most circumstances implies a logical/best/optimal setting.
In this particular case it’s the setting that nobody should be using. Why anyone would want fake Dolby Vision I have no idea.

Bottom line though, as I said, set it once and forget about it.


Thinking about this more a less confusing naming scheme would be “Auto”, “Forced” and “Off.”

“Auto” being the file playing in the format that’s supported.

“Forced” implies exactly that. The device is being forced into DV mode regardless of it not being able to play back the DV metadata.


The problem is that there are some DV8 files that cannot be predetermined and that is why these three options exist instead of two. Files that play in auto and not in limited can be “real” DV and not “fake”. But with auto you could also be enabling “fake”

Not forgetting all profile 7

These settings only apply to profile 8

Or course but the point I was making was that in “Auto” all profile 7 will do fake DV as well as unsupported profile 8.
And therefore another reason why there are three settings. :grin:


Or actually I was sure one of my Profile 7 played as fake DV whilst testing a few weeks ago in “auto” but I’m probably wrong.


Confirmed that I got it totally wrong regarding profile 7