Colour science/08/Dynamic range

Dynamic range

SDR and HDR

Not merely a brighter picture but a complete system: BT.2100, reference white, PQ/HLG, wide colour, mastering displays, tone/gamut mapping, metadata and delivery control.

BT.2100203 nit whitePQ / HLGColour volumeMonitoring
In plain language

HDR expands display-light range and colour volume while keeping diffuse objects at a sensible level. The core idea is not to raise the whole image but to leave room between ordinary white and very bright highlights.

13 sections4 primary references

Quick reference

Definitions and numbers worth keeping in view

Standard
ITU-R BT.2100-3

Two HDR systems: PQ and HLG; BT.2020/D65 colorimetry.

HDR Reference White
203 cd/m²

Diffuse/graphics white in ITU production guidance.

PQ
Absolute luminance

ST 2084; mathematical ceiling 10,000 cd/m².

HLG
Relative + system gamma

75% HLG = reference white; ≈203 cd/m² on a nominal 1000-nit display.

HDR SYSTEM MAP

HDR is a state of the whole chain, not a 'make it brighter' switch

Display luminancecd/m² · nit
0.1
1
10
100
203
1000
4000
10000
203 · REF WHITE
SDR
smaller display range
PQ
absolute luminance
HLG
relative broadcast system
Do not confuse
Display peak ≠ ordinary white ≠ diffuse white.
Colour
HDR often travels with wide-gamut signalling, but luminance range and gamut are separate axes.
Monitoring
You need the transfer, target, peak and output transform; an HDR flag alone is not enough.
01

HDR is a system design, not one format

In professional video, HDR describes a coordinated capture/rendering/display chain. ITU-R BT.2100 defines two HDR systems, PQ and HLG, and uses BT.2020 colorimetry. A file must still signal transfer characteristics, matrix, range and other states correctly. An 'HDR' label alone is therefore not enough for diagnosis.

02

What BT.2100 actually brings

BT.2100 combines UHD/HDR colorimetry, transfer-system parameters and digital representation. Its primaries correspond to BT.2020 and its white point is D65. That does not mean a real display must physically cover the entire Rec.2020 triangle; mastering/display gamut can be smaller and the output pipeline must handle unavailable colours gracefully.

03

HDR Reference White: 203 cd/m²

In current ITU production practice, HDR Reference White is the nominal signal level from a 100% reflectance white card that produces 203 cd/m² on a PQ display or an HLG display with a nominal 1000 cd/m² peak. It is a reference for diffuse white and graphics white, not the HDR ceiling. That is why ordinary faces, walls and white shirts should not automatically jump to 1000 nits.

04

Diffuse white and specular highlight play different roles

Most of the picture can retain a familiar tonal hierarchy while extra HDR headroom is used for glints, fire, the sun, practical lights and other objects that should feel brighter than a white diffuse surface. This preserves natural visual hierarchy instead of turning HDR into an exhausting bright version of SDR.

05

PQ and HLG solve a similar problem with different philosophies

PQ/ST 2084 is display-referred absolute-luminance encoding: a signal value relates to a defined luminance. HLG/STD-B67 is a more scene-oriented relative system with a hybrid OETF and display system gamma. A PQ master and an HLG broadcast signal are therefore not two names for the same gamma preset.

06

HDR usually adds a colour-volume problem too

BT.2100 uses BT.2020 colorimetry, so an output may differ from SDR both in luminance and in available saturation at different brightness levels. A 2D gamut triangle shows chromaticity only. The real HDR problem is three-dimensional colour volume: gamut × luminance × display limits.

07

Mastering peak is not the brightness of the whole frame

1000, 2000 or 4000 cd/m² in a mastering-display description refers to an upper capability of the reference display/workflow, not a requirement for every frame to use that level. Content peak, mastering peak, HDR Reference White and average picture brightness are four different concepts.

08

HDR cannot be judged on an SDR viewer

Final evaluation needs a monitor path that receives the target HDR signal correctly and can actually reproduce the intended range. A GUI Viewer is useful for work but does not replace a calibrated HDR reference display. Scopes also need the right scale: 0–1023 code values, IRE-like scales and nits answer different questions.

09

Graphics white must be deliberate

White titles and interface elements are not specular highlights. ITU production guidance aligns Graphics White with HDR Reference White. If a title is encoded much brighter without reason, it can dominate faces and the scene and may behave poorly during HDR-to-SDR conversion.

10

Metadata helps but does not repair a bad master

PQ-based distribution ecosystems can carry mastering/display metadata and content-light metadata, while some dynamic-HDR systems add scene/shot guidance. Such data can assist downstream display mapping but cannot replace a correct grade, output transform and signal-state control.

11

HDR→SDR is rendering, not a simple Gain

Moving to SDR requires simultaneous decisions about luminance compression, highlight hierarchy, possible gamut reduction and graphics behaviour. Good conversion preserves intent: important detail and relative relationships remain readable. Simple gain or clipping destroys the very information HDR was meant to preserve.

12

A practical HDR workflow in DaVinci Resolve

Identify every clip's source state, choose a wide scene-referred timeline/working space, define a specific HDR output such as BT.2100 ST2084/PQ or BT.2100 HLG, and only then evaluate tone/gamut mapping. In managed RCM, output rendering is handled by the system transform; in a manual CST workflow, make sure CST does not duplicate a project-level transform. For HDR10-like delivery, separately verify mastering metadata and encoder/container signalling.

13

Minimum pre-delivery check

Verify five things independently: target primaries/colorimetry, transfer (PQ or HLG), signal range, bit depth/chroma format, and mastering/stream metadata. Then inspect the actual render with scopes and the target display path. A correct-looking picture in one window does not prove the file is correct.

What this changes in post

HDR is built around signal states and display intent. If you cannot name the target transfer, target colorimetry, reference white and monitoring path, the workflow is not fully defined yet.

Common mistakes
Raising the whole frame to make it feel HDR.
Treating 1000 nits as the normal level for a white wall or title.
Judging HDR only through the GUI Viewer.
Confusing BT.2020 container/colorimetry with the display's physical gamut.
Doing HDR-to-SDR with ordinary Gain/Contrast.
Forgetting to verify signalling in the final file.