Dolby Vision now possible through MP4 Mux.

Please post here for issues related to UHD discs
Trees
Posts: 58
Joined: Sat Sep 03, 2022 8:04 am

Re: Dolby Vision now possible through MP4 Mux.

Post by Trees »

I don't know. I cannot reproduce it even with the same exact name/folder you used minus '')''
So maybe your file has an issue?
Perhaps. I'm sending the file to my Mega account, I'll send you the link if you'd like to try it for yourself.

Either way, here's the terminal output with echo on, maybe we can learn something from it?:

Code: Select all

Reordering metadata... Done.
Reading parsed dynamic metadata... Done.
Generating and writing metadata to JSON file... Done.
Parsing RPU file...
Exporting metadata...
Done.
Exporting shots list from a HDR10plus JSON to a text file...

E:\Movie_Tools\DoVi_Scripts>type nul  1>"E:\Movie_Tools\DoVi_Scripts\TEMP.folder77\S05E01.scene.cuts.txt"

E:\Movie_Tools\DoVi_Scripts>"E:\Movie_Tools\DoVi_Scripts\tools\jq-win64.exe" "to_entries | .[] | select(.value.vdr_dm_data.scene_refresh_flag == 1) | .key" "E:\Movie_Tools\DoVi_Scripts\TEMP.folder77\rpu-text.json"  1>"E:\Movie_Tools\DoVi_Scripts\TEMP.folder77\S05E01.scene.cuts.txt"

E:\Movie_Tools\DoVi_Scripts>if NOT ["0"] == ["0"] echo The script failed to make the scene cuts   & pause   & exit

E:\Movie_Tools\DoVi_Scripts>if "y" == "y" (
del "E:\Movie_Tools\DoVi_Scripts\TEMP.folder77\S05E01.scene.cuts.txt"
 type nul  1>"E:\Movie_Tools\DoVi_Scripts\TEMP.folder77\S05E01.scene.cuts.txt"
 echo {  1>"E:\Movie_Tools\DoVi_Scripts\TEMP.folder77\scene.json"
 echo     "mode": 0,  1>>"E:\Movie_Tools\DoVi_Scripts\TEMP.folder77\scene.json"
 echo     "scene_cuts": {  1>>"E:\Movie_Tools\DoVi_Scripts\TEMP.folder77\scene.json"
 echo         "0-0": true  1>>"E:\Movie_Tools\DoVi_Scripts\TEMP.folder77\scene.json"
 echo           }  1>>"E:\Movie_Tools\DoVi_Scripts\TEMP.folder77\scene.json"
 echo }  1>>"E:\Movie_Tools\DoVi_Scripts\TEMP.folder77\scene.json"
 "E:\Movie_Tools\DoVi_Scripts\tools\dovi_tool.exe" editor -i "E:\Movie_Tools\DoVi_Scripts\TEMP.folder77\rpu.h.bin" -j "E:\Movie_Tools\DoVi_Scripts\TEMP.folder77\scene.json" --rpu-out "E:\Movie_Tools\DoVi_Scripts\TEMP.folder77\RPU-flag.added.bin"  1>Nul
 "E:\Movie_Tools\DoVi_Scripts\tools\dovi_tool.exe" export -i "E:\Movie_Tools\DoVi_Scripts\TEMP.folder77\RPU-flag.added.bin" -o "E:\Movie_Tools\DoVi_Scripts\TEMP.folder77\rpu-text.json"
 "E:\Movie_Tools\DoVi_Scripts\tools\jq-win64.exe" "to_entries | .[] | select(.value.vdr_dm_data.scene_refresh_flag == 1) | .key" "E:\Movie_Tools\DoVi_Scripts\TEMP.folder77\rpu-text.json"  1>"E:\Movie_Tools\DoVi_Scripts\TEMP.folder77\S05E01.scene.cuts.txt"
)
Parsing RPU file...
Exporting metadata...
Done.

E:\Movie_Tools\DoVi_Scripts>set shotlist=--shot-list "E:\Movie_Tools\DoVi_Scripts\TEMP.folder77\S05E01.scene.cuts.txt"

E:\Movie_Tools\DoVi_Scripts>"E:\Movie_Tools\DoVi_Scripts\tools\mediainfo.exe" "E:\The Grand Tour\Series 5\S05E01.mkv" --output=Video;%FrameRate%\r\n     *.ts *.mp4 *.mkv *.m2ts *.mov *.hevc *.h265 *.avi  1>"E:\Movie_Tools\DoVi_Scripts\TEMP.folder77\Framerate.txt"

E:\Movie_Tools\DoVi_Scripts>for /F "tokens=1 delims=(,)" %x in (E:\Movie_Tools\DoVi_Scripts\TEMP.folder77\Framerate.txt) do set FPS=%x

E:\Movie_Tools\DoVi_Scripts>set FPS=25.000

E:\Movie_Tools\DoVi_Scripts>if "25.000" == "23.976" set FPS=24000/1001

E:\Movie_Tools\DoVi_Scripts>if "25.000" == "24.000" set FPS=24

E:\Movie_Tools\DoVi_Scripts>if "25.000" == "25.000" set FPS=25

E:\Movie_Tools\DoVi_Scripts>if "25" == "29.970" set FPS=30000/1001

E:\Movie_Tools\DoVi_Scripts>if "25" == "30.000" set FPS=30

E:\Movie_Tools\DoVi_Scripts>if "25" == "50.000" set FPS=50

E:\Movie_Tools\DoVi_Scripts>if "25" == "59.940" set FPS=60000/1001

E:\Movie_Tools\DoVi_Scripts>if "25" == "60.000" set FPS=60

E:\Movie_Tools\DoVi_Scripts>if ".mkv" == ".mov" set prores="E:\The Grand Tour\Series 5\S05E01.mkv"  & goto :skip.prores

E:\Movie_Tools\DoVi_Scripts>"E:\Movie_Tools\DoVi_Scripts\tools\FFMS2\ffmsindex.exe" "E:\The Grand Tour\Series 5\S05E01.mkv" "E:\Movie_Tools\DoVi_Scripts\TEMP.folder77\index.ffindex"
Indexing, please wait... 100%
Writing index... done.

E:\Movie_Tools\DoVi_Scripts>echo LoadPlugin("E:\Movie_Tools\DoVi_Scripts\tools\FFMS2\ffms2.dll")  1>"E:\Movie_Tools\DoVi_Scripts\TEMP.folder77\script.avs"

E:\Movie_Tools\DoVi_Scripts>echo FFVideoSource("E:\The Grand Tour\Series 5\S05E01.mkv", cachefile="E:\Movie_Tools\DoVi_Scripts\TEMP.folder77\index.ffindex")  1>>"E:\Movie_Tools\DoVi_Scripts\TEMP.folder77\script.avs"

E:\Movie_Tools\DoVi_Scripts>"E:\Movie_Tools\DoVi_Scripts\tools\ffmpeg.exe" -i "E:\Movie_Tools\DoVi_Scripts\TEMP.folder77\script.avs" -c:v prores_ks -profile:v 3 -vendor apl0 -qscale:v 4 -pix_fmt yuv422p10le -an -y -hide_banner "E:\Movie_Tools\DoVi_Scripts\TEMP.folder77\S05E01_prores.422.mov"
E:\Movie_Tools\DoVi_Scripts\TEMP.folder77\script.avs: Unknown error occurred

E:\Movie_Tools\DoVi_Scripts>set prores="E:\Movie_Tools\DoVi_Scripts\TEMP.folder77\S05E01_prores.422.mov"

E:\Movie_Tools\DoVi_Scripts>if "NO" == "YES" goto :skipframecount

E:\Movie_Tools\DoVi_Scripts>for /F "delims=" %a in ('E:\Movie_Tools\DoVi_Scripts\tools\mediainfo.exe "--Output=Video;%FrameCount%" "E:\Movie_Tools\DoVi_Scripts\TEMP.folder77\S05E01_prores.422.mov"') do set "frameCount=%a"

E:\Movie_Tools\DoVi_Scripts>echo   1>>"E:\Movie_Tools\DoVi_Scripts\TEMP.folder77\S05E01.scene.cuts.txt"

E:\Movie_Tools\DoVi_Scripts>if "NO" == "YES" set cpu.only=--cpu-only

E:\Movie_Tools\DoVi_Scripts>if exist "E:\Movie_Tools\DoVi_Scripts\Files_for_batch\S05E01.bat" call "E:\Movie_Tools\DoVi_Scripts\Files_for_batch\S05E01.bat"

E:\Movie_Tools\DoVi_Scripts>if [7] == [] set MDL=20

E:\Movie_Tools\DoVi_Scripts>if "7" == "21" set min=1  & set MDL1=1000

E:\Movie_Tools\DoVi_Scripts>if "7" == "7" set min=50  & set MDL1=4000

E:\Movie_Tools\DoVi_Scripts>if "7" == "20" set min=1  & set MDL1=1000

E:\Movie_Tools\DoVi_Scripts>if "7" == "8" set min=50  & set MDL1=4000

E:\Movie_Tools\DoVi_Scripts>if "7" == "30" set min=50  & set MDL1=2000

E:\Movie_Tools\DoVi_Scripts>if "7" == "31" set min=50  & set MDL1=2000

E:\Movie_Tools\DoVi_Scripts>if [0] == [] set right=0

E:\Movie_Tools\DoVi_Scripts>if [0] == [] set left=0

E:\Movie_Tools\DoVi_Scripts>if [0] == [] set right=0

E:\Movie_Tools\DoVi_Scripts>if [0] == [] set bottom=0

E:\Movie_Tools\DoVi_Scripts>E:\Movie_Tools\DoVi_Scripts\tools\cm_analyze.exe --shot-list "E:\Movie_Tools\DoVi_Scripts\TEMP.folder77\S05E01.scene.cuts.txt" -m 7 -r 25 --source-format "pq bt2020" --letterbox 0 0 0 0 --analysis-tuning 1  "E:\Movie_Tools\DoVi_Scripts\TEMP.folder77\S05E01_prores.422.mov" "E:\Movie_Tools\DoVi_Scripts\TEMP.folder77\S05E01_DV.xml"
Copyright (c) 2013-2023 Dolby Laboratories, Inc. All Rights Reserved
09/07/2023/21:24:27.612000000 CPU: Intel(R) Core(TM) i7-6600U CPU @ 2.60GHz (GenuineIntel) [ mmx sse sse2 sse3 ssse3 sse41 sse42 avx avx2 ]
09/07/2023/21:24:27.612000000 cm_analyze: ERROR Unable Open Sequence 'E:\Movie_Tools\DoVi_Scripts\TEMP.folder77\S05E01_prores.422.mov'. Check file permissions are/or existence

E:\Movie_Tools\DoVi_Scripts>"E:\Movie_Tools\DoVi_Scripts\tools\mediainfo.exe" "E:\The Grand Tour\Series 5\S05E01.mkv" --output=Video;%Width%\r\n     *.ts *.mp4 *.mkv *.m2ts *.mov *.hevc *.h265 *.avi  1>"E:\Movie_Tools\DoVi_Scripts\TEMP.folder77\\Width.txt"

E:\Movie_Tools\DoVi_Scripts>"E:\Movie_Tools\DoVi_Scripts\tools\mediainfo.exe" "E:\The Grand Tour\Series 5\S05E01.mkv" --output=Video;%Height%\r\n     *.ts *.mp4 *.mkv *.m2ts *.mov *.hevc *.h265 *.avi  1>"E:\Movie_Tools\DoVi_Scripts\TEMP.folder77\\Height.txt"

E:\Movie_Tools\DoVi_Scripts>for /F "tokens=1 delims=(,)" %x in (E:\Movie_Tools\DoVi_Scripts\TEMP.folder77\\Width.txt) do set Width_path=%x

E:\Movie_Tools\DoVi_Scripts>set Width_path=3840

E:\Movie_Tools\DoVi_Scripts>for /F "tokens=1 delims=(,)" %x in (E:\Movie_Tools\DoVi_Scripts\TEMP.folder77\\Height.txt) do set Height_path=%x

E:\Movie_Tools\DoVi_Scripts>set Height_path=2160

E:\Movie_Tools\DoVi_Scripts>if not "NO" == "NO" set rem_trims=y  & set L2.100=,1

E:\Movie_Tools\DoVi_Scripts>if not "YES" == "NO" set rem_trims=y  & set L2.600=,27,28

E:\Movie_Tools\DoVi_Scripts>if not "YES" == "NO" set rem_trims=y  & set L2.1000=,48,49

E:\Movie_Tools\DoVi_Scripts>echo "S05E01"  1>"E:\Movie_Tools\DoVi_Scripts\TEMP.folder77\filename1.txt"

E:\Movie_Tools\DoVi_Scripts>findstr /c:"KEEPTRIMS" "E:\Movie_Tools\DoVi_Scripts\TEMP.folder77\filename1.txt"  1>Nul

E:\Movie_Tools\DoVi_Scripts>if 1 == 0 set rem_trims=n  & set overwrite.L2=NO

E:\Movie_Tools\DoVi_Scripts>findstr /c:"KEEPAUDIO" "E:\Movie_Tools\DoVi_Scripts\TEMP.folder77\filename1.txt"  1>Nul

E:\Movie_Tools\DoVi_Scripts>if 1 == 0 set mux_all_audio=YES

E:\Movie_Tools\DoVi_Scripts>findstr /c:"DONTMUX" "E:\Movie_Tools\DoVi_Scripts\TEMP.folder77\filename1.txt"  1>Nul

E:\Movie_Tools\DoVi_Scripts>if 1 == 0 set MUX=NO

E:\Movie_Tools\DoVi_Scripts>if "y" == "y" (
echo Removing L2 trims.
 "E:\Movie_Tools\DoVi_Scripts\tools\metafier.exe"  -o "E:\Movie_Tools\DoVi_Scripts\TEMP.folder77\S05E01_DV_trims_removed.xml" --remove-trim L2,27,28,48,49 "E:\Movie_Tools\DoVi_Scripts\TEMP.folder77\S05E01_DV.xml"
 echo Generate RPU from XML
 "E:\Movie_Tools\DoVi_Scripts\tools\dovi_tool.exe" generate --xml "E:\Movie_Tools\DoVi_Scripts\TEMP.folder77\S05E01_DV_trims_removed.xml" --canvas-width 3840 --canvas-height 2160 --rpu-out "E:\Movie_Tools\DoVi_Scripts\TEMP.folder77\rpu.bin"
 set RPU="E:\Movie_Tools\DoVi_Scripts\TEMP.folder77\rpu.bin"
)  ELSE (
"E:\Movie_Tools\DoVi_Scripts\tools\dovi_tool.exe" generate --xml "E:\Movie_Tools\DoVi_Scripts\TEMP.folder77\S05E01_DV.xml" --canvas-width 3840 --canvas-height 2160 --rpu-out "E:\Movie_Tools\DoVi_Scripts\TEMP.folder77\rpu.bin"
 set RPU="E:\Movie_Tools\DoVi_Scripts\TEMP.folder77\rpu.bin"
)
Removing L2 trims.
Copyright (c) 2013-2023 Dolby Laboratories, Inc. All Rights Reserved
09/07/2023/21:24:31.490000000 metafier: ERROR Unable to open Metadata file 'E:\Movie_Tools\DoVi_Scripts\TEMP.folder77\S05E01_DV.xml'
Generate RPU from XML
Parsing XML metadata...
Error: The system cannot find the file specified. (os error 2)

E:\Movie_Tools\DoVi_Scripts>findstr /m "0.0050" "E:\Movie_Tools\DoVi_Scripts\TEMP.folder77\masteringDL.txt"  1>Nul

E:\Movie_Tools\DoVi_Scripts>if 1 == 0 set min=50

E:\Movie_Tools\DoVi_Scripts>findstr /m "0.0001" "E:\Movie_Tools\DoVi_Scripts\TEMP.folder77\masteringDL.txt"  1>Nul

E:\Movie_Tools\DoVi_Scripts>if 0 == 0 set min=1

E:\Movie_Tools\DoVi_Scripts>findstr /m "0.0020" "E:\Movie_Tools\DoVi_Scripts\TEMP.folder77\masteringDL.txt"  1>Nul

E:\Movie_Tools\DoVi_Scripts>if 1 == 0 set min=20

E:\Movie_Tools\DoVi_Scripts>findstr /m "0.0010" "E:\Movie_Tools\DoVi_Scripts\TEMP.folder77\masteringDL.txt"  1>Nul

E:\Movie_Tools\DoVi_Scripts>if 1 == 0 set min=10

E:\Movie_Tools\DoVi_Scripts>findstr /m "0.0000" "E:\Movie_Tools\DoVi_Scripts\TEMP.folder77\masteringDL.txt"  1>Nul

E:\Movie_Tools\DoVi_Scripts>if 1 == 0 set min=0

E:\Movie_Tools\DoVi_Scripts>"E:\Movie_Tools\DoVi_Scripts\tools\dovi_tool.exe" info -s "E:\Movie_Tools\DoVi_Scripts\TEMP.folder77\rpu.bin"  1>"E:\Movie_Tools\DoVi_Scripts\TEMP.folder77\\sum.rpu.json"
Error: The system cannot find the file specified. (os error 2)

E:\Movie_Tools\DoVi_Scripts>type "E:\Movie_Tools\DoVi_Scripts\TEMP.folder77\\sum.rpu.json"   | findstr Frames:  1>"E:\Movie_Tools\DoVi_Scripts\TEMP.folder77\frames.txt"

E:\Movie_Tools\DoVi_Scripts>type "E:\Movie_Tools\DoVi_Scripts\TEMP.folder77\\sum.rpu.json"   | findstr L1  1>"E:\Movie_Tools\DoVi_Scripts\TEMP.folder77\L1.txt"

E:\Movie_Tools\DoVi_Scripts>FOR /F "tokens=4 delims=(:.)" %T IN (E:\Movie_Tools\DoVi_Scripts\TEMP.folder77\L1.txt) DO set maxcll_path=%T

E:\Movie_Tools\DoVi_Scripts>FOR /F "tokens=6 delims=(:.)" %T IN (E:\Movie_Tools\DoVi_Scripts\TEMP.folder77\L1.txt) DO set maxfall_path=%T

E:\Movie_Tools\DoVi_Scripts>FOR /F "tokens=2 delims=:" %T IN (E:\Movie_Tools\DoVi_Scripts\TEMP.folder77\frames.txt) DO set frameCount=%T

E:\Movie_Tools\DoVi_Scripts>echo {  1>"E:\Movie_Tools\DoVi_Scripts\TEMP.folder77\L6.json"

E:\Movie_Tools\DoVi_Scripts>echo    "level6": {  1>>"E:\Movie_Tools\DoVi_Scripts\TEMP.folder77\L6.json"

E:\Movie_Tools\DoVi_Scripts>echo        "max_display_mastering_luminance": 4000,  1>>"E:\Movie_Tools\DoVi_Scripts\TEMP.folder77\L6.json"

E:\Movie_Tools\DoVi_Scripts>echo        "min_display_mastering_luminance": 1,  1>>"E:\Movie_Tools\DoVi_Scripts\TEMP.folder77\L6.json"

E:\Movie_Tools\DoVi_Scripts>echo        "max_content_light_level": ,  1>>"E:\Movie_Tools\DoVi_Scripts\TEMP.folder77\L6.json"

E:\Movie_Tools\DoVi_Scripts>echo        "max_frame_average_light_level":   1>>"E:\Movie_Tools\DoVi_Scripts\TEMP.folder77\L6.json"

E:\Movie_Tools\DoVi_Scripts>echo    }  1>>"E:\Movie_Tools\DoVi_Scripts\TEMP.folder77\L6.json"

E:\Movie_Tools\DoVi_Scripts>echo }  1>>"E:\Movie_Tools\DoVi_Scripts\TEMP.folder77\L6.json"

E:\Movie_Tools\DoVi_Scripts>echo.


E:\Movie_Tools\DoVi_Scripts>echo {  1>"E:\Movie_Tools\DoVi_Scripts\TEMP.folder77\L5.json"

E:\Movie_Tools\DoVi_Scripts>echo    "active_area": {  1>>"E:\Movie_Tools\DoVi_Scripts\TEMP.folder77\L5.json"

E:\Movie_Tools\DoVi_Scripts>echo        "crop": false,  1>>"E:\Movie_Tools\DoVi_Scripts\TEMP.folder77\L5.json"

E:\Movie_Tools\DoVi_Scripts>echo        "presets": [  1>>"E:\Movie_Tools\DoVi_Scripts\TEMP.folder77\L5.json"

E:\Movie_Tools\DoVi_Scripts>echo            {  1>>"E:\Movie_Tools\DoVi_Scripts\TEMP.folder77\L5.json"

E:\Movie_Tools\DoVi_Scripts>echo                "id": 0,  1>>"E:\Movie_Tools\DoVi_Scripts\TEMP.folder77\L5.json"

E:\Movie_Tools\DoVi_Scripts>echo                "left": 0,  1>>"E:\Movie_Tools\DoVi_Scripts\TEMP.folder77\L5.json"

E:\Movie_Tools\DoVi_Scripts>echo                "right": 0,  1>>"E:\Movie_Tools\DoVi_Scripts\TEMP.folder77\L5.json"

E:\Movie_Tools\DoVi_Scripts>echo                "top": 0,  1>>"E:\Movie_Tools\DoVi_Scripts\TEMP.folder77\L5.json"

E:\Movie_Tools\DoVi_Scripts>echo                "bottom": 0  1>>"E:\Movie_Tools\DoVi_Scripts\TEMP.folder77\L5.json"

E:\Movie_Tools\DoVi_Scripts>echo            }  1>>"E:\Movie_Tools\DoVi_Scripts\TEMP.folder77\L5.json"

E:\Movie_Tools\DoVi_Scripts>echo        ],  1>>"E:\Movie_Tools\DoVi_Scripts\TEMP.folder77\L5.json"

E:\Movie_Tools\DoVi_Scripts>echo        "edits": {  1>>"E:\Movie_Tools\DoVi_Scripts\TEMP.folder77\L5.json"

E:\Movie_Tools\DoVi_Scripts>echo            "all": 0  1>>"E:\Movie_Tools\DoVi_Scripts\TEMP.folder77\L5.json"

E:\Movie_Tools\DoVi_Scripts>echo        }  1>>"E:\Movie_Tools\DoVi_Scripts\TEMP.folder77\L5.json"

E:\Movie_Tools\DoVi_Scripts>echo    }  1>>"E:\Movie_Tools\DoVi_Scripts\TEMP.folder77\L5.json"

E:\Movie_Tools\DoVi_Scripts>echo }  1>>"E:\Movie_Tools\DoVi_Scripts\TEMP.folder77\L5.json"

E:\Movie_Tools\DoVi_Scripts>echo {  1>"E:\Movie_Tools\DoVi_Scripts\TEMP.folder77\gen.default.l2.json"

E:\Movie_Tools\DoVi_Scripts>echo     "cm_version": "V40",  1>>"E:\Movie_Tools\DoVi_Scripts\TEMP.folder77\gen.default.l2.json"

E:\Movie_Tools\DoVi_Scripts>echo     "length": ,  1>>"E:\Movie_Tools\DoVi_Scripts\TEMP.folder77\gen.default.l2.json"

E:\Movie_Tools\DoVi_Scripts>echo     "default_metadata_blocks": [  1>>"E:\Movie_Tools\DoVi_Scripts\TEMP.folder77\gen.default.l2.json"

E:\Movie_Tools\DoVi_Scripts>echo         {  1>>"E:\Movie_Tools\DoVi_Scripts\TEMP.folder77\gen.default.l2.json"

E:\Movie_Tools\DoVi_Scripts>echo             "Level2": {  1>>"E:\Movie_Tools\DoVi_Scripts\TEMP.folder77\gen.default.l2.json"

E:\Movie_Tools\DoVi_Scripts>echo                 "target_max_pq": 2081  1>>"E:\Movie_Tools\DoVi_Scripts\TEMP.folder77\gen.default.l2.json"

E:\Movie_Tools\DoVi_Scripts>echo             }  1>>"E:\Movie_Tools\DoVi_Scripts\TEMP.folder77\gen.default.l2.json"

E:\Movie_Tools\DoVi_Scripts>echo         },  1>>"E:\Movie_Tools\DoVi_Scripts\TEMP.folder77\gen.default.l2.json"

E:\Movie_Tools\DoVi_Scripts>echo         {  1>>"E:\Movie_Tools\DoVi_Scripts\TEMP.folder77\gen.default.l2.json"

E:\Movie_Tools\DoVi_Scripts>echo             "Level2": {  1>>"E:\Movie_Tools\DoVi_Scripts\TEMP.folder77\gen.default.l2.json"

E:\Movie_Tools\DoVi_Scripts>echo                "target_max_pq": 2851  1>>"E:\Movie_Tools\DoVi_Scripts\TEMP.folder77\gen.default.l2.json"

E:\Movie_Tools\DoVi_Scripts>echo             }  1>>"E:\Movie_Tools\DoVi_Scripts\TEMP.folder77\gen.default.l2.json"

E:\Movie_Tools\DoVi_Scripts>echo         },  1>>"E:\Movie_Tools\DoVi_Scripts\TEMP.folder77\gen.default.l2.json"

E:\Movie_Tools\DoVi_Scripts>echo         {  1>>"E:\Movie_Tools\DoVi_Scripts\TEMP.folder77\gen.default.l2.json"

E:\Movie_Tools\DoVi_Scripts>echo             "Level2": {  1>>"E:\Movie_Tools\DoVi_Scripts\TEMP.folder77\gen.default.l2.json"

E:\Movie_Tools\DoVi_Scripts>echo                 "target_max_pq": 3079  1>>"E:\Movie_Tools\DoVi_Scripts\TEMP.folder77\gen.default.l2.json"

E:\Movie_Tools\DoVi_Scripts>echo             }  1>>"E:\Movie_Tools\DoVi_Scripts\TEMP.folder77\gen.default.l2.json"

E:\Movie_Tools\DoVi_Scripts>echo         },  1>>"E:\Movie_Tools\DoVi_Scripts\TEMP.folder77\gen.default.l2.json"

E:\Movie_Tools\DoVi_Scripts>echo         {  1>>"E:\Movie_Tools\DoVi_Scripts\TEMP.folder77\gen.default.l2.json"

E:\Movie_Tools\DoVi_Scripts>echo             "Level3": {  1>>"E:\Movie_Tools\DoVi_Scripts\TEMP.folder77\gen.default.l2.json"

E:\Movie_Tools\DoVi_Scripts>echo             }  1>>"E:\Movie_Tools\DoVi_Scripts\TEMP.folder77\gen.default.l2.json"

E:\Movie_Tools\DoVi_Scripts>echo         },  1>>"E:\Movie_Tools\DoVi_Scripts\TEMP.folder77\gen.default.l2.json"

E:\Movie_Tools\DoVi_Scripts>echo         {  1>>"E:\Movie_Tools\DoVi_Scripts\TEMP.folder77\gen.default.l2.json"

E:\Movie_Tools\DoVi_Scripts>echo             "Level8": {  1>>"E:\Movie_Tools\DoVi_Scripts\TEMP.folder77\gen.default.l2.json"

E:\Movie_Tools\DoVi_Scripts>echo                "target_display_index": 1  1>>"E:\Movie_Tools\DoVi_Scripts\TEMP.folder77\gen.default.l2.json"

E:\Movie_Tools\DoVi_Scripts>echo             }  1>>"E:\Movie_Tools\DoVi_Scripts\TEMP.folder77\gen.default.l2.json"

E:\Movie_Tools\DoVi_Scripts>echo         }  1>>"E:\Movie_Tools\DoVi_Scripts\TEMP.folder77\gen.default.l2.json

E:\Movie_Tools\DoVi_Scripts>echo     ]  1>>"E:\Movie_Tools\DoVi_Scripts\TEMP.folder77\gen.default.l2.json"

E:\Movie_Tools\DoVi_Scripts>echo }  1>>"E:\Movie_Tools\DoVi_Scripts\TEMP.folder77\gen.default.l2.json"

E:\Movie_Tools\DoVi_Scripts>echo {  1>"E:\Movie_Tools\DoVi_Scripts\TEMP.folder77\overwrite.l2.json"

E:\Movie_Tools\DoVi_Scripts>echo        "source_rpu": "RPU_generated.bin",  1>>"E:\Movie_Tools\DoVi_Scripts\TEMP.folder77\overwrite.l2.json"

E:\Movie_Tools\DoVi_Scripts>echo        "rpu_levels": [8]  1>>"E:\Movie_Tools\DoVi_Scripts\TEMP.folder77\overwrite.l2.json"

E:\Movie_Tools\DoVi_Scripts>echo }  1>>"E:\Movie_Tools\DoVi_Scripts\TEMP.folder77\overwrite.l2.json"

E:\Movie_Tools\DoVi_Scripts>"E:\Movie_Tools\DoVi_Scripts\tools\dovi_tool.exe" editor -i "E:\Movie_Tools\DoVi_Scripts\TEMP.folder77\rpu.bin" -j "E:\Movie_Tools\DoVi_Scripts\TEMP.folder77\L5.json" --rpu-out "E:\Movie_Tools\DoVi_Scripts\TEMP.folder77\L5.bin"  1>nul
Error: The system cannot find the file specified. (os error 2)

E:\Movie_Tools\DoVi_Scripts>if NOT ["1"] == ["0"] pause
Press any key to continue . . .
RESET_9999
Posts: 2410
Joined: Mon Aug 05, 2019 7:12 pm

Re: Dolby Vision now possible through MP4 Mux.

Post by RESET_9999 »

Trees wrote:
Thu Sep 07, 2023 7:33 pm
Perhaps. I'm sending the file to my Mega account, I'll send you the link if you'd like to try it for yourself.
No need to, I just tried with the original webdl, and no issue. Is your file original from the SMURF ?

sample from my file: https://drive.google.com/file/d/1GKVeL9 ... sp=sharing


Image
Sorry for my English.
G5 / AM6B+ / Denon 7.2.4
DoVi_Scripts
DoVi Playback Devices
Trees
Posts: 58
Joined: Sat Sep 03, 2022 8:04 am

Re: Dolby Vision now possible through MP4 Mux.

Post by Trees »

RESET_9999 wrote:No need to, I just tried with the original webdl, and no issue. Is your file original from the SMURF ?

sample from my file: https://drive.google.com/file/d/1GKVeL9 ... sp=sharing
I don't remember who it's from, not SMURF, though. I've PM'd you the file, just in case.
NiCE77
Posts: 86
Joined: Sat Mar 28, 2020 7:49 am

Re: Dolby Vision now possible through MP4 Mux.

Post by NiCE77 »

RESET_9999 wrote:
Thu Sep 07, 2023 12:09 pm
NiCE77 wrote:
Thu Sep 07, 2023 11:48 am
@RESET_9999

I'm trying the DoViBaker workflow, is it normal that with Ryzen 7 7840HS + RTX 4060 the conversion speed is about 2.4 fps (0.1x) only?
I don't know.
With my i9 13900ks + rtx3070, it's slightly slower than a regular HDR encode, about 6-7fps at slow preset.
It looks like, we can use the DoViBaker in multi thread:

Code: Select all

LoadPlugin("DoViBaker_x64.dll") 
LoadPlugin("DGDecodeNV.dll") 
bl = DGSource("BL.dgi") 
el = DGSource("EL.dgi")
SetFilterMTMode("DoViBaker",2) 
DoViBaker(bl, el, rpu="RPU_FEL.bin") 
ConvertToYUV420(matrix="2020")  
Prefetch(8)
RESET_9999
Posts: 2410
Joined: Mon Aug 05, 2019 7:12 pm

Re: Dolby Vision now possible through MP4 Mux.

Post by RESET_9999 »

NiCE77 wrote:
Fri Sep 08, 2023 6:36 am
It looks like, we can use the DoViBaker in multi thread:

Code: Select all

LoadPlugin("DoViBaker_x64.dll") 
LoadPlugin("DGDecodeNV.dll") 
bl = DGSource("BL.dgi") 
el = DGSource("EL.dgi")
SetFilterMTMode("DoViBaker",2) 
DoViBaker(bl, el, rpu="RPU_FEL.bin") 
ConvertToYUV420(matrix="2020")  
Prefetch(8)
Nice , on my PC, this even allows real-time decoding in MPC.
Sorry for my English.
G5 / AM6B+ / Denon 7.2.4
DoVi_Scripts
DoVi Playback Devices
Mrmorrison
Posts: 33
Joined: Thu Oct 20, 2022 2:13 pm

Re: Dolby Vision now possible through MP4 Mux.

Post by Mrmorrison »

Is there any difference between a P7 Fel film and the same P8 film (or P7 MEL) if the displays on the market have 10bit?
bivoj
Posts: 4
Joined: Thu May 21, 2020 8:37 pm

Re: Dolby Vision now possible through MP4 Mux.

Post by bivoj »

Trees wrote:
Thu Sep 07, 2023 5:52 pm
RESET_9999 wrote:
Thu Sep 07, 2023 4:43 pm
Trees wrote:
Thu Sep 07, 2023 4:36 pm
That's the thing. I processed an MKV earlier, netting me the same error. So I figured an HEVC would be succeed:
Oh yeah, I forgot to mention that input with '')'' in the filename will not work so just rename your file.
Same error. I even removed all special characters. Also the + and the -. Seems like there is an issue with:

Code: Select all

E:\Movie_Tools\DoVi_Scripts\TEMP.folder77\script.avs: Unknown error occurred
Or not?
I had the same message when uninstalled avisynth+. After instalation bellow it is ok.
https://github.com/AviSynth/AviSynthPlus/releases/
My english is very bad, forgive me for that. :-)
NiCE77
Posts: 86
Joined: Sat Mar 28, 2020 7:49 am

Re: Dolby Vision now possible through MP4 Mux.

Post by NiCE77 »

Mrmorrison wrote:
Fri Sep 08, 2023 7:27 pm
Is there any difference between a P7 Fel film and the same P8 film (or P7 MEL) if the displays on the market have 10bit?
Yes, if the FEL expands brightness.
bivoj
Posts: 4
Joined: Thu May 21, 2020 8:37 pm

Re: Dolby Vision now possible through MP4 Mux.

Post by bivoj »

Issue with encode to prores.422.mov as Interlaced, as i wrote in post before solved. After uninstall LAV filters and Avisynth+ and install it again, DoviS_cripts 1.9.2.9 and 1.9.3 works perfectly. Now i get prores Progresive.

If CM_analyse will be very slow, check your prores.422.mov files in mediainfo if is progresive. Probably can't be interlaced. Can you see in previous post. Maybe this will help someone.

Previous post:
viewtopic.php?p=140237#p140237
My english is very bad, forgive me for that. :-)
RESET_9999
Posts: 2410
Joined: Mon Aug 05, 2019 7:12 pm

Re: Dolby Vision now possible through MP4 Mux.

Post by RESET_9999 »

bivoj wrote:
Sat Sep 09, 2023 10:27 am
If CM_analyse will be very slow, check your prores.422.mov files in mediainfo if is progresive. Probably can't be interlaced.
yep, that might be it.
Sorry for my English.
G5 / AM6B+ / Denon 7.2.4
DoVi_Scripts
DoVi Playback Devices
ans40
Posts: 12
Joined: Thu Sep 07, 2023 7:54 am

Re: Dolby Vision now possible through MP4 Mux.

Post by ans40 »

RESET_9999 wrote:
Mon Sep 04, 2023 12:14 pm
CM_Analyse with L1 tuning is the latest version of the Dolby Algo which evolved a lot since Dolby was created. It went from fully dynamic with very aggressive/higher L1 values to lower & less dynamic metadata(10nits/1000nits floor). I wonder if they did that because of the complaints you often hear about DV being darker than HDR10.

With dark movies like Expendables and Prometheus, the difference is small. You'll notice a more significant difference with a brighter movie like in the example below.

Higher L1 means:
- more tone mapping, less clipping, darker image compared to HDR10
Lower L1 means:
-less tone mapping, *more clipping, brighter image closer to HDR10
* more clipping only if your TV is not capable of displaying the actual brightness. Basically, it just means that the image is displayed with less tone mapping, similar to static HDR10.

And here's a direct comparison using my x800m2 and an HDMI capture card:
PQ: https://slow.pics/c/vnEnoTiU
Plot: https://slow.pics/c/3QzuYren

the main benefit of CM:
- you can use official studios scene cuts.
- latest/best version of the Dolby algo
- Black metadata improved
- No need to use some strange resolve settings (1080p cubic)
- CLI tool. can be scripted/batch mode.

Not sure why it's still slow even when you don't touch your PC because I did 5 movies last night in batch mode with workflow (3-2) and some movie does indeed take more time but nothing close to your 7h
These time results include: Prores conversion, CM analyse, demuxing, Injection and mixing.

Image

first movie took about 1h30 to process
2nd 1h20
3rd : took 3h
4th: took 2h
5th: took 1h20
Is there a consensus on whether the new algo is better than Resolve, or is it more preference on how dynamic we want the DV?
skull88
Posts: 69
Joined: Mon Mar 27, 2023 3:08 pm

Re: Dolby Vision now possible through MP4 Mux.

Post by skull88 »

ans40 wrote:
Sat Sep 09, 2023 3:34 pm
Is there a consensus on whether the new algo is better than Resolve, or is it more preference on how dynamic we want the DV?
My personal take: that is like asking do experts all agree that modern phones or cars are better than older models, of which you'll always get differing opinions (this even happens with some older industry guys who are employed to do HDR/DV grading who actively reject/dislike HDR as a format!). What is rational and logical is that the latest version is the one Dolby recommends and has improved over previous iterations so it is the best at this time -- personal opinion nor user consensus is really relevant, even if some movies are still released with old v2.9 algo DV passes at retail or have bad QC or simply happen to be SDR in an HDR container without trims. Unless Dolby buys DaVinci or something lol, Resolve is always going to have a slightly outdated DoVi SDK unless they state otherwise in release notes compared to official Dolby pro tools, not to mention having a brightness lift bug/issue when working with compressed files (even HEVC REMUX->proRes) over studio masters and running analysis at full UHD res (a.k.a. requiring the "cubic downscaling" tweak).

Having said that, you can do whatever you wish with your personal files to match your own preferences, either if you have the Dolby license and/or want to do your own custom grading in DaVinci Resolve, or just use different tuning presets with the recent Dolby cm_analyze version, as RESET states in his script and has a switch for tuning btw. If you can properly A/B test different DV metadata, meaningfully tell a difference on your setup and prefer one methodology/tool over all others, just go ahead and don't worry what anyone else does or states. Objectively, the default recommended tuning with official Dolby cm_analyze v5.4 is the best/most accurate option, provided proper QC'd retail DV is not available and the film does not have variable L5 blanking. That's my take after reading/watching/discussing this for a long time now with others and doing comparisons on my LG C2. What's most important is your TV, calibration and viewing conditions, the differences in how DV is generated are further down the line. Cheers!
ans40
Posts: 12
Joined: Thu Sep 07, 2023 7:54 am

Re: Dolby Vision now possible through MP4 Mux.

Post by ans40 »

skull88 wrote:
Sat Sep 09, 2023 10:33 pm
ans40 wrote:
Sat Sep 09, 2023 3:34 pm
Is there a consensus on whether the new algo is better than Resolve, or is it more preference on how dynamic we want the DV?
My personal take: that is like asking do experts all agree that modern phones or cars are better than older models, of which you'll always get differing opinions (this even happens with some older industry guys who are employed to do HDR/DV grading who actively reject/dislike HDR as a format!). What is rational and logical is that the latest version is the one Dolby recommends and has improved over previous iterations so it is the best at this time -- personal opinion nor user consensus is really relevant, even if some movies are still released with old v2.9 algo DV passes at retail or have bad QC or simply happen to be SDR in an HDR container without trims. Unless Dolby buys DaVinci or something lol, Resolve is always going to have a slightly outdated DoVi SDK unless they state otherwise in release notes compared to official Dolby pro tools, not to mention having a brightness lift bug/issue when working with compressed files (even HEVC REMUX->proRes) over studio masters and running analysis at full UHD res (a.k.a. requiring the "cubic downscaling" tweak).

Having said that, you can do whatever you wish with your personal files to match your own preferences, either if you have the Dolby license and/or want to do your own custom grading in DaVinci Resolve, or just use different tuning presets with the recent Dolby cm_analyze version, as RESET states in his script and has a switch for tuning btw. If you can properly A/B test different DV metadata, meaningfully tell a difference on your setup and prefer one methodology/tool over all others, just go ahead and don't worry what anyone else does or states. Objectively, the default recommended tuning with official Dolby cm_analyze v5.4 is the best/most accurate option, provided proper QC'd retail DV is not available and the film does not have variable L5 blanking. That's my take after reading/watching/discussing this for a long time now with others and doing comparisons on my LG C2. What's most important is your TV, calibration and viewing conditions, the differences in how DV is generated are further down the line. Cheers!
Ohh right yea, I missed how useful the tuning options were on that. All makes sense, thanks!
Mrmorrison
Posts: 33
Joined: Thu Oct 20, 2022 2:13 pm

Re: Dolby Vision now possible through MP4 Mux.

Post by Mrmorrison »

Hi everyone!
Lately I've been imagining videos with profile 8 that played on my Sony TV have some lowering of the Frame.

So I went looking in the DoviScript menus to find something that could fix this very annoying problem.
The function is there! And it's the fps fix (2-1-3).

However, I am curious to know if this problem is caused by something wrong on the part of whoever injects profile 8 into the video.
Can you tell me something?

Thank you!

EDIT:
By any chance, is there a way to understand if the frame needs to be adjusted even before watching the video?
EncodeThis420
Posts: 8
Joined: Wed Aug 02, 2023 6:49 pm

Re: Dolby Vision now possible through MP4 Mux.

Post by EncodeThis420 »

sw5163 wrote:
Thu Sep 07, 2023 3:09 am
EncodeThis420 wrote:
Thu Aug 03, 2023 8:43 pm
bobbymkV wrote:
Thu Aug 03, 2023 8:05 pm


I stopped grabbing p8 hybrids earlier this year when I learned all of this. There is really only one uploader that I trust.
Is there any way that you could share which uploader you trust? Not sure of the rules here or if you can even send private messages. Feel free to decline if I am crossing a line.

But yea. I just don't understand it.....uploaders who used to upload source P5 materials just randomly all switched to uploading P8 files. I have no idea what happened. I legit cannot find any P5 files of recent streamed shows. They're literally all P8 lol. If they know that P8 files are bad form....then why do they keep doing it?
Most dv release groups I know stop releasing P5. There's a Chinese group still releases itunes P5, but I don't know if they were the original uploader or they just modified someone else. And I'm also looking for more trusted release group, their releases sometimes just broke, frame rate slightly off, etc.
Indiana.Jones.and.the.Dial.of.Destiny.2023.2160p.iTunes.WEB-DL.DDP.7.1.Atmos.DV.H.265-DreamHD
I really hope groups could upload P5 and P8.1 separately, instead of just hybrid them. I think with the increase of brightness in screen panel, brightness mapping in RPU is becoming less important. The 11.5 bit color of P5 and 4:2:2 sampling of P7 seems more beneficial.
Why do none of the encoders seem to care that there may be brightness grading differences between the p5 and hdr10 streams?

The chinese group you are referring to only releases itunes p5s? Not from any other source? Don't itunes p5s have screwed up colors?
Post Reply