Workflow 3-2 is not recommended because the HDR10plus average pq metadata are calculated differently. Dolby latest cmv4.0 algo is very conservative(targets 92nits) while HDR10plus is more representative of the brightness and can have much higher values which could result in unexpected tone mapping when you straight convert HDR10plus to DV. see: https://slow.pics/c/WlGwchoEazreil24 wrote: ↑Sun Dec 31, 2023 10:39 amThank you for the great tool, sir. Quick question please. I have an MKV which only had HDR10+ for dynamic metadata, for which I used the other tools to turn into DV8. If I use the MODE.H flow, MODE.1 (as I see that MODE.2 which says HDR10plus to DoVi maker, is tagged as Not Recommended), will it use the correct HDR10+ layer to generate a new DoVi or it will also take in consideration the Profile 8 I had in the MKV also?
LE: My first attempt on this and for some reason it couldn't find the files it generated, although they were there while it was processing prior to this step. Not sure what happened.
L1 avg_pq has none to very little effect on 1000nits RPU though but for 4000nits RPU, it does react to avg a lot.
As for 3-1, when you input a file that contains HDR10plus or DV, the script will use only their original scene cuts and generate new proper dv metadata based on those cuts with the latest Dolby algo.
For your error, you did not provide enough information for me to help you. Post the complete log with echo set to on and mediainfo of your input.