Deflicker

Resolve 21 places Deflicker in Resolve FX Revival and marks it Studio Version Only. Resolve FX are available on the Fusion page inside DaVinci Resolve, while Blackmagic explicitly says Resolve FX are not available in standalone Fusion Studio. The previous Krokodove classification was therefore incorrect.

Blackmagic emphasizes two core behaviors: Deflicker targets rapid, temporally unstable changes in lightness, and it can target only the image regions where flicker appears instead of necessarily altering the whole frame. That is a more precise mental model than calling it a global exposure stabilizer.

Typical targets include frame-to-frame timelapse exposure flicker, fluorescent/LED pulsing, archival-film flicker and, in some subtle cases, rolling bars on displays recorded with mismatched shutter timing. Intentional flashes or slow real lighting changes should not automatically be treated as defects.

Deflicker Settings offers Timelapse and Fluoro Light presets plus Advanced Controls. The first two address common flicker classes quickly; Advanced Controls exposes the underlying Temporal NR / Isolate Flicker controls when a preset is not selective enough.

Frames Either Side defines how many neighboring frames are analyzed for motion. Resolve 21 explicitly warns that a larger value is not automatically better; the best temporal window depends on the scene.

Mo.Est. Type chooses motion estimation. Faster uses less processing and can sometimes behave better on very high-detail footage; Better tries harder to match fine detail and costs more; None disables motion analysis and is only appropriate for genuinely static material. The Resolve 21 text is internally inconsistent about the default, so this article does not invent one.

Motion Range selects Small, Medium or Large expected motion. It is a motion-analysis setting, not a flicker-strength control.

Luma Threshold and Chroma Threshold define the cutoff above which changes are no longer considered flicker. Resolve documents a 0–100 range where 0 deflickers nothing and 100 allows deflickering across the full change range. Luma Chroma Same Threshold gangs the two controls.

Motion Threshold defines the level above which motion should no longer be considered flicker. If moving edges are being repaired as if they were brightness instability, motion estimation and this threshold are the controls to diagnose before reaching for generic smoothing.

Reduced-Detail Motion speeds analysis by reducing the amount of detail used to detect flicker. Blackmagic recommends disabling it when fine detail is being smoothed too aggressively.

Limit Analysis Area reveals a sample box that limits deflickering to a specific image region. It is not a calm reference patch used to estimate the whole frame. Blackmagic gives two reasons to use it: the flicker exists only in one area, or another area is being smoothed too much while the target area is being repaired correctly.

Restore Original Detail After Deflicker protects/restores grain, fine detail and sharp edges that should not be affected by the temporal repair. Detail to Restore controls that preservation, while Show Detail Restored displays the edges selected by this operation for diagnosis.

Output is a diagnostic switch: Deflickered Result is the normal repaired image, Detected Flicker shows the detected flicker mask, and Magnified Flicker exaggerates that diagnostic map when the real signal is too subtle to judge easily. These are image-output views, not a separate blue mask output.

On the Fusion page the node lives in the normal 2D image flow: Image/Input → Deflicker → Output. An optional Effect Mask can spatially gate the node in the graph; that is distinct from the internal Limit Analysis Area control.

Judge Deflicker in playback and within a continuous shot. Temporal analysis across a hard cut compares unrelated frames, while a single still frame cannot prove whether flicker has actually been removed without harming real motion.

Preset modes and Advanced Controls solve the same problem at different levels. Timelapse and Fluoro Light provide tuned detector models while Advanced exposes the variables required to validate and correct behavior on a specific shot.

Frames Either Side defines temporal context rather than effect strength. A wider window can include increasingly different scene states and make motion/flicker separation worse, so it should be chosen per shot rather than maximized.

None in Mo.Est. Type disables motion analysis. It only makes sense for truly static scenes; with motion it increases the risk of classifying object displacement as brightness instability.

Motion Range describes expected inter-frame movement. Small/Medium/Large should match actual subject motion rather than flicker amplitude or frequency.

Luma Threshold and Chroma Threshold define how much corresponding variation can still be classified as flicker. Reading them as simple strength sliders can produce the opposite of the intended result.

Luma Chroma Same Threshold is a useful baseline, but luminance and color flicker are not always identical. Decouple them only after inspecting Detected Flicker.

Motion Threshold is a separate safeguard for motion. If moving edges appear in the flicker map, fix the motion model/window/thresholds before trying to restore detail afterward.

Reduced-Detail Motion is a speed/robustness tradeoff. It can accelerate analysis and even help complex texture, but hair, fabric, foliage or grain should be checked with it disabled when detail is damaged.

Limit Analysis Area changes the internal region Deflicker analyzes/repairs. Effect Mask is an external Fusion mask input that gates node contribution. They can be combined but are not interchangeable.

When flicker only affects a display, light fixture or part of the background, localization is often safer than expanding thresholds aggressively across the entire frame.

Restore Original Detail After Deflicker is a compensation stage after temporal repair. It should not be used to hide a poorly configured detector: first obtain the correct flicker map, then restore detail.

Show Detail Restored diagnoses the detail-restoration contour specifically. It does not prove that flicker detection is correct; Detected/Magnified Flicker serve that purpose.

Detected Flicker and Magnified Flicker must be evaluated in motion. A static mask-like frame cannot show temporal consistency or expose incorrect response to movement.

Magnified Flicker only amplifies a subtle diagnostic map. It does not increase repair strength and is not a separate processing mode for the source image.

Deflicker should operate on a continuous temporal segment. Cuts, clip boundaries, speed changes and frame holds should be treated as potential analysis boundaries rather than ordinary neighboring frames.

Intentional flashes, strobes and rapid creative lighting changes can look like flicker to the detector. Preserve scene intent rather than forcing brightness to be uniformly stable.

Grain and fine texture are strong indicators of excessive temporal smoothing. A stable average exposure is not a successful repair if texture becomes frozen or washed away.

Final Deflicker evaluation has two parts: the diagnostic map must explain where the algorithm intervenes, and Deflickered Result must play naturally without temporal artifacts.

The three preserved Inspector captures show Controls with Timelapse selected, the Deflicker Settings popup and the Output popup. They do not expose the Advanced Controls panel: Frames Either Side, Mo.Est. Type, Motion Range and thresholds follow the manual and still require live confirmation in the installed Resolve 21 build.