Re: [csswg-drafts] [css-color-hdr] Define "media white" better (#11346)

I agree that there are many different definitions, as we reference a lot of different specifications of different ages and assumptions.

sRGB, from the 1990s and aimed at the CRT monitors of the time, picked 80 cd/m². Adobe RGB [picked 160 cd/m²](https://drafts.csswg.org/css-color-4/#predefined-a98-rgb) and ProPhoto RGB [picked 160.0 to 640.0 cd/m²](https://drafts.csswg.org/css-color-4/#predefined-prophoto-rgb). Display P3, derived from DCI PC (which uses 48 cd/m², appropriate for a digital projector in a totally dark movie theatre) went for sRGB compatibility and thus selected 80 cd/m².

Those examples are all SDR, meaning that users are expected to adjust their screen brightness up or down to suit their comfort and thus, that all luminances are relative to the actual luminance of media white, which is placed at 100%. This also means that there wasn't a lot of attention paid to the nominal absolute luminance level of white. And by and large, it didn't matter much.

The introduction of HDR changes things in a number of ways:

1. a comfortable white that could be used, for example, for subtitles or for a white background is no longer "the maximum value"
2. the maximum levels are uncomfortable to look at over a large area
3. the maximum levels can't even be _produced_ except over a small area and a limited time (power consumption, heating)
4. the adaptation state of the eye, derived from the whole screen contents, becomes more important
5. there is a need to display SDR and HDR content together (overlays, subtitles, etc)

and thus the concept of media white and the need to pick a value that works with HDR content. 80 cd/m² looks weirdly dim. 203 cd/m² looks good and is widely recommended. 2000 cd/m² (or whatever the whole-screen brightest white happens to be) is completely unusable.

-- 
GitHub Notification of comment by svgeesus
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/11346#issuecomment-2532568781 using your GitHub account


-- 
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config

Received on Tuesday, 10 December 2024 18:28:25 UTC