[DoVi_Scripts] Multi-Function Scripts for Dolby Vision processing and a lot more...

[dkangel]

both the player and TV must support it...
All the TVs made after 2019 support cmv4.0

ah ok so nothing to worry with a new tv from 2025 and a am6b+

thank you !!!!!!

[Gatorman3385]

All the TVs made after 2019 support cmv4.0

I have a Hisense 58R6E3 (not a great TV) manufactured in April of 2021, and do not see any brightness changes with these test files. Is it likely I have a "unicorn" TV, or are there other variables I could look into?

[Kuler087]

That's strange. I have a cheap Hisense TV too (from 2022, I think) and it supports CMV 4.0

[Gatorman3385]

I'm getting an error when trying to shorten then inject an RPU to an HDR file. It's with the edits2.json.
Converting Profile 5 RPU to Profile 8...
Done.

Editing L5... Left=0, Right=0, Top=42, Bottom=42
Error: No RPU found
Done.

Error: The system cannot find the file specified. (os error 2)
Missing operand.
Missing operand.

Video/RPU framecount mismatch. Duplicating frame =, -= times...
Error: expected value at line 4 column 15
Done.
The json doesn't have any values.

{
"duplicate": [
{
"source": =,
"offset": =,
"length": -=
}
]
}


Am I missing something?

[Kuler087]

I dont know. Looks like a problem with your rpu, it even fails to edit L5.
Hard to tell without the full log and ''echo on'' though...

[Gatorman3385]

Thanks. When I try to just use dovi_tool to convert the RPU from P5 to P8, I get the error
Error: Condition failed: `self.max_display_mastering_luminance <= MAX_PQ_LUMINANCE` (23040 vs 10000)

I'll dig deeper with "echo on"

[Kuler087]

Looks like your rpu has invalid L6 metadata.

[Gatorman3385]

I see. Thank you.

[Fuso]

Ok, so... I decided to "play" and think out-of-the-box.
I've demuxed ST-DL 7.6 file and muxed it to Profile 6 (no longer supported).
From this:
Dolby Vision, Version 1.0, Profile 7.6, dvhe.07.06, BL+EL+RPU, no metadata compression, Blu-ray compatible / SMPTE ST 2086, Version HDR10, HDR10 compatible
to this:
Dolby Vision, Version 1.0, Profile 6.1, dvhe.06.06, BL+EL+RPU, no metadata compression, HDR10 compatible / SMPTE ST 2086, Version HDR10, HDR10 compatible
Then played it through Plex on my LG C2 and to my suprise the file played fine showing Dolby Vision.
Then I've downloaded both FEL test - FEL TEST ST DL P7 CMV2.9 4000nits V3 and FEL TEST ST DL P7 CMV4.0 4000nits V3.
Tried the same but didn't show "THIS DEVICE CAN DECODE FEL". :(

[Kuler087]

Right, the last LG TV to support FEL(internal apps) is the C9. Every TV made since 2020 discards the EL and only processes the RPU

You have to bake FEL to P8(8-2-1) if you want your C2 internal player to show the "THIS DEVICE CAN DECODE FEL"

[coopzr]

My L2 and L8 plots are freaking out all of a sudden. For every film.
https://i.ibb.co/WNPw1BTT/The-Pitt-S01-E01-Do-Vi-L8-PLOT-100nits-trim.png (https://ibb.co/TDbS5PCC)

[Kuler087]

https://github.com/R3S3t9999/DoVi_Scripts/issues/67

[danny2576]

Hello,
How can I change the command-line parameters for x265 conversions?
I use cpu conversions and I need CRF18 and to enable hevc-aq mode. I would also like to be able to resize 4k content to 1080p resolution (for Plex storge)

Thank you
Danny

[Kuler087]

Yes, all the encoding settings and downscaling options are at lines 139-178.
FYI, in the latest beta (https://drive.google.com/file/d/128gq8aDUTKA_aT7SQsM9dkjA1EP1sosR/view?usp=drive_link), I added a new workflow(8-2-7) for aq_strenght/mode testing

https://i.ibb.co/5XB3JyXv/explorer-j-Pmuhi81r9.png

[danny2576]

Thanks

[MoonKnight]

Hello, @Kuler087

Any idea why when injecting an RPU in format .xml or .bin that was made with resolve at @24.000

after injection dovi_tool and metafier reports a change the framerate at 23.976

Copyright (c) 2013-2025 Dolby Laboratories, Inc. All Rights Reserved
08/18/2025/14:27:08.730000000 Metadata: INFO Validation Summary:
=========================
Metadata version: "5.1.0"
Level254 CMVersion: 4 1
Aspect Ratios (Canvas - Image): 1.77778 - 2.39402
Frame Rate: 23.976fps

how can i fix this bug ? it should stay like I made it, at 24 and not changed at 23.976 after injection

[Kuler087]

if you input a RPU, the default frame rate will be 23.976 because a binary file doesn't have a framerate.
Add ''24FPS'' in the filename and it should convert it to a 24fps XML.

For video input, it should be able to read the framerate automatically.

[MoonKnight]

if you input a RPU, the default frame rate will be 23.976 because a binary file doesn't have a framerate.
Add ''24FPS'' in the filename and it should convert it to a 24fps XML.

For video input, it should be able to read the framerate automatically.

my xml is already in 24 fps, I made it with resolve, resolve give me a good RPU xml at 24, metafier can confirm this.

But when I inject to BL.hevc
and use your script and give the rpu.xml at 24

after injection it becomes 23.976

its a bug,

But I can leave it like that ?

[Kuler087]

What file are you running in metafier exactly?

if you input the injected video and if your video framerate is 24fps(according to mediainfo), then the script should export a 24fps XML and metafier will report 24fps
if you input the injected RPU file (not XML), you have to specify the framerate in the filename because, as I said, a binary file doesn't have a frame rate and the script will fallback to 23.976.

[MoonKnight]

Yes, thank you, I did more testing, I had :

- BL.hevc
- RPU.xml

I renamed like this

BL24FPS.hevc
RPU24FPS.xml

and bug was fixed, but first metafier reports still show 23.976 (the one after injection 1-1)

but to be sure, I extracted again the RPU entirely and used metafier on it and it was good 24 fps

[badshah]

I used DoVi_Scripts_MKV.bat to experiment with DV baking on a sample mkv video which contains FEL.

but it does not show extracting EL or indexing EL as part of the process and simply doing RPU to P8 conversion and injecting.

I have copied this from CMD on a second attempt where it directly starts encoding after extracting BL and indexing.
No Nvidia GPU detected, enabling FFMS2 decoding

Do you want to crop? (default=n)

--> YES= y
--> NO= n
n


Reading input tracks format/id/language...
Done.
Indexing, please wait... 100%
Writing index... done.
Extracting track 0 with the CodecID 'V_MPEGH/ISO/HEVC' to the file 'D:\BD\DoVi.Scripts\temp.folder31\BL.hevc'. Container format: HEVC/H.265 elementary stream
Progress: 100%
Reordering metadata... Done.

=============================SCRIPT==============================================================================
LoadPlugin("D:\BD\DoVi.Scripts\tools\FFMS2\ffms2.dll")
LoadPlugin("D:\BD\DoVi.Scripts\tools\avs_libplacebo.dll")
LoadPlugin("D:\BD\DoVi.Scripts\tools\avsresize_r21\x64\Release\avsresize.dll")
FFVideoSource("D:\BD\DoVi.Scripts\DV_FEL_Sample.mkv", cachefile="D:\BD\DoVi.Scripts\temp.folder31\indexed.video.ffindex")
=================================================================================================================
D:\BD\DoVi.Scripts>if not "NO" == "YES" if not "0" == "2" "D:\BD\DoVi.Scripts\tools\x265.exe" --crf 15

[Kuler087]

Are you sure the input is FEL?

[badshah]

Are you sure the input is FEL?
yes, input file has BL+EL+RPU, EL is FEL

[badshah]

I tried another source and it's working fine, so most likely it's the problem with the earlier source. thanks for your script and sorry to waste time on above post :/

[en6ads]

Which method is better to create a Profile 8.1 from a P7 FEL source to play back on non-FEL devices? What are the strengths and weaknesses of each?
-Bake BL and FEL with workflow 8-2-1
-Use CM_Analyze on the BL HDR10 with workflow 3-1

Or, if it's known the FEL does not elevate combined BL+FEL brightness so the RPU can work for just the BL, What P8.1 workflow can just discard the P7 FEL? How can we tell if the FEL elevates overall brightness?

Thank you.

Edit: I should add I'm keeping the FEL source files for home theater playback (I have a couple of Ugoos CE CPM). My interest in correct FEL P8.1 conversion is for playback on Dolby Vision laptops / ipads etc...

[Kuler087]

-Bake BL and FEL with workflow 8-2-1
This re-encodes the video, so if you don’t use proper settings, visual quality can be lost.

Use CM_Analyze on the BL HDR10 with workflow 3-1
This leaves the video untouched, but if it’s graded beyond your TV’s capabilities, you’ll miss the artistic trims that fine-tune the tone mapping.

If FEL doesn’t change the brightness, then discarding the EL and converting the RPU to P8 is fine.
You can find out if FEL changes the brightness with workflow 7-1. Usually, the ones that do will have a 4000-nit MDL for the DV RPU and a 1000-nit MDL for the HDR10 base layer.

[en6ads]

but if it’s graded beyond your TV’s capabilities, you’ll miss the artistic trims that fine-tune the tone mapping.


Are you referring to the BL or EL grade?

For example, I create CM4.0 from HDR10 content. Almost all of it is 1000 nits P3 HDR10. My DV laptop is 675nits. So tone mapping required. Are you saying this workflow 3-1, the CDM_analyze L2 and L8 trims will be missed because MDL is greater than 675 nits?

I think what I am asking is: Will the CM4.0 generated from CM_Analyze from the HDR10 base layer look as good as the combined BL+FEL CM2.9 RPU from the studio on Laptops and Ipads (say ~1000 nits max).
I fully understand on a G5 you need the 4000 nits EL to make use of the TV's brightness. But for ipads and laptops? Wouldn't the CM4.0 from the 1000nits base layer be enough?

[Kuler087]

BL
When you replace the original metadata with generated metadata, you lose the artistic trims. The L8 trim(s) are created manually, shot by shot, by the colorist on the mastering display, just like the HDR master itself.
When you generate DV, the L8 trim is either blank or absent, and only L1+L3 handle the tone mapping.

[en6ads]

BL
When you replace the original metadata with generated metadata, you lose the artistic trims. The L8 trim(s) are created manually, shot by shot, by the colorist on the mastering display, just like the HDR master itself.
When you generate DV, the L8 trim is either blank or absent, and only L1+L3 handle the tone mapping.

OK thanks. Baking FEL preserves the original RPU with colorists trims, while generating a new one from HDR10 does not. It sounds like baking is the way to go.

thank you.

Edit: Is Resolve Studio much quicker at baking vs 8-2-1?

[Kuler087]

resolve can't bake fel

[Kuler087]

3.0.8 released:



https://github.com/R3S3t9999/DoVi_Scripts/releases

CHANGES:

- DoVi_Tool.exe (https://github.com/quietvoid/dovi_tool/releases/download/2.3.1/dovi_tool-2.3.1-x86_64-pc-windows-msvc.zip) must be updated to the latest version
- Added a prompt to specify the qscale value for ProRes encoding
- Added a prompt to specify the analysis tuning in 3-1 CM_analyze
- Added an option to bypass framecount check in workflow 1 for some rare cases when it doesnt work (default = NO) line 298
- Added an option to bypass HDD space check for some rare cases when it doesnt work (default = YES) line 300
- (6-4) Trims (L2/L8) plotter: Now supported natively in dovi_tool.exe (much faster). The old mode can still be enabled in the settings (line 222). Default = NEW
- (2-3) Dovi_tool can now transfer cmv4.0 to cmv2.9 natively.
- NEW (8-2-7): Added a new workflow for compression settings comparisons (aq-mode, aq-strength, psy-rdoq, psy-rd, qcomp etc...) settings at lines 188-203

[en6ads]

Hi, quick question:
Mission Impossible Fallout UHD (changing aspect ratios in the IMAX scenes) shows a Level 5 of this in workflow 1:
L5 offset: TOP=N.A., BOTTOM=N.A., LEFT=N.A., RIGHT=N.A.

Does this mean there is no Level 5, or that the dynamic nature of it cannot be reported properly in workflow 1?

I tried to plot level 5 using workflow 5-5 but got this message: Input doesn't have L5 metadata, skipping...

Did the UHD disk did not come with Level 5? If not, is there a way to recreate it including the dynamic aspect ratio changes?

Edit: And if the disk did not come with level 5, does that mean the measurements in the RPU is for the whole screen, including all letterboxing?

[coopzr]

OK thanks. Baking FEL preserves the original RPU with colorists trims, while generating a new one from HDR10 does not. It sounds like baking is the way to go.

thank you.

Edit: Is Resolve Studio much quicker at baking vs 8-2-1?

In case you or any other user needs instructions :)

Step 1: Extract DV from original_movie.mkv
Step 2: Bake FEL to ProRes using 8-2-3. This produces a prores.mov file that is essentially the HDR12 bit master. This file will be very large (upwards of 800GB sometimes!). If storage is limited, change qscale to 0 on line 168 (-qscale:v 1 --> -qscale:v 0). This should significantly reduce the size of the prores.mov, however, it may take twice as long to encode. There is no difference in quality between qscale 1 and 0.
Step 3: Rename original_movie_RPU.bin to the same file name as the prores.mov (and same path too)
Step 4: Run 3-1 on the prores.mov, using the same MDL and scene cuts as the original DV. If you did step 3 correctly, it will automatically grab the scene cuts from the original RPU. You cannot make your own scene cuts or force FBF using this method. This will produce a generated_RPU.bin
Step 5. Use 2-3 to transfer levels 12389 from generated_RPU.bin to original_movie_RPU.bin. This produces a transferred_RPU.bin
Step 6: Inject transferred_RPU.bin into original_movie.mkv using workflow 1.

Hope this helps!

[Kuler087]

Edit: And if the disk did not come with level 5, does that mean the RPU is for the whole screen, including all letterboxing?
yes

Hi, quick question:
Mission Impossible Fallout UHD (changing aspect ratios in the IMAX scenes) shows a Level 5 of this in workflow 1:
L5 offset: TOP=N.A., BOTTOM=N.A., LEFT=N.A., RIGHT=N.A.

Does this mean there is no Level 5, or that the dynamic nature of it cannot be reported properly in workflow 1?

I tried to plot level 5 using workflow 5-5 but got this message: Input doesn't have L5 metadata, skipping...

Did the UHD disk did not come with Level 5? If not, is there a way to recreate it including the dynamic aspect ratio changes?





Yes, that means the RPU doesn’t have any L5.

I’ve already created the proper L5 metadata for this movie. You can edit your RPU with this JSON. Just rename the JSON file to match the RPU (and place it in the same path), then run Workflow 1.

{
"mode": 0,
"active_area": {
"presets": [
{
"id": 0,
"left": 0,
"right": 0,
"top": 277,
"bottom": 277
},
{
"id": 1,
"left": 0,
"right": 0,
"top": 67,
"bottom": 67
},
{
"id": 2,
"left": 0,
"right": 0,
"top": 171,
"bottom": 171
}
],
"edits": {
"0-33428": 0,
"33429-38332": 1,
"38333-38412": 2,
"38413-38951": 1,
"38952-161534": 0,
"161535-161990": 1,
"161991-162028": 0,
"162029-162103": 1,
"162104-162594": 0,
"162595-163439": 1,
"163440-164082": 0,
"164083-166526": 1,
"166527-166623": 0,
"166624-166689": 1,
"166690-166851": 0,
"166852-166943": 1,
"166944-167008": 0,
"167009-167113": 1,
"167114-167181": 0,
"167182-167324": 1,
"167325-167448": 0,
"167449-168595": 1,
"168596-169024": 0,
"169025-171447": 1,
"171448-172543": 0,
"172544-172954": 1,
"172955-175358": 0,
"175359-176799": 1,
"176800-179240": 0,
"179241-179711": 1,
"179712-180450": 0,
"180451-181791": 1,
"181792-183440": 0,
"183441-185508": 1,
"185509-186612": 0,
"186613-191299": 1,
"191300-191689": 0,
"191690-191817": 1,
"191818-192111": 0,
"192112-192227": 1,
"192228-192747": 0,
"192748-193181": 1,
"193182-193993": 0,
"193994-194580": 1,
"194581-212065": 0
}
}
}

[en6ads]

Yes, that means the RPU doesn’t have any L5.

I’ve already created the proper L5 metadata for this movie. You can edit your RPU with this JSON. Just rename the JSON file to match the RPU (and place it in the same path), then run Workflow 1.


Wow thank you for sharing!
If the RPU is missing Level 5 by mistake, and the trims in RPU are meant to tone map excluding the letterboxes, then injecting it would be great.

However, if level 5 was omitted by design, does that mean the colorist graded the movie, and the trims are meant to include the letterboxing during tone mapping? If this is the case then injecting the dynamic level 5 data would create an incorrect RPU?

Or does it not matter?
Thanks again.

[Kuler087]

All Blu-ray players and HDMI devices on the market, except for the custom Ugoos, ignore L5 (and positive lift) and always apply tone mapping to the entire image, letterbox included.

All DV metadata, except for “trims positive lift offsets,” has no effect on the letterbox. And even if the colorist applies a slight positive lift, as long as the Dolby 0.0025 limit is respected, the letterbox will remain unaffected.

In other words, L5 is essentially useless during playback, but when active, it allows the positive lift to work.

No L5 at all is technically incorrect.

You can test the relationship between positive lift and L5 with these test files:
https://drive.google.com/drive/folders/1LbuwBDZj5x3i1bdbAntsZlr5CiYJ9KKj?usp=drive_link

[en6ads]

Thank you. Ok, I'll go ahead and inject your level 5 which will allow the trims to properly pass to the TV and be used.

Much appreciated.

All Blu-ray players and HDMI devices on the market, except for the custom Ugoos, ignore L5 (and positive lift) and always apply tone mapping to the entire image, letterbox included.

All DV metadata, except for “trims positive lift offsets,” has no effect on the letterbox. And even if the colorist applies a slight positive lift, as long as the Dolby 0.0025 limit is respected, the letterbox will remain unaffected.

In other words, L5 is essentially useless during playback, but when active, it allows the positive lift to work.

No L5 at all is technically incorrect.

You can test the relationship between positive lift and L5 with these test files:
https://drive.google.com/drive/folders/1LbuwBDZj5x3i1bdbAntsZlr5CiYJ9KKj?usp=drive_link

[coopzr]

Do you think we will ever see a cmv2.9 L2 --> cmv4.0 L8 conversion tool?

I hope one day we can keep old L2 artistic trims when converting to cmv4.0. A man can only dream...

[Kuler087]

No. The trims are created based on what the colorist sees from the default analysis tone mapping, and the metadata in a CMv2.9 workflow is calculated differently than in a CMv4.0 workflow.

Metafier has an option to update a CMv2.9 XML to CMv4.0, but it doesn’t actually recalculate anything; IIRC, it simply adds the 10/100-nit floor to L1 that CMv4.0 has.

[en6ads]

@coopzr thanks for sharing these instructions.
What is the end goal of these steps?

I'm not sure it helps me, If I understand the steps correctly? You generate a new RPU from the HDR12 ProRes (taking scene cuts from original RPU) and transfer these new generated levels back to the original RPU? My goal is to create a single layer P8.1. How do these steps achieve that?

Thanks again, appreciate your help.

In case you or any other user needs instructions :)

Step 1: Extract DV from original_movie.mkv
Step 2: Bake FEL to ProRes using 8-2-3. This produces a prores.mov file that is essentially the HDR12 bit master. This file will be very large (upwards of 800GB sometimes!). If storage is limited, change qscale to 0 on line 168 (-qscale:v 1 --> -qscale:v 0). This should significantly reduce the size of the prores.mov, however, it may take twice as long to encode. There is no difference in quality between qscale 1 and 0.
Step 3: Rename original_movie_RPU.bin to the same file name as the prores.mov (and same path too)
Step 4: Run 3-1 on the prores.mov, using the same MDL and scene cuts as the original DV. If you did step 3 correctly, it will automatically grab the scene cuts from the original RPU. You cannot make your own scene cuts or force FBF using this method. This will produce a generated_RPU.bin
Step 5. Use 2-3 to transfer levels 12389 from generated_RPU.bin to original_movie_RPU.bin. This produces a transferred_RPU.bin
Step 6: Inject transferred_RPU.bin into original_movie.mkv using workflow 1.

Hope this helps!

[coopzr]

@coopzr thanks for sharing these instructions.
What is the end goal of these steps?

I'm not sure it helps me, If I understand the steps correctly? You generate a new RPU from the HDR12 ProRes (taking scene cuts from original RPU) and transfer these new generated levels back to the original RPU? My goal is to create a single layer P8.1. How do these steps achieve that?

Thanks again, appreciate your help.

Sorry, those were instructions for generating a P7 FEL RPU. This way avoids having to encode x265 (takes a really long time).

To bake FEL and generate P8, do the following:
Step 1: Bake FEL to HDR x265 using 8-2-1. This will produce a HDR12 bit x265 (HEVC) master. There will be a slight loss of quality unless you use the right settings (unlike the previous method, which is lossless). This will take a very long time (days on my system). It should automatically convert the P7 RPU to P8.
Step 2: If you need to generate new DV, use 3-1. Another benefit of this method is that you can use your own scene cuts for force frame-by-frame if needed.

[en6ads]

Sorry, those were instructions for generating a P7 FEL RPU. This way avoids having to encode x265 (takes a really long time).


Isn't the RPU from a FEL disk already a FEL RPU? Surely it's not a base layer only RPU.

[coopzr]

Isn't the RPU from a FEL disk already a FEL RPU? Surely it's not a base layer only RPU.

The DV in a FEL disk is the RPU + EL.

My first instructions was how to generate new DV for a FEL movie (as 4000nit MDL cmv2.9 is broken on many displays) losslessly. (Sorry, should have clarified it was to generate new, cmv4.0 DV)

My second instructions was how to bake the EL into the HDR10 base layer so that you can have a P8 RPU (single layer). This way leaves the DV untouched.

[coopzr]

Metafier has an option to update a CMv2.9 XML to CMv4.0, but it doesn’t actually recalculate anything; IIRC, it simply adds the 10/100-nit floor to L1 that CMv4.0 has.

Does this fix the 4000nit cmv2.9 bug?

[Kuler087]

Does this fix the 4000nit cmv2.9 bug?

nop...

[dkangel]

Hi
I have more questions for your endless knowledge of DV :)
I saw your video to generate dv from hdr with resolve.
You told some guy that it's will be useless if your tv have enough nits.
So first question is : i have plan to buy TCL 75C8K TV, it's 5000 nits peak brightness , is it worth to generate DV or HDR is enough ?
I'm ready to generate dv for all my hdr movie but "est-ce que ca en vaut la peine ?" i know you speak french and my english is bad...
Second question : my second plan is to buy ugoos am6, so what to do with remux who have wrong L5 ? either N.A. or 0/0 instead of 277/277 for example...
L5 is useless with all the hdmi player but with the ugoos ?
Thank you

[Kuler087]

yes, DV tone mapping is useless for 99% of the movies on a 5000nits TV. It still can be useful if your TV has issues in HDR10 like my G5.

L5 + ugoos: it doesn't matter much because even if it's missing or incorrect, the ugoos output will still be accurate. So save your HDD life and avoid the editing/injecting/remuxing

[en6ads]

Does this fix the 4000nit cmv2.9 bug?

@coopzer, @Kuler087,

Do you generate CM4.0 (either 3-1 or in Resolve) for all your CM2.9 4000nit MDL UHD that do not have a web streaming CM4.0 RPU that can be used?

Or do you just keep the CM2.9 and accept the darker image?

I have an LG C4.

Many thanks.

[Kuler087]

Yes, I generate new metadata for any CMV2.9 4000-nit movie. I just can't accept any dimming for low-nit content on a 2500-nit G5 TV.

Did a bunch of comparisons with cmv2.9 4000nits content that can be displayed without any tone mapping on my G5:

https://slow.pics/c/ou5rw0zy?canvas-mode=fit-height
https://slow.pics/c/RcJlcJ4w?canvas-mode=fit-height
https://slow.pics/c/1mW5gzyv?canvas-mode=fit-height
https://slow.pics/c/96SmJmjF?canvas-mode=fit-height
https://slow.pics/c/SjaFh5i1

And I have many real DV examples here that show how 2.9 + 4000nits dims for no reason:
https://drive.google.com/drive/folders/1g5I-z_sJmVu-SAIPNiiSlcdMiy2ka0mf

[dkangel]

yes, DV tone mapping is useless for 99% of the movies on a 5000nits TV. It still can be useful if your TV has issues in HDR10 like my G5.

L5 + ugoos: it doesn't matter much because even if it's missing or incorrect, the ugoos output will still be accurate. So save your HDD life and avoid the editing/injecting/remuxing

Thank you so much for your help, you save me a lot of useless work :)

PS : So some hi-models TV with 6000-7000 nits and DV capable are in a way a non sense ? Except with a 10000 nits movie but there doesn't exist i think