KNOWLEDGE MAP · SPACES & STANDARDS
More than a tag. A coordinated SDR path.
From OETF to code values and reference display response. Separate gamut, tone response, Video/Full and metadata to diagnose disagreeing views.
Read the numbers. Notice the assumptions. Then apply the idea to your footage.
One level. Three meanings.
- 01 / INPUT L0.180→
- 02 / SIGNAL V0.40901→
- 03 / 10-BIT422
64 → 94011.676 cd/m²After integer quantization0.408676ΔV -3.32e-4BT.709-6 source OETF + BT.1886 reference model at white 100 cd/m². The display curve is not inverse OETF. Values are calculated, not measured on your screen. Only neutral/RGB nominal endpoints are modelled, not chroma codes.
TOPIC ILLUSTRATIONTHE ESSENTIAL IDEA
Rec.709 / BT.709
Rec.709 is an agreement about a video signal. Following it requires coordinating the route from file interpretation to viewing, not just matching primaries.
- Distinguish source OETF from reference display EOTF.
- Separate normalized signals from integer codes.
- Check the chain instead of hiding errors with an arbitrary gamma adjustment.
Why Rec.709 exists
BT.709 is an agreement on HDTV parameters for production and programme exchange. It links colorimetry to signal structure, picture dimensions and frame rates. It is not a creative look: scenes with very different lighting can both be represented correctly in Rec.709.
This chapter uses BT.709-6, the 2015 edition. In post-production, a “Rec.709 master” usually implies a coordinated chain: colour coordinates, output tone response, levels, metadata and viewing conditions. A filename alone cannot express that agreement.
What this means in practice
Turn a “Rec.709” delivery request into explicit questions about format, black/white levels, intended output and final-file checks.
What Rec.709 defines — and what the label alone does not
Separate four layers: RGB primaries and D65 white; transfer encoding; RGB or Y′CbCr representation; digital code range. These properties are related but are not interchangeable.
BT.709 specifies the source OETF; BT.1886 defines reference HDTV display behaviour. BT.2035 addresses evaluation conditions separately. “Everything is set to 709” therefore does not establish what the application is doing or what the monitor is showing.
What this means in practice
When two views disagree, record each layer separately. This avoids accidentally compensating for a range error with a gamma curve.
Primaries and D65: the geometry of the Rec.709 gamut
The CIE 1931 xy coordinates are R (0.640, 0.330), G (0.300, 0.600), B (0.150, 0.060), with D65 (0.3127, 0.3290). They determine a linear RGB ↔ XYZ matrix. Equal linear RGB components point towards D65.
An xy triangle represents chromaticities of primary mixtures, not luminance or the complete three-dimensional colour volume. It does not specify the light associated with code 0.5 or the brightest saturated colour a particular screen can display.
What this means in practice
Matching triangles on a diagram do not establish matching midtones in two files.
Why Rec.709 and sRGB share a gamut but are not complete synonyms
sRGB and Rec.709 share primaries and white. Their linear RGB coordinates require no change of basis when normalization matches. However, sRGB has its own piecewise transfer function, while video must be considered together with its display path.
Finished sRGB artwork already has a display-related meaning. It should not automatically be treated as camera data encoded by the BT.709 OETF. Establish the graphic’s interpretation first, then integrate it into the working pipeline and intended output.
What this means in practice
Identical logo RGB numbers in a browser and a log timeline do not yet describe the same signal.
The Rec.709 OETF: why it is not Gamma 2.4
For normalized linear input L, BT.709 specifies V = 4.5L below L = 0.018 and V = 1.099L^0.45 − 0.099 above the breakpoint. This maps light to a nonlinear signal; it is not display behaviour. The standard uses rounded coefficients, which the lab retains instead of smoothing the join.
The calculation teaches encoding. It does not imply that every finished Rec.709 master should automatically be decoded using the inverse OETF: the image may already have been creatively prepared for a reference display.
What this means in practice
Compare L = 0.18 with the resulting V in the lab. They are different quantities even though both use numbers between zero and one.
BT.1886: the reference EOTF for modern SDR displays
BT.1886 relates normalized signal V to screen luminance L. Its 2.4 exponent is combined with black Lb and white Lw. With zero black, L = Lw × V^2.4. Nonzero black changes the response, particularly in shadows.
The laboratory fixes white at 100 cd/m² and lets you change black. Its cd/m² readout is an equation result, not a reading of your screen. Checking a physical display requires an instrument and controlled conditions.
What this means in practice
Increase Lb from 0 to 0.1. White stays at 100, but the bottom of the curve no longer matches a pure 2.4 power.
OETF + EOTF create system contrast rather than mathematically cancelling
An OETF → EOTF chain need not reproduce the original relative light value. Television links a scene to a screen image with contrast, creative preparation and surround in mind. That differs from checking the reversibility of one encoding function.
The experiment displays input L, code V and model display luminance together. Different values of L and Lscreen/Lw do not automatically indicate an error. Applying the wrong function to a signal with an established meaning does.
What this means in practice
Do not alter a master merely to make numbers in different reference systems equal.
Reference viewing: why 100 nits, D65 and a controlled room matter
Colour decisions need a reference view. BT.2035 addresses HDTV evaluation: display characteristics, background, ambient illumination and viewing geometry. Its references include white around 100 cd/m², background relative to display white, and controlled low illumination.
These are decision-making conditions, not a requirement that every audience device have identical brightness. Compensating for an overly bright grading monitor inside the grade transfers that compensation into the file. Check the viewing path before changing the master for each player.
What this means in practice
Compare the export and timeline through one controlled path before judging differences between two screens.
Rec.709 is RGB colorimetry, but video is often stored as Y′CbCr
Video may store nonlinear R′G′B′ or the component representation Y′CbCr. BT.709 luma is Y′ = 0.2126R′ + 0.7152G′ + 0.0722B′. Colour-difference components express blue and red differences relative to luma.
Y′ is not the linear CIE Y coordinate: the prime indicates nonlinear signal values. Y′CbCr alone does not specify gamut either. The decoder needs the correct matrix coefficients and primary interpretation.
What this means in practice
If a neutral ramp looks right but colour bars disagree, check the matrix as well as gamma.
Video levels: 16–235 are not gamut or gamma
Nominal 10-bit video RGB/Y′ black and white are 64 and 940; the 8-bit equivalents are 16 and 235. Colour-difference components use a different range. Full range maps normalized values to integers differently. This does not shrink gamut or change the transfer function.
Switch Video/Full and 8/10 bits in the experiment. With matching readback, the normalized signal is nearly preserved; small differences come from rounding. Reading the same integers under a different range without remapping changes levels.
What this means in practice
10-bit code 64 is nominal Video black, but it is not zero in Full. That is a reproducible interpretation error.
Metadata and tags: correct pixels still need to be described correctly
Metadata can identify primaries, transfer characteristics and matrix coefficients separately. The decoder must also understand levels. A tag does not recalculate the signal, but it can change how an application interprets it.
Check both data and description. Files matching in one player may be interpreted differently elsewhere if tags differ or an application assumes defaults. Assigning a desired label cannot replace a missing conversion.
What this means in practice
Re-import is useful but cannot prove compatibility with every player: compare assigned input interpretation and export tags too.
Rec.709 Scene, Gamma 2.4 and Rec.709-A in Resolve express different intents
Resolve exposes Rec.709, Gamma 2.4 and specialized interpretation options. Do not treat them as interchangeable because they share a gamut label. Input settings describe the incoming signal; output settings prepare an image for a target.
Rec.709-A is an application option, not a separate ITU recommendation. Its behaviour and macOS viewing settings should be checked against your version’s documentation and a test export. This chapter does not prescribe it as a universal cure for Viewer/player differences.
What this means in practice
Save a short test and the project settings. Change one parameter and establish whether file values changed or only the viewing path.
A practical DaVinci Resolve workflow
Define the target and monitoring path first, then identify the clips’ source spaces. In a managed project, transforms can run outside the clip node graph. In a manual chain, a CST must receive the actual gamut and encoding present at its input.
A matching output-gamut name does not guarantee identical tone rendering between RCM and manual CST: tone mapping, gamut mapping and image state matter. After output, check levels, tags, re-import and a controlled external view.
What this means in practice
Do not add a final CST “just in case” when the project system already performs the output transform.
If Rec.709 looks wrong: diagnose the chain layer by layer
Investigate in order: source → input interpretation → working space → output → levels → metadata → viewing application → screen. Start with a neutral ramp and several colour samples rather than a complex creative shot.
Keep a control export and change one layer at a time. Fixing black while damaging colours does not prove success: one error may have compensated for another. Check tonal steps and coloured regions together.
What this means in practice
Write a testable hypothesis such as “Video was read as Full”, not merely “the video looks washed out”.
A MODEL YOU CAN CHECK
Four layers of one signal.
Keep the meaning, the calculation and the limitation together.
V = L < 0.018 ? 4.5L : 1.099L^0.45 − 0.099Rounded BT.709-6 constants for L from 0 to 1. BT.1886 is a separate display function, not simply this OETF’s inverse.
| Concept | What it describes | What not to conclude |
|---|---|---|
| Colorimetry | Rec.709 primaries and D65. | Does not choose the digital range. |
| OETF / EOTF | Source encoding / display response. | Not one automatically inverse pair. |
| Video / Full | Mapping codes to normalized values. | Full does not mean wider gamut. |
| Metadata | Signal interpretation information. | A tag does not perform missing processing. |
DO. OBSERVE. EXPLAIN.
Follow one level to output.
Start with L = 0.18 in the lab. For a Resolve check, use a duplicate SDR test project and a neutral reference frame, not your working master.
- 01
Light and signal
Record L, V and the BT.1886 result with zero black.
CHECKV and normalized output luminance need not equal L.
- 02
Codes and range
Switch 8/10 bits and Video/Full without changing L. Compare the integer code, its endpoints and recovered V.
CHECKInteger codes change; recovered normalized signal differs only through quantization.
- 03
Nonzero black
Raise model black to 0.05 cd/m² and compare the low end of the blue curve with the input unchanged.
CHECKCode meaning is unchanged, but the display model changes.
- 04
Check a file
In the project copy, compare input range, output and an independently reopened test render.
CHECKYou can identify each transform instead of compensating with a grade.
Check your understanding
TEST THE EXPLANATION
A situation, not a trick question.
Answer first. Open the reasoning afterwards.
01Both files say Rec.709, but one looks washed out. Why?+
Check range, transfer, matrix and viewing. Matching primaries does not eliminate errors elsewhere.
02Will Full Range increase saturation and bit depth?+
No. Code range changes neither primaries nor bit depth. A mismatched reading may change appearance, but that is an error, not an enhancement.
03BT.1886 with zero black did not recover the original L. Is it broken?+
Not necessarily: reference display response is not defined as inverse BT.709 OETF. The lab shows different functions and their composition.
Avoid these shortcuts
- Treating Rec.709 as a synonym for any 2.4 curve.
- Repairing range errors with exposure.
- Comparing players without checking their interpretation.
From the model to your workflow.
In production, identify the source, transform placement and required output separately. The lab verifies a bounded mathematical model; it does not measure your display, replace project settings or certify an exported file.
CHECK THE FOUNDATION
Sources and model limits.
Editorial review: 1 October 2026. Links identify the definitions and formulas; exercises are independent teaching examples.
- [1]ITU-R · BT.709-6 (2015) ↗
HDTV parameters: primaries, source OETF, component signals and digital levels. Tables 1 and 3 checked in the PDF.
- [2]ITU-R · BT.1886 (2011) ↗
Annex 1: reference EOTF including black and white luminance. Lab luminances are model calculations, not display measurements.
- [3]ITU-R · BT.2035 (2013) ↗
Reference HDTV evaluation conditions, not a setup recipe for every home screen.
- [4]ICC · sRGB ↗
Primary coordinates and D65; piecewise sRGB transfer function.
- [21]Blackmagic Design · Color ↗
Color and colour-management context. Setting names and locations depend on Resolve version and configuration; live projects were not tested here.
- [22]ITU-T · H.273 (2024) ↗
Identification of video primaries, transfer characteristics and matrix coefficients.