Gatorman wrote: ↑Fri Oct 27, 2023 10:11 pm
RESET_9999 wrote: ↑Fri Oct 27, 2023 8:53 pm
FYI, in the new Mission Impossible, it looks like the colorist missed the memo about L2 0.025 lift. These shots will most likely result in grey letterbox on devices that ignore L5
And you can clearly see on this video how the trims raise the brightness:
https://www.youtube.com/watch?v=Hk6ria8_PFo
Regarding this film, it looks like the MDL of the BL and RPU is .0050/4000 and the MaxCLL is 997 for both. Does the MDL need to be changed to 1/1000, when baking in the FEL with StaxRip?
no
BTW, 6-2 is crashing for me when I try to plot HDR.
In the latest version, I removed the 10nits and 100nits floor so you need to add in your tools folder, the modified version of the dovi_tool linked in the release note.
Trees wrote: ↑Fri Oct 27, 2023 10:33 pm
So I finally got round to do this. Question, though. The files I want to eventually CMv4.0 analyze are HDR10+. The plots are all coming back as dynamic, even though you instructed me to plot the static data (6-2). Is madVR checking the dynamic HDR10+ portion of the video instead of the HDR10 static metadata portion of the video? Is something going wrong? Or will it automatically check the dynamic metadata if the file is HDR10+?
6-2 is useful to find out about the content brightness you're about to generate DV. It helps you select a better MDL, that's it.
In 3-1, any dynamic metadata(only the scene cuts matter) regardless of the source is used for the Shot list during the CM analysis.
Shot list source is selected in this order:
1- any external file with the same filename as the input (rpu, json, text)
2- internal RPU (in case of original rpu that has no shot, add ''IGNORERPU'' in the input filename.)
3- internal hdr10plus
4- if no dynamic metadata is found, it uses madvr to generate a shot list which means that if your source doesn't have any dynamic metadata, you can use the generated RPU from your previous 6-2 measurement.