This is a possibility. Unfortunately we can't test for this as DV isn't supported. However, most if not all DV titles are mastered on the Dolby Vision monitor, which is 4,000nits, and I wonder if Dolby doesn't require to report 4,000nits in the HDR10 metadata in that case. It might be worth asking @Kris Deering if he has an answer on that point. I will try to see if any of the titles reporting higher than 1,000nits MaxCLL when MaxDL is 1,000 are DV titles.That may be the case with titles that come with Dolby Vision enhancement layer, HDR10 version can be locked to 1000 nits to prevent image from looking to dim, but video stream has information beyond that that's accessible to DV because of dynamic metadata.
I generally agree that anything above 4000 nits can be safely clipped.
I don't think I ever asked to always clip at 4,000nits, given that I've implemented in the Vertex ages ago an algo to clip lower when the metadata allows us to clip lower. It's all about getting the most possible contrast. I might have suggested never resolving above 4,000nits for projectors, and I still believe in that, because I don't think it's ever desirable to try to fit 10,000nits when you only have 100nits to play with, although arguably the loss of contrast doing so is minimal vs clipping at 4,000. It is more significant vs clipping at 1,000nits.Yes, but at that time I didn't know that mastering monitors always clip. Also IIRC you suggested to always clip at 4,000nits, which I still don't like. It's different to clip at the mastering monitor peak luminance vs to always clip at 4,000nits.
I have also suggested that MadVR gives us an option to specify what is the most we want to show on our display, in any case. I still believe it would be a good option to have. You might want to show up to 10,000nits if one day mastering displays show up to 10,000nits, I doubt I'll ever want to do that if I have the choice. In any case, I'm looking forward to do an A/B compare with/without limiter, but to do this I need to get a version that works here .
Damn you! It's all your faultI have small suggestion: make .measurements files hidden by default.
None of my completed measurements files is taken into account at the moment (only saying so others understand my feedback post earlier).Remeasuring should not be needed. Do you see "measured frame % nits, tone map to % nits" in the OSD, or "frame % nits, scene % nits, movie % nits"? The former means the measurement file was either not accepted at all, or not considered "complete". The latter means it was accepted as complete.
Thanks for the correction, I was blaming the wrong person KoKlusz must be happy now, we have to show our hidden files permanently... I really hope we'll get an option to show/hide them by default. I hate having to show hidden files when I don't have to, and at least during testing I don't see another way to be sure of what I have.I wasn't the one asking for hidden files