
First confirm that the node is shared and identify the clips using it. Unlocking a shared node enables a change that can affect more than the current shot. The Resolve 20 Colorist Guide also warns that shared-node changes cannot be undone through the ordinary per-clip color-page Undo history.
Key Takeaways
- A shared node is intentionally linked across clips.
- Preserve a recovery checkpoint before a global change.
- Review every affected use, not just the current shot.
Identify the intended scope
A shared creative treatment may be useful across several scenes, while a one-shot exposure repair should remain local to that shot. Decide which kind of change you intend.
Look for the node's shared status and descriptive label. If its purpose is unclear, investigate the existing graph and project notes before turning a locked control into an editable one.
Preserve a recovery point
Blackmagic's Resolve 20 Colorist Guide describes shared nodes as linked, locked nodes that can be added to other clips in the project. It documents disabling Lock Node for global adjustments and explains the Undo limitation.
Create an identifiable project checkpoint through the supported workflow before experimenting. Do not rely on the current clip's Undo history as the only protection.
This guide follows the Resolve 20 training material. Check the behavior and controls in the installed version, especially before revising a project prepared by another colorist.
Make one controlled change
If the intention is a shared look revision, unlock the identified node and make a small, purposeful change. Review the current shot and other uses before continuing.
If the intention is only a local repair, keep the shared look's purpose intact and plan the correction in the appropriate local part of the graph. Avoid altering a project-wide treatment to solve one unusual shot.
In an illustrative sequence, a warmer shared look may flatter an exterior portrait but push an indoor face too far. The exterior's success does not establish acceptance for the indoor use.
Verify and document the affected set
Review representative bright, dark and mixed-light shots among the actual shared-node users. Compare against the preserved checkpoint and record which revision was accepted.
Keep the approved grade version identifiable. For the movie output, compare the render with the editing preview before treating the global revision as complete.
Source: Blackmagic's Resolve 20 Colorist Guide, printed page 239.
Related tasks
- How Do I Keep the Approved AI Image or Video from Getting Lost Among Revisions?
- Captions look correct in preview but move in the export: isolate a small render test
Sources and scope
- The Colorist Guide to DaVinci Resolve 20, Shared Nodes: Printed239: shared corrector node links/locks across clips; disabling Lock Node permits global tweaks; shared-node changes cannot use per-clip Undo.
Prepared by Imagild Editorial, the company editorial team responsible for these guides. AI assisted research and drafting. This is documentation-based guidance, not a claim of hands-on testing or independent review. Report a correction.
Cover: Pignatta / Pixabay, Content License. The city photograph is an illustrative source asset; it does not show this application or a test result.