Choosing a Color Management Approach
Choose one of five color-management approaches:
- Display Referred, un-color-managed: the look is baked into the grade, with no recoverable scene-referred master.
- Manually Color Managed: a hand-made pipeline with a consistent scene-referred working space, color-space transforms in, node- or layer-based grading, and a standard or bespoke display transform out. This is typically what people mean when they talk about "node-based color management" in Resolve.
- ACES: an open, standardized, scene-referred pipeline (SMPTE ST 2065).
- DaVinci Resolve Color Management (RCM): Blackmagic's in-application managed workflow on DaVinci Wide Gamut / Intermediate.
- FilmLight Truelight Color Spaces (TCS) + T-CAM: FilmLight's managed workflow on E-Gamut / T-Log with a color-appearance display transform.
In every managed approach, track whether the image is scene-referred or display-referred and apply the display transform last. All but the first approach retain a scene-referred working space and recoverable master.
This is a choice about interchange, not image quality
Managed systems enforce consistency across cameras, vendors, applications, and deliverables. They do not guarantee better images. Choose based on interchange, workflow, and archival needs.
The five approaches
Display Referred, un-color-managed
You grade the footage more or less as the camera and monitor present it: a camera-native log or even a display-space signal, and bake the look directly into the grade. There is no defined working space, no separately applied display transform, and no route back to a graded assembly master. The master is the look. There is no scene-referred version to re-render from.
- What it is not. A simple job with a consistent working space and the display transform applied last is Manually Color Managed. An un-color-managed finish leaves only a baked image for future deliverables.
- Why it fails. Technical and creative decisions are entangled. It does not scale to multi-camera, multi-vendor, or multi-deliverable work, and it fails quietly rather than loudly: you discover the cost only when someone needs the scene-referred master that cannot be produced.
Avoid an un-color-managed finish
A second deliverable, re-grade, show LUT, VFX preview, or archival master requires a recoverable scene-referred source. Establish the working space and deliverables with the colorist before engagement.
Manually Color Managed
The colorist maps each source into a common scene-referred working space, grades with node- or layer-based tools, and renders through a standard or custom display transform. CSTs, LUTs, and DCTLs replace an automatic vendor framework.
- Benefits. Full control over the working space, tone mapping, and look while retaining a recoverable graded master.
- Drawbacks. Requires an experienced colorist to design, document, test, and distribute every transform. An undocumented manual pipeline is as fragile as an unmanaged one.
ACES
A scene-referred interchange encoding (ACES2065-1, SMPTE ST 2065-1), working spaces derived from it (ACEScg for comp, ACEScct for grading), an Input Transform at the front and an Output Transform at the back, delivered in practice as an OCIO config.
- Benefits. Open, vendor-neutral interchange through OCIO and a documented scene-referred archival encoding in ACES2065-1.
- Drawbacks. Requires setup, testing, and version discipline. Its interchange benefits may go unused on a single-camera, single-deliverable project. Use another approach when the desired look conflicts with the standard Output Transform.
DaVinci Resolve Color Management
Blackmagic's DaVinci YRGB Color Managed mode: per-clip Input Color Space → a timeline working space → an Output Color Space per deliverable, with the display transform applied last.
- Benefits. Low-friction Resolve workflow. Documented DWG/Intermediate working space. Straightforward SDR, HDR, Rec.709, P3, and Rec.2020 outputs.
- Drawbacks. The display rendering is internal to Resolve and is not an archival interchange standard. External vendors need supplied transforms and guidance.
FilmLight TCS + T-CAM
FilmLight's Truelight Color Spaces: an E-Gamut / T-Log working space and the T-CAM v2 color-appearance display transform, in Baselight and Daylight.
- Benefits. Scene-referred Baselight workflow with a documented CAM-based DRT and portable FilmLight transform files, OCIO config, and Flame policy.
- Drawbacks. FilmLight controls the implementation. Cross-application support is narrower than ACES.
Side-by-side1
| Display Referred, un-color-managed | Manually Color Managed | ACES | Resolve RCM | FilmLight TCS | |
|---|---|---|---|---|---|
| Working space | None (camera-native / display) | Consistent scene-referred (colorist's choice) | ACEScg / ACEScct | DaVinci Wide Gamut + Intermediate | E-Gamut + T-Log |
| Display transform | Baked into grade | Chosen standard or bespoke DRT | ACES Output Transform | Resolve DRT (internal) | T-CAM v2 (CAM-based) |
| Enforces the discipline | No | By the colorist | Automatically | Automatically | Automatically |
| Route back to a scene-referred master | No | Yes, if documented | Yes (ACES2065-1) | Yes (working-space master) | Yes (working-space master) |
| Open standard? | n/a | No, hand-built | Yes, SMPTE ST 2065 | No, single vendor | No, single vendor |
| Published? | n/a | As the colorist documents it | Fully (free SMPTE library + open CTL) | Encoding yes (white paper). Rendering no | Color-space/DRT files + OCIO config. Not a spec |
| Cross-app native support | n/a | Only via the colorist's exported transforms | Broad via OCIO | In-application (Resolve) | Via published files / OCIO config / Flame policy |
| In-app setup (single facility) | None | Moderate–high (build and test) | A little config | Low (if in Resolve) | Low–moderate (if in Baselight) |
| Multi-camera normalization | Poor | Strong (manual CSTs) | Strong | Strong | Strong, equal labor to ACES |
| Multi-vendor VFX (total effort) | Fails | High, colorist supplies transforms + guidance | Low, vendors already speak it | High, colorist authors transforms + guidance per vendor | High, same despite portable files |
| Interoperates with ACES | n/a | Yes, if built on ACES | Is ACES | Yes (Resolve has ACES modes) | Yes (v7 ACES 2.0) |
Which should an independent production choose?
Rule out truly un-color-managed. For a production that will deliver professionally, a baked, unrecoverable master is not a reasonable option. This is particularly true for a VFX production.
The baseline is a manually color-managed pipeline: a consistent scene-referred working space, the display transform(s) applied last, and a documented master you can re-render from. That floor costs almost nothing over "just grading," and it is the difference between a show you can repurpose and one you cannot.
Reach for a framework (ACES / RCM / TCS) when:
- You have multiple camera systems or VFX vendors. Prefer ACES when work crosses applications and vendors.
- You lack the color-science resources to build and vet a bespoke workflow. A documented, standardized pipeline you can adopt is safer than a homemade one you cannot fully test: a framework gives you the discipline of a manually color-managed pipeline without having to author it.
Between the frameworks:
- Choose ACES for the widest, most vendor-neutral interchange and for a scene-referred archival master: the Graded Archival Master case.
- Choose Resolve RCM for a single-facility Resolve finish with scene-referred VFX deliveries in an agreed working space.
- Choose FilmLight TCS / T-CAM when you finish at a Baselight house or specifically want T-CAM's rendering. Its published files and OCIO config make it more portable than Resolve's DRT, and it interoperates with ACES.
A manually color-managed pipeline earns its place when:
- You have the color-science resources to design, document, and test it, plus a specific reason to control the DRT or look.
- The job is small enough that a full framework is overkill but you still want a consistent working space and a recoverable master: the responsible version of "keep it simple."
- Bear in mind it costs the same as a vendor framework to push across VFX vendors: the colorist has to supply the transforms and written guidance, just as with RCM or TCS.
Even a single-deliverable commercial benefits from a consistent working space: controls behave predictably and grades and looks remain reusable across camera sources.
Use interchange and archival as the tie-breaker
More sources, tools, vendors, deliverables, or uncertainty favor a framework and often ACES. A small, fixed pipeline can remain manual. In either case, retain a consistent working space and a recoverable master.
Choose the pipeline in pre-production with the colorist. Record it in the format specifications and prove it with a confidence package before shot work. Preserve a defined working space and re-renderable master.
-
Sources include Blackmagic's DaVinci Resolve 21 Reference Manual, The Colorist Guide to DaVinci Resolve 20, and DWG/Intermediate white paper, Kirk's Colour: Sense & Measurement, and FilmLight's TCS documentation. See Supplemental Reading & Resources. ↩