Vapoursynth ReduceFlicker

From wiki.selur.net
Revision as of 08:57, 15 November 2026 by Selur (talk | contribs) (New filter page (via create-page on MediaWiki MCP Server))
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to navigation Jump to search

ReduceFlicker reduces temporal flicker – small frame-to-frame fluctuations of single pixels, such as shimmer in static areas – by limiting each pixel against the values of the neighboring frames.

Filtering → Vapoursynth → Frame → Stabilize

ReduceFlicker controls in Hybrid
ReduceFlicker controls in Hybrid

What it does

Each pixel is compared with the same pixel in a few previous and following frames and limited so it can not jump beyond what its neighbors allow. Unlike Vapoursynth Deflicker it works per pixel, not on the global brightness, and it filters all planes (luma and chroma).

Settings

Control Parameter Range / values Hybrid default Meaning
Strength strength 1 – 3 2 Frame window: 1 = current, 2 previous and 1 next frame; 2 = current, 2 previous and 2 next; 3 = current, 3 previous and 3 next. Higher is stronger.
aggressive aggressive on/off off Use a much more aggressive variant of the algorithm.

Example

Default settings on a 10-bit YUV 4:2:0 source (640x356):

# removing flickering using ReduceFlicker
clip = core.rdfl.ReduceFlicker(clip, aggressive=0)

How Hybrid calls it

  • ReduceFlicker works on gray, YUV and RGB clips, 8–16-bit integer and 32-bit float; no value depends on the bit depth.
  • Interlaced frames are filtered as they are, without separating the fields.
  • Strength is only written when it differs from the default; aggressive is always written.
  • Frame count and frame rate do not change.
  • ReduceFlicker also offers the common options (Masked, ApplyOnlyTo, Merge, OnRegion, Gimmick).

Background

Origin

ReduceFlicker is chikuzen's VapourSynth port of Rainer Wittmann's AviSynth filter of the same name. Only ReduceFlicker itself was ported; ReduceFluctuation and LockClense from the original package were not. The plugin has SSE2, SSE4.1 and AVX2 code paths and runs on the CPU.

Sources