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

[Emulgator]

BTW, that green plane means: all component pixel values are zero.
(this is what MPC returns when the illegal triplet Y=U=V=0 is rendered.
U=0 gives (illegal FullScale) Yellow, V=0 gives (illegal FullScale) Cyan, U,V=0 give (illegal FullScale) Green)

[SubSeven]

Hi everyone,

great tools and great discussions.
Unfortunately I wasn't successful to convert my MKV Hybrid Release (DV with HDR10 fallback) Profile 8 into an mp4 + DV format that can be played on my LG OLED TV.

Can someone help me here?

Thanks and best regards.

[SeeMoreDigital]

Originally Posted by SeeMoreDigital

Thanks for the reply GodzilaAvenger,

The thing that really annoys me (and probably everybody else) about Dolby Vision on 4K UHD disc is that the encodes are not all FEL. Indeed, I feel quite ripped off when I find out that the secondary stream on the disc has been encoded with a green video stream!

Well just for a laugh I did some tinkering this morning.

I added a 'MEL' secondary video stream from '2001: A Space Odyssey' to the 1982 release of 'Blade Runner' using TSmuxerGUI. Upon playback both my OPPO UDP-203 and 2016 LG television flagged a Dolby Vision signal. Suffice to say, the image was brighter and the colours were a bit off. But it just goes to show how easy it is to create 'fake' Dolby Vision content!

EDIT: Today I swapped the 'MEL' secondary video stream from '2001: A Space Odyssey' with 'James Bond: Casino Royale' and created a new 'Blade Runner' mux. Doing this saved around 2GB in overall file size and seemed to reduce the brightness of the image.

[lemaireus]

Originally Posted by Kuler087

Of course, it can bake FEL: Workflow 8-2-1
Dovi_scripts can do ANYthing that is DV-related and there's no such thing as ''fake FEL''
and all the modes/workflows are described on the main page:

Thank you, Kuler, for joining the conversation. You've always been hearteningly, illuminatingly helpful, and you are a veritable encyclopedia when it comes to matters related to Dolby Vision. I still have some nigging doubts left over with reference to "baking" (is "injecting" in DDVT tools an equivalent term? I ask because I've been using DDVT to "inject" MEL/FELs into re-encodes of blu-ray sources which, as the conversation here suggests, is not quite the right way of going about the process.), and perhaps it would be better if I raise those questions in the DoVi_Scripts forum in which you have already answered so many of my queries.

[Kuler087]

Originally Posted by lemaireus

Thank you, Kuler, for joining the conversation. You've always been hearteningly, illuminatingly helpful, and you are a veritable encyclopedia when it comes to matters related to Dolby Vision. I still have some nigging doubts left over with reference to "baking" (is "injecting" in DDVT tools an equivalent term? I ask because I've been using DDVT to "inject" MEL/FELs into re-encodes of blu-ray sources which, as the conversation here suggests, is not quite the right way of going about the process.), and perhaps it would be better if I raise those questions in the DoVi_Scripts forum in which you have already answered so many of my queries.

I don't know what DDVT does or can do, I never used it but baking FEL requires re-encoding the base layer with x265 or NVenc (+ dovi baker).

Injecting or muxing the EL back into the BL is NOT the same as baking it and will be wrong.

But yeah, you probably should ask DS questions in the DS thread. The process is easy though, just make sure you have avisynthplus installed and run workflow 8-2-1 with your P7 mkv rip. The output will be P8 with the FEL essence baked in the BL. You can control the encoding type( crf, 1-pass, 2-pass), bitrate and settings at lines 148-158

[lemaireus]

Originally Posted by Kuler087

I don't know what DDVT does or can do, I never used it but baking FEL requires re-encoding the base layer with x265 or NVenc (+ dovi baker).

Injecting or muxing the EL back into the BL is NOT the same as baking it and will be wrong.

But yeah, you probably should ask DS questions in the DS thread. The process is easy though, just make sure you have avisynthplus installed and run workflow 8-2-1 with your P7 mkv rip. The output will be P8 with the FEL essence baked in the BL. You can control the encoding type( crf, 1-pass, 2-pass), bitrate and settings at lines 148-158

Thank you, Kuler, for confirming what quietvoid and GodzillaAvenger had also pointed out regarding injecting EL into BL being the wrong way to go about the process of re-encoding. I'll take the questions about DoVi_Scripts to that forum, perhaps later, after I have played around long enough with DoVi_Scripts and become familiar with it. At the moment, I use it for EAC3 7.1 audio encodes of 7.1 TrueHD Atmos and DTS: X streams and it does a great job and, to my knowledge, is the only application that offers 7.1 audio encoding.

In the meantime, if someone here can tell us exactly what DDVT tools does when it "injects" an FEL/MEL into an x265 re-encode of the BL, that would help.

[GodzilaAvenger]

From the code, my understanding is that DDVT uses dovi_tool's inject-rpu function, which based on the documentation "Interleaves RPU NAL units between slices in an HEVC encoded bitstream."

[lemaireus]

Originally Posted by GodzilaAvenger

From the code, my understanding is that DDVT uses dovi_tool's inject-rpu function, which based on the documentation "Interleaves RPU NAL units between slices in an HEVC encoded bitstream."

Yes, it says as much when it injects the RPU. The question is about the FEL/MEL hevc file. Since DDVT offers the option to first demux and later inject the hevc FEL/MEL, one would think that it would/should take into account the problem that you, quietvoid, and Kuler refer to. If DDVT cannot sync the EL with the BL, then maybe the option to inject the EL should come with that cautionary note?

[GodzilaAvenger]

Perhaps. I guess it depends on the EL, if it is MEL (i.e. just RPU) then injecting it is probably fine.

[lemaireus]

I suppose the ones who compiled this wonderful, incredibly user-friendly set of tools are the only ones who can tell us what DDVT tools do when they "inject" an FEL hevc into an x265 re-encoded video from a blu-ray source.

[SeeMoreDigital]

Wrong topic

[leotwo]

The tool "can't find" the RPU in newly released web-dl videoes from Amazon Prime.

Mediainfo seems ok - showing there's and RPU and Profile 5.6, dolby vision profile 5 is found by the tool, but it somehow doesn't find the RPU or isn't able to extract it..

[pejok]

It is not possible to convert DV profile 5 only (it doesn't contain HDR10) into DV Profile 8.1.
DV Profile 8.1 needs HDR10 base. You cannot have DV Profile 8.1 only without HDR10 base.
In this case, you have to find HDR10 version of the video (even without DV layer) and inject/make hybrid with DV Profile 5 file.

Or did you try to do direct hybrid with HDR10 video and not to demux only the DV Profile 5?

Correct me if I am wrong.

// EDIT:
I know what you meant now.
I just tried to demux and convert DV 5 file from AMZN Prime, and everything worked.
Latest v0.65.3

SOURCE:


DEMUX SETTINGS:


DEMUX DONE:


EXPORTED FILE:

[Amateur]

Suddenly I'm getting a lot of errors with trying to use the Hybrid tool in the folder. After getting the error, I came back here to download an update but I still get the error.

From my pictures, the HDR file has HDR10+ and the DV file has Dolby Vision Profile 5.06. I drag-and-drop the files into the Hybrid window so it's not like I'm typing anything incorrectly.

The original DV mp4 file had some weirdness with the FPS so I muxed it into an MKV to see if that helped but it didn't.

I also notice that the screen says that it can turn HDR10+ into Dolby Vision 8 so I tried that as well and still got an error

What is going on?

[GodzilaAvenger]

Does the file path contain any special characters like ( & %?

[Amateur]

Originally Posted by GodzilaAvenger

Does the file path contain any special characters like ( & %?

Only a dash (-) or a period. But I've been doing files from the same folder for a little while now.

I tried moving it into a shorter file path with no characters at all. This time I watched the process and noticed this for the DV file. How does it have DV profile 5 but no RPU?

[Hansolo]

Hello!

I did some test injecting with original metadata and modified metadata (removing some frames), and i cant see any difference seeing the film.

I thought that using modified metadata, the image will flash or similar when changing scene but film goes well.
What is supposed to be?

Regards!

[Amateur]

Originally Posted by Amateur

Suddenly I'm getting a lot of errors with trying to use the Hybrid tool in the folder. After getting the error, I came back here to download an update but I still get the error.

From my pictures, the HDR file has HDR10+ and the DV file has Dolby Vision Profile 5.06. I drag-and-drop the files into the Hybrid window so it's not like I'm typing anything incorrectly.

The original DV mp4 file had some weirdness with the FPS so I muxed it into an MKV to see if that helped but it didn't.

I also notice that the screen says that it can turn HDR10+ into Dolby Vision 8 so I tried that as well and still got an error

What is going on?

My desktop happened to have v0.61.4 which still worked. Any ideas what my issue could be? As far as I remember, you should only have to unpack the rar into its own folder and everything works right? No other other installations are necessary?

[TempToday25]

Hi Kuler!

I believe I may have uncovered a bug or some unintended behavior. I am trying to create a Dolby Vision Profile 8.4 file from a higher-bitrate base HLG stream and an RPU from a Dolby Vision stream that has a lower-bitrate on it's own. Besides trying to create a best-of-both-worlds hybrid file, it's also the file that will be most compatible across the most platforms. The issue I'm running into is that the DDVT tool seems to force a "color_transfer" function value of "bt2020-10" when the original HLG file used "arib-std-b67". The reason that this is important is that this breaks HLG/HDR recognition on many devices (Infuse on Apple devices, VLC on Android and others). Is there a particular reason why DDVT pigeonholes HLG files to use this color transfer function? Here's the mediainfo of the original HLG file (using

ffprobe -v error -show_streams -of json -i file.mkv

:

"color_range": "tv",
"color_space": "bt2020nc",
"color_transfer": "arib-std-b67",
"color_primaries": "bt2020",
"chroma_location": "topleft",

And after running DDVT_Demuxer to convert a Profile 5 RPU to Profile 8.4 and then DDVT_Injector to interleave the RPU in the HLG file, here's what the mediainfo says:

"color_range": "tv",
"color_space": "bt2020nc",
"color_transfer": "bt2020-10",
"color_primaries": "bt2020",
"chroma_location": "topleft"

As you can see the "color_transfer" parameter changed. I've tried using ffmpeg to set the value of the parameter/metadata after the fact but to no avail. FFMPEG doesn't throw an error but the output of this command still shows the same "color_transfer" parameter value:

ffmpeg -i input.mp4 -map 0 -c copy -metadata:s:v:0 color_transfer="arib-std-b67" output.mkv

Can you help me with this please?

[GodzilaAvenger]

Just to clarify, Kuler is the maintainer of DoVi_Scripts, -QfG- is the maintainer of DDVT.

As for the issue you're describing, I think (based on the DDVT code) it is related to dovi_tool that handles the DV stuff inside DDVT, perhaps @quietvoid can provide some more info about this.