Min pq is mostly set to 0 on hdr10plus, & produces the same result on hdr10 plus to dv rpu.chros wrote: ↑Mon Oct 11, 2021 9:15 amquietvoid wrote: ↑Sat Oct 09, 2021 3:45 pmAnyways, it made me create a cropped test sample for the important metadata: https://mega.nz/file/8YsRRKJa#_g_vX2voc ... raveYPpiIAIndeed, really nice, thanks! Now we could see L2 metadata in action!
RESET_9999 wrote: ↑Sat Oct 09, 2021 3:54 pminteresting thanks... will try on my x700.
that sample has very small black bars thoughTried it on Oppo, and yes, grey bars are there.RESET_9999 wrote: ↑Sat Oct 09, 2021 3:54 pmhaha, trust me you will.
Having this exact problem with my x700, I just can't stand the grey black bars(especially the 1600px content). I even prefer my Shield with the red push for p8 cropped content(no red push with p5).
The interesting part is that how grey it is depends on the metadata! E.g. from the previously linked Dolby manual (thanks for thjis for you RESET and Mannix):
"... Blu-ray players ... Due to this implementation on these devices, any positive lift applied to Dolby Vision content during the “trim pass,” will raise the black levels in the letterbox/blanking areas of the image and can become distracting to the end user. Dolby recommends a maximum positive lift value of 0.025 while doing the trims on letterboxed content during the Dolby Vision content creation process."
Thanks, now that's interesting. Maybe we can ask mashdi to provide this value as well in the measurement file.
What do you think what would happen if it's not 0 during tonemapping? I mean what's the effect of this value?
Does anyone compared the result this type of metadata RPU (from madvr) vs static metadata RPU (1 for all frames), if so is there any difference?
Reset, Mannix?
There should definitely be a difference per frame vs 1 for all frames.
But on true min pq value dv dynamic meta it varies more often
If mad vr handles scenes changes the same way as dv, the dynamic meta produced should be very close I would assume.