mpetech wrote:
I don't know how Windows deal with HDR but it would probably be unable to adjust based on the myriad of the possibilities DR can do (P3, 2020, HLG, PQ, 600 nit, 1000, 4000, etc.).
Doesn't matter, HDR content works outside of Resolve. What does Resolve show in the preview? Is it HDR10, HLG? My TV switch to the HDR mode it receives. If other content doesn't have a problem, then the problem is within Resolve. How does it handle HDR on a HDR monitor?
Or is it that no one at Blackmagic had the idea to implement HDR viewing of the preview and UI, only the output signal? So, we're working on a preview image that is totally different from the output view?
In that case, maybe just implement the ability to actually show HDR content within the UI in order to at least be close to what the output view shows. It's easy, just put in a setting where we can choose what HDR standard we want for the preview and it tone maps it towards that for the preview window. I guess it's not a thing.
mpetech wrote:We don't use ACES for HDR correction. We manually set each parameter. For the 1000 nit that is definitely a setting issue. Normally, we set the timeline and display nit settings manually.
ACES is ACES and HDR is HDR, has nothing to do with each other really. Doesn't matter if you use it or not. If the settings all match up towards a set goal for HDR, be it 1000 or 2000 nits and the metadata gamma and color spaces are through and through handled correctly, it shouldn't matter how it looks in the UI, the output should be an HDR file. Still doesn't explain why the scopes won't show the maximum nits you set. 2000 nits should not cap out at 900 nits.