www.makemkv.com

RESET_9999 wrote: Fri Dec 15, 2023 4:09 pm

HotFudge wrote: Fri Dec 15, 2023 3:51 pm How do I use the original scene cuts with your script 3-1

its all automated but read the instructions on the github webpage for more info: MODE.H (3)

looks like Resolve the way to go. Do you discard the L2 100nit when you generate L1 Resolve metadata? or only discard the L2 600-1000 trims?

The script discard 600-1000nits and keep 100nits by default but you can control which trims is kept or removed


::Choose if you want to remove the 100 L2 trim pass. (only valid for 1-1xml and 3-1) (require the dolby metafier) (default=NO)
set remove_100=NO
::Choose if you want to remove the 600 L2 trim pass.(only valid for 1-1xml and 3-1) (require the dolby metafier)(default=YES)
set remove_600=YES
::Choose if you want to remove the 1000 L2 trim pass.(only valid for 1-1xml and 3-1) (require the dolby metafier) (default=YES)
set remove_1000=YES

Which tools have implemented the new analysis tuning?
As of September 2023, the new analysis tuning is supported in DaVinci Resolve Studio version 18.6 and later. Other partner products such as Filmlight Baselight and Colorfront Transkoder will implement the new analysis tuning in their upcoming versions.

Are those changes considered as new Dolby Vision CM version?
No. This update only affects how the L1 metadata is generated and can be considered an update to the existing CM version 4.0.

RESET_9999 wrote: Fri Dec 15, 2023 4:33 pm yes, my script use the same Dolby algo. You can control the tuning in the script main settings

:: choose the L1 analysis tuning... Choices are: old=0 - Most Highlight Detail/Most Mapping=1(default) - More Highlight Detail/More Mapping=2 - Balanced=3 - Less Highlight Detail/Less Mapping=4 - Least Highlight Detail/Least Mapping=5
set L1_Tuning=1

RESET_9999 wrote: Mon Dec 18, 2023 7:20 pm never i guess.

RESET_9999 wrote: Thu Dec 21, 2023 12:06 am use 281/280, L5 works just fine with non-even or non mod 2 crop.
in fact, when you select 2.39(not manually) in resolve you get L5 : 276/277

RESET_9999 wrote: Thu Dec 21, 2023 12:00 pm In the script 3-1 it works properly, I just tested it.
If you do the xml in resolve , you have to edit L5 when you inject in 1-1 because otherwise, the dovi_tool cannot know which side is 281 or 280 but the analysis itself in resolve is correct.