[DDVT Tool] Dolby Vision RPU Demuxing / Injecting / Editing.

[ed_co]

I found out more things by accident.

Just hold on and put on hold the mentioned bug.

So, as I said before:
- The file 2.mkv is cropped 3840x1606 and RPU is v4.0 (so this RPU should be cropped).
- The file 3.mkv is uncropped (as it is a remux) and RPU is v2.9.
I have both extracted, and for v2.9 (I have it extracted cropped and uncropped, although lets just consider the cropped one). So let's consider both RPU cropped.

So I thought, lets start clean, and as I know the remux 3.mkv has RPU injected (because this film does not have DV in its UHD release), get an untouched remux for some tests doing encodes from it. So now we have:
- The file 4.mkv, which is a clean remux without DV (just have HDR10). Size and quality looks the same vs the 3.mkv remux but with nothing injected. I will not use this file for anything but for encode a cropped version from it.
- The file 5.mkv, which is an encode from the previous remux (automatically cropped with handbrake and reduced file with CRF19). Remember just has just HDR10, and it was cropped curiously to 3840x1606 (not 1608, like 1.mkv).

So, from now we can have the bug context again.

So now I thought, OK now lets inject the RPU v4.0 to 5.mkv (from 2.mkv, which has the exact same resolution), and remember this RPU was complaining when injected to 1.mkv, but now it SHOULD WORK with no WARNINGS.
But it didn't!! It informs in RPU: [NOT MATCH WITH VIDEO] and just sets bottom 1, and not in the top!
so is complaining the same way as injecting to 1.mkv (which remember that has different resolution 3840x1608).
So with RPU v4.0 coming from 2.mkv (3840x1606), injecting to 1.mkv (3840x1608) and 5.mkv (3840x1606) is complaining with BOTH resolutions the same way.
Some problem with RPU v4.0 maybe???

So obviously I thought, let's try with the RPU v2.9 (3.mkv remux) to 5.mkv. I am considering the one I extracted cropped.
So with RPU v2.9 coming from 3.mkv -remux- (extracted cropped), injecting to 1.mkv (3840x1608) and 5.mkv (3840x1606) is NOT complaining at all with any of the resolutions.
So maybe the RPU v2.9 is more permissive or something?

So I guess, probably the DDVT tool is not considering something with RPU v4.0? Or maybe is just a bug, I don't know. The tool does not seem to have any problem with RPU v2.9.

Just one thing to remember: even the message of [NOT MATCH WITH VIDEO], I was able to inject DV to the files with no problem, as it was just a warning but is still a possible bug.

By the way the HDR10+ (which I have only in 2.mkv), does not have any problem with any file or any resolution... I guess HDR10+ is not tied to resolution at all? Don't know.

Well, I could provide any file:
- 1.mkv, 2.mkv, 3.mkv, 4.mkv, 5.mkv (although I think with just 1.mkv (7Gb) and 5.mkv (6Gb) is more than enough, maybe 2.mkv (15Gb), but definitely not the remuxes)
- RPU v4.0, RPU v2.9 cropped (and not cropped also), and HDR10+ json (everything is like 200Mb)
so maybe the author of the DDVT tool could have a look and fix the bug, if it exists. Please let me know and I will provide a link to download.

Jeez, I did a lot of work. I hope is worth it.

Thanks


P.S.: First, sorry for my English, and second, sorry for the big chunks posts!! Please read them carefully, I know there are a lot of information and is important to read it carefully and trying to understand, so please don't read diagonally or you will miss important details.

[ed_co]

BTW, just as a final note, it should be great to have the DDVT tool for macOS too. I had to do all of this with a Virtual Machine, which I can say is not the most optimised way I guess. Thanks!!

[GodzilaAvenger]

A few things:

1. You do not have to specify the cropping when extracting the RPU. You can extract the RPU from the remux with ~280 border and then set it to 0 when injecting it. You can make this change using the [Edit Active Area] option in the injector.

2. DDVT uses ffmpeg (or maybe ffprobe? doesn't really matter) to auto detect borders from the video file, and it does not analyze every frame, but a subset of frames, if I remember correctly. Because of this, it can be (and in my experience many times is) off by a few pixels, which can cause that [Not Match with Video] error. At the end of the day though, you can just go in and set the borders manually. What you are encountering has nothing to do with the source file of the RPU or whether it is v2.9 ir v4.0.

P.S. yes, HDR10+ doesn't care about borders.

[Arbok]

Why does DDVT INJECTOR.cmd crashes when I drag and drop .mkv file?

EDIT: When using DDVT_DEMUXER.cmd to get Profile 8.1, the process runs just fine, but I cannot find the resulting file(s). If I understand this right, there sholud be an Output folder in the Dolby.Vision.Tool.v0.65.3 folder, but it's not there. Can anyone help me, please?

[winoni71]

Hello, the "DDVT_MKVTOMP4.cmd" command doesn't work on the latest version of the file (v0.65.5), when I type "s" to start the window closes immediately, no error is shown and no log file is created.
Reverting back to the "v0.65.4" version of the file fixes the issue.

[ManilaByNight]

I tried "DDVT_REMOVER.cmd" on a .mkv file (Ironheart.S01E05.Karmas.a.Glitch.2160p.DSNP.WEB-DL.DDP5.1.Atmos.H.265.mkv) and it gave an error saying:

Dolby Vision Profile 5 not supported.

The file has a RPU included, but the RPU cannot be removed.

What does this mean and why does the script not work?

Can this be fixed?

[GodzilaAvenger]

I think this is because Dolby Vision Profile 5 is not backwards compatible with HDR10, i.e. the file needs the RPU to be playable.

[TR-9970X]

Originally Posted by GodzilaAvenger

I think this is because Dolby Vision Profile 5 is not backwards compatible with HDR10, i.e. the file needs the RPU to be playable.

Why is the latest build labeled 0.65.5, yet the download file is labeled DDVT_v0.63.5.rar.

Even the downloads on Mega are all DDVT_v0.63.5.

[ManilaByNight]

DDVT_Remover script with Folder support no longer works with the new released version 0.65.5. It suddenly quits and does not proceed. It used to work with version 0.65.4 after I requested for that feature to be added.

[cdth]

I have a question regarding remuxing the latest The Lost World Jurassic Park UHD that comes with a new DV FEL layer into a new .iso file.
The trick here is that the new UHD suffers from some nasty DNR so I'm thinking of using the 2018 HDR10 only transfer with better PQ but has 8 more black frames at the beginning.
So what can I do if I want to create a synchronized .iso remux file that has the HDR10 base layer from the 2018 UHD with the DV FEL layer from the 2025 UHD?

I hope my description isn't too confusing...

Would really appreciate any help from anyone!

[alexmorph3us]

I have a question. Can this tool be used to convert HDR to SDR content with tone mapping. If not, what would you recommend in this case?

[LisanAlGaib]

Quick question - I've been wanting to play some remuxes on my lg g3. I've tried the mkvtomp4 script but it says that profile 7 mel is not supported. Would my workflow then be - convert to DV profile 8 through the demux script and then inject it back to the original file, proceed to use the mkvtomp4 script? or am I missing something.

[GodzilaAvenger]

Originally Posted by alexmorph3us

I have a question. Can this tool be used to convert HDR to SDR content with tone mapping. If not, what would you recommend in this case?

As far as I know, no. But I think a lot of tools like Davinci Resolve, Handbrake, and FastFlix can do it. They probably all use FFmpeg to do this so you might as well use FFmpeg if you want control over the tonemapping.

Originally Posted by LisanAlGaib

Quick question - I've been wanting to play some remuxes on my lg g3. I've tried the mkvtomp4 script but it says that profile 7 mel is not supported. Would my workflow then be - convert to DV profile 8 through the demux script and then inject it back to the original file, proceed to use the mkvtomp4 script? or am I missing something.

I believe so, yes, but keep a copy of the original file just in case.

P.S. how's Chani?

[sirbod]

I've noticed the scripts fail if used from the command-line if filenames contain characters DOS considers special...ampersands for example.

The fix is to move the delayed expansion so it occurs before the INPUTFILE variables are set, instead of after. This goes for most of the scripts, but here's the corrected DEMUXER as an example:

setlocal EnableDelayedExpansion
rem --- Hardcoded settings. Cannot be changed ---
set "INPUTFILE=%~dpnx1"
set "INPUTFILEPATH=%~dp1"
set "INPUTFILENAME=%~n1"
set "INPUTFILEEXT=%~x1"

[hidef_rec]

Can a kind soul walk me through the steps to convert a DV P7 UHD rip to a P8, baking the FEL into the latter? Here's what I did, but I still ended up with a P7 instead of a P8:

1. Used Demuxer on P7 MKV

Save BL     : [YES]
Save EL     : [YES]
Save RPU    : [YES]
Convert RPU : [PROFILE 8.1 HDR10]
Crop RPU    : [NO]

2. Used Injector like so

Filename        : P7movie.4K.HDR.DV.ATMOS_[BL].hevc
DV Filename     : P7movie.4K.HDR.DV.ATMOS_[EL].hevc

3. Used MKVMerge to mux the resulting
P7movie.4K.HDR.DV.ATMOS_[BL]_[BL+EL+RPU].hevc
with the audio from the original

Obviously, I messed up somewhere or everywhere

[GodzilaAvenger]

As far as I know DDVT can't bake the FEL into the stream. You can use the injector to inject the RPU.bin converted from P7 to P8 into the .hevc stream, but not the EL.hevc (i.e. you'll be losing the FEL).

[hidef_rec]

Hmm, thanks, thought it was possible, but re-encoding would be necessary... which is a big negative. Just wanted to check my understanding. There's a FEL w/Ugoos AM6B+ or just used 'baked' P8 w/Zidoo debate going on in an AVSForum thread.

Edit: Found a post by the expert that seems to indicate so...

[GodzilaAvenger]

I'd say FEL doesn't even matter unless the studio did a terrible job of encoding the base HDR layer and you need the FEL info to recover the picture. Case in point, non of Nolan's films even have DV.

[LisanAlGaib]

Originally Posted by hidef_rec

Hmm, thanks, thought it was possible, but re-encoding would be necessary... which is a big negative. Just wanted to check my understanding. There's a FEL w/Ugoos AM6B+ or just used 'baked' P8 w/Zidoo debate going on in an AVSForum thread.

Edit: Found a post by the expert that seems to indicate so...

Try watching this video if you want to reencode yourself (actually, check out the whole channel, that guy is crazy good). The problem is that it'll probably take hours to reencode a 4k UHD movie. But if that's not an issue you can technically bake the FEL and convert the P7 into P8 without noticeable quality loss. The output will be 10 bit instead of 12 bit, but visually it'll look the same. If you want the best possible quality, use x265 instead of nvenc for the encoding, but that'll be 2-4 times slower.

[ManilaByNight]

I am on Windows 11 Pro 25H2 Build 26200.6901 (the latest version) and I tried using the Dolby Vision Tool Remover and I just get stuck on the "Analysing file. Please wait ....." section at the beginning of the process. Nothing else happens and the process does not complete. What is wrong here? Please help!

Screenshot 2025-10-26 063528.jpg