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

[Hellboy.]

Originally Posted by AngelGraves13

Is there anyway to know if the hybrid remux I made is incorrect? Like would the colors be off or something if I did it wrong?

Ok, so my UHD Remux of The Nun (2018) is 138932 frames and the Web-DL DV is 138910 so I would delay "+22" frames by my understanding and everything will line up correctly? Is that all there is to it? I wish the frame mismatch would be automatically adjusted if that's the case.

What about "matchL6 metadata"?? What's that for exactly and when would one need enable it?

There could be different frames at the end of the video.

[GodzilaAvenger]

Originally Posted by AngelGraves13

Is there anyway to know if the hybrid remux I made is incorrect? Like would the colors be off or something if I did it wrong?

Ok, so my UHD Remux of The Nun (2018) is 138932 frames and the Web-DL DV is 138910 so I would delay "+22" frames by my understanding and everything will line up correctly? Is that all there is to it? I wish the frame mismatch would be automatically adjusted if that's the case.

What about "matchL6 metadata"?? What's that for exactly and when would one need enable it?

Looking at the number of frames is not enough to figure out the sync, the web-dl may have a few additional frames of a logo or something at the beginning, while also having cut out a few seconds at the end. In your case the remux may only have extra frames at the end which means you should leave the delay at 0. This is very often the case which is why the mismatch is not automatically adjusted

The main thing DV does is dynamically adjust scene brightness, so if your RPU is out of sync with the base video layer you may see weird brightness changes slightly before or after scene cuts, depending on the scene of course.

One way to check your remux is to extract the RPU from it using the Demuxer script, and then using the Fileinfo script on it. This gives you all the scene cut frames in the RPU, which you can then use to check if they match the actual video.

I don't think the L6 data matters, if I remember correcrly that's what quietvoid said a while back in this thread.

[AngelGraves13]

Well that's confusing.

Ok...let's say I downloaded a DV Hybrid of a x265 rip and want to only save the DV layer that's already synced to a 4K UHD rip and inject it into a 4K UHD Remux. If the video is cropped but mine is standard 2160p, do I have to enable anything when saving the DV layer? It seems no matter what I select for Convert, or crop rpu it always says the RPU and Video don't match because of the video borders, but the file output says "match with video"

Filename = [Red Sparrow 4K (2018).mkv]
Video Info = [Resolution = 3840x2160] [Codec = HEVC-10Bit-YUV-4:2:0] [Frames = 201740] [FPS = 23.976]
HDR Info = [HDR]
Borders = [LEFT=0 px], [TOP=280 px], [RIGHT=0 px], [BOTTOM=280 px] [NOT MATCH WITH RPU]

== RPU INPUT ===========================================================================================================
Filename = [RPU.bin]
RPU Info = [DV Profile = 8] [CM Version = 2.9] [Frames = 201740]
Borders = [LEFT=0 px], [TOP=0 px], [RIGHT=0 px], [BOTTOM=0 px] [NOT MATCH WITH VIDEO]

== FILE OUTPUT =========================================================================================================
Filename = [Red Sparrow 4K (2018)_[BL+RPU].hevc]
RPU Info = [DV Profile = 8] [CM Version = 2.9] [Frames = 201740]
Borders = [LEFT=0 px], [TOP=280 px], [RIGHT=0 px], [BOTTOM=280 px] [MATCH WITH VIDEO]
Delay = [0 FRAMES]

So for the demuxer...just leaving everything untouched is fine?

1. SAVE HDR BL : [NO]
2. SAVE RPU : [YES]
3. CONVERT RPU : [LEAVE UNTOUCHED]
4. CROP RPU* : [NO] *Whenever the final result doesn't have letterboxed bars set to [YES].

[GodzilaAvenger]

The RPU contains border information for each frame, what's called L5 data. It doesn't matter if you change it when you are saving it using the demuxer or when injecting it using the injector. At the end of the day the L5 data of the injected RPU should match the borders of the video it's injected into.

In your example above, DDVT is telling you that the borders on the RPU (0) don't match the borders on the video (280), so it will rewrite the L5 data before injecting the RPU so that it matches the video. I generally save the RPU as is and apply necessary changes when injecting it.

I suggest looking at dovi_tool's documentation, which is what DDVT uses. Hopefully that can clear things up.

[AngelGraves13]

Thanks!

[Keemy]

Is there a version of this script for Macos or any equivalents?

[-QfG-]

Originally Posted by AngelGraves13

Filename = [Red Sparrow 4K (2018).mkv]
Video Info = [Resolution = 3840x2160] [Codec = HEVC-10Bit-YUV-4:2:0] [Frames = 201740] [FPS = 23.976]
HDR Info = [HDR]
Borders = [LEFT=0 px], [TOP=280 px], [RIGHT=0 px], [BOTTOM=280 px] [NOT MATCH WITH RPU]

NOT MATCH WITH RPU tells you, that the border entries in the RPU are incorrect.


== RPU INPUT ===========================================================================================================
Filename = [RPU.bin]
RPU Info = [DV Profile = 8] [CM Version = 2.9] [Frames = 201740]
Borders = [LEFT=0 px], [TOP=0 px], [RIGHT=0 px], [BOTTOM=0 px] [NOT MATCH WITH VIDEO]

NOT MATCH WITH VIDEO tells you, that the border entries in the RPU are incorrect.


== FILE OUTPUT =========================================================================================================
Filename = [Red Sparrow 4K (2018)_[BL+RPU].hevc]
RPU Info = [DV Profile = 8] [CM Version = 2.9] [Frames = 201740]
Borders = [LEFT=0 px], [TOP=280 px], [RIGHT=0 px], [BOTTOM=280 px] [MATCH WITH VIDEO]
Delay = [0 FRAMES]

Blue: This is your BL Layer (HDR Stream) and the discovered borders.
Red: This is the section from your RPU with the discovered borders.
Green: Your final settings for injecting with corrected borders in the RPU to match the HDR Stream

[lemaireus]

I cannot work with a command prompt interface, but wish to use DDVT tools to extract and later inject the Dolby Vision metadata in my x265 encodes of 4k blu-rays. However, each time I start DDVT_DEMUXER.cmd, the cmd window flashes "waiting for 30 seconds, press a key to continue . . .". Thereafter, when I drag and drop the MKV file onto the DDVT_DEMUXER.cmd window, the cmd window instantly disappears. In fact, all the DDVT_XXX.cmd files, with the exception of DDVT_HYBRID.cmd and DDVT_OPTIONS.cmd, perform the same disappearing act after 30 seconds, or the moment when I drag and drop an MKV file onto the cmd window. Here's how the cmd window looks before disappearing:



I am unable to figure out exactly what it is that I might be doing wrong. Any help would be much appreciated. Thank you.

[lemaireus]

Elementary, dear Watson, elementary. Some wonderful, generous, and precisely articulated help in PMs provided the correct diagnosis. I should have dragged the mkv file over the DDVT_DEMUXER.cmd script. Instead, I was double clicking DDVT_DEMUXER.cmd and dragging the file on the cmd window that opened thereafter. That is the first step out of the way; now to the next. Many thanks for helping out.

[lemaireus]

I succeeded in getting my first Ripbot encode with Dolby Vision metadata, all thanks to the wonderfully generous forum members walking me through in PMs and, in the Ripbot forum, thanks to Ryushin. Once my elementary but fundamental mistake became clear, the rest was a cakewalk.

Ryushin and my PM-ing friends, much, much gratitude.

[sk2316]

i'm newbie for ddvt tool
i would like to try this tool
1.sdr file with sharp picture
2.hdr10 file with worse picture
can i extract hdr10 meta and inject to sdr file?

[GodzilaAvenger]

DDVT is for working with Dolby Vision metadata and adding it to HDR10 or extracting it. It can't do what you want. I'm not sure if anything can. HDR10 uses the 10-bit BT.2020 colorspace whereas SDR uses the BT.709 colorspace.

[lemaireus]

Now that I have had the time to work with DDVT tools, I cannot be thankful enough: these scripts are exactly what so many of us had been missing since the introduction of Dolby Vision. Thank you so very much -QfG- and quietvoid (and that is a lovely nick!). You guys have done such awesome work that even an old dog like me, who has the will but no longer the energy to learn new tricks, can work effortlessly in extracting and injecting Dolby Vision into my encodes. Much, much gratitude for these incredibly useful and awesomely user-friendly batch scripts.

[sk2316]

Originally Posted by GodzilaAvenger

DDVT is for working with Dolby Vision metadata and adding it to HDR10 or extracting it. It can't do what you want. I'm not sure if anything can. HDR10 uses the 10-bit BT.2020 colorspace whereas SDR uses the BT.709 colorspace.

thank for quick reply
hdr10(not hdr10+) is not metadata? it's just have 10-bit BT.2020 colorspace

[GodzilaAvenger]

Technically speaking, it has some overall brightness metadata, but it is part of the whole HDR10 package, it's not something you can take out and put on an SDR video and call it a day. You can Google "how HDR works".

[sk2316]

Originally Posted by GodzilaAvenger

Technically speaking, it has some overall brightness metadata, but it is part of the whole HDR10 package, it's not something you can take out and put on an SDR video and call it a day. You can Google "how HDR works".

ok i got it
if i encode hdr10 file (SMPTE ST 2084) to h265 10 bits file
why output file information is not show "SMPTE ST 2084"
it's not hdr10? but color is like original file!

[GodzilaAvenger]

Bit depth isn't the defining factor, both HDR and SDR can be 10-bit. You are encoding to BT.709 colorspace, which is still SDR.

[sk2316]

Originally Posted by GodzilaAvenger

Bit depth isn't the defining factor, both HDR and SDR can be 10-bit. You are encoding to BT.709 colorspace, which is still SDR.

i forgot to tell you ,output file is BT2020
i don't understand why output file color is like original file
it should be waste out color?

[Z2697]

The HDR part of HDR10 is PQ (ST2084). BT.2020 is WCG part.

[sk2316]

Originally Posted by Z2697

The HDR part of HDR10 is PQ (ST2084). BT.2020 is WCG part.

ok i got it
if i encode hdr10 file (SMPTE ST 2084) to h265 10 bits file
why output file information is not show "SMPTE ST 2084"
it's not hdr10? but color is like original file!