Colour science/15/Quick reference

Quick reference

Cheat sheets and tables

8 working tables covering RGB spaces, transfer functions, HDR reference points, Y′CbCr matrices, video levels, bit depth/chroma sampling, pipeline checks and CST/RCM/ACES choices.

8 tablesSpacesHDRSignalResolve
In plain language

These are not presets but a reference layer: a table helps verify a specific parameter, while the actual decision still comes from source → working → output context.

6 sections7 primary references

Quick reference

Definitions and numbers worth keeping in view

Tables
8

Spaces, transfer, HDR, Y′CbCr, levels, precision, pipeline and Resolve architecture.

Signal tuple
Primaries · Transfer · Matrix · Range

Plus bit depth and chroma sampling.

HDR anchors
203 · 1000 · 4000 · 10000 nit

Reference white, mastering classes and the PQ ceiling have different meanings.

Use
Reference, not preset

Final parameters are defined by the delivery specification.

Quick reference

8 tables for real production checks

Use these tables to verify assumptions, not as presets. Every row separates independent signal properties instead of collapsing everything into one colour-space label.

01

RGB spaces and working systems

Keep gamut geometry, white point and transfer separate; the table lists them independently.

SystemPrimaries / gamutWhiteTransfer / encodingTypical use
Rec.709Rec.709D65Video OETF + display convention/BT.1886 contextHD/SDR video
sRGB= Rec.709 primariesD65sRGB piecewise transferWeb / desktop graphics
Display P3P3 primariesD65sRGB-like transferWide-gamut consumer displays
DCI-P3P3 primariesDCI white ≈ x .314, y .351Gamma 2.6 cinema conventionDigital cinema projection
Rec.2020Very wide Rec.2020 primariesD65Depends on system; BT.2100 uses PQ/HLGUHD / HDR signalling base
DaVinci Wide GamutVery wide Blackmagic working primariesD65DaVinci Intermediate (typical pair)Resolve scene-referred working space
ACEScgAP1ACES white ≈ D60LinearVFX / CG compositing
ACEScctAP1ACES white ≈ D60Log-like with toeACES colour grading
Rec.2020 primaries do not automatically mean HDR; PQ/HLG and rendering context are separate.
02

Transfer functions: what belongs where

The best defence against Gamma/Log/PQ/HLG confusion is knowing which side of the chain the function describes.

NameClassAbsolute?Primary purposeDo not confuse with
Gamma 2.4 / BT.1886-styleDisplay response conventionNoSDR reference viewingCamera Log
sRGBPiecewise encoding/display pairNoDesktop/web RGBRec.709 mastering convention
Camera LogScene-oriented encodingNoStore wide camera exposure rangeFinal display gamma
DaVinci IntermediateScene-referred working encodingNoWide-range Resolve working stateDisplay output
PQ / ST 2084EOTFYesSignal → absolute display luminanceMastering display peak = 10,000 nit
HLGRelative signal + system OOTFNoBroadcast-oriented HDRPQ-style absolute code meaning
03

HDR / SDR reference points

These are reference anchors for understanding the system, not universal creative targets for every shot.

ParameterSDRPQ HDRHLG HDRComment
Signal modelRec.709 / BT.1886-style displayST 2084 absolute EOTFSTD-B67 / BT.2100 relativePQ and HLG are not interchangeable tags
Reference whiteProject/display target-dependentNominal HDR white ≈203 cd/m²75% HLG ≈ reference whiteReference white ≠ peak highlight
Peak meaningTarget display/master contextMaster may be 600/1000/4000… nitNominal display peak enters system gamma10,000 nit = PQ mathematical ceiling
Colour primariesTypically Rec.709Typically Rec.2020 container/BT.2100Rec.2020 / BT.2100Actual display gamut can be smaller
04

Y′CbCr: luma coefficients

Matrix coefficients are part of signal interpretation. The wrong matrix produces hue/saturation shifts.

StandardKrKgKbY′ formulaTypical context
BT.6010.29900.58700.1140.299 R′ + .587 G′ + .114 B′Legacy SD digital video
BT.7090.21260.71520.0722.2126 R′ + .7152 G′ + .0722 B′HD / Rec.709
BT.2020 NCL0.26270.67800.0593.2627 R′ + .6780 G′ + .0593 B′UHD / BT.2020 non-constant luminance
Y′ here is built from nonlinear R′G′B′ and is not CIE luminance Y.
05

Bit depth and chroma sampling

Two independent quality axes: tonal/code precision and spatial chroma detail.

ParameterWhat it changesStrengthsRisk/limit
8-bit256 code levels/componentDelivery, light processingBanding after heavy transforms
10-bit1024 levels/componentLog, HDR, gradingDoes not restore clipped/compressed source
12-bit4096 levels/componentHigh-end capture/intermediate precisionMore bandwidth/storage
4:4:4Full chroma gridKeying, graphics, compositingSays nothing about bit depth/compression
4:2:2½ horizontal chromaProduction/broadcast compromiseLess fine chroma detail than 4:4:4
4:2:0≈½ H × ½ V chromaEfficient deliveryFine coloured edges / keys
06

Typical digital video levels

Nominal narrow-range anchors. Always consider the format/codec specification and the application's interpretation.

RepresentationBlack / minWhite / maxChroma neutralNote
8-bit luma narrow16235Head/footroom outside nominal black/white
8-bit chroma narrow16240128Cb/Cr centred on neutral
10-bit luma narrow649404× 8-bit nominal code values
10-bit chroma narrow64960512Nominal chroma range
Full range and video range are not creative contrast modes. They define mapping between code values and the nominal signal range.
07

Pipeline: what to check in order

The same diagnostic sequence works for most colour problems.

StepQuestionExampleIf wrong
1 · SourceWhat is actually encoded?S-Log3/S-Gamut3.Cine, BRAW, Rec.709Wrong input interpretation
2 · DecodeHow is RAW/codec decoded?WB, ISO, debayer, data levelsSource state already differs
3 · WorkingWhere do nodes operate?DWG/Intermediate, ACEScctTools behave unexpectedly
4 · RenderingHow does scene become display?RCM output, ACES Output Transform, CSTDouble/missing transform
5 · SignalWhich tags/range/matrix?Rec.709 + Gamma 2.4, video rangePlayer interprets bytes incorrectly
6 · DisplayWhere are we viewing?Calibrated reference pathCorrect signal looks wrong
08

Resolve: quick architecture choice

Not a better/worse ranking, but a guide by project type.

ApproachWhen usefulStrengthMain risk
Manual CSTExplicit node-level control neededEvery transform is visibleEasy to omit/double a stage
RCMResolve-centric project, mixed camerasProject-wide source/working/output managementWrong clip tagging / hidden assumptions
ACESCross-app/VFX/interchange pipelineStandardised architectureRequires strict understanding of input/working/output choices
01

A cheat sheet verifies facts; it is not a recipe

A row saying 'Rec.709 · D65' does not decide which gamma/display target your deliverable needs, and '10-bit' does not identify the encoded gamut. The tables deliberately separate parameters to avoid creating another set of magic presets. Every value must be interpreted in source, operation and target context.

02

For a file, verify a tuple of properties rather than one label

A minimum digital-video tuple is: primaries + transfer characteristics + matrix coefficients + range + bit depth + chroma sampling. For camera sources add camera gamut/log or RAW decode; for HDR add rendering/mastering context; for colour-managed projects add the working state and output transform.

03

Working space and delivery space solve different problems

DWG/Intermediate or ACEScct can serve as convenient wide scene-referred working representations, while Rec.709, P3 or BT.2100/PQ are target display/output systems. A wide working gamut need not match the final master, and a delivery space is not automatically the best place for every creative operation.

04

HDR reference numbers are anchors, not creative ceilings

203 cd/m² helps describe nominal diffuse/reference white, 10,000 cd/m² is the mathematical PQ ceiling, and 1000/4000 nits often describe real mastering classes. These values are not mechanical rules such as 'faces = X nits' or 'all highlights = peak'. Rendering remains a creative and technical decision within the standard.

05

Resolve: verify settings in signal-flow order

RAW decode/clip attributes → Input Colour Space/Gamma → Timeline/working space → node transforms/LUTs → Output Colour Space/Gamma → Data Levels/export codec/tags → physical monitoring. This order exposes missing/double transforms quickly and prevents correcting a downstream symptom of an upstream error.

06

A table does not replace a deliverable specification

Standards evolve, platforms add constraints and broadcast/cinema/streaming deliveries can require specific codec profiles, legal ranges, metadata, mastering peaks or QC. Use quick reference for understanding and first-pass checks, but always verify final parameters against the current client/platform delivery specification.

What this changes in post

If a table helps choose a value but you cannot explain the input state and target state, the decision is not yet verified. Return to the full chapter for that parameter.

Common mistakes
Copying a table row as a project preset.
Mixing properties from different layers: gamut, transfer, range, bit depth and codec.
Treating reference numbers as mandatory creative targets.
Ignoring the current delivery specification.