Application-Native Color Management: Resolve and FilmLight

Blackmagic DaVinci Resolve and FilmLight Baselight include scene-referred color-management frameworks. Each assigns source color spaces, maps clips into one working space, and applies a display transform at output. Unlike ACES, these systems live inside a vendor product.

These frameworks automatically apply a defined chain of input, working-space, and output transforms. A colorist can instead build that chain manually with color space transforms (CSTs), LUTs, DCTLs, and a chosen display rendering transform. Manual construction offers more control but requires the colorist to maintain consistency.

DaVinci Wide Gamut is documented, and FilmLight publishes portable color-space files. Neither is an open standard like ACES (ST 2065-1) or has ACES's ecosystem-wide support through OpenColorIO. They are published and partially portable, but single-vendor.

Each system works in its own wide-gamut internal space. The three you will meet are ACES's AP1 (the ACEScg working gamut), DaVinci Wide Gamut, and FilmLight's E-Gamut (what T-CAM renders from). All are deliberately wide, encompassing most camera and display gamuts, with virtual primaries that fall outside the spectral locus:

The three managed working color spaces on the CIE 1931 diagram: ACES AP1 (ACEScg), DaVinci Wide Gamut, and FilmLight E-Gamut, the gamut T-CAM renders from. DaVinci Wide Gamut is the widest. All three reach beyond the spectral locus, but not to the same degree: DWG and E-Gamut do so dramatically, with negative blue-y and greens close to y = 1, while AP1 does so only slightly. Its blue primary sits at y = +0.044 and its green at y = 0.830. Interactive: drag to pan, scroll to zoom. Static version.

DaVinci Resolve Color Management (RCM)

Objective: normalize multiple cameras into one scene-referred working space and retarget deliverables inside Resolve. Assign each clip's camera profile. Resolve applies the corresponding log and gamut transform.¹

RCM inside one application: each source clip is assigned an input color space, mapped into the DaVinci Wide Gamut / Intermediate working space, then rendered through one output display transform (the Resolve DRT, applied last) to each deliverable: Rec.709, P3-D65, and Rec.2100.

RCM and ACES are both automatic, scene-referred systems. RCM is a configurable, single-vendor framework with selectable working spaces and output tone-mapping methods. Resolve can also run ACES directly, so grading in Resolve does not preclude an ACES pipeline.³

Blackmagic recommends DaVinci Wide Gamut (DWG) with the DaVinci Intermediate log curve.² Its primaries, white point, matrices, and log equations are published and can be reproduced in OCIO. Resolve's tone and gamut mapping remain internal. The encoding is specified. The rendering is not.

FilmLight: Baselight, Daylight, and the Truelight Color Spaces

Objective: manage a grade in E-Gamut / T-Log and render through the T-CAM v2 display transform. Baselight and Daylight implement this as the Truelight Color Spaces system. These are FilmLight product names, not standards. See FilmLight Truelight.

The same shape as RCM, inside Baselight / Daylight: each source clip is assigned a Truelight input, mapped into the E-Gamut / T-Log working space, then rendered to each display through the T-CAM v2 display transform (applied last).

T-CAM uses a lighter appearance model plus viewing-condition correction. ACES 2.0 uses a Hellwig-derived color appearance model. The difference affects display rendering and should be evaluated with the colorist.⁴

FilmLight publishes .flspace and .fltransform files, a Truelight OCIO config, and an Autodesk Flame color policy. Baselight can also run a full ACES pipeline. These files improve portability but remain vendor-controlled rather than independently implemented standards.⁶

Application-native color management vs. ACES: easier and harder

Setup effort depends on whether the pipeline crosses applications and vendors:

	Application-native (RCM / TCS)	ACES
Assigning input color spaces (camera normalization)	The same metadata-driven menu	The same metadata-driven menu: virtually identical labor
Single-app, single-facility finish	On by a project setting	Also a project setting. Runs in one app just as well
Multi-vendor VFX interchange	More work: no path to VFX vendors. The colorist hand-authors LUTs or transforms and workflow guidance for each vendor	Less work: VFX tools already ship OCIO/ACES configs. Vendors are already set up
Neutral archival master	No: a working space, not an interchange encoding	Yes: ACES2065-1

• Camera normalization requires similar labor in either system.
• ACES and OpenColorIO already ship in standard VFX applications through the VFX Reference Platform. Extending RCM or TCS across vendors requires the colorist to supply matching LUTs, transforms, and documentation.

Use an application-native system for a single-facility finish. Prefer ACES when the pipeline crosses vendors or requires a neutral archival master.

Why choose application-native color management over ACES?

Choose an application-native system when:

• The finish stays in one facility or application. For a documentary, commercial, or Resolve-only grade, ACES's interchange advantage may go unused.⁵
• Grading-tool behavior and working-space preference. Colorists often choose a timeline space because the grading controls behave the way they like in it: you can set RCM's timeline space to DaVinci Wide Gamut or any log format for exactly this reason.⁵
• You prefer its display rendering. The colorist may favor T-CAM or Resolve's DRT over the ACES Output Transform.⁶
• Only part of the pipeline needs ACES. Resolve and Baselight can use native working spaces while retaining ACES where interchange requires it.

Using a custom display transform

Either system can manage inputs and the working space while a custom LUT, DCTL, or DRT handles output. In ACES, this removes the guarantee that standard transforms alone can reconstruct the delivered look. Archive the custom transform with the master in a durable, documented form.

Documentary vs. single-camera narrative

Camera count and vendor count are separate considerations:

• Documentary: many source formats but usually one finishing facility. Application-native color management is often the lower-friction choice.
• VFX-heavy narrative: fewer source formats but multiple vendors, applications, and deliverables. ACES usually provides better interchange and archival support.

Many cameras do not inherently favor ACES. Many vendors, applications, deliverables, or an archival requirement do.

When to decide

Choose the working space and display transform in pre-production. Record them in the format specifications and prove the pipeline with a confidence package before shot work begins. See Choosing a Color Management Approach.

---

1. DaVinci Resolve 21 Reference Manual (Blackmagic Design, July 2026), Ch. 9, pp. 225–290. The Colorist Guide to DaVinci Resolve 20 (Blackmagic Design, 2025), Lesson 4. ↩

2. DaVinci Resolve 21 Reference Manual, Ch. 9, pp. 241–243. DaVinci Resolve 17: Wide Gamut Intermediate white paper (Blackmagic Design, 2021), including the corrected v1.1 green-x coordinate. ↩

3. DaVinci Resolve 21 Reference Manual, Ch. 9, covers the two color-science modes, the Output DRT tone-mapping options (incl. None), Resolve's ACES signal flow, working space, and AMF 2.0 support. ↩

4. Richard Kirk, Colour: Sense & Measurement (FilmLight, 2022): the T-CAM rationale (Ch. 5–6) and "simplest model" argument. FilmLight hosts a free PDF. The E-Gamut/T-Log/T-CAM-v2 product names and the portability specifics below come from FilmLight's own materials rather than the book. ↩

5. Resolve Color Management vs ACES, Which Should You Choose? (Frame.io Insider, 2024). See also Mixing Light and the ACESCentral RCM-vs-ACEScct discussion. Both RCM and ACES are scene-referred systems solving the same problem. ↩↩

6. FilmLight: Colour Management / Truelight and Baselight v7 Truelight Colour Space improvements. ↩↩