COLOR / TOOL GUIDE 11 / 13
Pipeline.
Describe the source. Control the output.
DaVinci YRGB, RCM and ACES organize transforms rather than provide beauty presets. Build a clear path from source encoding to delivery.
what the source code values mean
the state in which grading tools operate
the display/delivery state being produced
Distinguish the two levels: Project Settings define the project system; ACES Transform and CST are individual node tools. Each caption identifies the level shown.
BEFORE MOVING A CONTROL
Understand what you are changing.
Three states rather than a single “color” label
Identify source encoding, the space used for grading and the intended output conditions. MOV or MP4 describes neither of these states. Incorrect Input Color Space cannot reliably be fixed by random saturation compensation.
Choose where transforms occur. RCM delegates part of the work to project settings and clip tags; a manual workflow uses explicit nodes. Both require accurate source information. Automation reduces repetitive work but does not make incorrect metadata true.
Perform each technical transition once
If RCM already converts input log into the working space, a second node expecting that camera-log input may misinterpret the signal. Similarly, an early Rec.709 output transform must not silently be repeated at project output. Label each transform’s input and output explicitly.
A LUT may be technical, creative or both. Establish the encoding it expects. Do not reduce a required transform via Key Output Gain just to lower contrast; make that creative adjustment separately.
Validate the path through delivery and viewing
Output Color Space, file tags and actual pixel transforms are related but distinct. No single gamma switch guarantees agreement in every player. Compare under understood viewing conditions and check for additional display transforms.
ACES is useful in coordinated production interchange. Record version, input/output transforms, AMF and required LUTs with the project. The ACES Transform screenshot here shows a node tool, not the project’s ACES settings panel.
FROM PURPOSE TO CONTROL
Choose deliberately, not by trial and error.
The interface images are collected in the viewer above. Here, focus on what each control changes and when to use it; values in the captures are not universal presets.
Three approaches to color management
DaVinci YRGB
The base mode where you define the technical transform path yourself. It is useful when you know exactly where the transform happens: through CST, LUTs, Camera Raw or inside specific nodes.
- Useful for manual node-based workflows
- Requires understanding of source and output spaces
- Good for deliberate CST-based pipelines
DaVinci YRGB Color Managed
Resolve handles much of the transform chain for you. That works well for mixed-camera projects, clean SDR/HDR delivery and stable grading in a wide working space such as DaVinci Wide Gamut.
- Faster to configure at project start
- Well suited to SDR and HDR deliverables
- Reduces the risk of accidental double transforms
ACEScct / ACEScc
ACES is especially relevant in larger mixed pipelines where a shared standard between cameras, VFX, grading and delivery matters. In Resolve it is a separate color-management system, not simply a prettier mode.
- Works well for multi-camera and VFX pipelines
- Uses Input and Output Transforms
- Requires stricter discipline in setup choices
Decisions before grading
Color management defines the technical foundation of the project
This is not just an extra setting. It tells Resolve what came from the camera, which working space you use and what the signal should become at the output.
DaVinci YRGB, YRGB Color Managed and ACES are different approaches
Plain YRGB leaves more manual control, a managed workflow automates transforms inside the project, and ACES is useful when a unified standardized color system matters.
CST is used when you need an explicit transform
Color Space Transform lets you describe the path honestly: which color space and gamma you start from and which one you convert to. That is better than guessing with LUTs by eye.
Log → Rec.709 is a technical transform, not a creative look
First normalize the signal, then shape contrast, skin tone, saturation and style. If the technical base is broken, creative grading starts to fall apart.
Technical pipeline checks
Applying LUTs before understanding the pipeline
A LUT can be useful, but if the signal state is unclear, the LUT easily becomes a random patch on top of a broken foundation.
Applying a double transform
One of the most common mistakes is transforming already-normalized footage again through CST, an input LUT or a managed transform. That often creates a harsh or unnatural image.
Mixing technical and creative nodes into one mess
When CST, contrast, skin work and the look are piled together without structure, it becomes harder to trace errors and maintain the project. A clean structure saves time throughout the whole job.
Expecting color management to create a cinematic look by itself
Color management is mainly about technical predictability. It does not replace taste, references, lighting or full creative grading.
TECHNICAL REFERENCE
Colour management starts with three questions: what came in, where we grade, where we output
The most common colour-management mistake is treating RCM, CST, ACES and LUTs as interchangeable buttons. They are different ways of describing transitions between image states. Each clip needs a known input colour space, the grade needs a working/timeline space, and delivery needs an output space. If one stage happens twice or not at all, the image is already wrong before creative grading begins.
RCM, CST, ACES and LUTs — what each actually solves
Choose an architecture for the project, not by fashion. The key test is whether you can state unambiguously what colour state the signal is in at each point in the chain.
| Approach | Where transforms are defined | Strength | Main risk |
|---|---|---|---|
| DaVinci YRGB + CST | explicit CST/LUT/node transforms | maximum visibility and order control | missing or duplicated transform |
| DaVinci YRGB Color Managed | Project Settings + clip input tags + output | scalable mixed-camera workflow | wrong Input Color Space or a hidden manual conversion on top of RCM |
| DaVinci Wide Gamut / Intermediate | as a wide working space inside RCM or a manual pipeline | wide gamut/headroom for scene-referred grading | an early Rec.709 transform inside the graph |
| ACEScct | IDT/input transform → ACES working state → Output Transform | standardised interchange and VFX pipeline | mixing ACES and non-ACES transforms without a clear reason |
| LUT-only | a lookup table at a chosen point | fast fixed transform/look | a LUT does not automatically know input state, display peak or project context |
FROM KNOWLEDGE TO A REPEATABLE RESULT
One exercise. A result you can check.
Use a separate test project with two known sources, such as log and already prepared Rec.709. Record each encoding and the delivery target. Do not change color science mid-approved-grade without a controlled copy.
- 01
Decide which system the project lives in
Do not start with a LUT. First decide whether the project is in DaVinci YRGB, a managed workflow or ACES. Otherwise every later decision becomes random.
- 02
Describe the source honestly
If the camera shot Log, choose the correct input. If the clip is already transformed to Rec.709, do not make Resolve apply another transform on top of it.
- 03
Separate technical and creative grading
Normalize the signal first, then add contrast, saturation, skin work and the look. That makes node trees easier to read and fix.
- 04
Check the result on both the Viewer and scopes
Even the most correct workflow does not replace image evaluation. Watch the levels, channels and saturation instead of trusting one checkbox in settings.
Self-check in Resolve; the site does not evaluate your work. Progress is not saved after reloading.
An editorial exercise for your own footage, not an automated check of a Resolve project. Work on a copy or separate version and evaluate the complete shot.
WHEN THE RESULT IS NOT WHAT YOU EXPECT
Find the cause, not a compensating slider.
01Log suddenly becomes too contrasty and saturated+
Possible cause. an input/output transform is applied twice: RCM + CST/LUT or RAW decode + RCM
What to check. Project Color Science, clip Input Color Space, Camera Raw and every technical node
02One camera family looks wrong in a mixed-camera project+
Possible cause. wrong input tag/gamma/gamut or a camera LUT before colour management
What to check. metadata, Input Color Space and the first technical transform for that camera
03Resolve looks correct but exported playback differs+
Possible cause. output tags, display management and player behaviour are being confused with the grade
What to check. Output Color Space, video/data levels, tags, calibrated output path and an independent reference player
A SITUATION TO THINK THROUGHAdding a camera-log-to-Rec.709 CST in an RCM project radically changed the image. Which Contrast value fixes it?Compare your reasoning ↓
Inspect the pipeline first. The CST may expect original log while receiving the RCM working space, or it may duplicate the output transform. Remove duplication and align signal states; Contrast compensation only hides the technical error.
Sources and version notes
Checked against Blackmagic Design’s Color documentation and the relevant new-feature guides. Screenshots are from the site’s own supplied library; controls and layout can differ between versions. Examples are instructional, not universal production settings.
Back to the interface reference ↑