RESOLVE FX · HARD GAMUT COMPLIANCE · FREE
Gamut Limiter.
Describe the signal.
Clip only the boundary you actually owe.
Gamut Limiter is a late technical guard for strict chromaticity compliance. Its three-field contract is intentionally small: Current Gamut + Current Gamma describe what enters the FX, and Limit Gamut to defines the legal target. Everything outside is hard clipped.
Current Gamut
Current Gamma
Target boundary
In the lab, deliberately set Current Gamut/Gamma wrong, then enable both project-level and node-level limiting. The useful lesson is not the symbolic picture — it is how quickly confidence collapses when signal description or ownership becomes ambiguous.
Teaching model only. The circles and sample points are deliberately symbolic and do not reproduce CIE primaries, Resolve color science, proprietary limiting math, or pixel output. The lab teaches ownership: describe the actual node signal, choose a specification-driven target, preserve appearance upstream, and avoid duplicate hard limiting.
4 actual Resolve captures + independent contract/boundary teaching model
3 CONTROLS · HARD CLIP · NO BLEND01CONTRACT → BOUNDARY → OWNERSHIP
Three simple fields sit on top of three non-negotiable decisions.
The effect is easy only after you know the signal state and the delivery specification. Without those two facts, the dropdowns are just plausible-looking guesses.
Describe the signal first, then enforce the boundary.
Current Gamut + Current Gamma form one input signal contract. The limiter does not infer what an upstream CST, DCTL, LUT, Group/Timeline node, or RCM stage has done. Use timeline is correct only while the actual node input still matches timeline state.
Gamut Limiter is a hard clip, not perceptual compression.
Blackmagic explicitly describes the operation as limiting and says out-of-bounds values are hard clipped. Multiple distinct colors beyond the boundary can collapse onto it and lose separation. Preserve difficult saturation relationships upstream with gamut mapping/grading, then keep the limiter as a final guard.
One owner for limiting — avoid duplicate hard boundaries.
The FX works with or without RCM, but a managed pipeline can already own the requirement through project-level Limit Output Gamut To. If the project already enforces the same boundary, a second node-level limiter needs an explicit reason or clipping ownership becomes ambiguous.
Resolve 21.1 manual boundary: Gamut Limiter can be used with or without RCM, out-of-bounds values are hard clipped, and Blackmagic recommends keeping it among the last operations so useful image data is not clipped too early.
02REAL RESOLVE 21 CONTROLS
Only three visible controls — but each belongs to a different layer of the contract.
All four screenshots below are actual Resolve captures. Note the live Inspector label Limit Gamut to; the current manual transcript contains a wording typo but its behavior description is unambiguous.
AA · Input signal contract
Two fields describe what actually enters Gamut Limiter.
- Current Gamut
The primaries/gamut of RGB values at the FX input. Use timeline inherits timeline gamut; choose an explicit value when an upstream transform has already changed the state.
VERIFYAudit the preceding CST/DCTL/LUT, Group/Timeline nodes, and project color management. Do not choose a camera gamut by name if the signal has already been normalized.
- Current Gamma
The current transfer function/encoding of the RGB values. A gamut boundary cannot be evaluated correctly if the numbers are interpreted in the wrong gamma/log/PQ/HLG system.
VERIFYCheck whether Log has already been converted to PQ/HLG/display gamma or another working gamma before this node.
BB · Compliance boundary
The third field defines an allowed target gamut, not a look.
- Limit Gamut to
The gamut within which final chromaticities must remain. Values beyond the boundary are hard clipped. The target must come from the delivery/QC specification: Rec.709, P3-D65, P3-DCI, and other variants are not interchangeable.
VERIFYDo not choose a smaller gamut merely because saturation looks strong. Start with a technical requirement and the exact specification.
CC · Behavior / placement
There is no Blend control: the real controls are signal state and pipeline placement.
- Hard clipping
Out-of-gamut differences can be irreversibly lost as values beyond the target boundary are forced onto that boundary.
VERIFYCheck neon, LEDs, synthetic graphics, gradients, and highly saturated highlights on CIE Chromaticity, the Viewer, and RGB Parade.
- Node placement
Blackmagic recommends the limiter as one of the last operations in the node tree so useful image data is not clipped before creative/mapping work.
VERIFYAvoid unexpected saturation/transform operations after the limiter that push chromaticities beyond the required boundary again.
03ONE JOB PER STAGE
Preserve appearance upstream. Describe the actual state. Hard-limit late. Verify the real output.
Switch the graph between manual YRGB and managed RCM. The details differ, but the ownership rule survives both pipelines.
Set Current Gamut + Current Gamma
Describe the actual RGB state entering the FX. Use timeline only if that statement is literally true at this node; otherwise select the explicit gamut/gamma pair produced by the upstream chain.
The graph is decision order, not mandatory node count. The durable split is: define the specification → preserve appearance → describe the actual signal → enforce one strict boundary → verify the delivered output.
04BUILD IT IN RESOLVE
Four exercises cover HDR container limiting, manual transforms, managed ownership, and clipping stress-tests.
These are workflow exercises, not universal presets. The target gamut and signal state always come from the real job, project, and delivery specification.
Rec.2020 container → P3-D65 boundary
Build the classic HDR/QC case with a large delivery container and a smaller allowed chromaticity boundary.
PrepareUse material already in the final Rec.2020/PQ output state plus a specification that explicitly requires P3-D65-limited content.
- 01
Confirm Current Gamut = Rec.2020 and the actual Current Gamma = the matching ST2084/PQ variant at this point.
- 02
Set Limit Gamut to = P3-D65 only because the specification requires it.
- 03
Inspect CIE Chromaticity and the most saturated shots before/after the limiter.
- 04
If separation visibly collapses, perform smooth gamut mapping upstream and return the limiter to its role as final guard.
Chromaticities stay within the required P3-D65 boundary while visible clipping is minimized by upstream mapping.
Manual YRGB after an output CST
Avoid a false Use timeline assumption after a manual transform.
PrepareBuild a node chain where a CST before Gamut Limiter converts the working space into delivery gamut/gamma.
- 01
Write down the output CST pair. That is the limiter’s actual input state.
- 02
In Gamut Limiter choose explicit Current Gamut/Gamma instead of Use timeline when timeline state differs.
- 03
Choose the target boundary from QC spec and compare against deliberately wrong Use timeline as a diagnostic exercise.
- 04
Restore the correct pair and verify scopes.
The limiter interprets RGB in the same state actually emitted by the CST; Current pair selection is no longer guesswork.
RCM: establish the limiting owner first
Avoid duplicating project-level Limit Output Gamut To with a node-level Gamut Limiter.
PrepareAn RCM project using Custom Settings, an Output Color Space, and potentially Limit Output Gamut To.
- 01
Check whether the project setting already enforces the required gamut.
- 02
Assign one owner for strict limiting: project level or node-level FX.
- 03
If a local FX is required, document why and record its Current Gamut/Gamma.
- 04
Compare scopes/output with one and two limiting stages and keep only the justified architecture.
The pipeline has one clear hard-boundary responsibility with no hidden double limiting.
Stress-test with neon / LEDs / graphics
See the cost of hard clipping before master delivery.
PrepareFind shots containing saturated LEDs, neon, synthetic gradients, graphics, or intense reflections.
- 01
Inspect the out-of-gamut distribution with the limiter bypassed.
- 02
Enable the limiter and look for multiple colors flattening onto the same boundary.
- 03
If the artifact is visible, try upstream gamut mapping or targeted hue/saturation shaping.
- 04
Re-enable the limiter and confirm final compliance after appearance-preserving correction.
Hard clipping acts as a residual guard rather than the primary way to tame saturation.
05DO NOT CONFUSE THE JOBS
Limiter, mapping, transform, and targeted compression can all change saturation — but they own different problems.
| Tool | What it owns | Use it when |
|---|---|---|
| Gamut Limiter | Hard-limits chromaticities to a selected gamut boundary. | Final compliance guard when the specification requires a strict boundary. |
| Gamut Mapping | Remaps/compresses saturation relationships instead of only hard clipping. | When you need to preserve more hue/saturation separation while fitting a smaller gamut. |
| Color Space Transform | Explicit input→output colorspace/gamma transform with tone/gamut mapping options. | When the job is to transform signal state, not merely enforce a final boundary. |
| Color Compressor | Compresses selected Hue/Saturation/Luminance variation toward a Target Color. | When the problem is localized by color/subject rather than a global delivery boundary. |
06SYMPTOM → CAUSE → FIX
Most failures are either a wrong signal description, duplicate ownership, or the visible cost of hard clipping.
01Enabling the limiter changes most of the palette.+
Current Gamut/Gamma likely do not describe the real node input. Audit the previous technical transform and replace Use timeline with an explicit pair if the state has already changed.
02Neon/LED colors are legal but several hues collapsed together.+
This is typical of hard clipping a large out-of-gamut region. Use smooth gamut mapping/targeted grading upstream and keep the limiter only for residual excursions.
03The CIE scope is legal at the limiter but an excursion returns at output.+
Another color-changing stage follows the limiter: Timeline/Group node, output CST/DRT, LUT, or saturation. Move the guard closer to the true final stage or verify the monitoring point.
04P3 is selected but QC still fails.+
Verify the exact P3 variant/white point, Current Gamma, output metadata, and QC measurement point. “P3” is not one universal signal contract.
05In RCM the result is hard to explain and some shots look over-limited.+
Check project-level Limit Output Gamut To. Strict limiting may be happening twice. Keep one owner for the boundary and document it.
06You want to reduce the effect with Blend, but there is no Blend control.+
This is a technical limiter with three Inspector fields and no Global Blend. If hard clipping is too destructive, preserve relationships upstream with gamut mapping/grading rather than trying to mix the compliance boundary partially.
CIE Chromaticity
Primary scope check for the gamut boundary itself: inspect where saturated chromaticities fall relative to target primaries/standard.
Viewer + RGB Parade
The Viewer reveals posterization/flattening and lost hue separation; RGB Parade helps expose channel clipping/plateaus after hard limiting.
Final output point
Do not verify only at the node-local stage: the final output transform, timeline nodes, and metadata must match the same delivery/QC requirement.
07BEFORE YOU DELIVER
Approve the contract, the boundary, and the final measured output — not just the node itself.
The checklist is a workflow guardrail. It does not replace your delivery specification, installed Resolve build, calibrated monitoring, scopes, or external QC.
08FAQ
The distinctions that keep a compliance tool from becoming a destructive saturation shortcut.
Are Gamut Limiter and Gamut Mapping the same thing?
No. Gamut Limiter hard-clips out-of-gamut values to the selected boundary. Gamut Mapping/compression attempts to remap them while preserving more hue/saturation relationships and gradation. In demanding delivery workflows, mapping often comes first and the limiter acts as the last guard.
What does Use timeline mean?
The FX uses timeline gamut or gamma as the current signal description. This is correct only if the signal at this point in the node tree still matches timeline state. After a manual CST/DCTL/LUT, an explicit setting may be required.
Why is Current Gamma needed if the tool limits gamut?
Because RGB numbers must be interpreted in their real transfer function before a color-space boundary operation. Primaries without encoding are an incomplete signal description.
Why should Gamut Limiter sit near the end of the node tree?
Hard clipping irreversibly discards useful out-of-gamut differences. Blackmagic recommends the limiter as one of the last operations so creative grading and gamut compression work with fuller data upstream.
Does Gamut Limiter have Global Blend?
Not in the Resolve 21 Inspector shown here. It exposes Current Gamut, Current Gamma, and Limit Gamut to only. If the result is too destructive, fix the upstream mapping/grade rather than trying to partially mix the limiter.
Can the FX be used without Resolve Color Management?
Yes. The manual explicitly says Gamut Limiter can be used whether or not RCM is enabled. In manual YRGB, you are responsible for setting Current Gamut/Gamma correctly.
Should the limiter always be placed on a Timeline node?
No. A Timeline node can be convenient for a program-wide rule, but the correct point depends on output architecture. The FX must see the signal state you describe, and unexpected color-changing stages should not follow it.
Why does the manual say “Limit Gamma to” while the Inspector says “Limit Gamut to”?
In the current manual transcript this appears to be a typo: the accompanying description says to choose the gamut to restrict, while the actual Resolve 21 capture clearly shows “Limit Gamut to”. This guide follows the live UI label.
Sources and verification boundaries
Visible names and dropdown state were checked against the four actual Resolve captures in the project archive. Behavior was cross-checked against the current Resolve 21.1 manual, Blackmagic’s support release, project-level color-management documentation, and the Dolby delivery discussion linked below. The interactive chromaticity cloud is deliberately symbolic and does not reproduce CIE geometry, proprietary Resolve math, or pixel output.
This web pass does not claim live Resolve-render certification. Final acceptance belongs to the installed Resolve build, the real mastering pipeline, calibrated scopes/monitoring, and the rendered delivery file.