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

[MwenDavo]

Hi! Just wanted to confirm something about the script for the P7 -> P8 baking:
If the movie uses BT.2020, it uses the following Master Display Primaries: G(8500,39850)B(6550,2300)R(35400,14600)WP(15635,16450)
If the movie is not BT.2020, it uses these ones instead: G(13250,34500)B(7500,3000)R(34000,16000)WP(15635,16450)
Then, if its MEL, it adds the luminance based on the HDR10 MaxCLL and MaxFALL.
Otherwise it's FEL, in which case it gets the MaxCLL and MaxFALL from the RPU.
Am I right?

[Kuler087]

correct

[MwenDavo]

correct

Awesome. I managed to port the baking workflow to Linux then, since that was the only remaining doubt I had. Had to replace a bunch of things due to compatibility, such as:

FFMS and DGIndex with BestSource
NVEncC with QSVEnc since I have an ARC A310
Avisynth+ with Vapoursynth since it was better supported on Linux
DoviBaker with FelBaker, as it had a native Linux version


All in all, I'm pretty happy with the result. I even changed from VBR 50000 to ICQ 15 (Intel's own CQP) which I don't notice any difference at all, but it's about 75% of the VBR size. I still have to compare VMAF between them, but I'm satisfied nonetheless.

I'm still debating if I'll implement the cropping step. It seems like a nice feature to have, but I have some doubts about compatibility with various devices. I'll look into it a bit more before deciding.

Big thanks for your work, as it taught me a lot about media and pushed me into making this!

[Kuler087]

Nice new addition to workflow 3-1 to test. The script can now control Davinci Resolve (with scene cut detection or EDL).

latest BETA: https://drive.google.com/file/d/128gq8aDUTKA_aT7SQsM9dkjA1EP1sosR/view?usp=drive_link
and put this file in your tool folder: https://drive.google.com/file/d/1l5sY4yvFvdhq8O1VZ4G73dk_EVGGAlHD/view?usp=drive_link

Full FEL processing is also supported; for example, I just did a FEL movie in less than 1H40. So unless we have to do MSC or variable L5, the whole process is now fully automated.

The default tuning is 3, and to use another one, you must create a preset in Resolve and put the same name into line 290 (use something short, such as ''1''):

::===================================== DV Generator (3-1) SETTINGS====================================================================================
:: Select if you want to use cm_analyze(free) or Davinci Resolve(payware) in 3-1, CM or RESOLVE (default = CM)
set Mode_31=RESOLVE
:: Select a Resolve preset. (default = none)
set Resolve_Preset=1
::workaround for movies that wont work in madvr scene cut generation in 3-1 (default= NO)
set madvr_workaround=NO
:: choose the prores encoding quality/size in 3-1 (default = 4) higher values means faster encoding(depending on your cpu) and smaller filesize.
set qscale=4
:: force cpu for the CM_analyze (3-1) YES or NO (default=NO)
set CM_CPU=NO
:: choose if you want to force frame by frame analysis in 3-1 (default = NO)
set force.FBF=NO
:: Bake FEL and upgrade a P7 rpu with new metadata in workflow 3-1 (default = NO)
set Bake_FEL_31=YES

Try with a short file first to see if it works. If it doesnt work, you will have to install the latest python(to path) and if you do, dont forget to run the Python libraries installation.
pip install opencv-python colour-science scikit-image matplotlib numpy colour opencv-python-headless PyQt5 OpenImageIO plotly
https://www.python.org/ftp/python/3.14.3/python-3.14.3-amd64.exe

Batch mode is also supported if you create a config bat with the same name/path as the videos:

:: Configure the active area (Level 5) and Mastering display for (3-1) batch CM analysis.Each file need a config.

:: MDL choices are: 1000nits-P3= 20(default) / 1000nits-BT2020= 21 / 4000nits-P3= 7 / 4000nits-BT2020= 8 / 2000nits-P3= 30 / 2000nits-BT2020= 31


set MDL=7

set left=0

set right=0

set top=277

set bottom=277


https://i.ibb.co/7JG0HqJT/doviscripts-resolve.png

[Kuler087]

Special Thanks to @Gatorman3385

[TR-9970X]

This app of yours is getting quite complex.

So stupid question, obviously Resolve has to be installed somewhere (default location), does it matter what version it is ?

Blackmagic Design DaVinci Resolve Studio 20.3.2, is getting big too, 7.5Gb !!!

Cheers

[Kontrarian]

The script can control the Davinci Resolve API!
So what are we gaining with this, faster and better scene cut detection?

[Kuler087]

This app of yours is getting quite complex.

So stupid question, obviously Resolve has to be installed somewhere (default location), does it matter what version it is ?

Blackmagic Design DaVinci Resolve Studio 20.3.2, is getting big too, 7.5Gb !!!

Cheers

Yes, install it to the default location or edit the script path to wherever you want to install it:

line 464:

:: Full path to the DaVinci Resolve executable EG: C:\Program Files\Blackmagic Design\DaVinci Resolve\Resolve.exe
set resolve_exe=C:\Program Files\Blackmagic Design\DaVinci Resolve\Resolve.exe
::Change to a full path if python is not on PATH, e.g.: C:\Python312\python.exe
set python=python

[Kuler087]

The script can control the Davinci Resolve API!
So what are we gaining with this, faster and better scene cut detection?

right, much faster and better scene cuts.

[TR-9970X]

Thanks for the info :)

[SamuriHL]

Omg that’s awesome! Once I get my new laptop setup I’ll be checking that out asap! Thanks for this!

[Kontrarian]

It didn't work for me.

I have Resolve installed in the exact same path as line 464 wants (which was it's default location).
I put write_resolve_dv_generate.py in DoVi_Script\tools.
What am I missing?

[Gatorman3385]

Latest Python in PATH?

[Kuler087]

as I said here (https://forum.doom9.org/showthread.php?p=2029575#post2029575), if it doesnt work, install the latest python.


Try with a short file first to see if it works. If it doesnt work, you will have to install the latest python(to path) and if you do, dont forget to run the Python libraries installation.
pip install opencv-python colour-science scikit-image matplotlib numpy colour opencv-python-headless PyQt5 OpenImageIO plotly
https://www.python.org/ftp/python/3.14.3/python-3.14.3-amd64.exe

[Kontrarian]

Yeah, I did everything with Python.
Installed latest to PATH, ran PIP command, etc.
So I'm not sure what step I'm missing.

https://pastebin.com/cP95zbFj


# write_resolve_dv_generate.py
# Place in the tools folder alongside DoVi_Scripts_MKV.bat.
# Called by Workflow.H_Resolve to write the Resolve DV CMv4.0 generation API script.


"alongside DoVi_Scripts_MKV.bat"?

My .bat files are in the root DoVi-Scripts folder, not the "tool" folder?

[Kuler087]

3-1 default is CM_analyze because it's a free tool.
You have to enable it to use resolve.

:: Select if you want to use cm_analyze(free) or Davinci Resolve(payware) in 3-1, CM or RESOLVE (default = CM)
set Mode_31=RESOLVE


FEL baking is also disabled by default:
:: Bake FEL and upgrade a P7 rpu with new metadata in workflow 3-1 (default = NO)
set Bake_FEL_31=YES

[Kontrarian]

Got it.
I was thinking the script was going to ask me at some point if I wanted to CM or Resolve.
"set Resolve_Preset=1" would use "1= Most Highlight Detail/Most Mapping (Safest, no clipping)"?

[Kuler087]

The resolve preset is no longer required if you download the latest script (https://drive.google.com/file/d/128gq8aDUTKA_aT7SQsM9dkjA1EP1sosR/view?usp=drive_link) and py file (https://drive.google.com/file/d/1l5sY4yvFvdhq8O1VZ4G73dk_EVGGAlHD/view?usp=drive_link). The script will ask for a tuning.

[Kontrarian]

Writing Resolve DV Generate script...

Resolve DV Generate script written to: D:\DoVi_Scripts\temp.folder77\resolve_dv_generate.py

Running Resolve API...

Project: Untitled Project
MDP: P3 D65 @ 4000 nits
Canvas: 3840x1606 Mode: resolve_detect
WARNING: Project preset '1' not found - continuing.
Setting DV project settings...
colorScienceMode = davinciYRGB -> True
separateColorSpaceAndGamma = 0 -> True
colorSpaceTimeline = Rec.2100 ST2084 -> True
colorSpaceOutput = Same as Timeline -> True
hdrDolbyControlsOn = 1 -> True
hdrDolbyVersion = 4.0 -> True
hdrMasteringOn = 1 -> True
hdrMasteringLuminanceMax = 4000 -> True
hdrDolbyMasterDisplay = 4000-nit, P3, D65, ST.2084, Full -> True
timelineResolutionWidth = 3840 -> True
timelineResolutionHeight = 1606 -> True
timelineOutputResolutionWidth = 3840 -> True
timelineOutputResolutionHeight = 1606 -> True
Clearing Media Pool...
Importing ProRes: D:\DoVi_Scripts\temp.folder77\Baby.Driver.Chapter-002_prores.422.mov
Imported: Baby.Driver.Chapter-002_prores.422.mov
Creating timeline from ProRes (Resolve scene detection mode)...
Timeline: DV_Generate_Baby.Driver.Chapter-002_prores.422
Clip appended.
Color page open.
Running Resolve scene detection...
Scene detection complete.
Running AnalyzeDolbyVision...
Traceback (most recent call last):
File "D:\DoVi_Scripts\temp.folder77\resolve_dv_generate.py", line 141, in <module>
result = timeline.AnalyzeDolbyVision()
TypeError: 'NoneType' object is not callable
Error: The system cannot find the file specified. (os error 2)
Error: The system cannot find the file specified. (os error 2)
Error: The system cannot find the file specified. (os error 2)
Parsing XML metadata...
Error: The system cannot find the file specified. (os error 2)
File not found - Baby.Driver.Chapter-002_DV.xml
The system cannot find the file specified.
Error: The system cannot find the file specified. (os error 2)
Reading generate config file...
Error: expected value at line 3 column 15
Error: The system cannot find the file specified. (os error 2)
Error: The system cannot find the file specified. (os error 2)
Parsing RPU file...
Error: The system cannot find the file specified. (os error 2)
Press any key to continue . . .


Now I just get this... :angry:

[Kuler087]

not the latest py file (https://drive.google.com/file/d/1l5sY4yvFvdhq8O1VZ4G73dk_EVGGAlHD/view?usp=drive_link)

[Kontrarian]

Could have sworn I had the latest, but I downloaded it again with your link and ran the script again and got this:


Writing Resolve DV Generate script...

Resolve DV Generate script written to: D:\DoVi_Scripts\temp.folder77\resolve_dv_generate.py

Running Resolve API...

D:\DoVi_Scripts\temp.folder77\resolve_dv_generate.py:39: SyntaxWarning: "\P" is an invalid escape sequence. Such sequences will not work in the future. Did you mean "\\P"? A raw string is also an option.
tuning = "C:\ProgramData"
ERROR: Cannot import DaVinciResolveScript.
Expected: 1604\Blackmagic Design\DaVinci Resolve\Support\Developer\Scripting\Modules
Make sure DaVinci Resolve is running and scripting is enabled.
Error: The system cannot find the file specified. (os error 2)
Error: The system cannot find the file specified. (os error 2)
Error: The system cannot find the file specified. (os error 2)
Parsing XML metadata...
Error: The system cannot find the file specified. (os error 2)
File not found - Baby.Driver.Chapter-002_DV.xml
The system cannot find the file specified.
Error: The system cannot find the file specified. (os error 2)
Reading generate config file...
Error: expected value at line 3 column 15
Error: The system cannot find the file specified. (os error 2)
Error: The system cannot find the file specified. (os error 2)
Parsing RPU file...
Error: The system cannot find the file specified. (os error 2)
Press any key to continue . . .


I'm doing everything from scratch again and I'll report back...

[Kuler087]

you need both the latest script and py file

[Kontrarian]

Everything's the latest, so I'm not sure what's going on...


Writing Resolve DV Generate script...

Resolve DV Generate script written to: D:\DoVi_Scripts\temp.folder77\resolve_dv_generate.py

Running Resolve API...

Project: Untitled Project
MDP: P3 D65 @ 4000 nits
Canvas: 3840x1604 Mode: resolve_detect
Setting DV project settings...
colorScienceMode = davinciYRGB -> True
separateColorSpaceAndGamma = 0 -> True
colorSpaceTimeline = Rec.2100 ST2084 -> True
colorSpaceOutput = Same as Timeline -> True
hdrDolbyControlsOn = 1 -> True
hdrDolbyVersion = 4.0 -> True
hdrMasteringOn = 1 -> True
hdrMasteringLuminanceMax = 4000 -> True
hdrDolbyMasterDisplay = 4000-nit, P3, D65, ST.2084, Full -> True
timelineResolutionWidth = 3840 -> True
timelineResolutionHeight = 1604 -> True
timelineOutputResolutionWidth = 3840 -> True
timelineOutputResolutionHeight = 1604 -> True
hdrDolbyAnalysisTuning = Most Mapping -> True
Clearing Media Pool...
Importing ProRes: D:\DoVi_Scripts\temp.folder77\Baby.Driver.Chapter-002_prores.422.mov
Imported: Baby.Driver.Chapter-002_prores.422.mov
Creating timeline from ProRes (Resolve scene detection mode)...
Timeline: DV_Generate_Baby.Driver.Chapter-002_prores.422
Clip appended.
Color page open.
Running Resolve scene detection...
Scene detection complete.
Running AnalyzeDolbyVision...
Traceback (most recent call last):
File "D:\DoVi_Scripts\temp.folder77\resolve_dv_generate.py", line 122, in <module>
result = timeline.AnalyzeDolbyVision()
TypeError: 'NoneType' object is not callable
Error: The system cannot find the file specified. (os error 2)
Error: The system cannot find the file specified. (os error 2)
Error: The system cannot find the file specified. (os error 2)
Parsing XML metadata...
Error: The system cannot find the file specified. (os error 2)
File not found - Baby.Driver.Chapter-002_DV.xml
The system cannot find the file specified.
Error: The system cannot find the file specified. (os error 2)
Reading generate config file...
Error: expected value at line 3 column 15
Error: The system cannot find the file specified. (os error 2)
Error: The system cannot find the file specified. (os error 2)
Parsing RPU file...
Error: The system cannot find the file specified. (os error 2)
Press any key to continue . . .

[Kontrarian]

I changed the folder I have been using all this time to "DoVi_Scripts.old".
I went to your github and downloaded the tool pack and extracted it to D:\.
It made a "DoVi.Scripts" folder.
I downloaded the latest beta and py from your post in this thread (post #1804).
I edited DoVi_Scripts_MKV.bat from "set Mode_31=CM" to "set Mode_31=RESOLVE".
I put the latest DV EXEs in the tools folder (Dolby_Vision_Professional_Tools_Windows_v5.6.2_2026-02-21_18-23-58.exe).
I ran the script and got this: https://pastebin.com/CjCHk1tF


File "D:\DoVi.Scripts\temp.folder77\resolve_dv_generate.py", line 122, in <module>
result = timeline.AnalyzeDolbyVision()
TypeError: 'NoneType' object is not callable
Error: The system cannot find the file specified. (os error 2)
Error: The system cannot find the file specified. (os error 2)
Error: The system cannot find the file specified. (os error 2)
Parsing XML metadata...
Error: The system cannot find the file specified. (os error 2)
File not found - Baby.Driver.Chapter-002_DV.xml
The system cannot find the file specified.
Error: The system cannot find the file specified. (os error 2)
Reading generate config file...
Error: expected value at line 3 column 15
Error: The system cannot find the file specified. (os error 2)
Error: The system cannot find the file specified. (os error 2)
Parsing RPU file...
Error: The system cannot find the file specified. (os error 2)
Press any key to continue . . .


I don't know what I'm missing, it's probably something silly, but I'm out of ideas.
I used Beyond Compare to compare the .bat and .py from my old folder and the new folder and they are identical.
My DaVinci Resolve version is 18.6.5 build 7 if that matters.
I really appreciate your patience and your advise!

[Gatorman3385]

This was built on Resolve 20.0 build 49. APIs are updated and this could be you problem. I'm not sure.

[Gatorman3385]

I changed the folder...

Can you confirm the latest Python is in your path?

[Kontrarian]

This was build on Resolve 20.0 build 49. APIs are updated and this could be you problem. I'm not sure.

This was it.

I upgrade to 20 build 49 and everything worked perfectly.

Thank you for your patience my friends!

I really appreciate all the hard work and effort you guys put into this stuff and then helping other users out as well.

[ac777103]

I have a question regarding my current workflow for generating DV for HDR10 titles vs the new option for using Resolve via the script. Currently I run 6-2 first to get a plot and a .bin file which I rename and move to match the source mkv, then run 3-1 and select the MDL input based on what's reported in the 6-2 plot. I guess the .bin file from 6-2 is then used as input scene cuts. If I install Resolve, would I drop 6-2 entirely, or just run 6-2 if I want the plot and the MDL info? In the absence of 6-2 I wonder how the correct option for the MDL prompt in 3-1 is identified. Thanks.

[Kuler087]

Yes, you can still use 6-2 for MDL selection even though it doesn’t matter in CMV4.0. Just don’t use those scene cuts in 3-1, since Resolve’s detection is much better than madVR’s.

[DaMacFunkin]

Hi - Say i had a FEL DV Movie that only has a CMv2.9 RPU is there an advantage to creating a CMv4.0 and if so what is the procedure on DoVi tools to generate a CMv4.0 RPU? Thanks.

[Kuler087]

It depends on how bright the grade is and how bright your display can get. If the grade stays below your TV’s peak brightness, you can use workflow 3-1 to generate new metadata (don’t forget to enable FEL baking), or simply use the Ugoos R9 CMV4.0 append function, which may actually be safer than generating new metadata. It’s considered safer because L1 can be adjusted by the colorist, for example, by blending or copying values between shots with similar brightness levels to avoid fluctuations.

https://i.ibb.co/2738txqX/firefox-MTh9-Jw-N24-I.png

[ac777103]

Yes, you can still use 6-2 for MDL selection even though it doesn’t matter in CMV4.0. Just don’t use those scene cuts in 3-1, since Resolve’s detection is much better than madVR’s.

thanks. If I want to re-do a film that has had P8 DV added via 3-1 already, do I add ignore_rpu or something like that to the filename, or do I have to remove the DV layer?

[Kuler087]

Yes, you add ''ignoremetadata'' in the filename and it should ignore it

findstr /i /c:"ignoremetadata" "%TEMP%filename1.txt" >nul
if %errorlevel%==0 goto :skipinternalshotlist

[Kontrarian]

Yes, you can still use 6-2 for MDL selection even though it doesn’t matter in CMV4.0.

Why does it not matter with CMv4.0?

[Kuler087]

Because CMV4.0 doesn't care about MDL and always acts the same.

[DaMacFunkin]

It depends on how bright the grade is and how bright your display can get. If the grade stays below your TV’s peak brightness, you can use workflow 3-1 to generate new metadata (don’t forget to enable FEL baking), or simply use the Ugoos R9 CMV4.0 append function, which may actually be safer than generating new metadata. It’s considered safer because L1 can be adjusted by the colorist, for example, by blending or copying values between shots with similar brightness levels to avoid fluctuations.

https://i.ibb.co/2738txqX/firefox-MTh9-Jw-N24-I.png

Hi, This is the second time I have tried this 3-1 today, it just seems to 'go to sleep' after a few hours and I can't resume it and need to start again, is there a way to post a log? Or start the process from the last point, it hasn't progressed now for 3 hours?
19120

[Gatorman3385]

Are you on the latest version of cm_analyze?

[SamuriHL]

My first attempt with the Resolve automation wasn't too bad. But it didn't detect the crop values. Or if it did it did something bizarre with them. It stretched the video into the black bars. Never seen that before. I know manual is recommended for that part. I guess now I know why. LOL

[DaMacFunkin]

Are you on the latest version of cm_analyze?
I've just downloaded the atest version ans will try again.

[DaMacFunkin]

I've just downloaded the latest version and will try again.

So I downloaded the latest version and left the job running - over 6 hours to be left with nothing, absolute zero, can anybody explain why this might happen?

frame=176029 fps= 12 q=-0.0 Lsize=161012407KiB time=02:02:21.87 bitrate=179656.2kbits/s speed=0.487x
Access is denied.
Parsing XML metadata...
Error: The system cannot find the file specified. (os error 2)
File not found - Filename- redacted (2017)_DV.xml
The system cannot find the file specified.
Error: The system cannot find the file specified. (os error 2)
Reading generate config file...
Generating metadata: Profile 8.1 (HDR10)...
Generated metadata for 176029 frames
Done.
Error: The system cannot find the file specified. (os error 2)
Error: The system cannot find the file specified. (os error 2)
Parsing RPU file...
Error: The system cannot find the file specified. (os error 2)
Press any key to continue . . .

=================
- MUXING TO MKV -
=================

mkvmerge v91.0 ('Signs') 64-bit
Error: The type of file 'E:\Dolby-Vision-Tools\Filename- Redacted (2017)_Generated.hevc' could not be recognized.
Deleting TEMP folder...


Start time: 23:30:04.17
End time: 6:24:05.84
Time taken: -17:0-5:0-59

The script has been completed. Do you want to quit or go back to main menu (q or m default=q)?

[Kuler087]

Make sure you have enough space on the drive used for your temp/output paths. ProRes files can be hundreds of gigabytes.

Also, post the complete log, not just a portion of it. And as I mentioned earlier, test with a small file first.

[SamuriHL]

So the movie I started with was an IMAX mixed aspect ratio which needs to be done manually. I've done 3 more movies since then and everything is working perfectly. This is awesome. Very nice work!

[Kuler087]

So the movie I started with was an IMAX mixed aspect ratio which needs to be done manually. I've done 3 more movies since then and everything is working perfectly. This is awesome. Very nice work!

thanks :)

[Gatorman3385]

So I downloaded the latest version and left the job running - over 6 hours to be left with nothing, absolute zero, can anybody explain why this might happen?

Have you tried this?

Nice new addition to workflow 3-1 to test. The script can now control Davinci Resolve (with scene cut detection or EDL)... Try with a short file first to see if it works.

[Kuler087]

new version (https://drive.google.com/file/d/128gq8aDUTKA_aT7SQsM9dkjA1EP1sosR/view?usp=drive_link).

write_resolve_dv_generate.py (https://drive.google.com/file/d/1l5sY4yvFvdhq8O1VZ4G73dk_EVGGAlHD/view?usp=drive_link) must be updated too.

There was an issue with 24 or 25 fps videos. 23.976 is fine.

[dkangel]

i'm trying my first movie but i see something that is weird

i put 0/0/276/276 but in resolve the 2*276 are in bottom

https://i.postimg.cc/R0F095Zs/resolve.jpg (https://postimages.org/)

[Gatorman3385]

The prores is cropped before being processed by Resolve. This is normal.

[dkangel]

ok thank you for your answer

[Kuler087]

Right, since we couldn't find a way to set the blanking correctly in Resolve, the ProRes encode is cropped and the analysis runs without any letterboxing, with L5 adjusted before injection.

This might even speed up the process, since both the ProRes encoding and Resolve processing are done on fewer pixels.

[2themax]

I've been using the scripts for a few weeks now and everything is working well aside from the below error. It seems like a trivial thing to do, but it fails on every FEL stream I check. The source is a M2TS file and I am using the latest tools and BETA release. Am I missing a prerequisite for grabbing a PNG from a HEVC encode?

Checking if FEL expands the brightness... This should take only a few seconds...

[ WARN:0@0.020] global loadsave.cpp:278 cv::findDecoder imread_('E:\DoVi.Scripts\temp.folder1\FEL.png'): can't open/read file: check file path/integrity
ERROR=Unable to read the image. Please check the file path.