Luminance vs. Brightness: The Meter and the Eye
One slider drives everything: the marker on this plot, this swatch, and the patches in both photos below. Drag it, click the presets, or click a room to re-anchor your adaptation: every readout follows.
The pixels in the two squares are identical: a meter held to the screen would say so. If they look different, that surplus is brightness, manufactured entirely by context. The dark-room curve on the plot models this as adaptation one stop down; the real effect varies with the scene, but the direction never does.
Same black, same white, eleven steps each; the numbers are cd/m². The luminance row spends its last five steps looking nearly identical; the brightness row is visually even: its top two steps are 24 cd/m² apart, its bottom two barely 1. This is why display code values are spaced by brightness, not light: the transfer-function module is that idea, industrialized.
Two words, two worlds
Luminance is physics: candela per square metre, the same number for every observer. Brightness is perception: assembled inside a visual system from luminance plus adaptation and surround. Every display argument that confuses the two is already lost.
Luminance: the number a meter can defend+
Brightness: the answer a brain gives+
The cube-root eye+
Context is half the percept+
The word ladder: radiance to lightness+
Why code values follow brightness, not light+
HDR: ten times the light is twice the brightness+
In practice: measure luminance, manage brightness+
SI NO SE MIDE, NO ESTÁ CALIBRADO. · TRANSFER FUNCTIONS · DYNAMIC RANGE · Y′CBCR