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

[quietvoid]

The issue is most likely that the original MKV had the transfer set in the container.

[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!

Nobody cant tell me what will happen when injecting differente metada?
:(

[GodzilaAvenger]

You've given us very little information, as the answer to your question is completely dependent on the DV RPU, and your eyes. E.g. if brightness across your RPU is mostly uniform, there is a high chance you won't notice the difference. If there is e.g. one scene that has 10 nits brightness and the next 1000 nits or the other way around and you drop a few frames, you MAY notice weird brightness changes for a brief period before a scene cut.

[Hansolo]

You've given us very little information, as the answer to your question is completely dependent on the DV RPU, and your eyes. E.g. if brightness across your RPU is mostly uniform, there is a high chance you won't notice the difference. If there is e.g. one scene that has 10 nits brightness and the next 1000 nits or the other way around and you drop a few frames, you MAY notice weird brightness changes for a brief period before a scene cut.

Thanks for your reply!

This is the info regarding the file...
ídeo
ID : 1
Formato : HEVC
Formato/Info : High Efficiency Video Coding
Formato del perfil : Main 10@L5@High
HDR format : SMPTE ST 2094 App 4, Version 1, HDR10+ Profile B compatible
ID códec : V_MPEGH/ISO/HEVC
Duración : 1 h 48 min
Tasa de bits : 24,5 Mb/s
Ancho : 3 840 píxeles
Alto : 1 634 píxeles
Relación de aspecto : 2,35:1
Modo velocidad fotogramas : Constante
Velocidad de fotogramas : 23,976 FPS
Espacio de color : YUV
Submuestreo croma : 4:2:0 (Type 2)
Profundidad bits : 10 bits
Bits/(píxel*fotograma) : 0.163
Tamaño de pista : 18,6 GiB (77%)
Título : The Thing
Idioma : Español
Default : Sí
Forced : No
Rango de color : Limited
Colores primarios : BT.2020
Características transferencia : PQ
Coeficientes matriz : BT.2020 non-constant
Principios color monitor masterización : Display P3
Luminancia monitor masterización : min: 0.0050 cd/m2, max: 1000 cd/m2
Nivel ligero contenido máximo : 1034 cd/m2
Nivel ligero fotograma medio máximo : 794 cd/m2

I dont know what you told me about RPU.
The last test i did was to remove 60 frames from the metadata.json and injected into a 1minute clip with brighter scenes and darker scenes for seeing the difference as you told me, but i dont see anything.

Im starting to thing that the hdr10+ is a fake. Not sure, so i upload the 1minute clip with original metadata, not modified.
https://mega.nz/file/201QnYZD#HQd9z8-kFHJ47HpgsCDjOkiOirKi7SF8JFs9X96RGR0
Maybe you can tell me anything.
Regards!

[Amateur]

Is it possible to run the Hybrid tool to work in a batch to make hybrids from TV episodes? One folder of HDR files and another folder of DV files?

You can use the tool in posted above, very simple instructions. You don't need to do much for the file you have. It is more complicated to transform HDR layer into DV readable, but here you already have the DV layer baked into.

This is possible? I've had a couple instances where the Dolby stream is higher bitrate than HDR and wondered if I could add the HDR info to the Dolby stream.

[GodzilaAvenger]

Thanks for your reply!

This is the info regarding the file...
ídeo
ID : 1
Formato : HEVC
Formato/Info : High Efficiency Video Coding
Formato del perfil : Main 10@L5@High
HDR format : SMPTE ST 2094 App 4, Version 1, HDR10+ Profile B compatible
ID códec : V_MPEGH/ISO/HEVC
Duración : 1 h 48 min
Tasa de bits : 24,5 Mb/s
Ancho : 3 840 píxeles
Alto : 1 634 píxeles
Relación de aspecto : 2,35:1
Modo velocidad fotogramas : Constante
Velocidad de fotogramas : 23,976 FPS
Espacio de color : YUV
Submuestreo croma : 4:2:0 (Type 2)
Profundidad bits : 10 bits
Bits/(píxel*fotograma) : 0.163
Tamaño de pista : 18,6 GiB (77%)
Título : The Thing
Idioma : Español
Default : Sí
Forced : No
Rango de color : Limited
Colores primarios : BT.2020
Características transferencia : PQ
Coeficientes matriz : BT.2020 non-constant
Principios color monitor masterización : Display P3
Luminancia monitor masterización : min: 0.0050 cd/m2, max: 1000 cd/m2
Nivel ligero contenido máximo : 1034 cd/m2
Nivel ligero fotograma medio máximo : 794 cd/m2

I dont know what you told me about RPU.
The last test i did was to remove 60 frames from the metadata.json and injected into a 1minute clip with brighter scenes and darker scenes for seeing the difference as you told me, but i dont see anything.

Im starting to thing that the hdr10+ is a fake. Not sure, so i upload the 1minute clip with original metadata, not modified.
https://mega.nz/file/201QnYZD#HQd9z8-kFHJ47HpgsCDjOkiOirKi7SF8JFs9X96RGR0
Maybe you can tell me anything.
Regards!

I thought you were talking about Dolby Vision, the RPU I was refering to was for that.

For your case, go into the tools folder of DDVT on cmd or Powershell and run

hdr10plus_tool plot metadata.json

This will plot the min/avg/max brightness for each frame and should give you an idea of what the metadata contains.

[hidef_rec]

My very small contribution to helping less techie DV/HDR fans use this great tool to make hybrid videos:
https://youtu.be/FMqhb7ppGWY

[asarian]

I'm getting the following error on a movie with the following characteristics: HDR Info = [HDR10, Dolby Vision Profile 7 (FEL)]. I am trying to create an RPU file:

Please wait. Demuxing EL...
frame=197674 fps=2047 q=-1.0 Lsize=49958925KiB time=02:17:24.52 bitrate=49640.6kbits/s speed=85.4x
EL Done.

Please wait. Demuxing DV Reference Processing Unit...
Error: No frames parsed!
Done.

[Amateur]

My very small contribution to helping less techie DV/HDR fans use this great tool to make hybrid videos:
https://youtu.be/FMqhb7ppGWY

The other guy hasn't replied but maybe you can help me with this

http://forum.doom9.org/showthread.php?p=2017261#post2017261

I know how to convert DV5 to DV8 and inject that into an HDR stream. But the above post that I quoted makes it sound like you can use a DV stream as your base and inject the HDR info into that maybe. Am I understanding that correctly?

Also, are there any drawbacks in creating DV info from an HDR10+ file? Is that considered fake DV and not quality?

[GodzilaAvenger]

The color space of the video stream of a P5 DV is different from P8. P8 is backward compatible with HDR, P5 is not, and injecting DV metadata will not change that.

[asarian]

I'm getting the following error on a movie with the following characteristics: HDR Info = [HDR10, Dolby Vision Profile 7 (FEL)]. I am trying to create an RPU file:

Please wait. Demuxing EL...
frame=197674 fps=2047 q=-1.0 Lsize=49958925KiB time=02:17:24.52 bitrate=49640.6kbits/s speed=85.4x
EL Done.

Please wait. Demuxing DV Reference Processing Unit...
Error: No frames parsed!
Done.

Anyone have an answer to this? Thanks.

[Amateur]

A while ago, I had shared a mass convert script adapted from yours so that it would do all files in a given folder sequentially...

Is it possible to apply this method to the Hybrid feature of the tool using two folders? When it first asks for the HDR file, a folder can be dropped into the window (hdr1.mkv, hdr2.mkv, hdr3.mkv). Then when it asks for the DV file, a second folder can be dropped into the window (dv1.mkv, dv2.mkv, dv3.mkv). Then the tool will sequentially convert the DV profile to 8.1 and inject into the HDR file automatically? (The automatic starting of each process might also need to be changed because it currently needs user input to type S to start)

This would really help me for TV series.

Thank you

[ed_co]

Hello guys,

I am fairly new with adding DV/HDR10+ to encodes (I did just around a dozen now). I wanna thank the creator/s of the scripts for such a nice tool.

I have 2 files of the same movie.

The file 1.mkv:
- HDR10. Mediainfo:
SMPTE ST 2086, HDR10 compatible
- Size/quality is good. A little bit more yellowish tinted than the 2.mkv
- Resolution: 3840x1608
- Framerate: 23.976
- Has a delay of 198 frames respecting the following movie file

The file 2.mkv:
- HDR10+, DV. Mediainfo:
Dolby Vision, Version 1.0, Profile 8.1, dvhe.08.06, BL+RPU, no metadata compression, HDR10 compatible / SMPTE ST 2086, Version HDR10, HDR10 compatible / SMPTE ST 2094 App 4, Version HDR10+ Profile B, HDR10+ Profile B compatible
- Size is the double.
- Resolution: 3840x1606 (2 pixels less in height than the previous one)
- Framerate: 23.976

That 2 pixels height difference is weird. There are no black bars to any of them, and is imperceptible to know what the exact mismatch is. I don't know if it is:
- A crop thing: one was cropped more than the other.
- Aspect ratio management: they were cropped the same but the ratio was modified.
- Maybe the two movies, as they are probably from different releases of different countries, they came cropped differently.
In any case I don't know which of the three possibilities is.

As you can guess, I want to put DV and HDR10+ of 2.mkv in 1.mkv, so I proceeded in the following way:

1) Extract DV and HDR10+ from 2.mkv, steps:
- Drag and drop 2.mkv to DDVT_DEMUXER.cmd
It found: HDR Info = [HDR10, HDR10+, Dolby Vision Profile 8]
- So I guess, I must choose: SAVE BL[NO], SAVE RPU [YES], CONVERT RPU [PROFILE 8.1 HDR10], CROP RPU [NO], Remove HDR10+ Metadata from BL [NO], SAVE HDR10+ [YES]
- Then I started the process and I get the .bin and .json files.

Are these options correct? Do I have to change anything in my selection? Please, let me know.

2) Inject DV and HDR10+ in 1.mkv
- Drag and drop 2.mkv to DDVT_DEMUXER.cmd
- RPU file: Drag and drop the .bin file
- HDR10+ file: Drag and drop the .json file
- CUSTOM EDIT FILE: I just press ENTER (I don't even know what it is)
- Now I get this.
18952

The only thing I have clear is that I have to put 198 frames in the delay. Then I don't know what more to do and haven't continued.

- Don't know what is RPU L6, and don't know if I have to change anything in options 3 or 4.
- Don't know if I have to EDIT ACTIVE AREA as I don't have to crop it and the area of the target movie is 2 pixels higher than the DV/HDR10+ movie. It just detects a crop 1 in the bottom in RPU input... (which IMHO I don't think it should be cropped in any way...)

Maybe could be stupid, but I don't know how to proceed.

Can anyone help me?

Thank you very much,

E.

[GodzilaAvenger]

Hi,

Generally speaking, you don't need to do anything about L6 metadata, because the one in the RPU usually doesn't even matter. But if you want, you can use the FILEINFO tool with the RPU you have (enter a random frame number, I usually go for 12345) to see what the L6 values for the RPU are, and you can open the mkv in mediainfo to see what those values are for the video (frame average light level, etc.) Then you can see if they are different and decide if you want to match them.

As for cropping, based on what you have said, you're good to go, you don't need to change anything.

[ed_co]

Hi,

Generally speaking, you don't need to do anything about L6 metadata, because the one in the RPU usually doesn't even matter. But if you want, you can use the FILEINFO tool with the RPU you have (enter a random frame number, I usually go for 12345) to see what the L6 values for the RPU are, and you can open the mkv in mediainfo to see what those values are for the video (frame average light level, etc.) Then you can see if they are different and decide if you want to match them.
.
I have no idea about what L6 metadata is.
I don't know what is matching what.
Could you please develop a little bit, so I could understand and I could decide what to do?


As for cropping, based on what you have said, you're good to go, you don't need to change anything.

The problem I see is that even though does not need any crop, it crops RPU, even for 1 pixel height (which it shouldn't crop anything at all as the RPU source file is shorter than the target file, and I think is a bug).

I kept going with the script and continued the injection, adding the 198 frames delay. And it crops the RPU based on what I see in the script:

18954

So, I guess if this is a bug, it should be great to be fixed.

[ed_co]

Apart from my previous reply (please @GodzilaAvenger or any other, reply if you can), I was thinking about another plan to avoid the RPU not match with VIDEO.

I just got another 3.mkv file, which is a UHD remux, and contains DV (not HDR+ though).
Obviously the resolution is not cropped: 3840x2160
So, I could add it to the 1.mkv, which has a resolution of 3840x1608.

So the steps for new plan could be:
1- Extract DV from 3.mkv (with CROP enabled or disabled? I did it with enabled)
2- Use the HDR10+ JSON file that I already extracted from 2.mkv
3- Inject DV from 3.mkv and HDR+ from 2.mkv to 1.mkv

By the way, extracting the 3.mkv I realised the size of the RPU.bin is much different from 2.mkv (28.3 vs 22.1), and then I realize the
2.mkv --> RPU .bin file size 28.3Mb --> RPU Info = [Dolby Vision Profile 8] [DM = CM v4.0]
3.mkv --> RPU .bin file size 22.1Mb --> RPU Info = [Dolby Vision Profile 8] [DM = CM v2.9]

What is this CM v4.0 vs v2.9?? Can anyone explain to me? The more size is better/more quality?

Thanks

[GodzilaAvenger]

CM refers to Dolby Vision Content Mapping, v4.0 is a newer, expanded version of v2.9, so it makes sense for the file to be larger.

As for L6 (and DV metadata labels in general), see here (https://professionalsupport.dolby.com/s/article/Dolby-Vision-Metadata-Levels?language=en_US).

As for the cropping, first of all, I doubt being 1 pixel off on one side would make any difference noticeable to the human eye. Second, in general you want the RPU borders to match the video. Your remux probably has ~280 for the top and bottom borders, when you are injecting it you would want to set all those to zero.

[ed_co]

CM refers to Dolby Vision Content Mapping, v4.0 is a newer, expanded version of v2.9, so it makes sense for the file to be larger.

As for L6 (and DV metadata labels in general), see here (https://professionalsupport.dolby.com/s/article/Dolby-Vision-Metadata-Levels?language=en_US).

Thanks for the info.


As for the cropping, first of all, I doubt being 1 pixel off on one side would make any difference noticeable to the human eye.
Still a bug: if we are injecting RPU from a 3840x1606 video into a 3840x1608 video, the RPU shouldn't be cropped in any way, right?

Anyway, there is something more I will comment later, as this bug looks to be more complicated.


Second, in general you want the RPU borders to match the video. Your remux probably has ~280 for the top and bottom borders, when you are injecting it you would want to set all those to zero.
I don't understand what you mean with this one, as I never wanted to inject anything in the remux.

Just wanted to extract the RPU from the remux, which the RPU was cropped at RPU extraction, and no problems at injecting time in 1.mkv having a message of [MATCH WITH VIDEO], and not like the RPU from the 2.mkv video (3840x1606) as was saying [NOT MATCH WITH VIDEO].

I have some new findings that I will post later.

[GodzilaAvenger]

Does the 1608 video fill out all pixel rows? Or are the top and bottom pixel rows black? If it is the former, RPU top & bottom border should be 0, if the latter, 1.

As for the remux, what I meant was that when you extract the remux RPU the borders in it are probably set to ~280 (if the film has standard cinematic aspect ratio). When you want to inject said RPU into a cropped video (e.g. 1606) then you should set the borders to 0.

I recommend looking at the L5 description in the link in my previous post. The top/bottom borders are basically the amount of "Letterbox/Blanking".

[ed_co]

Does the 1608 video fill out all pixel rows? Or are the top and bottom pixel rows black? If it is the former, RPU top & bottom border should be 0, if the latter, 1.

Is totally filled out, as I explained in detail in a comment before:

That 2 pixels height difference is weird. There are no black bars to any of them, and is imperceptible to know what the exact mismatch is. I don't know if it is:
- A crop thing: one was cropped more than the other.
- Aspect ratio management: they were cropped the same but the ratio was modified.
- Maybe the two movies, as they are probably from different releases of different countries, they came cropped differently.
In any case I don't know which of the three possibilities is.




As for the remux, what I meant was that when you extract the remux RPU the borders in it are probably set to ~280 (if the film has standard cinematic aspect ratio). When you want to inject said RPU into a cropped video (e.g. 1606) then you should set the borders to 0.

I guess it depends how you extract the RPU:
- If you extract it cropped you add it -in a cropped video- with 0
- If you extract it not cropped you add it -in a cropped video- with 280
This is quite clear to me. I extracted both ways and I think it is how it works.

As a reminder, the bug [NOT MATCH WITH VIDEO] just sets bottom 1, and not top.


I recommend looking at the L5 description in the link in my previous post. The top/bottom borders are basically the amount of "Letterbox/Blanking".
Yep I read it, and I understand it. But it is not explaining anything about the bug.

[ed_co]

I found out more things by accident.

Just hold on and put on hold the mentioned bug.

So, as I said before:
- The file 2.mkv is cropped 3840x1606 and RPU is v4.0 (so this RPU should be cropped).
- The file 3.mkv is uncropped (as it is a remux) and RPU is v2.9.
I have both extracted, and for v2.9 (I have it extracted cropped and uncropped, although lets just consider the cropped one). So let's consider both RPU cropped.

So I thought, lets start clean, and as I know the remux 3.mkv has RPU injected (because this film does not have DV in its UHD release), get an untouched remux for some tests doing encodes from it. So now we have:
- The file 4.mkv, which is a clean remux without DV (just have HDR10). Size and quality looks the same vs the 3.mkv remux but with nothing injected. I will not use this file for anything but for encode a cropped version from it.
- The file 5.mkv, which is an encode from the previous remux (automatically cropped with handbrake and reduced file with CRF19). Remember just has just HDR10, and it was cropped curiously to 3840x1606 (not 1608, like 1.mkv).

So, from now we can have the bug context again.

So now I thought, OK now lets inject the RPU v4.0 to 5.mkv (from 2.mkv, which has the exact same resolution), and remember this RPU was complaining when injected to 1.mkv, but now it SHOULD WORK with no WARNINGS.
But it didn't!! It informs in RPU: [NOT MATCH WITH VIDEO] and just sets bottom 1, and not in the top!
so is complaining the same way as injecting to 1.mkv (which remember that has different resolution 3840x1608).
So with RPU v4.0 coming from 2.mkv (3840x1606), injecting to 1.mkv (3840x1608) and 5.mkv (3840x1606) is complaining with BOTH resolutions the same way.
Some problem with RPU v4.0 maybe???

So obviously I thought, let's try with the RPU v2.9 (3.mkv remux) to 5.mkv. I am considering the one I extracted cropped.
So with RPU v2.9 coming from 3.mkv -remux- (extracted cropped), injecting to 1.mkv (3840x1608) and 5.mkv (3840x1606) is NOT complaining at all with any of the resolutions.
So maybe the RPU v2.9 is more permissive or something?

So I guess, probably the DDVT tool is not considering something with RPU v4.0? Or maybe is just a bug, I don't know. The tool does not seem to have any problem with RPU v2.9.

Just one thing to remember: even the message of [NOT MATCH WITH VIDEO], I was able to inject DV to the files with no problem, as it was just a warning but is still a possible bug.

By the way the HDR10+ (which I have only in 2.mkv), does not have any problem with any file or any resolution... I guess HDR10+ is not tied to resolution at all? Don't know.

Well, I could provide any file:
- 1.mkv, 2.mkv, 3.mkv, 4.mkv, 5.mkv (although I think with just 1.mkv (7Gb) and 5.mkv (6Gb) is more than enough, maybe 2.mkv (15Gb), but definitely not the remuxes)
- RPU v4.0, RPU v2.9 cropped (and not cropped also), and HDR10+ json (everything is like 200Mb)
so maybe the author of the DDVT tool could have a look and fix the bug, if it exists. Please let me know and I will provide a link to download.

Jeez, I did a lot of work. I hope is worth it.

Thanks


P.S.: First, sorry for my English, and second, sorry for the big chunks posts!! Please read them carefully, I know there are a lot of information and is important to read it carefully and trying to understand, so please don't read diagonally or you will miss important details.

[ed_co]

BTW, just as a final note, it should be great to have the DDVT tool for macOS too. I had to do all of this with a Virtual Machine, which I can say is not the most optimised way I guess. Thanks!!

[GodzilaAvenger]

A few things:

1. You do not have to specify the cropping when extracting the RPU. You can extract the RPU from the remux with ~280 border and then set it to 0 when injecting it. You can make this change using the [Edit Active Area] option in the injector.

2. DDVT uses ffmpeg (or maybe ffprobe? doesn't really matter) to auto detect borders from the video file, and it does not analyze every frame, but a subset of frames, if I remember correctly. Because of this, it can be (and in my experience many times is) off by a few pixels, which can cause that [Not Match with Video] error. At the end of the day though, you can just go in and set the borders manually. What you are encountering has nothing to do with the source file of the RPU or whether it is v2.9 ir v4.0.

P.S. yes, HDR10+ doesn't care about borders.

[Arbok]

Why does DDVT INJECTOR.cmd crashes when I drag and drop .mkv file? :(

EDIT: When using DDVT_DEMUXER.cmd to get Profile 8.1, the process runs just fine, but I cannot find the resulting file(s). If I understand this right, there sholud be an Output folder in the Dolby.Vision.Tool.v0.65.3 folder, but it's not there. Can anyone help me, please?

[winoni71]

Hello, the "DDVT_MKVTOMP4.cmd" command doesn't work on the latest version of the file (v0.65.5), when I type "s" to start the window closes immediately, no error is shown and no log file is created.
Reverting back to the "v0.65.4" version of the file fixes the issue.

[ManilaByNight]

I tried "DDVT_REMOVER.cmd" on a .mkv file (Ironheart.S01E05.Karmas.a.Glitch.2160p.DSNP.WEB-DL.DDP5.1.Atmos.H.265.mkv) and it gave an error saying:

Dolby Vision Profile 5 not supported.

The file has a RPU included, but the RPU cannot be removed.

What does this mean and why does the script not work?

Can this be fixed?

[GodzilaAvenger]

I think this is because Dolby Vision Profile 5 is not backwards compatible with HDR10, i.e. the file needs the RPU to be playable.

[TR-9970X]

I think this is because Dolby Vision Profile 5 is not backwards compatible with HDR10, i.e. the file needs the RPU to be playable.

Why is the latest build labeled 0.65.5, yet the download file is labeled DDVT_v0.63.5.rar.

Even the downloads on Mega are all DDVT_v0.63.5. :confused:

[ManilaByNight]

DDVT_Remover script with Folder support no longer works with the new released version 0.65.5. It suddenly quits and does not proceed. It used to work with version 0.65.4 after I requested for that feature to be added.

[cdth]

I have a question regarding remuxing the latest The Lost World Jurassic Park UHD that comes with a new DV FEL layer into a new .iso file.
The trick here is that the new UHD suffers from some nasty DNR so I'm thinking of using the 2018 HDR10 only transfer with better PQ but has 8 more black frames at the beginning.
So what can I do if I want to create a synchronized .iso remux file that has the HDR10 base layer from the 2018 UHD with the DV FEL layer from the 2025 UHD?

I hope my description isn't too confusing...

Would really appreciate any help from anyone!

[alexmorph3us]

I have a question. Can this tool be used to convert HDR to SDR content with tone mapping. If not, what would you recommend in this case?

[LisanAlGaib]

Quick question - I've been wanting to play some remuxes on my lg g3. I've tried the mkvtomp4 script but it says that profile 7 mel is not supported. Would my workflow then be - convert to DV profile 8 through the demux script and then inject it back to the original file, proceed to use the mkvtomp4 script? or am I missing something.

[GodzilaAvenger]

I have a question. Can this tool be used to convert HDR to SDR content with tone mapping. If not, what would you recommend in this case?

As far as I know, no. But I think a lot of tools like Davinci Resolve, Handbrake, and FastFlix can do it. They probably all use FFmpeg to do this so you might as well use FFmpeg if you want control over the tonemapping.

Quick question - I've been wanting to play some remuxes on my lg g3. I've tried the mkvtomp4 script but it says that profile 7 mel is not supported. Would my workflow then be - convert to DV profile 8 through the demux script and then inject it back to the original file, proceed to use the mkvtomp4 script? or am I missing something.

I believe so, yes, but keep a copy of the original file just in case.

P.S. how's Chani?

[sirbod]

I've noticed the scripts fail if used from the command-line if filenames contain characters DOS considers special...ampersands for example.

The fix is to move the delayed expansion so it occurs before the INPUTFILE variables are set, instead of after. This goes for most of the scripts, but here's the corrected DEMUXER as an example:

setlocal EnableDelayedExpansion
rem --- Hardcoded settings. Cannot be changed ---
set "INPUTFILE=%~dpnx1"
set "INPUTFILEPATH=%~dp1"
set "INPUTFILENAME=%~n1"
set "INPUTFILEEXT=%~x1"

[hidef_rec]

Can a kind soul walk me through the steps to convert a DV P7 UHD rip to a P8, baking the FEL into the latter? Here's what I did, but I still ended up with a P7 instead of a P8:

1. Used Demuxer on P7 MKV
Save BL : [YES]
Save EL : [YES]
Save RPU : [YES]
Convert RPU : [PROFILE 8.1 HDR10]
Crop RPU : [NO]

2. Used Injector like so
Filename : P7movie.4K.HDR.DV.ATMOS_[BL].hevc
DV Filename : P7movie.4K.HDR.DV.ATMOS_[EL].hevc

3. Used MKVMerge to mux the resulting
P7movie.4K.HDR.DV.ATMOS_[BL]_[BL+EL+RPU].hevc
with the audio from the original

Obviously, I messed up somewhere or everywhere :confused: :)

[GodzilaAvenger]

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

[hidef_rec]

Hmm, thanks, thought it was possible, but re-encoding would be necessary... which is a big negative. Just wanted to check my understanding. There's a FEL w/Ugoos AM6B+ or just used 'baked' P8 w/Zidoo debate going on in an AVSForum thread.

Edit: Found a post by the expert that seems to indicate so...
https://i.imgur.com/qO4N0Al.png

[GodzilaAvenger]

I'd say FEL doesn't even matter unless the studio did a terrible job of encoding the base HDR layer and you need the FEL info to recover the picture. Case in point, non of Nolan's films even have DV.

[LisanAlGaib]

Hmm, thanks, thought it was possible, but re-encoding would be necessary... which is a big negative. Just wanted to check my understanding. There's a FEL w/Ugoos AM6B+ or just used 'baked' P8 w/Zidoo debate going on in an AVSForum thread.

Edit: Found a post by the expert that seems to indicate so...
https://i.imgur.com/qO4N0Al.png

Try watching this (https://www.youtube.com/watch?v=8BvXqw_cGJE) video if you want to reencode yourself (actually, check out the whole channel, that guy is crazy good). The problem is that it'll probably take hours to reencode a 4k UHD movie. But if that's not an issue you can technically bake the FEL and convert the P7 into P8 without noticeable quality loss. The output will be 10 bit instead of 12 bit, but visually it'll look the same. If you want the best possible quality, use x265 instead of nvenc for the encoding, but that'll be 2-4 times slower.

[ManilaByNight]

I am on Windows 11 Pro 25H2 Build 26200.6901 (the latest version) and I tried using the Dolby Vision Tool Remover and I just get stuck on the "Analysing file. Please wait ....." section at the beginning of the process. Nothing else happens and the process does not complete. What is wrong here? Please help!

19043

[ManilaByNight]

Some development .....

I double clicked the mouse and hit the space bar and for some reason the removal process started but I am perplexxed why it would do this? Shouldn't the process start immediately the moment I hit the enter key after typing in the command line? Why would it do this or is there something wrong here?

Thanks.

[Thaddäus]

I have a question about the profile and whether I should choose to convert it:
My attempt is to mux a DV-layer from a Web-source to it's HDR10-only UHD Blu-ray-counterpart. But I not just want to have the MKV, I want to mux it into a Blu-ray structure. I've only done it once before and IIRC here's what I did:

1. Demuxing BL and RPU from the DV-version with DDVT Demuxer
2. Converting the BL to a H.265 HDR10 1080p-version with low bitrate, e.g. 2500 kBit/s
3. Injecting the RPU into the converted BL to be come my new EL-layer
4. Muxing the Blu-ray source (as BL) and the newly created EL together into an ISO or Blu-ray folder using tsMuxeR

However, the DV-source I have has Profile 8 and when trying to demux it, I can choose between "No conversion", "Profile 8.1 HDR10" and "Profile 8.4 HLG". Which would be best for what I'm trying to do? I guess either just leaving it as it is or converting it to 8.1 would be the right choice, but I just wanted to check back. :)

[GodzilaAvenger]

Blu-rays use Profile 7 (P7) DV, which can be MEL or FEL. DDVT (and the underlying dovi_tool) can't convert P8 to P7.

Also, I'm a bit confused with your process. Why are you turning the BL into a 1080p stream and adding that in as the EL?

[Thaddäus]

I know Blu-ray usually use P7. I'm not really into all that stuff about the profiles, but I thought P7 is more or less the same just with a MEL or FEL-layer, which I'm trying to recreate with the 1080p-version plus the RPU-data.
Unfortunately I just can't find it right now, but I once saw a tutorial somewhere, where they did the exact same thing and when I tried it myself around the same time last year it also worked. So I just wanted to try it again, I just can't remember how exactly which settings I used to extract the DV-layer. ;)

[GodzilaAvenger]

P7 is either RPU on its own (MEL) or RPU plus a 1080p stream (FEL). The 1080p stream is the remainder of the original 12-bit video signal and when added to the BL would reconstruct it. When you add in an encoded version of BL as the EL you're probably messing up the tonemapping and brightness settings applied by the RPU since that RPU came from a web source that has calculated those parameters for only the BL, not BL+EL (and your EL is not the source EL anyways). Aside from this, I think the frame order of your encoded version won't match that of the BL (I ran into this when I wanted to inject the original EL into a re-encoded BL). Bottomline is, I don't think you need that 1080p stream and are better off just injecting the RPU into the BL.

[Deithwen]

What's casuing this error? I'm trying to convert P5 file to P8
== INFORMATIONS ========================================================================================================

Filename : test.mkv
DV Filename : test_[RPU_CONVERTED-P8.4]_[P8].xml

== OPERATIONS ==========================================================================================================

[Extracting Video Layer]
Command: "D:\Programs\DDVT_v0.72.1_FULL\tools\mkvextract.exe" "C:\Users\Name\Desktop\New folder\test.mkv" tracks --ui-language en 0:"C:\Users\Name\Desktop\New folder\DDVT_NCgXO_TMP\temp.hevc"
Done.

[Creating DV RPU Binary]
Command: "D:\Programs\DDVT_v0.72.1_FULL\tools\dovi_tool.exe" generate --xml "C:\Users\Name\Desktop\New folder\DDVT Demuxer (test_[RPU_CONVERTED-P8.4].bin).log""C:\Users\Name\Desktop\New folder\test_[RPU_CONVERTED-P8.4]_[P8].xml" --canvas-width 1920 --canvas-height 1080 --rpu-out "C:\Users\Name\Desktop\New folder\DDVT_NCgXO_TMP\RPU-CREATED.bin"
Parsing XML metadata...
Error.
.
== ERROR(S) ============================================================================================================

1 Error(s) during processing.

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

[sk2316]

How to Convert a Dolby Vision Profile 8 file to Profile 7?

[GodzilaAvenger]

I don't think you can, at least not with DDVT. There's a small chance dovi_tool supports it but I'm not sure so check it's documentation.

[sk2316]

I don't think you can, at least not with DDVT. There's a small chance dovi_tool supports it but I'm not sure so check it's documentation.

Kuler087 [DoVi_Scripts]
In the next Beta, there will be a way to encode profile 7 FEL/MEL but it will require DEE. It will even have the option to tone map the base layer to lower brightness like the studios often do.

[JazzCZ]

I'm not super familiar with how HDR works but can I extract the DV metadata from one inferior source and inject it into a superior SDR stream?
I somehow managed it but the result is looking quite different from the original, and it wouldn't work unless I changed the transfer characteristics, color primaries, ... headers.