View Full Version : [DoVi_Scripts] Multi-Function Scripts for Dolby Vision processing and a lot more...
Kuler087
27th August 2025, 00:07
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
Not completely because a lot of Blu-rays have the full enhancement layer encoded at 4000+ nits, while the HDR10 base layer is a trim pass of the HDR12 master (1000 nits or even 600 nits), so brighter TVs benefit more from those discs in DV. But when it comes to tone mapping with dynamic metadata, yeah, it’s pretty much useless on a bright TV.
https://i.ibb.co/S708Bc8f/xnviewmp-An-Gnbo-GBp-L.gif
coopzr
27th August 2025, 04:28
@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.
I have an LG C4 as well. I will never use a CMV2.9 4000nit MDL due to the brightness hit.
There is a very slight dimming with every other MDL with a CMV2.9 RPU. Unless the movie is already very dark I will usually take this tiny brightness hit.
Thank you so much for your help, you save me a lot of useless work :)
Don't sleep on the benefits of FEL!
Check out this banger of a video https://youtu.be/iKUf2GpqoeU ;)
dkangel
27th August 2025, 15:53
Not completely because a lot of Blu-rays have the full enhancement layer encoded at 4000+ nits, while the HDR10 base layer is a trim pass of the HDR12 master (1000 nits or even 600 nits), so brighter TVs benefit more from those discs in DV. But when it comes to tone mapping with dynamic metadata, yeah, it’s pretty much useless on a bright TV.
https://i.ibb.co/S708Bc8f/xnviewmp-An-Gnbo-GBp-L.gif
Thank you for your explanation, always full of interesting things :)
Xillix
29th August 2025, 01:35
This may be a dumb question, but -
Is there a way to get the workflow 7-1 DoVi screenshot baker to output images without the text in the top left corner? Couldn't find anything related in the batch file.
Kuler087
29th August 2025, 01:45
Of course, line 131
::choose if you want OSD information in your screenshot for 7-1 / 7-2 / 7-3 (default= YES)
set screenshot_OSD=YES
en6ads
29th August 2025, 17:07
Coincidentally I have been testing best practice with this movie!
So now in my Jellyfin server for this movie I have: unaltered CM2.9 FEL UHD rip; P7 FEL with generated CM4.0; Baked FEL P8.1 generated CM4.0. I use the P7 CM4.0 on Ugoos, and the single layer CM4.0 on DV laptops and ipads.
It's a lot of work, but now I have what I like. Thank you for your guidance and help.
Not completely because a lot of Blu-rays have the full enhancement layer encoded at 4000+ nits, while the HDR10 base layer is a trim pass of the HDR12 master (1000 nits or even 600 nits), so brighter TVs benefit more from those discs in DV. But when it comes to tone mapping with dynamic metadata, yeah, it’s pretty much useless on a bright TV.
https://i.ibb.co/S708Bc8f/xnviewmp-An-Gnbo-GBp-L.gif
en6ads
13th September 2025, 04:02
Workflow 8 - 2 - 6:
I'm interested in converting my FEL movies to ICtCp Dolby Vision P5. Should be the best way to preserve as much of the 12 bit BL+FEL as possible when a single layer is required.
But it says I need the DEE.exe encoder. I don't have this.
Is anyone here doing this? Do you like the results? Did you pay for a license? Is it worth it? Can I get it free somewhere?
TR-9970X
13th September 2025, 07:39
Workflow 8 - 2 - 6:
I'm interested in converting my FEL movies to ICtCp Dolby Vision P5. Should be the best way to preserve as much of the 12 bit BL+FEL as possible when a single layer is required.
But it says I need the DEE.exe encoder. I don't have this.
Is anyone here doing this? Do you like the results? Did you pay for a license? Is it worth it? Can I get it free somewhere?
You can get DEE here:-
https://customer.dolby.com/content-creation-and-delivery/dolby-encoding-engine-with-dolby-ac-4-v521
As best I can remember, you have to sign up to gain access to these tools, (and other Dolby stuff) it's free. (to sign up, that is)
However, come to think of it, I had to get these elsewhere :(
Kuler087
13th September 2025, 13:37
the dolby encoding engine (https://professional.dolby.com/product/media-processing-and-delivery/dee--dolby-encoding-engine/)(DEE) is not free.
Also, script 8-2-6 uses FFmpeg ProRes, which doesn’t support 12-bit encoding, so even though the DoVi Baker output is 16-bit RGB, the 12-bit data from the FEL is lost during ProRes encoding. The solution would be to use JPEG 2000, but I haven’t found a way to produce files compatible with DEE in FFmpeg.
The encoding quality is as good as x265.exe, if you edit the Dolby Python script to use CRF and custom settings as explained in the workflow notes (their default settings are terrible: no wonder many streaming platforms have worse DV encoding than HDR10). Overall, I find DEE’s HEVC compression slower and less efficient.
en6ads
13th September 2025, 15:13
OK thanks for letting us know. I'll stick with workflow 8 - 2 - 1 for now if the 12 bits FEL data is lost. Hopefully you can find a 12-bit solution in the future!
the dolby encoding engine (https://professional.dolby.com/product/media-processing-and-delivery/dee--dolby-encoding-engine/)(DEE) is not free.
Also, script 8-2-6 uses FFmpeg ProRes, which doesn’t support 12-bit encoding, so even though the DoVi Baker output is 16-bit RGB, the 12-bit data from the FEL is lost during ProRes encoding. The solution would be to use JPEG 2000, but I haven’t found a way to produce files compatible with DEE in FFmpeg.
The encoding quality is as good as x265.exe, if you edit the Dolby Python script to use CRF and custom settings as explained in the workflow notes (their default settings are terrible: no wonder many streaming platforms have worse DV encoding than HDR10). Overall, I find DEE’s HEVC compression slower and less efficient.
tormento
13th September 2025, 20:10
I keep on getting the error:
Calculating per shot MaxFALL threshold...
usage: Percent.target.py [-h] -i INPUT -t THRESHOLD -m {over,under}
Percent.target.py: error: the following arguments are required: -m/--mode
usage: Percent.target.py [-h] -i INPUT -t THRESHOLD -m {over,under}
Percent.target.py: error: the following arguments are required: -m/--mode
usage: Percent.target.py [-h] -i INPUT -t THRESHOLD -m {over,under}
Percent.target.py: error: the following arguments are required: -m/--mode
usage: Percent.target.py [-h] -i INPUT -t THRESHOLD -m {over,under}
Percent.target.py: error: the following arguments are required: -m/--mode
usage: Percent.target.py [-h] -i INPUT -t THRESHOLD -m {over,under}
Percent.target.py: error: the following arguments are required: -m/--mode
Done.
Calculating per shot MaxCLL threshold...
usage: Percent.target.py [-h] -i INPUT -t THRESHOLD -m {over,under}
Percent.target.py: error: the following arguments are required: -m/--mode
usage: Percent.target.py [-h] -i INPUT -t THRESHOLD -m {over,under}
Percent.target.py: error: the following arguments are required: -m/--mode
usage: Percent.target.py [-h] -i INPUT -t THRESHOLD -m {over,under}
Percent.target.py: error: the following arguments are required: -m/--mode
usage: Percent.target.py [-h] -i INPUT -t THRESHOLD -m {over,under}
Percent.target.py: error: the following arguments are required: -m/--mode
usage: Percent.target.py [-h] -i INPUT -t THRESHOLD -m {over,under}
Percent.target.py: error: the following arguments are required: -m/--mode
Done.
usage: maxcll.shot.finder.py [-h] -i INPUT -m {max,min}
maxcll.shot.finder.py: error: the following arguments are required: -m/--mode
usage: maxcll.shot.finder.py [-h] -i INPUT -m {max,min}
maxcll.shot.finder.py: error: the following arguments are required: -m/--mode
Deleting TEMP folder...
I have python installed with all the requirements that I've found in the requirements.txt around the directories.
Any idea?
Kuler087
13th September 2025, 20:40
It looks like you’re using older versions of Percent.target.py and maxcll.shot.finder.py alongside the latest script version. Replace them with these, but you should probably update your entire tools folder.
https://drive.google.com/drive/folders/1LIzRvPi_uXQQi7t3qK9mFHCXGDZBdmyv?usp=sharing
tormento
13th September 2025, 22:55
It looks like you’re using older versions
It's the last version of the complete package.
It happens when running HDR10 Plotter. I haven't tested the others as I don't use them.
Kuler087
13th September 2025, 23:20
Are you using the latest script version? At some point, those two files that calculate the HDR10 measurement stats were updated with a new CLI (--mode) and the error message you get tells you that this new cli is missing. (the following arguments are required: -m/--mode)
tormento
14th September 2025, 15:56
Are you using the latest script version? At some point, those two files that calculate the HDR10 measurement stats were updated with a new CLI (--mode) and the error message you get tells you that this new cli is missing. (the following arguments are required: -m/--mode)
Would be possible that the bug is originated from Windows Terminal set as default instead of normal command prompt? How can I debug it?
Kuler087
14th September 2025, 16:21
I dont know, but the error clearly shows that it's a missing argument(--mode) for the Python script that was added in later versions of the main script. I don't see how you can have the latest script bat + tools pack and get this error.
en6ads
14th September 2025, 18:06
How can I create screenshot comparisons comparing original BL+FEL vs Baked FEL encodes without and NVidia GPU? I tried 7-2 but it says FEL processing disabled because I don't have an NVidia GPU.
Thank you.
Kuler087
14th September 2025, 18:19
The problem is that without an NVIDIA GPU, the script has to use FFMS2 for frame indexing. For some reason, this is incredibly slow when exporting each frame one by one because it re-parses the entire video every time a new frame is requested.
In 8-2-1, this isn’t really a problem because the parsing happens only once and then the encoding proceeds normally. But in the screenshot workflows, I use AviSynth’s trim function with a separate AviSynth script for each frame (to ensure frame accuracy). As a result, for every new frame to export, the whole video is parsed again with ffms2, which makes the process extremely slow and adds a lot of wear on the HDD/SSD.
7-2 FEL processing is disabled for non-nvidia GPU setups, but I think 7-1 isn’t. Instead, it forces ‘quick mode’ when no NVIDIA GPU is detected. This way, the script doesn’t have to parse the entire video for each frame; it parses only a smaller 20-minute sample. Not ideal but better than nothing I guess...
en6ads
15th September 2025, 19:42
7-1 works for FEL without nvidia, but only the first 10 minutes (even if "full mode" is chosen, not quick mode).
To make a comparison I need to: Split the files into 10 minute sections in mkvtoolnix, then 7-1 the FEL file, then 7-2 the FEL baked encode file. And hope the frames match.
7-2 FEL processing is disabled for non-nvidia GPU setups, but I think 7-1 isn’t. Instead, it forces ‘quick mode’ when no NVIDIA GPU is detected. This way, the script doesn’t have to parse the entire video for each frame; it parses only a smaller 20-minute sample. Not ideal but better than nothing I guess...
Kuler087
15th September 2025, 19:51
right , quick mode is forced for non-NVIDIA GPU.
you can delete '& set quickFEL=q' at line 14889 but expect the process to be very slow.
if %errorlevel%==1 echo No Nvidia GPU detected, enabling FFMS2 decoding and forcing quick mode because otherwise the process is too slow & set force_ffms2=YES& set quickFEL=q
Korbus
16th September 2025, 14:41
Hey @R3S3t, when using 7-5 for creating FEL vs BL video comparison, are there anywhere in the config file options to manually set the timestamps for that 19-min quick clip and to pick the frames to be measured/exported outside of that 1000-10000 default interval? I'm asking because in certain movies the algorithm happens to select mostly dark or some fast-moving scenes, where either the difference in brightness between FEL and BL is very small or non-existant (whereas it's significant in bright, daylight scenes), or you can't make much of what's displayed (fast-moving scenes). Thanks in advance for any answer.
Kuler087
16th September 2025, 15:19
Just enter the frames you want manually, and make sure you don’t select any frames after the 19-minute mark if you’re using quick mode. Regardless of the interval, auto mode can and will output random frames that may be blurry or too dark.
You can change the auto-selected frames at line 19,484.
if /i "%mode%"=="a" set quickmode=q& set frame1=2000& set frame2=5000& set frame3=10000& set frame4=15000& set frame5=20000& set frame6=25000& set frame7=27000& set frame8=23000& set frame9=17000& set frame10=7500& goto :LOOP.FELBL.SAMPLES
Korbus
16th September 2025, 15:30
Thanks!
coopzr
20th September 2025, 05:02
@Kuler087
Please remind me again how to generate DV with variable L5? Is this possible in Dovi.Scripts or only in Davinci Resolve?
Kuler087
20th September 2025, 14:46
You have to use Resolve. In my tutorial, it is a movie with variable AR.
Gatorman3385
20th September 2025, 18:32
When converting a file from DV with variable L5 and original metadata to SDR, is it necessary to set the correct blanking within Resolve?
Kuler087
20th September 2025, 19:16
I’m not sure if the dynamic blanking gets imported into Resolve. If it doesn’t, you’ll need to use the values from the IMAX shots; otherwise, the delivery file will crop them.
As for how much it affects SDR tone mapping, I have no idea.
DaMacFunkin
21st September 2025, 08:26
I have just attempted to Dovi Bake a P7 FEL title to P8 with Prores, option 8-2-3 and I get a 683gb MOV file that doesn't contain any DV or HDR flags.
The original file is only 43gb, I am using default Prores settings, do I need to change something first?
If I convert the same Movie with 8-2-1 using Nvenc the file converts properly and at a Normal size.
Kuler087
21st September 2025, 13:44
It's normal. ProRes is an intermediate format for video editing; it's not intended for playback.
If you load it into Resolve or other editing software, it will appear as HDR.
DaMacFunkin
21st September 2025, 22:08
It's normal. ProRes is an intermediate format for video editing; it's not intended for playback.
If you load it into Resolve or other editing software, it will appear as HDR.Ok, so to bake P7 FEL to P8.1 just use Nvenc?
Kuler087
21st September 2025, 23:05
yes 8-2-1 x265.exe or nvenc
en6ads
21st September 2025, 23:47
Profile 10 support possible?
Do you think you may support profile 10 in the future? I tried workflow 1 ("INJECT / EDIT / EXTRACT / INFO / VALIDATE") on a P10 file but it came back saying it's HDR10 only, nothing to do.
Format/Info : AOMedia Video 1
Format profile : Main@L5.0
HDR format : SMPTE ST 2086, Version 1.0, dav1.10.08, BL+RPU, no metadata compression, HDR10 compatible / Dolby Vision, HDR10 compatible / SMPTE ST 2086, HDR10 compatible
Kuler087
22nd September 2025, 00:31
i dont think dovi_tool support av1 yet
dkangel
22nd September 2025, 09:28
Hello
Just a question, with older version of dovi_script qscale was 4 by default for prores encoding, now it's 1
Can you explain why ?
Thank you
Kuler087
22nd September 2025, 11:59
I have just changed the default to the value I use most often.
For HDR to SDR conversion, I use 1
For just generating DV, I use 4
dkangel
22nd September 2025, 12:12
I have just changed the default to the value I use most often.
For HDR to SDR conversion, I use 1
For just generating DV, I use 4
Thank you
1 is better quality then 4 i think so no problem to use 1 also for generating DV by default. Correct ?
Kuler087
22nd September 2025, 12:24
yes but using 1 just for generating DV is a waste of time and space.
dkangel
22nd September 2025, 12:31
yes but using 1 just for generating DV is a waste of time and space.
ok file will be smaller with 4
thank you very much
dkangel
2nd October 2025, 14:50
Hello
I see that Davinvi Resolve 20 is available, do you know if the upgrade worth it just for generate DV ?
Kuler087
2nd October 2025, 15:26
No change related to DV generation in v20.
dkangel
2nd October 2025, 15:48
thank you
Z2697
3rd October 2025, 17:34
Will the videos look visually different after baking? I mean apart from the more accurate scene light level and other playback related things.
Kuler087
3rd October 2025, 17:47
The difference between the BL and EL can be anything. For example in LaLa Land (https://slow.pics/c/m1rRrqSQ), the colors are very different with FEL. In Watchmen (https://slow.pics/c/xlpglnYA), the black get raised with FEL.
In Annihilation (https://slow.pics/c/yBmeMXtA), FEL uncrush the black.
Those are IMO, studio errors and usually, FEL just improves compression or increases brightness or does nothing.
en6ads
5th October 2025, 04:13
I've been playing with Cavernize and the newly released TrueHDD (https://github.com/truehdd/truehdd). It can take a TrueHD Atmos track from a UHD and convert it to Dolby Atmos Master Format (DAMF). This can be read by Davinci Resolve and also the free Dolby Atmos Conversion Tool - however this only converts to either: .atmos, .rpl, .wav(ADM BWF), or .mxf(IMF IAB).
So we can now edit Atmos tracks from the TrueHD Atmos while preserving the Atmos.
The last step I need to find is how to convert DAMF to DDP Atmos without having to pay the $400 per year for Dolby Encoder Engine. One can hope a free solution can be reverse engineered soon. Or do you know of a way?
Thank you.
Kuler087
5th October 2025, 12:41
No, I dont know.
Gatorman3385
5th October 2025, 16:12
The last step I need to find is how to convert DAMF to DDP Atmos without having to pay the $400 per year for Dolby Encoder Engine. One can hope a free solution can be reverse engineered soon. Or do you know of a way?
Thank you.
Look into AWS. There's a small fee for storage and processing.
https://youtu.be/0oEEiR9fRoQ?si=NEFLvFggay0SCfUt
en6ads
5th October 2025, 19:53
Look into AWS. There's a small fee for storage and processing.
https://youtu.be/0oEEiR9fRoQ?si=NEFLvFggay0SCfUt
This looks great. Might be what i'm looking for. I'll test it out and report back.
Gatorman3385
6th October 2025, 23:22
TrueHDD + DEE + Deezy seems to work for me. Without an Atmos speaker setup I can't test it. However, Cavern does show objects moving through a 9.1.6 virtual space.
It may be possible without Deezy, but I don't know the correct DEE syntax.
Hellboy.
8th October 2025, 22:35
@Kuler087
I tried bake FEL for the first time and the process got stuck. What could be the problem?
Donate: https://www.paypal.com/donate/?hosted_button_id=6ML5KUZG9XGB6 Date: 10/07/2025 10:57 PM
Contact: R3S3T_9999@proton.me Version: 3.0.8_MKV
Tutorials: https://www.youtube.com/playlist?list=PLFGpkrmX_eOL2Dre1ZyIJP2uMtcQYH8ql
WARNING! No EAE folder found, disabling 7.1 EC3 encoding (the script will still work correctly).... See line 395
WARNING! "E:\DoVi_Scripts_v3.0.8\tools\metafier.exe" not found. Disabling L2 trims removal and metadata validation . Some workflow will not work but most should be fine...
You can download the Dolby exe here: https://customer.dolby.com/content-creation-and-delivery/dolby-vision-professional-tools-v550
_____ __ ___ _____ _ _
| __ \ \ \ / (_) / ____| (_) | |
| | | | __\ \ / / _ | (___ ___ _ __ _ _ __ | |_ ___
| | | |/ _ \ \/ / | | \___ \ / __| '__| | '_ \| __/ __|
| |__| | (_) \ / | | ____) | (__| | | | |_) | |_\__ \
|_____/ \___/ \/ |_| |_____/ \___|_| |_| .__/ \__|___/
-Author: RESET_9999--------------------------|__|-----------
1) MODE.I= INJECT / EDIT / EXTRACT / INFO / VALIDATE
2) MODE.F= VERIFY SYNC / REMOVER / TRANSFER LEVELS
3) MODE.H= DoVi MAKER from HDR10 (Dolby Algo or MadVR or HDR10+)
4) MODE.7= DoVi Profile 7 Input (MKV/BDMV)
5) MODE.B= DoVi MKV Batch Muxer
6) MODE.P= Plotter (DoVi/HDR10/HLG/SDR)
7) MODE.S= Screenshots & Player
8) MODE.E= Encoders (video and audio)
9) MODE.M= MORE
Choice? [1,2,3,4,5,6,7,8,9]?8
======================
- SELECT A MODE -
======================
1) MODE.A= AUDIO Encoding (DDP, THDAC3, DEE)
2) MODE.V= VIDEO Encoding (x265/Prores/dovi_baker/libplacebo/cm_offline)
Choice? [1,2,3]?2
=========================
- SELECT A WORKFLOW -
=========================
1) Workflow.1= X265: HDR to HDR (DVP7/DVP8/DVP5/HDR10/HLG)
2) Workflow.2= X265: HDR to SDR (DVP7/DVP8/DVP5/HDR10/HLG)
3) Workflow.3= PRORES: HDR to HDR (DVP7/DVP8/DVP5/HDR10/HLG)
4) Workflow.4= PRORES: DV to SDR (Dolby CM_Offline DV Trim Pass delivery)
5) Workflow.5= PRORES: SDR to HDR-100nits
6) Workflow.6= DoVi-P5: P8/P7/prores/MXF to Profile 5 DV HEVC (require DEE.exe)
7) Workflow.7= AQ _strength compression tool
8) Workflow8= back to main menu
Choice? [1,2,3,4,5,6,7,8]?1
============
- ENCODERS -
============
-------------------------------------------------------------------------------------
-- Encode any HDR source(DVP7/DVP5/DVP8/HDR10/HLG) to HDR x265.exe or NVenc.exe. see line 150
-- DV P5/P7/P8 will be converted/injected to DV P8.1
-- FEL Tutorial: https://youtu.be/8BvXqw_cGJE?list=PLFGpkrmX_eOL2Dre1ZyIJP2uMtcQYH8ql
-- Does not support P5 to P5 encoding
-- Encode settings can be configured at line 143-182
-- Require Avisynthplus https://github.com/AviSynth/AviSynthPlus/releases
-- Libplacebo SDR tone mapping and P5/HLG input require a gpu with vulkan support
-------------------------------------------------------------------------------------
Drag and drop a video and press enter...
"D:\Downloads\Sanctum (2011)\Sanctum.2011.2160p.UHD.BluRay.REMUX.mkv"
Do you want to crop? (default=n)
--> YES= y
--> NO= n
Reading input tracks format/id/language...
Done.
Extracting track 0 with the CodecID 'V_MPEGH/ISO/HEVC' to the file 'E:\DoVi_Scripts_v3.0.8\temp.folder31\BL.P7.hevc'. Container format: HEVC/H.265 elementary stream
Progress: 100%
Indexing the HDR10 base layer...
Project
100
Indexing the DV 12bits enhancement layer...
Project
100
Reordering metadata... Done.
=============================SCRIPT==============================================================================
LoadPlugin("E:\DoVi_Scripts_v3.0.8\tools\dgdecnv_242\DGDecodeNV.dll")
LoadPlugin("E:\DoVi_Scripts_v3.0.8\tools\DoViBaker_x64.dll")
LoadPlugin("E:\DoVi_Scripts_v3.0.8\tools\avs_libplacebo.dll")
LoadPlugin("E:\DoVi_Scripts_v3.0.8\tools\avsresize_r21\x64\Release\avsresize.dll")
bl = DGSource("E:\DoVi_Scripts_v3.0.8\temp.folder31\BL.dgi")
el = DGSource("E:\DoVi_Scripts_v3.0.8\temp.folder31\EL.dgi")
SetFilterMTMode("DoViBaker",2)
DoViBaker(bl, el, rpu="E:\DoVi_Scripts_v3.0.8\temp.folder31\RPU_FEL.bin")
z_ConvertFormat(pixel_type="YUV420P10",colorspace_op="rgb:st2084:2020:full=>2020ncl:st2084:2020:limited",dither_type="error_diffusion",resample_filter="spline36",resample_filter_uv="spline36",chromaloc_op="left=>top_left")
Prefetch(8)
INPUT: "D:\Downloads\Sanctum (2011)\Sanctum.2011.2160p.UHD.BluRay.REMUX.mkv"
=================================================================================================================
E:\DoVi_Scripts_v3.0.8>if not "NO" == "YES" if not "0" == "2" "E:\DoVi_Scripts_v3.0.8\tools\x265.exe" --crf 18 --preset slow --profile main10 --level-idc 5.1 --output-depth 10 --colorprim bt2020 --transfer smpte2084 --colormatrix bt2020nc --range limited --chromaloc 2 --hdr10 --hdr10-opt --max-luma 1023 --sar 1 --repeat-headers --aud --hrd --no-open-gop --min-keyint=24 --keyint=240 --no-strong-intra-smoothing --no-rect --vbv-maxrate=160000 --vbv-bufsize=160000 --master-display "G(13250,34500)B(7500,3000)R(34000,16000)WP(15635,16450)L(10000000,1)" --max-cll "586,50" --dolby-vision-profile 8.1 --dolby-vision-rpu "E:\DoVi_Scripts_v3.0.8\temp.folder31\P8.RPU.bin" --input "E:\DoVi_Scripts_v3.0.8\temp.folder31\script.avs" --output "E:\DoVi_Scripts_v3.0.8\Sanctum.2011.2160p.UHD.BluRay.REMUX_DV-FEL_to_DVP8-HDR10.hevc"
avs+ [INFO]: AviSynth+ 3.7.3 (r4003, 3.7, x86_64)
avs+ [INFO]: 3840x2160 fps 24/1 i420p10 sar 1:1 frames 0 - 156261 of 156262
raw [INFO]: output file: E:\DoVi_Scripts_v3.0.8\Sanctum.2011.2160p.UHD.BluRay.REMUX_DV-FEL_to_DVP8-HDR10.hevc
x265 [INFO]: HEVC encoder version 4.0+4+2-c591f33d4 [Mod by Patman]
x265 [INFO]: build info [Windows][GCC 14.2.0][64 bit] 10bit
x265 [INFO]: using cpu capabilities: MMX2 SSE2Fast LZCNT SSSE3 SSE4.2 AVX FMA3 BMI2 AVX2
x265 [INFO]: Main 10 profile, Level-5.1 (High tier)
x265 [INFO]: Thread pool created using 12 threads
x265 [INFO]: Slices : 1
x265 [INFO]: frame threads / pool features : 3 / wpp(34 rows)
x265 [INFO]: Coding QT: max CU size, min CU size : 64 / 8
x265 [INFO]: Residual QT: max TU size, max depth : 32 / 1 inter / 1 intra
x265 [INFO]: ME / range / subpel / merge : star / 57 / 3 / 3
x265 [INFO]: Keyframe min / max / scenecut / bias : 24 / 240 / 40 / 5.00
x265 [INFO]: Lookahead / bframes / badapt : 25 / 4 / 2
x265 [INFO]: b-pyramid / weightp / weightb : 1 / 1 / 0
x265 [INFO]: References / ref-limit cu / depth : 4 / on / on
x265 [INFO]: AQ: mode / str / qg-size / cu-tree : 1 / 1.0 / 32 / 1
x265 [INFO]: Rate Control / qCompress : CRF-18.0 / 0.60
x265 [INFO]: VBV buffer / maxrate / init : 160000 / 160000 / 0.900
x265 [INFO]: tools: limit-modes rd=4 psy-rd=2.00 rdoq=2 psy-rdoq=1.00
x265 [INFO]: tools: rskip mode=2 rskip-edge-threshold=0.05 signhide tmvp
x265 [INFO]: tools: lslices=4 deblock sao selective-sao
[13.7%] 21358/156262 Frames @ 4.458 FPS | 47017 kb/s | 1:19:50 [-8:24:20] | 5230.2 MB [38266 MB]
I have a small request. Can you share an example of the command lines to do the bake FEL. I want to see if the process is not to complicated and maybe in the future create a gui in c#. I checked the code in the "DoVi_Scripts_MKV.bat" but i don't understand some of the terms. It is more easy for me to just see examples of the command lines.
Thanks.
Kuler087
8th October 2025, 22:42
I don’t know, did you accidentally pause the encode? I think on Windows 10, when you click within the command window, it pauses the process, and you have to press Space to resume. For some reason, Windows 11 doesn’t behave the same and doesn’t seem to be able to pause the process.
As for the CMD lines, you already have pretty much everything you need in the example you posted. You just need to demux the BL, EL, and RPU, then index the videos with dgindex, create the AviSynth script, and encode with x265.exe.
avisynth script:
LoadPlugin("E:\DoVi_Scripts_v3.0.8\tools\dgdecnv_242\DGDecodeNV.dll")
LoadPlugin("E:\DoVi_Scripts_v3.0.8\tools\DoViBaker_x64.dll")
LoadPlugin("E:\DoVi_Scripts_v3.0.8\tools\avs_libplacebo.dll")
LoadPlugin("E:\DoVi_Scripts_v3.0.8\tools\avsresize_r21\x64\Release\avsresize.dll")
bl = DGSource("E:\DoVi_Scripts_v3.0.8\temp.folder31\BL.dgi")
el = DGSource("E:\DoVi_Scripts_v3.0.8\temp.folder31\EL.dgi")
SetFilterMTMode("DoViBaker",2)
DoViBaker(bl, el, rpu="E:\DoVi_Scripts_v3.0.8\temp.folder31\RPU_FEL.bin")
z_ConvertFormat(pixel_type="YUV420P10",colorspace_op="rgb:st2084:2020:full=>2020ncl:st2084:2020:limited",dither_type="error_diffusion",resample_filter="spline36",resample_filter_uv="spline36",chromaloc_op="left=>top_left")
Prefetch(8)
x265.exe cmd:
"E:\DoVi_Scripts_v3.0.8\tools\x265.exe" --crf 18 --preset slow --profile main10 --level-idc 5.1 --output-depth 10 --colorprim bt2020 --transfer smpte2084 --colormatrix bt2020nc --range limited --chromaloc 2 --hdr10 --hdr10-opt --max-luma 1023 --sar 1 --repeat-headers --aud --hrd --no-open-gop --min-keyint=24 --keyint=240 --no-strong-intra-smoothing --no-rect --vbv-maxrate=160000 --vbv-bufsize=160000 --master-display "G(13250,34500)B(7500,3000)R(34000,16000)WP(15635,16450)L(10000000,1)" --max-cll "586,50" --dolby-vision-profile 8.1 --dolby-vision-rpu "E:\DoVi_Scripts_v3.0.8\temp.folder31\P8.RPU.bin" --input "E:\DoVi_Scripts_v3.0.8\temp.folder31\script.avs" --output "E:\DoVi_Scripts_v3.0.8\Sanctum.2011.2160p.UHD.BluRay.REMUX_DV-FEL_to_DVP8-HDR10.hevc"
vBulletin® v3.8.11, Copyright ©2000-2026, vBulletin Solutions Inc.