RESOLVE FX · EXPOSURE MAPPING · STUDIO
False Color.
Map the signal.
Do not confuse the map with the grade.
False Color is both a camera-matched diagnostic and a programmable creative band map. The robust workflow starts by deciding which job you need, validating the signal contract, reading the map together with scopes, and explicitly removing the diagnostic node before delivery.
Camera ↔ Creative
Camera · Mode · ISO · Node
Legend can burn in
In the lab, break the camera contract on purpose: switch the signal to Normalized / CST or untick ISO match. Then move to Creative and change band count, Black/White/Gamma, and Blend. The two branches solve different problems.
Teaching model only. Camera mode checks contract ownership and uses symbolic bands; it does not reproduce Blackmagic camera thresholds or Resolve pixel output. Creative mode demonstrates band-count/range shaping conceptually. Verify exact installed behavior in Resolve and on scopes.
Actual Resolve captures + independent contract/band teaching model
21 DOCUMENTED CONTROLS · 9 CAPTURES · STUDIO01MAPPING × CONTRACT × DELIVERY
False Color becomes reliable when mapping, signal ownership, and render safety stay separate.
The effect can imitate supported Blackmagic camera false color or build custom creative bands. Neither branch corrects exposure by itself.
False Color is mapping, not correction
The FX remaps current-image brightness into diagnostic colors. It helps locate tonal/exposure regions spatially, but it does not fix exposure, white balance, or dynamic range. Corrections belong to Primaries, HDR, Curves, and other grading tools.
Camera-specific mode lives by a signal contract
Specific Camera Model is meaningful only when Camera, Camera Mode, and ISO match the real configuration and the signal at that node is still in the expected camera state. A CST, LUT, or output transform placed before the FX can break that match even when the camera model is selected correctly.
The legend is image content, not a viewer-only overlay
Scale / Legend explains the map directly in-frame, but the manual states that the legend is burned into the image. That is useful for teaching and technical reference renders, but dangerous for a final master: bypass or remove the diagnostic node before delivery.
Resolve 21.1 manual boundary: Specific Camera Model selects a Blackmagic camera sensor, Camera Mode, and ISO; Creative exposes editable Color Bands. Preprocessing can reshape the analyzed map, while Scale/Legend is explicitly burned into the image.
02REAL RESOLVE 21 CONTROLS
Twelve controls are visible in the captured camera state; the manual documents the conditional Creative and preprocessing controls as well.
Nine screenshots below are actual Resolve captures. Creative Color Bands and the missing Black/White/Gamma state are explained from the current manual and are not fabricated as Inspector UI.
AGENERAL + CAMERA MODEL
First decide which logic should own the mapping.
- Plugin Mode
Switches between two conditional branches: Specific Camera Model for matching Blackmagic camera false-color readout and Creative for preset/custom color bands.
VERIFYDo not carry exposure conclusions from a camera-specific scale into a Creative palette or vice versa.
- Camera
Selects the exact Blackmagic Design camera/sensor used for camera-specific mapping. The available list can vary by Resolve version.
VERIFYUse the actual source camera; a similar name does not guarantee the same false-color response.
- Camera Mode
Sets the camera dynamic-range/image mode — the capture shows Film, Video, and Extended Video. This describes the input camera state, not a look preset.
VERIFYAfter a CST/LUT/RCM transform, the signal may no longer match the selected mode.
- ISO Level
Sets the ISO/light-sensitivity setting used by camera-specific false-color mapping. The current URSA Mini Pro 4.6K capture shows 200, 400, 800, 1600, and 3200.
VERIFYRead ISO from metadata/production notes. A wrong ISO makes camera-accurate interpretation unreliable.
BCREATIVE BANDS + PREPROCESSING
Creative builds custom bands; Preprocessing changes the tonal signal being analyzed.
- Creative Style
In Creative mode, selects a built-in style preset as a starting color map.
VERIFYA preset is a creative/diagnostic convention, not a universal camera exposure standard.
- Number of Bands
Sets how many distinct colors participate in the creative scale. More bands create a finer posterized map; fewer bands create broader zones.
VERIFYDo not confuse band count with measurement precision: a waveform remains the more exact continuous readout.
- Show Sliders
Exposes Top and Bottom so the tonal range of a specific band can be defined explicitly.
VERIFYCheck overlaps and gaps between ranges when building a teaching or technical palette.
- Top
The upper brightness boundary of the selected creative band, expressed in percentage values.
VERIFYTop describes this band boundary, not a target exposure correction for the image.
- Bottom
The lower brightness boundary of the selected creative band. Together with Top it defines which pixels are painted with the chosen Color.
VERIFYWith narrow ranges, check noisy/fine detail in motion: the map can visually chatter.
- Color
Color swatch/picker for a specific creative band. It is a visualization code for a brightness range, not a source-hue correction.
VERIFYChoose a palette where adjacent important ranges remain visually distinct.
- Blur
Applies blur to the image before analysis, reducing fine-detail and noise-driven zone chatter.
VERIFYBlur improves readability but does not fix underexposure or replace noise reduction.
- Black Level
Raises or lowers the shadow range assigned to colors at the low end of the false-color legend.
VERIFYThis remaps the analysis; it does not actually lift or lower the source black level.
- White Level
Raises or lowers the highlight range assigned to colors at the high end of the false-color legend.
VERIFYDo not use it to “save” clipped highlights — source pixels are not recovered.
- Gamma
Shifts the mid-tone range toward lower or higher color regions of the legend.
VERIFYChanging Gamma changes the interpretation map, not the source grade.
CSCALE / LEGEND + FINAL MIX
The legend explains the mapping, but it also becomes part of the processed image.
- Show Scale
Shows/hides the color legend at the left of frame. The manual explicitly states that the legend is burned into the image.
VERIFYBefore final render, hide the Scale or, more safely, bypass/remove the diagnostic node entirely.
- Show Values
Adds numeric values to the legend in the format selected by Value Style.
VERIFYThe numbers label the scale; they are not a separate measurement engine.
- Show Labels
Adds labels for important data points including black clipping, white clipping, and middle gray.
VERIFYLabels help interpretation, but use Waveform for precise continuous verification.
- Contrast
Changes the transparency/readability of the legend background underlay, not image contrast.
VERIFYIf the image seems changed only around the legend, that is UI burn-in behavior, not tonal correction.
- Value Detail
Increases or decreases the number of axis value labels shown on the legend.
VERIFYOn a small viewer, fewer labels can read better; this does not change band thresholds.
- Value Style
Percentage shows 0–100%, Hundredths shows 0–100 without the % sign, and Normalized shows 0.0–1.0. The notation changes; the color mapping does not.
VERIFYCheck Value Style before interpreting numbers — Hundredths should not automatically be called IRE.
- Blend
Global Blend mixes the complete False Color result with the node input. For technical mapping, partial Blend usually weakens color certainty; for a creative effect, it can be an intentional mix.
VERIFYFor camera/technical diagnosis, keep Blend=1.000 and compare via bypass; remove/bypass the diagnostic node before delivery.
03TWO DIFFERENT OWNERSHIP MODELS
Specific Camera validates a real capture contract. Creative defines a convention you must document.
Treating the two modes as interchangeable is the fastest way to produce confident but wrong exposure conclusions.
Match Camera · Mode · ISO
Specific Camera Model is only as trustworthy as these selections and the signal state feeding it. Read metadata or production notes instead of guessing.
The graph is decision order, not a required node count. The durable split is: camera mode validates a real signal contract; Creative mode defines and documents a custom band convention. Both require an explicit delivery decision because the processed image and legend can be rendered.
04BUILD IT IN RESOLVE
Four exercises cover camera matching, a custom palette, noisy footage, and safe reference delivery.
These are teaching workflows, not universal thresholds. Exact camera behavior belongs to the selected Blackmagic configuration and the installed Resolve build.
Camera-matched exposure reference
Reproduce the false-color readout of a supported Blackmagic camera inside Resolve.
PrepareYou need the exact Camera, Camera Mode, ISO, and a known signal state at the node.
- 01
Place False Color in a diagnostic node before transforms that change the expected camera signal.
- 02
Choose Specific Camera Model and match Camera, Camera Mode, and ISO to metadata/production notes.
- 03
Enable Show Scale + Values/Labels, inspect regions, and keep Waveform open at the same time.
- 04
To change exposure, bypass the diagnostic node, correct with a separate grading tool, then return to False Color for verification.
False Color and camera monitoring agree spatially, while Waveform verifies the levels.
Custom teaching palette
Build a clear teaching palette without pretending it is camera-specific.
PrepareUse Creative; the current archive has no exact Creative-UI captures, so verify against the installed Resolve/manual.
- 01
Choose a Creative Style as a starting point.
- 02
Set Number of Bands, enable Show Sliders, and define Bottom/Top for key ranges.
- 03
Assign Color so adjacent ranges are easy to distinguish.
- 04
Enable the legend and label the lesson/reference render so viewers understand the scale convention.
You get a reproducible custom palette with explicitly documented ranges.
Noisy low-light shot
Make the false-color map readable without hiding the real underexposure problem.
PrepareThe source is noisy and tiny pixels chatter between colors.
- 01
First inspect the source Waveform and make sure noise is not mistaken for useful detail.
- 02
Add only enough Pre-Processing Blur to calm micro-chatter.
- 03
Do not change camera/creative thresholds just to make poor exposure look calmer.
- 04
Fix exposure/noise with separate tools, then check False Color again.
The map reads more steadily without disguising the source diagnosis.
Safe technical reference render
Create a reference clip with the legend without leaving False Color in the final master.
PrepareYou need a separate diagnostic export and a clean delivery master.
- 01
Keep False Color on a separately named diagnostic node.
- 02
For the reference export, enable Scale/Values/Labels and confirm that a burned-in legend is intentional.
- 03
After the reference export, bypass/remove the diagnostic node and inspect both the viewer and a rendered test frame.
- 04
Verify that the final master contains no false-color palette, legend, or partial Global Blend.
The reference render is self-explanatory while the delivery master remains clean.
05CHOOSE BY RESPONSIBILITY
False Color locates. Waveform measures. Grading tools correct.
A trustworthy exposure workflow usually uses more than one visualization because spatial location and continuous signal level are different questions.
| Tool | What it owns | Use it when |
|---|---|---|
| False Color | Spatial color-band map painted directly over the image. | When you need to see exactly where exposure/brightness zones sit in the frame. |
| Waveform | Continuous signal-level measurement across image width. | For exact levels, clipping, matching, and verifying that false-color interpretation is not misleading. |
| Zebras | One or more selected thresholds rather than a full multi-band map. | For quick threshold warnings during acquisition/monitoring when a full palette is unnecessary. |
| HDR / Primaries | Actual grading controls that modify the signal. | After diagnosis, when exposure/tonal balance actually needs to change. |
06SYMPTOM → CAUSE → FIX
Most False Color failures are contract mistakes, convention mistakes, or delivery mistakes.
01The map does not match camera false color+
Check Camera, Camera Mode, ISO, and especially the signal state before the node. A LUT/CST/RCM transform before the FX can make a camera-specific setup logically wrong.
02A Creative palette is treated as an exact camera meter+
Creative is custom mapping. Document style/bands/ranges and do not import camera-specific thresholds without an explicit basis.
03The legend appeared in the final render+
That is expected: the manual says the legend is burned into the image. Keep the effect on a separate diagnostic node and bypass/remove it before delivery.
04At Blend=0.5 the colors no longer match the scale cleanly+
Partial Global Blend mixes false-color output with the source. For technical diagnosis use 1.000 plus bypass comparison.
05Noise turns into a flickering mosaic of zones+
Add modest Pre-Processing Blur for readability only, and address the noise/exposure cause separately.
06Hundredths is assumed to mean IRE+
Value Style sets notation: Percentage, Hundredths, or Normalized. Use Waveform and color-management context for exact signal-level semantics.
07Changing Black/White/Gamma makes the shot seem “fixed”+
Those Preprocessing controls change false-color analysis mapping. They are not a substitute for an actual grade. Return the diagnostic mapping to a documented state and correct the source separately.
False Color + Waveform
False Color gives the spatial answer — where the region is. Waveform gives the continuous answer — what the level is and how close it is to clipping. Use them together rather than as competing tools.
A diagnostic node should be temporary
Node naming, bypass state, and render checks matter more than a “pretty” tree. False Color changes the image and can burn in the legend; it should not accidentally become part of the final look.
Creative workflows need their own documentation
If custom bands become a team technical convention, document the preset, Number of Bands, Bottom/Top ranges, colors, and Value Style. Otherwise the same colors stop meaning the same levels across projects.
07BEFORE YOU DELIVER
Approve the interpretation, then prove the diagnostic layer is gone from the master.
The checklist is a workflow guardrail. It does not replace the installed Resolve build, real footage, scopes, calibrated monitoring, or delivery QC.
08FAQ
The distinctions that keep a diagnostic map from turning into a false sense of measurement.
Does False Color correct exposure?
No. It remaps current brightness/exposure regions into diagnostic colors. Make corrections with Primaries/HDR/Curves, then return to False Color for verification.
Can Specific Camera Model be used for another camera brand?
As a creative visualization, an image will still be processed, but the camera-accurate meaning is lost. The mode is intended to match specific Blackmagic Design camera configurations.
Why do Camera Mode and ISO matter so much?
Because camera-specific mapping reproduces the readout of the selected configuration. A wrong mode/ISO changes the relationship between source brightness and color zones.
Does Value Style change thresholds?
No. Percentage, Hundredths, and Normalized only change legend-number notation. The false-color mapping itself is not redefined by that choice.
Will the legend appear in the render?
Yes, if the effect and Show Scale remain active: the manual explicitly states that the legend is burned into the image. Bypass/remove the diagnostic node for final delivery.
What do Black Level, White Level, and Gamma do in Preprocessing?
They change how shadow/highlight/midtone ranges are assigned to false-color zones before display. That is analysis mapping, not an actual tonal grade of the source.
Do I still need Waveform if I use False Color?
Yes when exact levels matter. False Color excels at spatial localization; Waveform excels at continuous signal relationships and clipping. They are stronger together.
Should I use partial Global Blend for technical checking?
Usually not: the source mixes with diagnostic colors and makes the mapping less unambiguous. For technical checking, use Blend=1.000 and bypass comparison. Partial mix makes more sense as a creative effect.
Sources and verification boundaries
Visible names and defaults were checked against the nine actual Resolve captures in the project archive. Conditional Creative controls, Preprocessing behavior, Studio status, and the burned-in legend warning were cross-checked against the current Resolve 21.1 manual and Blackmagic documentation. The interactive map is deliberately an independent teaching model and does not reproduce proprietary camera thresholds or Resolve pixel output.
This web pass does not claim live Resolve-render certification. Final production acceptance belongs to the installed Resolve build, the actual camera pipeline, scopes, and the rendered delivery file.