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

[Kontrarian]

update cm_analyze. Fixed in v5.6.1


P.s. RESET, maybe you can post a note in your GitHub release saying to update cm_analyze? I think this is the 3rd or 4th user to report this issue (myself included)

Got the latest cm_analyze from Dolby and that fixed it.
Thank you for pointing me in the right direction!

[TR-9970X]

V5.6.2 beta is the latest available from Dolby.

[DMD]

V5.6.2 beta is the latest available from Dolby.
it is the beta version

[Kontrarian]

it is the beta version

I got the BETA. Do you think that's an issue? It's been working fine for me.


What's new in v5.6.2 Beta

Changes in this version
Fixed a retiming bug where 2.0.5 XMLs (CM 2.9) failed due to missing CM 4 metadata.

Added missing parameter for the ./metafier -h and ./metafier --help-advanced outputs in the user guide.

[DMD]

I got the BETA. Do you think that's an issue? It's been working fine for me.
I don't know, I always wait for stable versions.

[Kontrarian]

When using 3-1, what logic should we be using when choosing tuning?


Which Tuning do you want to use? (default=3) (0= darkest / 5= brightest)

--> 0 = Old legacy mode (not recommended)
--> 1= Most Highlight Detail/Most Mapping
--> 2= More Highlight Detail/More Mapping
--> 3= Balanced (default)
--> 4= Less Highlight Detail/Less Mapping
--> 5= Least Highlight Detail/Least Mapping

[Kuler087]

The best/safest tuning is:
1= Most Highlight Detail/Most Mapping

The other options are brighter but may have clipping if the content is brighter than your TV

example https://slow.pics/c/jzYzSr3g

[Kontrarian]

Gothca!
So I'm going through my MCU titles right now and most of them are 400~600 nits so T3 (default) is completely safe too for these titles right?

[Kuler087]

yes, if the content is within your TV capabilities, the tunning doesnt matter.

[en6ads]

The best/safest tuning is:
1= Most Highlight Detail/Most Mapping

The other options are brighter but may have clipping if the content is brighter than your TV

example https://slow.pics/c/jzYzSr3g

Suggest update the the tuning menu with this info, something like:

--> 0 = Old legacy mode (not recommended)
--> 1= Most Highlight Detail/Most Mapping (Best option, recommended for most)
--> 2= More Highlight Detail/More Mapping
--> 3= Balanced (default, but can clip if the content is brighter than your TV)

[Kuler087]

good suggestion

[Kontrarian]

So in what situation would one reasonably choose anything other than T1 then?

[Kuler087]

So in what situation would one reasonably choose anything other than T1 then?

Someone who wants DV to be brighter.

[Kontrarian]

Meh, I only watch movies at night with all the lights out so I don't need anything brighter, so I'll just use T1 moving forward.
Some of these movies switch from dark scenes to bright scenes pretty quick and I feel like my retinas are burning already!

[Kuler087]

“DV to be brighter” was not the right way to phrase it. What I should have said is “someone who wants the tone mapping to be less aggressive (less dim).”

The tunings only control tone-mapping aggressiveness. They do not make DV brighter overall; they simply reduce how much the image is dimmed when tone mapping is required.

[Kontrarian]

That makes more sense; thank you for clarifying that.
I really appreciate all your hard work and input!

[Gatorman3385]

Running 6-8 (Waveform) on a THD Atmos to DDP+JOC file I only get 6 channels, no objects plotted. Objects are visible when viewed with Cavern. If I run the same workflow on a DDP+JOC from an official DDP+JOC I get 6 channels plus objects plotted. Is this normal.

[Kuler087]

Do you have truehdd.exe in your tools folder?
And the mkv first audio track must be Atmos, IIRC.

[Gatorman3385]

...the mkv first audio track must be Atmos, IIRC.

This is the fix. Thanks.

[Kontrarian]

Twice in a row 3-1 has given me a bad file on Thor: Ragnarok.
Made remux with MakeMKV v1.18.3 as usual with no errors.
Ran it through 3-1 and the script says it's complete but then I'm left with a 23GB file that doesn't play.

What the script gives me afterwards:

General
Unique ID : 197453132136988307197577590176830436075 (0x948C1708E6A3E7002B5131FE098FB2EB)
Complete name : D:\DoVi.Scripts\TR_DV.mkv
Format : Matroska
Format version : Version 1
File size : 23.3 GiB
Overall bit rate mode : Variable
Frame rate : 23.976 FPS
Title : Thor: Ragnarok
Writing application : mkvmerge 91.0 ('Signs') 64-bit
Writing library : libebml v1.4.5 + libmatroska v1.7.1
SegmentSizeIsZero : Yes
Conformance errors : 1
Matroska : Yes
General compliance : File size is less than expected size (actual 25040001883, expected >=72057594037927987, offset 0x34)

Video
ID : 1
Format : HEVC
Format/Info : High Efficiency Video Coding
Format profile : Main 10@L5.1@High
HDR format : 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
Codec ID : V_MPEGH/ISO/HEVC
Width : 3 840 pixels
Height : 2 160 pixels
Display aspect ratio : 16:9
Frame rate mode : Constant
Frame rate : 23.976 (24000/1001) FPS
Color space : YUV
Chroma subsampling : 4:2:0 (Type 2)
Bit depth : 10 bits
Writing library : ATEME Titan File 3.8.13 (4.8.13.0)
Default : Yes
Forced : No
Color range : Limited
Color primaries : BT.2020
Transfer characteristics : PQ
Matrix coefficients : BT.2020 non-constant
Mastering display color primaries : Display P3
Mastering display luminance : min: 0.0000 cd/m2, max: 1000 cd/m2

Audio #1
ID : 2
Format : MLP FBA 16-ch
Format/Info : Meridian Lossless Packing FBA with 16-channel presentation
Commercial name : Dolby TrueHD with Dolby Atmos
Codec ID : A_TRUEHD
Bit rate mode : Variable
Maximum bit rate : 5 889 kb/s
Channel(s) : 8 channels
Channel layout : L R C LFE Ls Rs Lb Rb
Sampling rate : 48.0 kHz
Frame rate : 1 200.000 FPS (40 SPF)
Bit depth : 24 bits
Compression mode : Lossless
Title : Dolby TrueHD 7.1 Atmos
Language : English
Default : Yes
Forced : No
Number of dynamic objects : 13
Bed channel count : 1 channel
Bed channel configuration : LFE

Audio #2
ID : 3
Format : AC-3
Format/Info : Audio Coding 3
Commercial name : Dolby Digital
Codec ID : A_AC3
Bit rate mode : Constant
Bit rate : 640 kb/s
Channel(s) : 6 channels
Channel layout : L R C LFE Ls Rs
Sampling rate : 48.0 kHz
Frame rate : 31.250 FPS (1536 SPF)
Compression mode : Lossy
Title : Dolby Digital 5.1
Language : English
Service kind : Complete Main
Default : No
Forced : No
Dialog Normalization : -27 dB
compr : -0.56 dB
dynrng : -0.42 dB
Center mix level (cmixlev) : -3.0 dB
Surround mix level (surmixlev) : -6 dB
dmixmod : Lo/Ro
ltrtcmixlev : -3.0 dB
ltrtsurmixlev : -4.5 dB
lorocmixlev : -3.0 dB
lorosurmixlev : -4.5 dB
Dialogue normalization, average : -27 dB
Dialogue normalization, minimum : -27 dB
Dialogue normalization, maximum : -27 dB

Text
ID : 4
Format : PGS
Muxing mode : zlib
Codec ID : S_HDMV/PGS
Codec ID/Info : Picture based subtitle format used on BDs/HD-DVDs
Title : English SDH PGS
Language : English
Default : Yes
Forced : No




The script does have this error in it:
Error: Could not write to the destination file: 112 (T)

I have 290GB of free space.

Full output from the script: https://pastebin.com/c10ZeR68

Temp folder is deleted by the script.
All I have besides the bad TR_DV.mkv is:

TR.mkv.measurements 108.9MB
TR_Generated_T3.bin 40.6MB
TR_Generated_T3.xml 4.3MB


If you want to look at the measurements, bin, or xml file they are hosted here: https://limewire.com/d/NixD3#i8gvNqbE6B

[Kuler087]

Your output/temp does not have enough free space...

The ProRes intermediate alone can be larger than 290gb

[Kontrarian]

So the prores took up all my free space but 23GB and then it runs out of space making the final MKV?
I thought the script made the prores, then generated the DV, then deleted the prores, then applied the DV to the original file.

So if the xml and bin I am left with are fine then and I can just inject that into the the original I would think.
So I did that and it gave me a presumably okay file but I saw a lot of warnings.


Copyright (c) 2013-2026 Dolby Laboratories, Inc. All Rights Reserved
02/28/2026/18:55:12.666000000 plugin_manager: [33;1mWARNING[0m [Kplugin does not contain dlb_plugin_file_io_init_v1
02/28/2026/18:55:12.698000000 plugin_manager: [33;1mWARNING[0m [Kplugin does not contain dlb_plugin_file_io_init_v1
02/28/2026/18:55:12.713000000 plugin_manager: [33;1mWARNING[0m [Kplugin does not contain dlb_plugin_file_io_init_v1
02/28/2026/18:55:12.713000000 plugin_manager: [33;1mWARNING[0m [Kplugin does not contain dlb_plugin_file_io_init_v1
02/28/2026/18:55:12.713000000 plugin_manager: [33;1mWARNING[0m [Kplugin does not contain dlb_plugin_file_io_init_v1
02/28/2026/18:55:12.713000000 plugin_manager: [33;1mWARNING[0m [Kplugin does not contain dlb_plugin_file_io_init_v1
02/28/2026/18:55:12.729000000 plugin_manager: [33;1mWARNING[0m [Kplugin does not contain dlb_plugin_file_io_init_v1
02/28/2026/18:55:12.745000000 plugin_manager: [33;1mWARNING[0m [Kplugin does not contain dlb_plugin_file_io_init_v1
02/28/2026/18:55:13.844000000 Metadata: [32;1mINFO[0m [KValidation Summary:


Is that anything of concern or just ignore it?

Here's the full script run: https://pastebin.com/vZTmkuvU

Let me know what you think.

[Kuler087]

the temp folder is deleted only when the script has finished and you should never use the last 10% of a hdd/ssd

your xml is probably ok and those warnings show up just in the old cm_analyze.

[dkangel]

“DV to be brighter” was not the right way to phrase it. What I should have said is “someone who wants the tone mapping to be less aggressive (less dim).”

The tunings only control tone-mapping aggressiveness. They do not make DV brighter overall; they simply reduce how much the image is dimmed when tone mapping is required.

So with a TCL 85C9K 4500-5000 nits, balanced is the best choice ?

[Kuler087]

No, it doesn’t matter how bright your TV is. The tuning only comes into play when the content exceeds your TV’s peak brightness capability.

On a 5,000-nit TV, most content can be displayed without any tone mapping, so the tuning rarely makes a difference in practice.

[dkangel]

clear to me, thank you :)

[Kontrarian]

the temp folder is deleted only when the script has finished and you should never use the last 10% of a hdd/ssd

your xml is probably ok and those warnings show up just in the old cm_analyze.

Yeah, I cleared up some more space and did it again from scratch then compared the XMLs in Beyond Compare and they were identical (besides the UniqueIDs).

[Rootdown4594]

For baking FEL (8-2-1) and disregarding file size.

What would have to be changed in lines 149-172 to achieve a lossless x265 file for both X265 and NVENC encoders?

[Kuler087]

x265: the script default settings(crf-15 + slow) are already pretty much lossless, but if you want better, use the ''slower'' preset + a lower CRF value.
Nvenc: AFAIK, this will never be lossless, no matter what setting you use.

[Rootdown4594]

What about using a CRF of 0 and a much faster preset?

again, disregarding file size. I'm looking for speed more than anything.

[Kuler087]

i dont know about a much faster preset but yeah, CRF-0 + slow preset should be lossless

[Xillix]

Ran into an unusual error message for the first time yesterday! As I do often I was using the madVR HDR brightness measurement function, in this case on a rip of Dungeons & Dragons: Honor Among Thieves. I'd already plotted the Dolby Vision metadata without issue, but trying to measure brightness resulted in the following output:

For some reason, measurement didn't produce a "complete" file.
Reading generate config file...
Parsing madVR measurment file...
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)

Then that error repeated several times and the process ultimately failed, leaving only a file in the source directory of the video file with a .incomplete extension. Retried it a few times with identical results.

Any ideas on troubleshooting?

[Kuler087]

Yes sometimes madvr fails to measure a video.

you can try converting to ProRes as a workaround.

[Kuler087]

I wonder if Dolby finally fixed the slow ProRes processing.

In the latest DV professional tools release notes:
''Corrects a latency issue when reading long QuickTime MOV files.''

[Xillix]

Yes sometimes madvr fails to measure a video.

you can try converting to ProRes as a workaround.

Thanks for the suggestion. I actually got an error that halted the attempted ProRes conversion too, about clip length not matching the RPU.

I did eventually get things to work, so in the unlikely event anyone encounters my specific issue - when I ripped the disc via MakeMKV, there were two playlists that appeared essentially the same, but one had chapter markers included and the other did not. I originally ripped the version with chapter markers, which is the one that gave me all the errors. I re-did the rip and selected the playlist without chapter markers, and for whatever reason the madVR brightness measurement worked on that file immediately.

[Gatorman3385]

I wonder if Dolby finally fixed the slow ProRes processing.

Sure looks like it. (1:47:00 long movie)

Workflow 3-1

Ryzen 9 9900X, RTX 3070 8GB, 64GB DDR5 6000 CL30

https://imgur.com/VVv8cDZ.png

[Kuler087]

yep, looks faster on mine too. :D

[ac777103]

running 3.12 BETA, have an issue with Lawrence of Arabia I've not encountered before. I joined parts 1 and 2 together with mkvtoolnix, my base HDR10 mkv seems fine. Ran 6-2 without issue, unsurprisingly not a particularly bright film, but I thought I'd run 3-1 anyway. I noticed that the initial call to ffmpeg showed some warnings: an invalid block message and could not find codec parameters for stream 2 (subtitle hdmv_pgs....) unspecified size. Then, the pro-res creation step ran at warp speed, and then I got an endless stream of messages featuring constant repeats of "skipping NAL unit 63". I quit and it looks like no proper prores file was created. Any ideas?

[Kuler087]

Sounds like a corrupted source. You could try converting it to prores without ffms2 but I doubt it will work.
line 317 set disable_indexing=YES
Workflow 8-2-3

[ac777103]

Something odd here. Discs 1 and 2 of Lawrence of Arabia are DV. MediaInfo, Kodi and my TV all report DV when played from mkv. But if I open disc 2 with DoviScripts, it says it's HDR10, even though other tools identify it as DV. I must have seen that and assumed there was no DV at all. DS reports MEL for disc 1.

[Kuler087]

not much I can do without a sample... I dont have this movie, I hate old movies.

[en6ads]

not much I can do without a sample... I dont have this movie, I hate old movies.

I have this one, and had no problems using mkvtoolnix to combine the 2 disks, then use your scripts to convert from MEL to 8.1 CM2.9.

I'm not sure what the problem could have been.

They could try to do whatever scripting they need on each disk part separately first, then lastly combine the outputs with mkvtoolnix into a single file.

[ac777103]

I too was able to join the parts and convert to P8, the odd thing being that part 2 on its own was identified by DS as HDR10 while other tools reported P7. If you still have your part 2 file could you try that? I'm done with it as I've now got a seamless file for the whole film without either of the 4min overtures at the startof each disc (not my cup of tea).

[Kuler087]

The script uses mediainfo to determine if DV is present. If no flag is present in the rip, then the script assumes HDR10.

[Kontrarian]

yep, looks faster on mine too. :d

awesome!

[Kontrarian]

I too was able to join the parts and convert to P8, the odd thing being that part 2 on its own was identified by DS as HDR10 while other tools reported P7. If you still have your part 2 file could you try that? I'm done with it as I've now got a seamless file for the whole film without either of the 4min overtures at the startof each disc (not my cup of tea).

You don't need to merge the two discs. I just ripped both discs to their own files and put put ".disc1.mkv" and ".disc2.mkv" at the end of each file name. Kodi will then treat them as one in your library. Disc 1 fades out to an "INTERMISSION" title on screen, and yes, disc 2 has 4 minutes of black screen at the beginning but nothing a few clicks on the right direction of the remote doesn't fix.

Media info for my disc 2 if it helps you at all:


General
Unique ID : 265577840394736673999258513544773520735 (0xC7CC6E7949747FC830E6439B6FB64D5F)
Complete name : N:\Movies\Lawrence of Arabia (1962) 60th Anniversary Limited Edition [UHD.DV.Atmos.Remux].disc2.mkv
Format : Matroska
Format version : Version 2
File size : 37.7 GiB
Duration : 1 h 27 min
Overall bit rate mode : Variable
Overall bit rate : 61.5 Mb/s
Frame rate : 23.976 FPS
Title : Lawrence of Arabia
Encoded date : 2022-06-18 22:01:26 UTC
Writing application : MakeMKV 1.16.7 win(x64-release)
Writing library : libmakemkv 1.16.7 (1.3.10/1.5.2) win(x64-release)

Video
ID : 1
ID in the original source medium : 4113 (0x1011)
Format : HEVC
Format/Info : High Efficiency Video Coding
Format profile : Main 10@L5.1@High
HDR format : 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
Codec ID : V_MPEGH/ISO/HEVC
Duration : 1 h 27 min
Bit rate : 58.1 Mb/s
Width : 3 840 pixels
Height : 2 160 pixels
Display aspect ratio : 16:9
Frame rate mode : Constant
Frame rate : 23.976 (24000/1001) FPS
Color space : YUV
Chroma subsampling : 4:2:0 (Type 2)
Bit depth : 10 bits
Bits/(Pixel*Frame) : 0.292
Stream size : 35.5 GiB (94%)
Title : Lawrence of Arabia
Language : English
Default : Yes
Forced : No
Color range : Limited
Color primaries : BT.2020
Transfer characteristics : PQ
Matrix coefficients : BT.2020 non-constant
Mastering display color primaries : Display P3
Mastering display luminance : min: 0.0001 cd/m2, max: 1000 cd/m2
Maximum Content Light Level : 774 cd/m2
Maximum Frame-Average Light Level : 263 cd/m2
Original source medium : Blu-ray

Audio #1
ID : 2
ID in the original source medium : 4352 (0x1100)
Format : MLP FBA 16-ch
Format/Info : Meridian Lossless Packing FBA with 16-channel presentation
Commercial name : Dolby TrueHD with Dolby Atmos
Codec ID : A_TRUEHD
Duration : 1 h 27 min
Bit rate mode : Variable
Bit rate : 2 736 kb/s
Maximum bit rate : 4 374 kb/s
Channel(s) : 8 channels
Channel layout : L R C LFE Ls Rs Lb Rb
Sampling rate : 48.0 kHz
Frame rate : 1 200.000 FPS (40 SPF)
Bit depth : 24 bits
Compression mode : Lossless
Stream size : 1.67 GiB (4%)
Title : Dolby TrueHD 7.1 Atmos
Language : English
Default : Yes
Forced : No
Original source medium : Blu-ray
Number of dynamic objects : 11
Bed channel count : 1 channel
Bed channel configuration : LFE

Audio #2
ID : 3
ID in the original source medium : 4352 (0x1100)
Format : AC-3
Format/Info : Audio Coding 3
Commercial name : Dolby Digital
Codec ID : A_AC3
Duration : 1 h 27 min
Bit rate mode : Constant
Bit rate : 640 kb/s
Channel(s) : 6 channels
Channel layout : L R C LFE Ls Rs
Sampling rate : 48.0 kHz
Frame rate : 31.250 FPS (1536 SPF)
Compression mode : Lossy
Stream size : 401 MiB (1%)
Title : Dolby Digital 5.1
Language : English
Service kind : Complete Main
Default : No
Forced : No
Original source medium : Blu-ray
Dialog Normalization : -31 dB
compr : -0.28 dB
Center mix level (cmixlev) : -3.0 dB
Surround mix level (surmixlev) : -3 dB
Dialogue normalization, average : -31 dB
Dialogue normalization, minimum : -31 dB
Dialogue normalization, maximum : -31 dB

Text #1
ID : 4
ID in the original source medium : 4769 (0x12A1)
Format : PGS
Codec ID : S_HDMV/PGS
Codec ID/Info : Picture based subtitle format used on BDs/HD-DVDs
Duration : 1 h 18 min
Bit rate : 25.1 kb/s
Frame rate : 0.336 FPS
Count of elements : 1592
Stream size : 14.2 MiB (0%)
Title : English PGS
Language : English
Default : Yes
Forced : No
Original source medium : Blu-ray

Text #2
ID : 5
ID in the original source medium : 4768 (0x12A0)
Format : PGS
Codec ID : S_HDMV/PGS
Codec ID/Info : Picture based subtitle format used on BDs/HD-DVDs
Duration : 1 h 19 min
Bit rate : 27.7 kb/s
Frame rate : 0.370 FPS
Count of elements : 1762
Stream size : 15.7 MiB (0%)
Title : English SDH PGS
Language : English
Default : No
Forced : No
Original source medium : Blu-ray

Menu
00:00:00.000 : en:Chapter 01
00:10:42.224 : en:Chapter 02
00:18:11.048 : en:Chapter 03
00:24:12.993 : en:Chapter 04
00:31:48.489 : en:Chapter 05
00:39:34.663 : en:Chapter 06
00:46:02.509 : en:Chapter 07
00:54:55.000 : en:Chapter 08
00:58:46.648 : en:Chapter 09
01:08:13.672 : en:Chapter 10
01:18:21.029 : en:Chapter 11
01:23:04.354 : en:Chapter 12

[en6ads]

You don't need to merge the two discs.

That's true. You don't need to.

It's personal preference. I prefer 1 file per movie. And if it's MEL (like it is for LoA), I also convert to P8.1 so it's easily playable on iPads, etc.

[dkangel]

yep, looks faster on mine too. :D

I confirm, much way faster now but i'm ok with resolve method so....

Just a question, when the script ask for Mastering Display Luminance/primaries, we have to calcul it with workflow 6-2 like with resolve method ?

[Kuler087]

I confirm, much way faster now but i'm ok with resolve method so....


Yes, CM_analyze and cm_offline are finally usable: much faster and far more stable.
Personally, I’ll only use Resolve when my source doesn’t have original scene cuts(Resolve has better SC detection than madvr 3-1); otherwise, I’ll stick with CM for everything OSC since it’s fully automated and supports batch processing.

I’ve also stopped using Resolve for my HDR/DV→SDR 100-nit trim pass encodes. The latest dovi_scripts can now handle encoding the trim pass directly to x265 or x264.
I also added FEL support in 3-1 (NVIDIA only for now), but I haven’t had time to test these two new features yet.

:: Select if you want workflow 8-2-4 to encode SDR to hevc or avc (default = NO)
set encodeSDR_824=NO
:: Bake FEL and upgrade a P7 rpu with new metadata in workflow 3-1 (default = NO)
set Bake_FEL_31=NO


Just a question, when the script ask for Mastering Display Luminance/primaries, we have to calcul it with workflow 6-2 like with resolve method ?

In CMv4.0, the MDL doesn’t matter at all, so any selection will work but I still choose the MDL based on 6-2 measurements.

[dkangel]

Thanks for all your explanations