If I was to buy a HDR display, I would make sure it has a linear response and high static contrast ratio (no dynamic contrast or local dimming techniques), and I would adjust the hardware brightness controls to max out at some fixed peak brightness e.g. Additionally, displaying large patches of very bright content might trigger built-in peak brightness limits, resulting in a very different curve than when looking at only a handful of pixels. For example, displays based on local dimming or other such dynamic contrast techniques will be almost impossible to accurately profile. Also, in HDR mode, the screen might have a very unstable and difficult-to-measure response curve. The only way to get HDR passthrough currently is via third party programs.Īnd if it does, what would be the difference than configuring it to output normal range but "upconverted" to match HDR tone response curve, (hopefully) like the way I did above?ĭepends on how much magic your screen is doing.
There are a couple of approaches here, each with their own limitations.ĪFAIK mpv still doesn't support sending HDR metadata to the screenĬorrect. Which confused me because I thought gamut reduction is handled by icc color management already, which by default with -icc-intent of relative colorimetric, will just clip the out of range colors.Īlso, is it correct that -tone-mapping won't do anything for a non-HDR video? playing back BT.2020 content on a standard gamut display). This is relevant for both HDR->SDR conversion as well as gamut reduction (e.g.
In the mpv manual, it explains -tone-mapping as: I also have two other questions which are kind of related:ĪFAIK mpv still doesn't support sending HDR metadata to the screen, and if it does, what would be the difference than configuring it to output normal range but "upconverted" to match HDR tone response curve, (hopefully) like the way I did above? I am not sure I'm doing it right, but with the above settings, I could see somewhat similar result compared with mpv playing the same file in SDR mode with default tone mapping ( -tone-mapping=mobius in v0.28), and also similar to madVR passthrough HDR metadata to the screen. Then if I understand correctly, I should use -tone-mapping=linear and leave -tone-mapping-param as 1.0 the default, to "disable" tone mapping, or say, to let mpv actually map the original luma of the video to the display using the measured tone response curve in the icc profile? Then in mpv, again with -icc-profile-auto to let mpv load the new profile, and since I already have a icc profile, I don't need to specify -target-trc=pq.
HDR SUM 2 PRO
I used i1 Display Pro with Displa圜al, with white level drift compensation enabled (not sure it's actually necessary here, though), and switched target "tone curve" under "calibration" tab to "as measured", and proceeded with "profile only". Given that the tone response curve in HDR mode is completely different from those in SDR (somewhat close to a power function), I think it would need a different icc profile measured when the screen is in HDR mode. The HDR screen I have at hand is a Sony X900E. But I am wondering what is the "correct" way to play HDR videos on a HDR screen with mpv. So currently mpv is able to handle HDR videos quite well: it does HDR tone mapping by default, assuming when one is using a SDR screen. This might be a silly question, but the answer is not obvious to me.