Tone & gamut mapping, DRTs

ExpertDuration ~30 min video + hands-onTools DaVinci Resolve (free)

Why this lesson

In 3.1 you learned that a scene-referred image is not yet a picture — it’s open-ended scene light that has to be rendered down to what a display can show. This lesson is about the thing that does the rendering: the display rendering transform, and the two jobs inside it, tone mapping (fit the brightness range) and gamut mapping (fit the colors). Get this and you gain the single most useful expert skill: the ability to look at a broken image and say where in the pipeline it broke — a tone-mapping problem, a gamut problem, or a viewing-condition mismatch — instead of reaching blindly for the wheels.

Watch

Segment: 3:47–12:17 — reworking a DRT: shadow detail, noise, saturation and hue stabilitywatch full video

Watch for: FilmLight walk through what they changed in their T-CAM V2 display rendering transform and why: shadow detail, how noise renders, saturation behavior, and hue stability as colors get bright. This is a DRT being designed in the open — every design goal they name is a lever you now understand exists.

The explainer

The problem, restated. Your camera captured (or your grade produced) a scene-referred image: linear-ish light, huge range, colors that may fall outside any real display’s gamut. Your monitor can show maybe 100 nits of range in Rec.709’s little triangle. Something has to negotiate between the two. That negotiator is the display rendering transform (DRT) — also called a display transform, an “RRT + ODT” in ACES terms, or “T-CAM” in Baselight. It is the single most important transform in the chain, and it does two conceptually separate jobs.

Job one: tone mapping. Tone mapping is the brightness squeeze. Scene light runs from deep shadow to an 800% specular; the display runs from its black to its white. Tone mapping is the curve that maps one onto the other — an S-shaped rendering that places middle grey sensibly, rolls the highlights off so they compress instead of clipping, and holds shadow detail. A good tone map is why a scene-referred pipeline “just looks like an image” the moment you turn it on: the DRT is applying a filmic tone curve for you. When someone says an image “clips harshly” or “the highlights go chalky,” they’re describing a tone-mapping decision.

Job two: gamut mapping. Gamut mapping is the color squeeze — the same problem in the chromaticity triangle from 3.1. A saturated color that lands outside your delivery gamut has to be brought inside it, and there are two ways. Clipping slams it flat onto the boundary: fast, but it flattens detail in saturated areas and often shifts hue (a clipped bright red drifts orange). Compression eases the outer colors smoothly inward, keeping their relative shape and hue at the cost of a little saturation. Compression is almost always the right answer — it’s why “gamut compression” is a checkbox worth turning on in a CST, and why ACES added a dedicated gamut-compress step. When someone says “the reds are blocking up” or “the neon sign lost its shape,” that’s a gamut-mapping problem, not a tone one.

Why there are competing DRTs. There is no single correct render — only trade-offs. FilmLight’s T-CAM, ACES’s RRT (and the newer ACES 2.0 transform), RED IPP2, ARRI’s Rec.709 rendering, Sony’s s709 — each is a DRT with a different opinion about contrast, saturation and hue stability. That’s exactly what the sRGB… We Need To Talk second half shows: five case studies where the “same” image renders differently, plus surround compensation (an image viewed in a dark cinema needs different rendering than one on a bright phone — the eye’s contrast sensitivity changes with the room). And it’s why Baselight ships camouflage looks that let one project match the ACES RRT or an IPP2 render on demand: DRT choice is a real creative and technical decision, and pros need to reproduce a known one.

The debugging payoff. Once you hold this model, image problems resolve into three buckets. Brightness wrong — clipping, milky blacks, crushed shadows? Tone mapping or the wrong output transform. Saturated colors blocking, hue-shifting, or a neon losing detail? Gamut mapping — turn on compression, or check your working gamut is wide enough. Looks right in the suite, wrong on delivery — phone, cinema, a client’s laptop? A DRT or viewing-condition mismatch: different display transform, different surround, or a tagging error like the sRGB shadow discrepancy from 3.1. You stop asking “what wheel fixes this” and start asking “which transform is doing this to me” — which is the whole difference between operating a color page and running a pipeline.

Do it

1. Take a scene-referred clip in DaVinci Wide Gamut / Intermediate. Add an output CST and toggle its gamut mapping on and off while a neon or a saturated flower fills frame. On the CIE scope, watch colors that were pinned to the triangle edge (clipping) ease inward (compression).
2. Swap the output color space / DRT: render the same graded clip to Rec.709, then to P3-D65. Note the tone-map and gamut differences on a wipe — same grade, different render.
3. Grade one shot under two DRTs (a DaVinci film-look output vs a plain Rec.709 CST). Match them by eye, then note how differently each one made you push. The DRT was doing half your grade.
4. Write, for one broken frame you’ve seen, one sentence naming whether it was a tone-mapping, gamut-mapping, or viewing-condition problem.

Level 3 workbook — every Do it exercise, 3.1–3.10, plus the capstone (printable)level-3-workbook.pdf764 KBOriginal course material — free to use

Terms introduced

Terms introduced in this lesson

• Tone mapping
• Gamut mapping / compression
• DRT (display rendering transform)

Each term links to the glossary, where it is defined by the way you just used it.

Check

Check yourself

1. What does a display rendering transform (DRT) actually do?

   It adds a creative lookIt only changes resolutionIt relinks media at conformIt maps a scene-referred image — unbounded scene light — into the bounded tone and gamut a specific display can show, doing tone mapping and gamut mapping together

2. Tone mapping and gamut mapping solve two different squeeze problems. Which is which?

   Tone mapping changes hue; gamut mapping changes exposureThey are the same operationTone mapping squeezes brightness range; gamut mapping squeezes colors that fall outside the display’s triangle back inside itTone mapping is for HDR only; gamut mapping is for SDR only

3. Why is gamut compression preferable to gamut clipping?

   Compression makes the image brighterClipping is illegal for broadcastIt is faster to computeClipping slams every out-of-gamut color flat onto the boundary, losing detail and often shifting hue; compression eases them in smoothly so highlights and saturated areas keep their shape

4. A grade looks right on your Rec.709 monitor but wrong on a phone. Reasoning in pipeline terms, the most likely culprit is…

   The camera was set wrong on the dayA DRT / viewing-condition mismatch — the phone is applying a different display transform or surround compensation than your referenceThe codec is corruptYou forgot to add grain

Check answers

You can move on when you can… define a DRT and name its two jobs, explain why compression beats clipping for out-of-gamut color, and — shown any broken image — say in one sentence whether it’s a tone, gamut, or viewing-condition problem.

Mark this lesson complete

Go deeper

FilmLight — sRGB… We Need To Talk (second half): five DRT and surround-compensation case studies as Baselight A/B comparisons, FilmLight’s proposed “sRGB Display” fix, and a Q&A on phone / Apple P3 delivery and dual-output remote grading. This is DRT reasoning applied to real delivery headaches.

Segment: 24:59–57:53 — five DRT / surround-compensation case studies + the sRGB Display fixwatch full video

Watch for: How the same image renders differently under different display transforms and surrounds, why a phone in a bright room needs different compensation than a dark grade suite, and FilmLight's proposed fix.

FilmLight Baselight — Scene Looks & camouflage looks: the segment where core looks can be built to match the ACES RRT, RED IPP2, ARRI and Sony renders — proof that DRT choice is something a facility deliberately controls and reproduces.

Segment: 23:10–34:50 — Scene Looks: core looks incl. camouflage looks matching ACES/IPP2/ARRI/Sonywatch full video

Watch for: Why a facility wants a look that can impersonate another vendor's display render, and how that's a gamut-and-tone matching exercise, not a creative one.

Read

• Chris Brejon — CG Cinematography, ch.1 (chrisbrejon.com): the clearest free write-up of what a view transform / DRT is and why naïve clipping breaks images.
• ACESCentral (acescentral.com): the ACES Output Transform and gamut-compression documentation — the reference for how one widely-used DRT is actually built.

The paid path: deep, systematic DRT and tone-mapping theory — building your own, not just choosing one — is the moat of colour.training’s advanced modules and Mixing Light’s color-management series. This page gives you the reasoning; those give you the bench time.

Next up: 3.3 · Show pipeline & show LUT design — assembling working space, DRT and look into a pipeline a whole production runs on.