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

[von Suppé]

:thanks: -QfG-

[SeeMoreDigital]

As a feature request...

How about an: TS/M2TSTOMP4 muxing option?

[-QfG-]

-v0.42
*Updated dovi_tool to v1.5.1.
*Updated hdr10plus_tool to v1.2.2.
*Fixed bad Bottom entry after analysing in RPU Output in INJECTOR.

How about an: TS/M2TSTOMP4 muxing option?

i will see if i can implate them.

[-QfG-]

-v0.43
*INJECTOR supports EL.hevc file for creating DV Profile 7 Single Layer Files.
Copy EL.hevc to source video file directory.
If exist EL.hevc and RPU.bin the tool automatically uses EL.hevc.
*Fixed wrong FPS Bug in REMOVER.
*Minor Bugfixes.

[SeeMoreDigital]

i will see if i can implate them.Many thanks...

[alexflin]

Hi, I'm testing this tool with a file to see if I'm able to add the DV to a HDR video, first I use DDVT_DEMUXER to extract the RPU.bin and then I inject with the DDVT_INJECTOR the RPU.bin to another file but i'm stuck in this step

https://i.ibb.co/17YjbR2/image.png (https://ibb.co/HBL3XGg)

[cool advertise]

Hi, I'm testing this tool with a file to see if I'm able to add the DV to a HDR video, first I use DDVT_DEMUXER to extract the RPU.bin and then I inject with the DDVT_INJECTOR the RPU.bin to another file but i'm stuck in this step

It's simple.
From the screenshot, your video is sdr (uncropped) and not hdr.
At this point if you want dolby vision to be muxed into an mkv file enable option 3 (mux stream in mkv) (by pressing 3), if you don't want to mux it don't touch it instead, and press S (Start) to begin the process of injecting dolby vision into your file.
If your rpu is a profile 8, you will get a dolby vision profile 8.2 (SDR backwards compatible) file, i.e. on dolby vision devices it plays in dolby vision, otherwise in SDR.
If your device does not play dolby vision in mkv, using the mp4 container instead of mkv may solve this.
The video where the rpu comes from and the video where the rpu is injected must be the same (the destination video can be an encoding of the original video), otherwise there is no logic in injecting the rpu on a different video if not to test the procedure.

[von Suppé]

I'm getting an error-window called "mkvextract.exe - Entry Point Not Found".

It says: "The procedure entry point CreatEventA could not be located in the dynamic link library api-ms-win-core-synch-l1-2-0.dll"

Please advice?

[alexflin]

It's simple.
From the screenshot, your video is sdr (uncropped) and not hdr.
At this point if you want dolby vision to be muxed into an mkv file enable option 3 (mux stream in mkv) (by pressing 3), if you don't want to mux it don't touch it instead, and press S (Start) to begin the process of injecting dolby vision into your file.
If your rpu is a profile 8, you will get a dolby vision profile 8.2 (SDR backwards compatible) file, i.e. on dolby vision devices it plays in dolby vision, otherwise in SDR.
If your device does not play dolby vision in mkv, using the mp4 container instead of mkv may solve this.
The video where the rpu comes from and the video where the rpu is injected must be the same (the destination video can be an encoding of the original video), otherwise there is no logic in injecting the rpu on a different video if not to test the procedure.

Ok, thanks, but what about the borders error, should I ignore it?.

The videos are not the same, I downloaded two versions from the internet one HDR only and the other DV.

https://i.ibb.co/pncNrZC/image.png (https://ibb.co/Fn2cqJG)

Also, I tested extracting the RPU from an MP4 but the script gets stuck in this step

https://i.ibb.co/BLmtTfM/image.png (https://ibb.co/F69K8hT)

[cool advertise]

Ok, thanks, but what about the borders error, should I ignore it?.

The videos are not the same, I downloaded two versions from the internet one HDR only and the other DV.

Generally, an hdr video will have this wording in mediainfo
HDR format : SMPTE ST 2086, HDR10 compatible
and this
Mastering display color primaries : Display P3 (or BT.2020)

Your hdr file does not have them, but I think it is a hdr video anyway.
Even the tool screenshot misled me by reporting:
HDR Info [n.a.].
I'm thinking how to help you, if I find an answer I'll tell you.

[cool advertise]

Your dolby vision video is a profile 5.
I've never used it, always used profile 8 or converted profile 7 to 8 and always in mkv (never mp4).
You could maybe try muxing it to mkv instead of mp4 and try injecting it again, or, convert rpu profile 5 to 8 and try injecting it again.
The tool fixes the borders automatically, it's not an error with the borders, it says that the source video has 276px above and 276px below black bands, while the rpu is cropped (0px), but normally it fixes it automatically when you inject the rpu.

[von Suppé]

What I find odd is that both videos are 3840x2160 and the native RPU shows no borders, where the video to be injected has 276px borders. Is it possible that the DV file is a totally different, "fullframe, zoomed in" 16:9 version?
Or does the DV file have borders but RPU is then flawed?

[alexflin]

What I find odd is that both videos are 3840x2160 and the native RPU shows no borders, where the video to be injected has 276px borders. Is it possible that the DV file is a totally different, "fullframe, zoomed in" 16:9 version?

Both videos have same aspect ratio and I think are the same source but one HDR and the another one with DV

https://i.ibb.co/SJ37kGk/image.png (https://ibb.co/vDjvNRN)

Or does the DV file have borders but RPU is then flawed?

No idea

[-QfG-]

Hi, I'm testing this tool with a file to see if I'm able to add the DV to a HDR video, first I use DDVT_DEMUXER to extract the RPU.bin and then I inject with the DDVT_INJECTOR the RPU.bin to another file but i'm stuck in this step

https://i.ibb.co/17YjbR2/image.png (https://ibb.co/HBL3XGg)

It looks so, that this video is a SDR Video. If u implant the RPU.bin into this video you create a 8.2 DV Profile file. If i understand quitvoid correct, his dovi_tool supports Only Profile 8.1 (HDR+RPU), not 8.2 (SDR+RPU) or 8.4 (HLG+RPU). If u 100% sure that this video is an HDR Video, use mkvtoolnix v67 and Remux the video, or use the raw hevc stream.

Both videos have same aspect ratio and I think are the same source but one HDR and the another one with DV

Many original RPUs in DV Profile 5 files have no borders set. In any thread quietvoid saids that is recommended to set this border entries. If your target video is cropped (You can ignore the AR) and have no black bars, set all border entries to 0 (0,0,0,0). You can ignore all borders or resolutions from the source video. Only interesting point ist the Delay, both videos must be frame identical.

[alexflin]

And it's possible to use the RPU to create a bluray structure?

[-QfG-]

No. For BD Structure you need Movie.mkv/hevc and EL.hevc. Than mux a Profile 7 Single Layer File and create an ISO file with TSMuxer.

[alexflin]

No. For BD Structure you need Movie.mkv/hevc and EL.hevc. Than mux a Profile 7 Single Layer File and create an ISO file with TSMuxer.

EL.hevc ? Sorry, I don't get it. What is that?

[cool advertise]

It looks so, that this video is a SDR Video.
If i understand quitvoid correct, his dovi_tool supports Only Profile 8.1 (HDR+RPU), not 8.2 (SDR+RPU) or 8.4 (HLG+RPU).
Dovi tool injection support profile 8.1 and 8.2, I have just tested it.
I have not tested profile 8.4.
And by the way, I could be wrong, but I think "alexflin" file is HDR and not SDR, as it contains this text in the mediainfo report:
Colour primaries : BT.2020
Transfer characteristics : PQ
Matrix coefficients : BT.2020 non-constant

So if you use the mkv container and convert profile 5 to 8, and then inject the RPU, you'll get dolby vision profile 8.1, in case the video is HDR, or dolby vision profile 8.2 in case the video is SDR.

If the file is SDR mediainfo should show something like this:
HDR format : Dolby Vision, Version 1.0, dvhe.08.03, BL+RPU, SDR compatible

If the file is HDR mediainfo should show something like this:
HDR format : Dolby Vision, Version 1.0, dvhe.08.06, BL+RPU, HDR10 compatible / SMPTE ST 2086, HDR10 compatible

EL.hevc ? Sorry, I don't get it. What is that?
EL stands for enhancement layer.
The enhancement layer can be full enhancement layer (FEL) or minimum enhancement layer (MEL).
It is present in dolby vision profile 7 and commonly in Dolby Vision UHD blurays.

[-QfG-]

EL.hevc ? Sorry, I don't get it. What is that?

A UHD BD is strictly based on Dolby Vision Profile 7 Double Layer.
You have the Main HDR Video Layer (called [B]ase [L]ayer), a 1080p Dolby Vision Video Layer (called [E]nhanced [L]ayer). You need this layers for creating a P7 UHD compatible BD Structur.

BL.hevc = HDR Base Layer.
EL.hevc = DV Enhanced Layer (FEL/MEL).
RPU.bin = DV Metadata.

[alexflin]

Ok, now I understand, so I think is not possible to get the EL.hevc with the RPU.bin. I'm creating bluray uhd for my private tv shows collection but actually they are HDR only, I was thinking to use this tool to add the DV but now I think is not possible without the EL.hevc

[zzreel]

Is there a good solution for identifying how many frames an alternative source RPU may be off by?

I've used VirtualDub64 to see the end frame number but some video sources don't even open in that haha, plus, we'd want a side-by-side or even overlay frame comparison between 2 source video files. How do others do it?

[cool advertise]

Is there a good solution for identifying how many frames an alternative source RPU may be off by?
It is not an official procedure, but
"dovi_tool.exe" info -i "RPU.bin" -f 999999
executed from the command line reports the number of frames contained in a rpu.bin file, returning an error.

[zzreel]

It is not an official procedure, but
"dovi_tool.exe" info -i "RPU.bin" -f 999999
executed from the command line reports the number of frames contained in a rpu.bin file, returning an error.

Any way to match up the frames tho when they don't match? People are definitely doing it somehow, but I've yet to find a good solution.

[cool advertise]

Any way to match up the frames tho when they don't match? People are definitely doing it somehow, but I've yet to find a good solution.

MPC (Media Player Classic), allows you to open as many videos as you like and move to an exact, precise frame to compare them.
dovi_tool injection, if the video has for example 10000 frames and RPU.bin 9000, it will paste the first 1000 frames metadata after 9000 again, to get to 10000.
If you mean editing the rpu, changing the order of the frames, I don't know, I've never done it.

[-QfG-]

Any way to match up the frames tho when they don't match? People are definitely doing it somehow, but I've yet to find a good solution.

i make a video of one way for check frame differences:
https://www.youtube.com/watch?v=gVZL1vwXFAg

You found MeGui here:
https://sourceforge.net/projects/megui/

executed from the command line reports the number of frames contained in a rpu.bin file, returning an error.

Nice idea.

Ok, now I understand, so I think is not possible to get the EL.hevc with the RPU.bin. I'm creating bluray uhd for my private tv shows collection but actually they are HDR only, I was thinking to use this tool to add the DV but now I think is not possible without the EL.hevc

I build some hybrid Custom UHDs for me. In most cases the ITA Eagle Pictures UHDs have a better picture as the UK StudioAnal UHDs. But no DV. Both Versions from the same Master, so i demux the EL Layer from the UK UHD and mux that Layer in the ITA UHD. But both movies must be frame identical, i know no way to delay a EL.hevc file. If u encode an P7 Movie you can crop the RPU in the EL.hevc and mux this with the Base Layer. Works fine on Shield 2019 pro / Zidoo Z10pro. The INJECTOR in v0.43 can crop RPUs within EL.hevc.

[von Suppé]

I'm getting an error-window called "mkvextract.exe - Entry Point Not Found".

It says: "The procedure entry point CreatEventA could not be located in the dynamic link library api-ms-win-core-synch-l1-2-0.dll"

Please advice?

After checking and rechecking I found out when replacing mkvextract.exe in the tools folder with another version things are working again.
Am I right to assume that this has to do with versions of Mosu's mkv software not running on Windows 7 anymore?

[rwill]

Any way to match up the frames tho when they don't match? People are definitely doing it somehow, but I've yet to find a good solution.

Have you tried to align the RPUs scene_refresh_flag=1 to scene changes in the video ?

[fkid]

@-QfG- I am also slightly confused by the automatic Injector values for crop/borders when the video file is full-frame. Is this to save on storage as the borders do not require metadata and thus are cropped off the RPU.bin when injecting? Please confirm in this situation just to leave all settings as is and Inject into .mkv ok? Thank you!!

https://i.ibb.co/ygmWt07/Screenshot-2022-05-12-132054.png (https://ibb.co/RQGzf2d)

[-QfG-]

The entries are correct.

VIDEO INPUT = 120px on Top and Bottom.
RPU INPUT = set in RPU now to 0,0,0,0 (it looks so, that the source DV file is a cropped video)
RPU OUTPUT = must be have the same values how VIDEO INPUT.

[fkid]

The entries are correct.

VIDEO INPUT = 120px on Top and Bottom.
RPU INPUT = set in RPU now to 0,0,0,0 (it looks so, that the source DV file is a cropped video)
RPU OUTPUT = must be have the same values how VIDEO INPUT.

But, the original DV file from which I demuxed the RPU.bin was also full-frame, NOT cropped? That is why I am confused. All files involved are 2160px in height. I guess in this case, if I DISCARD and leave UNTOUCHED, it wouldn't impact the final output file, as the 120px on top and bottom in the file are just black space? Just want to make sure the crop doesn't actually impact the final file when it combines the HDR and DV metadata and the file is 2160px in height. Thanks for the support.

[-QfG-]

Sometimes you have wrong values in original DV5 Profile. Or nothing CROP Values in the RPU. Also in original WEB-DLs. In most cases it works with 0,0,0,0 on Full Frame videos with borders. But it doesnt work with Crop values in RPU, but cropped videos without black borders. Shield 2019 pro cuts in the last fall the cropped video. If you have an Imax source with changing AR, use simply 0,0,0,0. This works fine with Shield Pro 2019 / Zidoo Z10pro.

[fkid]

Sometimes you have wrong values in original DV5 Profile. Or nothing CROP Values in the RPU. Also in original WEB-DLs. In most cases it works with 0,0,0,0 on Full Frame videos with borders. But it doesnt work with Crop values in RPU, but cropped videos without black borders. Shield 2019 pro cuts in the last fall the cropped video. If you have an Imax source with changing AR, use simply 0,0,0,0. This works fine with Shield Pro 2019 / Zidoo Z10pro.

Okay, it seems to make sense. Worst case, I can always try to watch and see if it looks good, and re-inject if something is wrong. Cheers!

[ShortKatz]

Interesting tool. Is this also available for Mac? I have seen that all the tool inside the "tools" folder are at least available for Mac (I am not sure about sfk, because couldn't find the GitHub page for this),

[korzh_yura]

I have an issue with my player - m9702 ( oppo 203 clone)

Almost all cropped 2160 DV MP4 videos start to freeze after 3 minutes of normal playing

Also - command line is not my strong skill

So can yоu please tell me what should i do step by step to try to demux this video?

[korzh_yura]

I dont seeany help file inside :(

[fkid]

@-QfG-

What do you make of this error when converting HDR10+ to DV?

UPDATE: I am getting this same error even when I forgo the DDVT_DEMUXER.cmd completely and try to use quietvoid's tools manually. I reached out to them about this possible bug and provided the .json file. I'll let you know if I figure anything out, but I don't think it's DDVT scripts at this point. If you're curious, .json is available @ https://mega.nz/file/8t4G0KSK#pAZfekDaOAoltcLOIp1iR2-m8wO1QBnqKCVYJ5uvFFY

Please wait. Extracting HDR10+ Metadata...
Reading parsed dynamic metadata... Done.
Reordering metadata... Done.
Generating and writing metadata to JSON file... Done.
Done.

Please wait. Prefetching HDR10+ Metadata...
Done.

Please wait. Generate RPU.bin...
Error: invalid type: floating point `0.025`, expected u16 at line 6 column 44
Error during RPU.bin creating.

Please wait. Cleaning and Moving files ...
Deleting Temp File - Done.
Deleting JSon Script - Done.
Deleting JSon Script - Done.

SOME Operations failed.

This happens at the end of particular HDR10+ metadata conversion I have tried, after it extracts successfully and does reordering (which takes longer than usual seemingly). If it matters, this .json file turned out to be almost 160MB, and I can provide it if it that helps. If it matters, it happens in both v0.41a and v0.43. Below is the Mediainfo metadata for the input video file, for reference.

General
Format : Matroska
Format version : Version 4
File size : 12.5 GiB
Duration : 1 h 55 min
Overall bit rate : 15.5 Mb/s
Encoded date : UTC 2021-04-14 16:56:20
Writing application : mkvmerge v54.0.0 ('F Maj Pixie') 64-bit
Writing library : libebml v1.4.2 + libmatroska v1.6.3

Video
ID : 1
Format : HEVC
Format/Info : High Efficiency Video Coding
Format profile : Main 10@L5@Main
HDR format : SMPTE ST 2094 App 4, Version 1, HDR10+ Profile B compatible
Codec ID : V_MPEGH/ISO/HEVC
Duration : 1 h 55 min
Bit rate : 14.9 Mb/s
Width : 3 840 pixels
Height : 1 600 pixels
Display aspect ratio : 2.40:1
Frame rate mode : Constant
Frame rate : 23.976 (24000/1001) FPS
Color space : YUV
Chroma subsampling : 4:2:0
Bit depth : 10 bits
Bits/(Pixel*Frame) : 0.101
Stream size : 12.0 GiB (96%)
Default : Yes
Forced : No
Color range : Limited
Color primaries : BT.2020
Transfer characteristics : PQ
Matrix coefficients : BT.2020 non-constant
Mastering display color primaries : Display P3
Mastering display luminance : min: 0.0250 cd/m2, max: 20000 cd/m2
Maximum Content Light Level : 2238 cd/m2
Maximum Frame-Average Light Level : 236 cd/m2

Audio
ID : 2
Format : E-AC-3
Format/Info : Enhanced AC-3
Commercial name : Dolby Digital Plus
Codec ID : A_EAC3
Duration : 1 h 55 min
Bit rate mode : Constant
Bit rate : 640 kb/s
Channel(s) : 6 channels
Channel layout : L R C LFE Ls Rs
Sampling rate : 48.0 kHz
Frame rate : 31.250 FPS (1536 SPF)
Compression mode : Lossy
Stream size : 527 MiB (4%)
Language : Korean
Service kind : Complete Main
Default : Yes
Forced : No

Text
ID : 3
Format : UTF-8
Codec ID : S_TEXT/UTF8
Codec ID/Info : UTF-8 Plain Text
Duration : 1 h 54 min
Bit rate : 26 b/s
Count of elements : 948
Stream size : 22.0 KiB (0%)
Title : SDH
Language : English
Default : No
Forced : No

Menu
00:00:00.000 : Scene 1
00:00:08.000 : Scene 2
00:00:35.000 : Title Sequence
00:00:40.000 : Scene 4
00:08:10.000 : Scene 5
00:16:09.000 : Scene 6
00:23:12.000 : Scene 7
00:31:11.000 : Scene 8
00:37:58.000 : Scene 9
00:46:18.000 : Scene 10
00:54:08.000 : Scene 11
01:00:06.000 : Scene 12
01:07:18.000 : Scene 13
01:15:12.000 : Scene 14
01:22:14.000 : Scene 15
01:29:12.000 : Scene 16
01:36:58.000 : Scene 17
01:42:09.000 : Scene 18
01:51:35.000 : End Credits


Thank you kindly. :)

[-QfG-]

I never seen a 160 MB HDR JSon metadata file before. This "error" comes by some movies for me, too. In all cases it was a Profile B file. I have no solution for this yet.

[quietvoid]

@-QfG-
UPDATE: I am getting this same error even when I forgo the DDVT_DEMUXER.cmd completely and try to use quietvoid's tools manually. I reached out to them about this possible bug and provided the .json file. I'll let you know if I figure anything out, but I don't think it's DDVT scripts at this point. If you're curious, .json is available @ https://mega.nz/file/8t4G0KSK#pAZfekDaOAoltcLOIp1iR2-m8wO1QBnqKCVYJ5uvFFY


It's not a dovi_tool bug. Either user error or the script's fault.
To me it looks like the generate config JSON (not the HDR10+ one) has wrong L6 metadata, because all the values are supposed to be integers.

Your source file has weird mastering display metadata, and it's invalid.

[fkid]

Thanks for the replies guys. I suppose it must be just the embedded HDR10+ metadata values in this particular input file (source) caused a bad companion config .json to be generated, but the actual HDR10+ .json may be fine. You are right @quietvoid: I did create the config .json file myself, using values derived from the MediaInfo metadata (similar to DDVT script) and can now see the integer error comes from the use of Mastering display luminance: min: 0.0250 cd/m2, max: 20000 cd/m2 in. Now when I set minimum to 0, it gave different error that max value was 20000 but should be 10000 max, so that one seems invalid too.

In the end, I just tried changing the config .json file to have min as 0 and max as 10000 and the new RPU.bin generated okay. I now re-injected that back into the original file and it plays great on my Shield Pro 2019 and TV displays the Dolby Vision metadata! :D Looking at DDVT_DEMUXER script, I guess 0.0250 should actually be converted to MinDML of 250? I re-did my final file with that value now, although wondering why the math is done that way for MinDML but MaxDML is kept as is?

@-QfG-, maybe you could consider modifying DDVT_DEMUXER.cmd to detect the 0.0250 'floating point' value for min luminance also and convert to correct integer value (I think you already have similar code for 3 values like below) and also keep the maximum luminance from going over 10000? I think that might solve this issue for those few, pesky source files.

if "%MinDML%"=="0.0250" set "MinDML=250" ???
if "%MinDML%"=="0.0050" set "MinDML=50"
if "%MinDML%"=="0.0010" set "MinDML=10"
if "%MinDML%"=="0.0001" set "MinDML=1"

[-QfG-]

and can now see the integer error comes from the use of Mastering display luminance: min: 0.0250 cd/m2, max: 20000 cd/m2 in. Now when I set minimum to 0, it gave different error that max value was 20000 but should be 10000 max, so that one seems invalid too.

Ah, the Master luminances forced in the batch file, because i can't read them correctly, i will add these settings in the next update. I will take a look for a solution for cutting the string correctly.

[fkid]

Ah, the Master luminances forced in the batch file, because i can't read them correctly, i will add these settings in the next update. I will take a look for a solution for cutting the string correctly.

Sounds great! Thanks for the continued hard work on this tool and your scripts. Glad we were able to figure out this issue I had, and thanks to quietvoid for guidance there too. Respect from Canada! :)

[-QfG-]

-v0.44
*Fixed wrong Min Luminance Bug in DEMUXER by HDR10+ to DV Conversion.

I hope now all works correctly.

[fkid]

-v0.44
*Fixed wrong Min Luminance Bug in DEMUXER by HDR10+ to DV Conversion.

I hope now all works correctly.

I think a small typo in the new DEMUXER.cmd

if "%MaxDML%"=="" set "MinDML=1"

I think supposed to be MinDML in that line in both cases?

Cheers. :)

[-QfG-]

Correct, my fault. %MinDML% is correct.

Please redownload v0.44 is it fixed now. Thanks.

[-QfG-]

-v0.45
*Added DoVi Profile 8.4 HLG Conversion in DEMUXER
*Fixed bad Frame choice in FRAMEINFO
*Updated mkvtoolnix to v 68.0.0.0.

[MoonKnight]

Hello

thank u for DDVT

I have one question : How do I trim for an example the first 128 frames of an HDR10Plus.json ?? I need to do that for some resynch

[-QfG-]

I think you must edit the Json manually. There is no option in the hdr10plus_tool from quietvoid. The only solution ist to change hdr10+ to DV, than you can edit the Delay of the RPU.

[panni]

Hey, thank you for this great tool. Do you have any plans to support smart batch operations (multiple operations at a time, multiple files at a time)?

BTW, typo in line 342 of DDVT_INJECTOR.cmd: `if "%P4Extract%%MUXINMP4%%HDR10P_exist%"` should be `if "%MP4Extract%%MUXINMP4%%HDR10P_exist%"`.

[-QfG-]

you can use multiple instances, you must only choose different source directories for each operation.

[-QfG-]

-v0.46
*Shows RPU/EL Layer Information in Injector (Profile, CM Version, Frames)
*Updated dovi_tool to v1.5.4.