03 / 04 COLOR · A CLEAR START
Node flow.Give each node a clear purpose.
Image and matte are two different signals. Explore serial chains, parallel branches, Layer Mixer and Outside so that your graph explains the grade.
4 structures · RGB and key · processing contexts
A correction with a named task. Select a connected node to trace its input and output.
Learning diagram, not an embedded Resolve editor. This example does not apply a grade to the image.
UNDERSTAND THE MECHANISM
Read a graph by its connections, not by where the boxes sit.
For each node, ask “what reaches its input?” and then “what limits the correction?” Those answers matter more than node count or a symmetrical layout.
Image and key solve different problems
An RGB connection carries the image between stages. Key is an influence-limiting signal—a matte—not another coloured copy of the shot. A blue connection therefore does not mean a second image branch. Trace the image route to the output and the source of the required matte separately.
Ask which downstream operations receive a changed image when balance is adjusted upstream. A colour-based isolation later in a serial chain may respond to that change. Before repairing a different-looking selection, identify what signal it is now analysing.
RememberWire colour indicates the signal type; the connections determine the dependency.
Order is part of the correction
“Change colour, then isolate a range” is not equivalent to “isolate a range, then change colour.” In the first case, the selection analyses altered material. In the second, its input differs. Decide which dependency suits the task before arranging nodes.
A few labelled stages—balance, tonal shape, local correction, style—are enough for learning. They are not a mandatory professional template or a rule to use four nodes everywhere. A separate node is useful when its contribution needs independent comparison, isolation, replacement or adjustment.
RememberA node label should explain its job, not imply a universal order.
The same wheels can act in different contexts
Before adjusting anything, check whether the Clip, group or Timeline graph is active. Tool names may stay the same while the correction scope becomes shared across shots. Use Clip for initial exercises to connect a change to one test shot without unintentionally affecting its neighbours.
In a larger project, shared technical or stylistic work can be separated from shot matching. Moving an operation to a shared context is not merely tidying the graph: it changes scope and position relative to other stages. Check several different clips after such a move, not one convenient example.
RememberBefore blaming a parameter, check the node’s processing scope.
Do not add technical transforms to make a graph look complete
Before adding a CST or LUT, identify the image’s current encoding and what the next operation expects. In a colour-managed project, some conversions are defined by project settings. In a manual workflow, conversions may appear in the graph. Do not mix approaches without understanding each operation.
If a new conversion makes the image excessively contrasty, do not start with a compensating node. On a project copy, inspect the input settings, upstream operations and shared contexts. Temporarily disabling the suspected stage is more informative than resetting the entire grade.
RememberEach transform should have an identifiable input, output and reason to exist.
UNDERSTAND THE TOOL
Connections determine the result.
How to read the Node Editor
The Color node graph is read from left to right. Green connections carry the image signal, while blue connections carry key or matte information. Once you start seeing nodes as a signal path instead of isolated boxes, complex graphs become much easier to understand.
- Green carries the image
- Blue carries key/matte
- Signal flow runs from input to output
Serial Nodes
A Serial Node receives the already processed result of the previous node. It is the clearest foundation for most grades: one node can handle the base balance, the next a local correction, another the look or final refinement.
- Each node sees the previous result
- The easiest structure to read
- Operation order really matters
Parallel Nodes
A Parallel structure is useful when several secondary corrections should work from the same upstream signal instead of altering one another in sequence. Skin, sky and background can live on separate branches and then merge through a Parallel Mixer.
- Useful for separating secondaries
- Branches do not have to be sequential
- Merged through a Parallel Mixer
Layer Mixer
Layer Mixer is for cases where branch order and compositing behavior matter, not just parallel processing. The layer order affects the result and the branches can be combined using layer-style compositing logic, which is useful for more complex looks and local combinations.
- Layer order affects the result
- Useful for more advanced mixing
- Not the same as a Parallel Mixer
Outside Node
An Outside Node is built around the inverse of the source node's key. Once you isolate a face, product or other subject, the next correction can act on everything outside that matte. It is a clean way to separate subject and environment without building a second mask from scratch.
- Uses the inverse of the source key
- Useful after a Qualifier or Window
- Great for separating subject and background
REASON THROUGH A CASE
When Serial is enough, and when a branch has a purpose.
No topology automatically makes a grade professional. Compare the tasks: the choice comes from dependencies between operations.
Balance first, then a creative look
You want the look to operate on the balanced shot and be independently disabled for comparison.
Check your reasoning
Start with a serial chain so the second node receives the first node’s result. Label both, then compare the look by toggling only its node. Branching needs an additional reason here; it does not inherently improve quality.
Two selections should analyse the same starting image
The first local correction changes the colour used by the second isolation. You want to adjust these tasks separately.
Check your reasoning
Consider two branches from a common input. Verify the actual connections: nodes at the same height do not prove a shared source. After combining them, inspect overlapping matte areas. Independent inputs do not guarantee that the final contributions never interact.
An object is isolated; its surroundings need a separate change
Do you need to create a second, almost identical isolation manually?
Check your reasoning
First consider an Outside correction linked to the existing key, rather than a separately maintained selection. Changes to the original matte also affect the linked outside region, so check both sides and the soft transition. Outside does not replace motion tracking or guarantee a clean edge throughout the shot.
UNDERSTAND THE TOOL
Build a workflow, not a universal recipe.
- 01
01 · Technical base
First check RAW decoding and color management. RAW controls operate before the Node Editor; RCM/ACES may transform the signal outside clip nodes. Add CSTs and noise reduction deliberately without duplicating processing already configured elsewhere.
- 02
02 · Primary correction
White balance, exposure and overall contrast. A clean base makes everything downstream easier, so there is little value in fixing the foundation with ten local nodes.
- 03
03 · Secondaries
Skin, sky, background, isolated objects, Qualifiers and Power Windows. This is where separating tasks into nodes and using Parallel or Outside structures often makes sense.
- 04
04 · Look
Creative styling, film look and broader color character. It is easier to control when the technical base and local fixes are not mixed into the same node.
- 05
05 · Final check
Final levels, saturation, clipping, scopes and output logic. This is not a mandatory universal recipe, but a readable teaching template you can adapt into your own node structure.
GUIDED PRACTICE
Practice: build a chain and isolate the source of an error.
Reversibility and readability matter more than node count. Work on a project copy and do not carry exaggerated test changes into the production edit.
Use one clip in the Clip context with known colour management. Leave working technical transforms unchanged. Use the Add Node menu for the exercise rather than keyboard shortcuts from someone else’s preset.
- 01
Create three roles
DO THISAdd serial correction nodes named Balance, Contrast and Local. Trace the RGB path from input through all three to the output.
WHAT TO CHECKEvery node has a clear job; a floating node outside the route is not an active processing stage.
- 02
Change only one role
DO THISMake a small adjustment in Balance and a separate tonal adjustment in Contrast. Toggle them individually while leaving other nodes enabled.
WHAT TO CHECKEach node’s contribution is distinguishable. If the result is unexpected, check selection before adding another compensating node.
- 03
Limit the third correction
DO THISCreate a simple soft window in Local and make a moderate adjustment inside it. Inspect the matte diagnostically, then return to the normal image.
WHAT TO CHECKThe intended area changes without an obvious soft boundary. A moving shot also requires checking the window’s motion.
- 04
Introduce a controlled error
DO THISOn the copy, exaggerate only Contrast until the result is clearly worse. Then locate the cause by toggling correction nodes instead of reading their values.
WHAT TO CHECKYou located the stage from its visible contribution. You do not need to disable technical conversions along with all nodes when the question concerns only contrast.
- 05
Restore a deliberate state
DO THISRemove the exaggerated test change, inspect the window edges, play the clip and save. Every remaining node should have a job you can explain in one sentence.
WHAT TO CHECKThe graph works and remains understandable enough to continue editing safely.
Completion criterion
The result is not a pretty arrangement of boxes: it is the ability to identify each operation’s contribution, trace RGB and key, and remove an error without discarding the whole grade.
Signal graph
A node is not merely a 'correction layer': input and output signal state matter
The Node Editor describes processing order and the relationship between image and key signals. Serial, Parallel, Layer Mixer and Outside are only the beginning: complex projects require understanding RGB/key connectors, group/timeline levels, Splitter/Combiner, Shared/Compound Nodes and transform placement. Then the graph reads like an engineering diagram rather than a collection of boxes.
green image connections
blue matte/key connections
upstream → downstream changes the result
Clip / Group / Timeline are different levels
Node Editor structures and when to use them
| Structure | Signal logic | Best for | Risk |
|---|---|---|---|
| Serial Node | the next node receives already-modified RGB | most sequential grading tasks | transform/key order can radically change the result |
| Parallel Mixer | several branches receive a common upstream state and are combined | independent secondaries | assuming branches have no interaction in the final mix |
| Layer Mixer | branches are composited as ordered layers | composite/order-dependent looks and keys | misunderstanding layer order and composite mode |
| Outside Node | uses the inverse of the source node key | adjusting the area outside an existing isolation | changing the source key also changes the Outside |
| Splitter / Combiner | splits and recombines RGB channels | specialised channel operations | easy to create non-obvious channel imbalance |
| Shared / Compound | reuse or packaging of graph logic | repeated logic and complexity management | hidden cross-clip dependencies or opaque compounds |
A deliberate working method
- 01
1. Name the signal state
Before grading, identify the signal state: source camera space? timeline working space? display-referred or scene-referred? Where are input/output transforms? Without this, node order cannot be judged correctly.
- 02
2. Separate technical and creative work
Transforms, noise reduction, balancing, secondaries and look do not have to occupy five specific nodes, but they should be logically separable. This speeds up diagnosis and versioning.
- 03
3. Branch only for a reason
Parallel/Layer structures are useful when an independent processing path or layer behaviour is genuinely needed. Branching for visual complexity makes key routing and debugging harder.
- 04
4. Audit the graph by bypassing
Disable individual nodes and task groups to see the contribution of each stage. If you cannot explain what a node does, the graph has already lost readability.
WHEN SOMETHING LOOKS WRONG
Trace the cause.
01CST/LUT produces an overly contrasty result+
Possible cause. double transform or a transform placed at the wrong graph level
What to check. inspect project colour management, clip input space, group/timeline nodes and every CST/LUT
02The qualifier changes after an upstream adjustment+
Possible cause. the selection is built from an input image altered upstream in the RGB chain
What to check. check upstream corrections and RGB/key routing; a downstream-only adjustment does not itself recalculate the original selection
03A large graph is hard to read+
Possible cause. there are no names, colours, logical blocks or levels
What to check. label nodes, use node colours/graph levels and in Resolve 21 try Layer List view
FROM READING TO DOING
One clip.
Three checks.
Use a copy of your project or a test clip. These small checks turn the article into a repeatable workflow.
Back to the Color index ↗Self-check in Resolve; the site does not evaluate your work. Progress is not saved after reloading.
COMMON QUESTIONS
The details that matter.
What are nodes in DaVinci Resolve?
Nodes are processing stages inside the Color page. Each node can hold a correction, effect, key or other operation, and the graph defines how the image flows through those stages.
What is the difference between Serial and Parallel Nodes?
Serial Nodes process one after another, so each node receives the previous result. Parallel branches can work from the same upstream state and are then merged, which is useful for independent secondary corrections.
When should I use Layer Mixer instead of Parallel Mixer?
Use Layer Mixer when layer order and compositing behavior matter. Parallel Mixer is better when the main goal is to combine independent correction branches without treating them as an ordered layer stack.
What is an Outside Node used for?
It lets you work with the inverse of a source key. For example, after isolating a face you can use an Outside Node to correct the surrounding background without rebuilding the mask.
How many nodes should a grade have?
There is no correct number. Use enough nodes to keep tasks separated and readable, but not so many that the graph becomes harder to understand than the correction itself.
Sources & version notes
Diagrams and interactives are teaching models, not replicas of Resolve’s interface or processing engine. Original screenshots are retained; layout depends on the version and workspace.
Illustrations in the interactive labs are teaching models. Resolve screenshots retain their original site URLs. Studio availability and control layouts should be checked against your installed version.