So, do we know what happens when only 1 L2 block is present? I mean do we have to specify all of them or it will use the only one for all?quietvoid wrote: Tue Oct 12, 2021 11:44 am In playback, you'd have to figure out what the TV says it can output, this might be the same peak as in the Dolby Vision configuration files used for calibration.
This is why I set multiple blocks to the same values in my L2 test sample.
Also, what nit number do these correspond to? 2081, 2851, 3079
My bad, sorry, L1. No worries, editing json is fine.quietvoid wrote: Tue Oct 12, 2021 11:44 amYou're asking for L2 but min_pq is L1 metadata.
Technically it could be added to the editor but I don't really see a good use case for it..
It's not that, but the binary measurement file doesn't have any data about this.Manixx2020beyound wrote: Tue Oct 12, 2021 12:33 pmBe interesting to find out what mad Vr considers as the active area. Did anyone try a movie without black bars to see if the min values changed?
Good point.Manixx2020beyound wrote: Tue Oct 12, 2021 12:39 pm I don’t think anyone needs l2/l8 trims if the creators intent is already within the source
U can select to bypass trim pass for l2 which won’t produce any l2 meta in resolve.
According to the manual L8 is for secondary trim controls only in v4.0 (and not backward compatible with v2.9)Manixx2020beyound wrote: Tue Oct 12, 2021 12:39 pmPlus isn’t l2 for mapping trims to 709
L8 trims maps to 1000/600nits dv which we have no acess to without a license which is blacked out in resolve
Yes, that's why I asked it. But this is a good point that then we have to use active area as well (otherwise it will be incorrect this timeRESET_9999 wrote: Tue Oct 12, 2021 12:54 pm I don't really know but Dolby clearly says that min 0 for all the scenes is incorrect.
When I get home, I'll do the analysis with the HDR10plus algorithm and see if I get a different min pq for that clip.
1- Oh, I seeRESET_9999 wrote: Tue Oct 12, 2021 12:54 pm1- the L6 metadata is edited manually, I just took the numbers from your post: viewtopic.php?p=113519#p113519chros wrote: Tue Oct 12, 2021 9:43 am It's Amazon hdr10+. Thanks for the test, measurement results are pretty close indeed (apart from the first avg value, where it's double), really interesting:
1- Resolve L6 maxCLL is set to 1680, but it measure more than 3000 nits? what's the unit of the values on the image, nits or PQ?
- - interestingly that's the measurement summary from madvr: MaxCLL 100%: 1680, 99.9%: 1545, MaxFALL: 58, AvgFALL: 9, AvgFMLL: 524 nits
2- Resolve set some L2 trim properties (that obviously dovi_tool doesn't by default), why is that? Did you set it or is it automatic?
3- Resolve has 3 blocks of L2 metadata, why is that? (target_max_pq: 2081, 2851, 3079; dovi_tool has just 1: 3079) Which one is used during playback?
Thanks, my question is what the effect of min_pq value is in reality.
2- this is the resolve default trim passes adjustments for each target display. You need a license to modify them in resolve but everything else is available and free to use.
3- As Quietvoid said.
2 - interesting, thanks