1. Describe current signal
Current Gamut + Current Gamma tell Resolve how to interpret the RGB values entering the FX.
A technical Resolve FX that hard-limits colour values to a specified gamut — useful when a large delivery gamut must contain content restricted to a smaller QC gamut.
What the limiter actually does
Blackmagic describes Gamut Limiter as a hard-clipping operation. Values outside the selected target gamut are forced to the boundary. That makes the FX predictable for compliance, but it also means colour differences beyond the boundary can be destroyed. It should therefore be treated as a late technical guard, not as the first tool for taming difficult saturation.
Current Gamut + Current Gamma tell Resolve how to interpret the RGB values entering the FX.
Limit Gamut to is the smaller target gamut demanded by the mastering or delivery specification.
Colours outside that target are hard-clipped, so the result cannot exceed the selected gamut boundary.
If a real mastering or delivery specification uses a Rec.2020 signal/container but restricts mastered chromaticities to a particular P3 boundary, Gamut Limiter can enforce that boundary at the appropriate output stage. This is an example of how the FX is used, not a replacement for the Rec.2020 or P3 theory: the exact P3 variant, white point, transfer function and measurement method still come from the specification.
The standards themselves are already covered in the Color Science section. Follow the chapters below when you need the underlying colourimetry rather than the operation of this Resolve FX.
Inspector controls
The tool is simple only when the signal state is known. Current Gamut and Current Gamma describe the input; Limit Gamut to defines the legal output boundary. A mistake in either current-state field changes what the limiter thinks is out of gamut.
Current Gamut describes the colour gamut of the signal at the exact point where Gamut Limiter is placed. Use timeline is convenient when the image really is in the Timeline Colour Space. If a CST, DCTL, LUT or another transform before the limiter has moved the signal into a different gamut, Use timeline is no longer automatically correct — Current Gamut must describe the actual node input.
Current Gamma specifies the current signal transfer function: ACEScc/ACEScct, Apple Log, ARRI LogC, HLG, Blackmagic Design Film and other options. The limiter needs the encoding as well as the primaries/gamut so it can interpret RGB correctly before testing the boundary. Use timeline is valid only when the gamma at this point in the node tree genuinely matches Timeline Gamma.
Limit Gamut to chooses the gamut within which the final colours must remain. This is not a soft compression model: Resolve FX Gamut Limiter is a limiting operation and hard-clips values that fall outside the selected boundary. The key point here is the limiter behaviour and the correct target from the delivery/QC specification; Rec.2020, P3 variants and gamut mapping are covered separately in the Color Science chapters rather than duplicated here.
Limiter vs neighbouring tools
Hard-clips values outside a specified gamut. Predictable boundary, but it can destroy separation beyond that boundary.
Remaps/compresses problematic colours into a target gamut to preserve more hue and saturation relationships.
Targeted creative/technical compression around a selected colour; useful upstream when only a local hue region is causing trouble.
Transforms between colour-space descriptions. A transform may also contain gamut mapping, but it is not automatically the same as a final compliance limiter.
Compliance workflow
Do not start by choosing a smaller gamut from the dropdown. Start by documenting the required output, then prove the signal state entering the limiter and verify the result on appropriate scopes.
Use Gamut Limiter because a specification requires a hard gamut boundary — not because saturated colours simply look uncomfortable. Write down the container/output gamut and the smaller allowed content gamut before touching the FX.
Ask what gamut and gamma the pixels have here, after every upstream CST, LUT, DCTL and colour-management stage. The limiter does not infer a custom manual transform chain for you.
Use timeline only when the current signal really matches timeline state. Otherwise choose the explicit current gamut/gamma pair that describes the node input.
Set Limit Gamut to the actual QC boundary: for example P3-D65 inside a Rec.2020 deliverable when the specification says so. Do not substitute Rec.709, P3 or another standard just because it is familiar.
Use CIE Chromaticity when available to see gamut excursions directly, then check RGB Parade/Viewer for hard-channel behaviour, hue discontinuities and gradients in LEDs, neon, graphics and synthetic colours.
Because out-of-bounds colours are hard-clipped, do creative saturation, hue shaping and smooth gamut mapping before the limiter. Use the limiter as a final compliance guard rather than an early grading tool.
Common failures
Cause: Current Gamut or Current Gamma does not describe the actual signal at the limiter input.
Fix: Audit the node tree from the previous technical transform forward. Replace Use timeline with an explicit pair when the signal has already left timeline space.
Cause: The target gamut is much smaller and the limiter is hard-clipping a large cloud of colours onto the boundary.
Fix: Use gamut compression/mapping upstream to preserve separation, then keep Gamut Limiter only as the final guard if QC still requires a strict boundary.
Cause: The limiter is not the last colour-changing operation, or the scope is viewing a different processing stage/output than the limiter target.
Fix: Check timeline/clip node order, group/timeline nodes and output transforms. Confirm what stage the scope is actually monitoring.
Cause: Compliance was achieved by hard clipping rather than by preserving colour relationships through mapping.
Fix: Treat the limiter as a compliance test/guard. Shape problematic colours upstream with Gamut Mapping, Color Compressor, curves or targeted grading before the final limit.
Think of Gamut Limiter as a late technical barrier: it receives RGB described by a known Current Gamut + Current Gamma pair, tests those values against the selected Limit Gamut to boundary and hard-clips values outside the target. That makes compliance predictable, but clipping is irreversible — colour differences beyond the boundary can disappear.
| Layer | What it means | How to verify |
|---|---|---|
| Current Gamut | Describes the primaries/gamut of RGB entering the effect. Use timeline inherits the timeline gamut; explicit options are needed when an upstream transform has already changed the state. | Audit upstream CST/DCTL/LUT, Group/Timeline nodes and project colour management. Do not choose a camera gamut by name if the signal has already been normalised. |
| Current Gamma | Describes the transfer function of the current RGB values. A gamut boundary cannot be applied correctly if the numeric encoding is interpreted incorrectly. | Check whether Log has already been converted to PQ/HLG/display gamma or another working gamma before this node. |
| Limit Gamut to | Chooses the smaller gamut that chromaticities must not exceed. Out-of-bound values are hard-clipped to the boundary. | The target must come from the mastering/QC specification: Rec.709, P3-D65, P3-DCI or another exact standard are not interchangeable. |
| Hard clipping | Several different out-of-gamut colours can collapse onto the same boundary, so local colour separation can disappear after the limiter. | Test neon, saturated LEDs, synthetic gradients, graphics and skin near saturated sources in the Viewer + CIE scope. |
| Placement | Because clipping is irreversible, creative hue/sat work, gamut compression and most look operations should happen earlier. | There should be no unexpected saturation/colour transform after the limiter that pushes chromaticities outside the required boundary again. |
Likely cause: Current Gamut/Gamma do not match the signal, so Resolve is evaluating the boundary in the wrong system.
Fix: Audit the previous technical transform and explicitly set the current pair instead of Use timeline if the signal state has changed.
Likely cause: A large cloud of colours is being hard-clipped onto the same target boundary.
Fix: Compress the gamut smoothly upstream and use the limiter only for remaining excursions.
Likely cause: A saturation/transform stage exists after the limiter, or the scope is monitoring a downstream stage with another colour-space conversion.
Fix: Check Group Post-Clip, Timeline nodes, output CST/DRT and the scope monitoring point; move the limiter later if necessary.
Likely cause: The wrong P3 variant/white point is selected, Current Gamma is wrong, or the delivery spec is checking a different signal-stage/metadata combination.
Fix: Verify the exact target standard, white point, transfer function, output metadata and QC measurement method.
Gamut Limiter belongs among the final colour-changing operations. In a manual YRGB pipeline it often sits after an output transform, or at the stage where the signal is already in the delivery container gamut and must be restricted to a smaller content gamut. In managed RCM/ACES, first check whether the Output Transform/Limit Output Gamut To function already handles the requirement at project level. Do not duplicate hard limiting without a reason.
CIE Chromaticity is the primary diagnostic scope for the gamut boundary itself because it shows chromaticity positions relative to primaries/standards. RGB Parade helps reveal channel clipping/flattening and Vectorscope shows general saturation/hue structure, but a normal Vectorscope does not replace exact target-gamut verification. Use the Viewer to find posterisation and lost colour separation.
Resolve FX Gamut Limiter can be used whether RCM is enabled or not. However, RCM also offers project-level Limit Output Gamut To and CST can perform gamut mapping. Assign one stage responsibility for appearance-preserving mapping, then one final stage for strict limiting if the specification actually requires it. Avoid stacking multiple unknown compressors/limiters.
explicit conversion between colour-space/gamma descriptions, including tone/gamut mapping
node-level input/output through the standardised ACES transform set
conversion between white points / illuminants through a CAT model
compressing hue/saturation/luminance variation around a selected Target Color
temporal matching of unwanted brightness/white-balance drift around a chosen reference and analysis region
selective increase or reduction of local contrast at a chosen structure scale and within a controlled tonal range
programmable host for custom transform code whose maths, UI and signal contract are defined by the selected DCTL/DCTLE
depth-weighted reduction of smog/airlight/haze through a simulated depth matte and coupled colour/contrast correction
suppression of reflected red/green/blue screen spill after the subject has already been isolated by key/matte/roto
spatial display of exposure zones through camera-matched or creative false-colour mapping and a legend
tone/gamut remapping through luminance roll-off, saturation compression/clip and OOTF without a separate input/output colour-space conversion
simple independent inversion of Red/Green/Blue/Alpha channels for creative and technical channel/key operations
AI-assisted SDR→HDR mapping with an explicit input/output signal contract, Middle Gray, target peak luminance and creative shaping
procedural Pan/Tilt/Rotation/Zoom motion with waveform, randomness, pauses and blanking handling
creative optical-look effect combining spatial diffusion, coloured Tone Lights, tonal protection, a falloff mask and a LUT-compatible subset
procedural texture/look effect combining blur/colour drift, vignette, changing dirt and up to five scratches with motion/flicker
procedural film-style texture with gauge presets, grain geometry, composite modes, tonal/RGB weighting and final mix
integrated scene-referred film-emulation environment combining a baked-in Blackmagic film response, colour shaping, halation/bloom/grain/flicker/gate weave and a LUT-compatible subset
dedicated temporal exposure modulation with tonal flicker modes, RGB selection, smoothness, randomness, pauses and a deterministic seed
film-style highlight scatter using an isolation matte, chromatic dye-layer reflections, secondary glow and optional grain
creative shadow/highlight colour separation through Natural/Strong/Custom modes, Pivot, Hue Angle, neutral protection and colour-space overrides
edge framing and visual-attention control through Basic/Advanced geometry, position, colour and compositing
solid-colour generation for Layer Mixer, masks, fills and simple colour washes
Full BT.2020 theory: primaries, D65, the UHD framework, container gamut and its distinction from BT.2100.
DCI-P3, P3-D65 and Display P3: the word P3 does not imply the same signal contract.
Why smooth compression/remapping and hard clipping solve different problems.
Timeline/output gamut, RCM and where project-level gamut limiting occurs.
CIE Chromaticity, RGB Parade and Vectorscope for checking boundaries and clipping artefacts.
How the upstream transform defines Current Gamut/Gamma and where smooth gamut mapping is better performed.
Why a final compliance limiter belongs in a clearly defined technical part of the node tree.
Panel names are cross-checked against the Resolve 21 screenshots already shown on each page. Where Blackmagic does not publish proprietary implementation math, the article describes documented signal semantics and observable behaviour rather than inventing an algorithm.
FAQ
No. Gamut Limiter enforces a hard boundary by clipping out-of-gamut values. Gamut Mapping/compression attempts to remap colours into the target gamut while preserving more relationships and gradation. They can be used together, with mapping first and a limiter last when a strict QC boundary is required.
It tells the FX to use the project/timeline gamut or gamma as its description of the current signal. That is correct only if the signal at this node still matches timeline state. A manual CST or other transform before the limiter can make an explicit setting necessary.
Because RGB values must be interpreted in their actual encoding before a colour-space boundary operation can be applied correctly. Primaries without the transfer function are an incomplete description of the signal state.
Not always. A Timeline node is useful when one output compliance rule applies to the whole program, but the correct position depends on your output transform and node architecture. The key rule is that the limiter should see the signal state you describe in Current Gamut/Gamma and should be after most creative colour operations.
The panel shown in Resolve 21 exposes Current Gamut, Current Gamma and Limit Gamut to. There is no Global Blend control in this UI; the effect is intended as a deterministic technical limiting stage rather than a creative mix.
Yes. Blackmagic documents the Resolve FX Gamut Limiter as usable whether Resolve Color Management is enabled or not. In a manual DaVinci YRGB pipeline, however, you are responsible for describing the current gamut/gamma correctly.
Next steps
Previous FX
Camera-specific and creative exposure analysis before output compliance work.
Use CIE Chromaticity plus RGB scopes to verify where colour excursions and hard boundaries occur.
Revisit the technical transform that defines the gamut/gamma state entering the limiter.
Next FX
Next in the Color FX sequence: tone and saturation remapping rather than a hard compliance clip.