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

[Mickkk]

Originally Posted by Fuso

What's the model of your LG?
You can use the DDVT_MKVTOMP4 with Option 2 (Fake P5) enabled.

LG C8. I have tried the Fake P5 option also. To my surprise it did not work, I just get a black screen with sound. Somebody in this thread stated that old LG's have problems with new MP4 containers.

Converting MKV to M2TS works fine for me for files 3840x2160. If the video stream is "thinner" (like 3840X1600) then I get grey (not black) bars - this is very annoying if watching in a dark room. I understand that it is happening because DV metadata is not limited just to the video size, it is applied to the whole screen. I want to find a way to change this

[JackNicko]

Originally Posted by tijgert

Hello all,

Running into a new situation here:
Source UHD with DV is 3840x1600 (letterboxed), destination UHD that needs DV is 3840x2160 (black bars).
When injecting the RPU it says video input matches with output RPU but RPU input does NOT match with video.

I also read that:
Originally Posted by Boulder View Post
My assumption is that whenever the final result doesn't have any black borders, you use the cropping option for the RPU.

So, does that mean that since the final result here WILL have black borders I do NOT need to crop?
I 'fear' the RPU will not be applied to the middle where the picture is but starts at the top so that the black bars will get DV.
Or WILL it be centered?

edit:
Made a json file where it specifies the crop, but it doesn't take over the values.

Hey, I have a question about your post. I sent you a private message about this. I would appreciate an answer! Thx.

[-QfG-]

Originally Posted by Mickkk

Perhaps it has been already discussed, but I cannot solve the following problem. I have a hybrid MKV video (DV + HDR10) 3840X1608. My old LG C8 shows the file in HDR10 with black bars - all OK. So to play DV, I converted the file into m2ts - now my LG shows it in DV, all OK, BUT the top & bottom bars are no longer black, they are grayish.

So I extracted the RPU & adjusted the top/bottom borders manually to 276 & injected them back into the video. Nothing changed - the bars are still not black, but grey.
Is there a solution? Please help.

Forgot to mention: I play the video with OPPO clone

BTW Great tool! Many thanks!!

The active Area 0,276,0,276 is wrong if the input video is cropped and has no borders. set the Active Area to 0,0,0,0 in this case. Active borders must set for the real resolution of video file, not the aspect ratio. Also the OPPO and his clone have problems with cropped content. I recommend Ugoos AM6b+ / Dune Homatics 4K R Plus Media Player with CoreELEC CPM builds. You have full FEL support with this Media Box and no problems with cropped content. The player plays MKV P7 FEL Single layer files without re-containering, too.

So, does that mean that since the final result here WILL have black borders I do NOT need to crop?

It's easy, simply ignore resolution/AR from DV input file. Important is the resolution and the black borders of the HDR target file where you inject the RPU. If your target file is an UHD with 3840x2160 and has 276px Black borders Top/Bottom and your input file with the DV content has 3840x1600 without black borders, set the Active Area to 0,276,0,276.

[-QfG-]

-v0.65.2
-FIXED Errors with FFMPEG and bitstream demuxing/pipelining (clipping and wrong colors on some movies)
*Minor Bugfixes.

[pejok]

Hi all,

I get below errors when using HYBRID script. Last version without this errors is 0.64.2.
There are no errors with exact same video files in DEMUXER or INJECTOR -> It demux and inject without any issues and final video file is OK.
It occurs with every video file, when i try to use HYBRID script. Source video file for demuxing has both RPU and HDR10+ .json as well.
Where should be the problem or what should i try to set up/change on my side?

OS: Win 11 Pro, 24H2

Thank you very much. Excellent tool

[-QfG-]

@pejok Problem fixed, please download this file and overwrite the hybrid script with this file:
https://github.com/DonaldFaQ/DDVT/bl...DVT_HYBRID.cmd

[pejok]

@-QfG- thank you, no errors so far but maybe last bug as i noticed is, while testing and trying to do hybrid with HDR10 only file + DV&HDR10+ file:

- tool correctly fetch all info about the files
- i have set also to inject HDR10+
- start the script -> DV extracted -> HDR10+ -> Scenecuts fixed -> DV injected -> muxing final video file
- injecting of HDR10+ completely ignored
- final video file contains DV + HDR10 only (not HDR10+)

[-QfG-]

You're right, sorry forgot to process this switch. Fixed now, simply update the script.
https://github.com/DonaldFaQ/DDVT/bl...DVT_HYBRID.cmd

[pejok]

Perfectly working again. THANK YOU !

[Fuso]

Originally Posted by Mickkk

LG C8. I have tried the Fake P5 option also. To my surprise it did not work, I just get a black screen with sound. Somebody in this thread stated that old LG's have problems with new MP4 containers.

Converting MKV to M2TS works fine for me for files 3840x2160. If the video stream is "thinner" (like 3840X1600) then I get grey (not black) bars - this is very annoying if watching in a dark room. I understand that it is happening because DV metadata is not limited just to the video size, it is applied to the whole screen. I want to find a way to change this

Strange. I have an LG B8 and the files play without any issue when they are converted to "fake" Profile 5.

[AgentXXL]

Originally Posted by -QfG-

You're right, sorry forgot to process this switch. Fixed now, simply update the script.
https://github.com/DonaldFaQ/DDVT/bl...DVT_HYBRID.cmd

Thank you for your continued efforts on improving these scripts! They have saved me so much storage by only needing 1 file that will play on pretty much anything.

Is it recommended to download the latest scripts from your github site and unzip them into the folder containing the full DDVT package, overwriting the original scripts from the Mega download? I see that 65.2 is the latest on Mega but the github scripts are showing as 65.3. Are there any gotchas like needing updates to other apps in the Tools folder?

For all:

I am experiencing a related issue - drag 'n drop is no longer working on the main Win 11 PC I use to run these scripts. A Win 11 VM running the same Win version does still work. I've been trying various recommended solutions (13 of them so far) but all I've managed is being able to drag 'n drop ONLY to the Desktop.

Not to open apps/windows/websites with a drag 'n drop function. Plus I can only drag to the sides or bottom, not up past the explorer window title bar - that just drops the item being dragged just like pressing the ESC key while dragging. If anyone else has experienced this and fixed it, I'd be grateful if you shared your solution. Right now it's looking like a full Win re-install, which I'm reluctant to do.

I can still use cut & paste to 'drop' the source files into the scripts, but drag 'n drop is preferred.

[Emulgator]

Maybe this helps, Ramesh Srinivasans fix helped on my Win10 too:
https://www.winhelponline.com/blog/d...file-explorer/

[AgentXXL]

Originally Posted by Emulgator

Maybe this helps, Ramesh Srinivasans fix helped on my Win10 too:
https://www.winhelponline.com/blog/d...file-explorer/

Thanks, but no-go. I hadn't come across this particular registry fix, but mine was already set properly for that Attributes key, and the other key in HKCU was not present.

I'm going to try removing the shell extensions for DDVT and clearing the registry of any DDVT specific keys. And then I'll try a fresh folder with the latest package and retry adding the shell extensions. If that fails, I'm going to reluctantly do the full fresh Win install.

[jl0292]

@-QfG-, sorry I am quite new here, but can we have updating version (currently it is 0.65.3 if I am correct).
I have tried to ddvt_demuxer to demux RPU.bin and HDR10+.json and then use ddvt_injector to inject these two into a compressed 4k film, but I kept constantly receiving error message on Editing Video HDR Metadata and Muxing test into MKV Container.
I honestly did not meet these issues on 0.64.x; however, I could not find previous versions on GITHUB database.
So whether you can provide previous version or possibly update version will be fine, hope it is not too much request for you, thanks!!

Here are the latest result of message as follows,

[Applying cropping values]
EditConfig {
"mode": 0,
"remove_cmv4": false,
"remove_mapping": false,
"active_area": {
"crop": false,
"presets": [
{
"id": 0,
"left": 0,
"right": 0,
"top": 0,
"bottom": 0
}
],
"edits": {
"all": 0
}
}
}
Parsing RPU file...
Editing active area offsets...
Final metadata length: 183837
Writing RPU file...
Done.

[Editing Video HDR Metadata]
Error.

[Fix Scenecuts]
EditConfig {
"mode": 0,
"remove_cmv4": false,
"remove_mapping": false,
"scene_cuts": {
"0-0": true
}
}
Parsing RPU file...
Editing scene cuts...
Final metadata length: 183837
Writing RPU file...
Done.

[Injecting RPU into stream]
Done.

[Muxing test into MKV Container]
Error.

== ERROR(S) ============================================================================================================

2 Error(s) during processing.

== LOGFILE END =========================================================================================================

2025/02/14 g 19:04:56.24

[AgentXXL]

Originally Posted by jl0292

I honestly did not meet these issues on 0.64.x; however, I could not find previous versions on GITHUB database.
So whether you can provide previous version or possibly update version will be fine, hope it is not too much request for you, thanks!!

The older releases are available on the MEGA site in the Older Versions folder. As for 65.3, you can download 65.2 from MEGA and then the 65.3 scripts from the Github site. Extract the MEGA archive to your destination folder and then extract the 65.3 scripts to that same folder to overwrite the 65.2 versions.

I've done this and so far it's working great. And once you use the Profile 8 Hybrid script with drag 'n drop support, you're unlikely to need the other scripts very often.

[lemaireus]

New as I am to Dolby Vision, I would appreciate an answer to what is presumably the most elementary question of all:

In Dolby Vision encodes in which the EL is excluded and only the RPU injected, does that RPU do any work at all without the FEL/MEL?

I'm sure an answer is hidden somewhere in this forum, but I haven't been able to find it and it would be great if you could please post a link or point me to the page. Thank you.

The second question is a little more elaborate so I shall post that in a separate message below.

[lemaireus]

Hi -QfG-, would you please help me with this one?:

Each time I try injecting an MEL/FEL into a cropped encode with, for example, 2.39:1 aspect ratio, I get the message that

a) VIDEO INPUT (all borders rightly with a zero value since I've cropped the top and bottom black bars in my encode) does not match with the RPU-EL.
b) And the EL INPUT which, rightly again, has borders (for example, LEFT=0 TOP=276 RIGHT=0 BOTTOM=276), since it's taken from a blu-ray, does not match with the video.
c) The borders of the FILE OUTPUT, however, match with video. Here is a screenshot of what I am talking about:



What am I supposed to in such a case?
a) Set "match L6 metadata to 'yes'?
b) Do I need to edit L6 metadata?
c) Do I need to 'EDIT ACTIVE AREA' and set the borders again? I am guessing that the answer to this question is a "No" because the cropped borders are correct.
d) Do nothing, because the encode is correctly cropped and the EL data is set for the active picture, that is, the EL data excludes the area with black bars?

I run into this problem only and only when I try to inject an EL into an encode, never when I leave the EL alone and inject only an RPU. Yes, I do set the correct crop values when extracting an RPU and an EL.

What would be the right way of injecting the EL in the scenario outlined above?

[PS: In case this is relevant: yes, I would like to retain DV Profile 7.6.]

[GodzilaAvenger]

Hi, I'm not -QfG- but I've used DDVT enough to think I can answer your questions.

First, MEL is simply the RPU, which is the dynamic metadata that tells your TV how to adjust its brightness and colors based on the scene. If you have FEL (i.e. EL + RPU) the EL is simply the layer added to the HDR10 stream to reconstruct the original 12-bit stream, i.e. EL = original 12-bit stream - 10-bit HDR10 stream.

As for your second question, a), b), do whatever you want with the L6 metadata, I don't think your TV cares what they are. c) and d), do D here because everything is correct, if somehow the auto-detected borders are wrong then you can use C to correct them.

I'm curious if your Profile 7.6 would even work though (assuming you have a player capable of showing it), because we had a discussion in this thread a few years ago about it and I remember being told that the order of frames in the NAL changes when encoding, which means if you add the EL into the encode the frames between the two streams don't match. Ask quietvoid though, he knows a lot more about this than I do.

[lemaireus]

Thank you, GodzillaAvenger, for providing exactly the kind of illuminating, helpful guidance I was looking for. Your reply settles all my queries nicely.

As for my decision to go with DV profile 7.6: I have a collection of 6000+ titles and I am in the process of re-encoding as many of them as have become available in 4k resolution. Currently there is no player that I know of which plays 7.6, nor do I have a 12-bit display. However, I do not wish to re-encode my entire library all over again as and when--if?--a player that supports 7.6 becomes available or when 12-bit displays become mainstream.

Until we get to the point where 7.6, 12-bit playback becomes mainstream--and maybe that might never happen--keeping 7.6 FEL gives me the option of running it through DDVT and converting to 8.1 right before I wish to watch the movie. That is, my library preserves 7.6 FEL in the hope that players and displays might support this format in the near future. Even if that never happens, I lose nothing: I simply run my FEL encode through DDVT before playback.

I wasn't aware of the change in the order of frames in the NAL when we re-encode and compress a blu-ray source. I wonder if there is any way in which I can verify that the FEL or the RPU I have injected back into the re-encode remains frame-by-frame-accurately-mapped to the source video. Any help from quietvoid or -QfG- or anyone else who knows the ins and outs of Dolby Vision better than I do would be much appreciated.

[GodzilaAvenger]

A few Bluray players like Sony's X800M2 can play FEL off the disk. But more recently, I know Ugoos AM6B+ with CoreELEC+PM4K can play full fat Profile 7.6 FEL straight from mkv. TVs are another story, but Dolby argues even on a 10-bit display FEL can help with banding. Personally, I think studios mostly use FEL to hide their shitty encoding. Case in point, Oppenheimer doesn't even have DV!

Your approach is interesting, I personally keep the remux if it has FEL (so as to not lose the EL) and an encoded version with P8.1 to stream over low bandwidths. It does take up space, but also, HDDs are relatively cheap.

Something that you may not know is that some of those FEL are fake. If the EL bandwidth is around 2 Mbps or less, the FEL is just a grey static image and you can discard it and only keep the RPU. Based on my experience out of the major studios that use DV (so not Disney and their cheap a**), WB and Sony generally include the fake FEL and only Universal and Paramount have a real FEL (if you look at their FEL bandwidth it's usually ~5-10 Mbps).