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
Cheers buddy
Reading the article this looks great! have your tools been updated with this new analysis tuning as it says its in Resolve 18.6 and later?
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.
I have a film where the top black bar is 281 and the bottom is 280.
How do I crop this correctly for dolby vision analysis?
If I under crop I will get wrong min values in my analysis and if I over crop I will not anaylze the whole active area?
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
AVSPMod show the Black bar area for my Inception clip test is Top 281 Bottom 280.
When I use Top 281 Bottom 280 using DoVi script the resulting rpu has L5 Top value of 280 and L5 bottom value of 281...(Should this not be the other way around?)
In resolve I tried to use Top 280 and Bottom 1879 in blanking but this also made the L5 values Top 280 and Bottom 281....
I could just edit the L5 values but I am unsure if the DV analyze process was based on an incorrect active area.
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.
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.
I updated to you 1.9.8.6 scipts and yes you are right your scripts work properly.
Resolve still gives top 280 bottom 281 (when I input top 281 bottom 1880 in the blanking section) so i guess i just edit the L5 for resolve xml's