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

[GodzilaAvenger]

As far as I know SDR uses the 8-bit BT.709 colorspace whereas HDR uses the 10-bit BT.2020 colorspace, so yeah, to go from SDR to HDR you need to do the things you mentioned. Once you have an HDR source (technically PQ when it doesn't have any metadata) you can add the DV metadata for dynamic tone mapping and brightness. I've never done SDR to HDR so I don't really know what exact steps it requires.

[JazzCZ]

Re-thinking the approach, I think it's impossible to make it look the same. Injecting DoVi/HDR10+ normally works because it's only dynamic metadata on top of the "static" HDR layer that's baked into video stream whereas what I'm trying to do is forcing the BT709 colorspace to be displayed as BT2020, which will inherently result in incorrect colors :(

[dbuser38]

Is it possible that we can get a MACOS version of the DDTV tools ?

[AgentXXL]

Is it possible that we can get a MACOS version of the DDTV tools ?

While you can run the scripts from Powershell on MacOS, many of the tools required for operations are only available on Windows. You could use VirtualBox or another VM engine and run a Win VM on your Mac.

[-QfG-]

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).

That is not correct. You can inject the full EL layer in the BL layer without problems.

[GodzilaAvenger]

Yes, but wouldn't injecting the EL into the BL result in the original P7 file?

Let's say you extract the BL, EL, and RPU. Then inject the EL into the BL, then convert the P7 RPU into P8 and inject that into BL+EL. Would that be playable? Wouldn't the player just ignore the EL at this point since P8 is not supposed to have the 1080p stream of the FEL?

[-QfG-]

If you inject a RPU in a single layer Profile 7 file, the RPU erases the EL. You have BL + EL and now you inject a Profile 8 RPU, You have BL+RPU (without EL).

But, you can edit a Profile 7 RPU and inject this RPU in the EL and then you can Mux this modified EL into the BL.

[frandan]

Hi to everyone.

I usually use Dovibaker for HDR ripping when FEL layer modifies the colors/luminance of the base layer. After the ripping, i inject the profile 8 RPU in the ripped HEVC file.

In the DDVT injector tool, I noticed the "RPU L6 to Video HDR" option, set by default on OFF: is this something about the modifications that the FEL layer makes on the luminance of the base layer? Thanks in advance for your answers, and excuse me for the probably not inherent question.

[Fuso]

I decided to test the capabilities of the Xbox Series X regarding Dolby Vision playback through PLEX. P8 is not supported but "my" "fake Profile 5" is playing with no problems, even supports Dolby TrueHD Atmos. I will test also fake P5 mp4 with DTS:X but I don't see a reason not to be played correctly. But no Profile 7 support (even through fake P5 - the EL is ignored).

[Valnjes]

Hello!

Thank you for this great tool!

My only issue is that it does not work on network drives.

My whole MKVs are on my NAS, and i would love to remux them to MP4s.

I mounted my network drive as an X:\ drive in WinOS, but i still cant use DDVT to convert MKVs to MP4s.

Could this be fixed?

Best regards :thanks:

[vertigo220]

Trying to use this to merge DV metadata from one file into another file that contains HDR10 (so far unsuccessfully), I'm finding this a bit frustrating to use. First of all, it takes over the command window and, if it errors (which I'm finding it does a lot, first because I didn't have the tools, which wasn't a clear/obvious need to download separately when downloading this, then for an unknown reason when trying to use it), it closes the window. This is a problem mostly because I had spent a bit of time trying to do what I needed with dovi_tools.exe, running numerous commands, and when the window was closed, I lost the history of all of that, which is now going to make it harder to go back to it if I can't get this to work, and also because every time the window closes, I have to go through the hassle of opening a new one, which isn't hard, but certainly annoying and a waste of time.

On my first attempt to use it after downloading the tools, I ran the injector and immediately found it unclear what to do, as it asked for a non-specific file. While I assume it means the file I want to inject, it should specify that, as for all I know it's asking for the file I want to inject _into_. I dragged the rpu.bin file I'd already extracted into it, and the next step asks for a custom edit file. I have no idea what this is, and I assumed this file is optional, since up to this point in messing around with this stuff, I'd not come across this, and dovi_tools.exe didn't seem to require one. So I simply pressed enter to skip it, and it exited with the following error:

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
RPU.bin

Unsupported Input File. Supported Files are:

*.mkv | *.mp4 | *.h265 | *.hevc | *.bin
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

despite the fact I'd supplied the rpu.bin file, which per that error is a supported file.

Also (and this isn't meant as criticism, as I realize QfG is likely ESL, it's just meant to help improve the wording), on the custom edit file screen, where it says

"For operation with a custom json file, drag 'n' drop here your CUSTOM EDIT FILE [.json] and hit ENTER. Attention! You can set in options if CUSTOM EDIT FILE will prcessed BEFORE or AFTER tool processings."

it should say

"For operation with a custom json file, drag 'n' drop your CUSTOM EDIT FILE [.json] here and hit ENTER. Attention! You can set in options if CUSTOM EDIT FILE will be processed BEFORE or AFTER tool processing."

I then tried to demux the RPU, but once it was done it didn't provide the option to do anything else, requiring me to exit and run a different tool. It would be a lot more user-friendly if it had a main menu to select the tool to run (which would allow for a single cmd file to run and would allow sending the user back to this menu once done with a certain action to make it easier to switch to a different tool) as well as more guidance on what to do when.

Then, after demuxing and getting a json file, I tried again to use the injector tool, this time providing the json file when asked for a custom edit file, and it again crashed with the above error. So I have no idea what's going on, why it's not accepting files it should accept, and I now have to go back to trying with dovi_tools, only now without the benefit of the command history from my earlier attempts.

[GodzilaAvenger]

Hi, I haven't used this tool in a while, but from what I remember you have to specify the file you want the RPU.bin to be injected into in the injector. The tool then looks in the file's directory to find the RPU file. The custom.json file is meant to specify what changes should be made to the RPU before injecting, e.g. changing L5 values.

[vertigo220]

I finally got what I was trying to do done by using the hybrid tool, though I'm still not sure if it's done *right* since there was very little info provided along the way, and the height of the two videos was slightly different. From what I can tell, this automatically compensates for that, but it's not at all clear, so hopefully when I go to play the video later on an HDR display it will work properly.

I also ran into another problem, where I've tried dropping an HDR10 file into the first (HDR/HDR10+ file) step hybrid tool, essentially trying to repeat what I'd already done successfully(?) with another video, but it keeps telling me "Only Single Layer files supported." Not fully sure what that means, but AFAICT it means only files with HDR10 and not hybrid files, but this file is HDR10 only, whereas I can drop a hybrid file on it and it works fine. So it's backwards.

[vertigo220]

Figured out the problem. If there's an exclamation mark (!) in the path, it gives the error. I'm guessing this tool is based on batch scripting and !'s in paths/filenames aren't properly accounted for, causing issues due to delayed expansion, causing the tool to not receive the proper input file path and therefore acting like no file was given, as the same error is shown in the case of no input file.

Another problem is that, despite it saying it needs a lot of drive space, it doesn't give any indication to how much space is necessary (this should be fairly trivial to calculate) or if enough exists (again, this should be simple to do). It also doesn't allow for changing the output to a different drive, which would help a LOT in this regard. And finally, if there's not enough space, it shows an error saying it's run out but then continues on anyways, wasting time as the final encode is not going to be complete (and potentially causing data loss if the user doesn't realize this and thinks it's complete because it finishes when it, in fact, is not).

I'm also still not clear on the borders/cropping functionality, since whenever I use two files with different heights with the hybrid tool, the borders are all zeroes (0's), when it seems they shouldn't be, so I'm still not convinced it's working properly.

It's also odd that the remover tool defaults to N instead of Y. Why would someone run this tool if they didn't want it to do its job?

So now I just need to figure out the cropping, because it's not clear at all if it's being applied (or not being applied) correctly and if my final output is going to play correctly or not.

[-QfG-]

v0.74 Online.

[sergio2]

Update to v0.30. Many Bugfixes, HDR10+ to DV Conversion still working.
https://1fichier.com/?86t4gujfcl3hrv8eezw7

DV Profiles:

DV Profile 7 (UHDs [HDR BL+EL+RPU]) = Dual Layer DV Profile, FEL or MEL. Can be repacked in a single Layer stream (not official supported) via makeMKV. Single Layer mkv needs special Hard/Software for viewing in DV. Fallback to HDR: YES
DV Profile 8 (8.1[HDR BL+RPU] 8.2[SDR BL+RPU] 8.4[HLG BL+RPU]) = Single Layer Dolby Vision with Fallback to HDR if DV is not supported. Official DV Profile, can be played on every DV Player in a MP4 Container.
DV Profile 5 (WEB [HDR BL+RPU]) = Single Layer Dolby Vision without Fallback to HDR if DV is not supported. Official DV Profile, can be played on every DV Player in a MP4 Container.



Yes, you can inject a converted Profile 8 RPU in a HDR Videostream, like UHD. The streams must be frame identical, if the stream have a delay you can set the delay with the scripts.

Where can I get the dovi_tool.exe able to mux BL + EL + RPU in a single Layer stream ?

[frandan]

Hello to everyone,
I have a doubt about custom json option in ddvt_injector.
In the past i worked on a video with variable aspect ratio and consequently with variable crop to apply.
i used a custom json file like this
{
"mode": 2,
"active_area": {
"crop": true,
"presets": [
{
"id":0,
"left":0,
"right":0,
"top":68,
"bottom":68},{
"id":1,
"left":0,
"right":0,
"top":34,
"bottom":34
}
],
"edits": {
"0-5000":0,
"5001-186112":1

}
}
}
called level5new.json
and created a new rpu with
"dovi_tool editor -i RPU_original.bin -j level5new.json -o RPU_new.bin".
The rpu_original file was with no crop applied during demuxing.
Will i obtain the same result using the custom file as injection option?
Should I keep the file without cropping in this case as well?
Thanks in advance for your answer.

[Shumbles]

Hey, I was wondering if anyone might know of a solution for a problem I'm having. I was on windows 10 and using the DDVT Tool to convert DV Profile 7 to 8.1 and remux files into mp4 containers. It worked perfectly.
However, I did in in-place upgrade to windows 11, and ever since then, I can't drag and drop any files. I'm currently using the administrator account. Anyone know of any settings I need to change? Thank you.