Vapoursynth KillerSpots

From wiki.selur.net
Jump to navigation Jump to search

KillerSpots removes small spots and dirt specks, as found on old film transfers. It compares each frame with motion-compensated versions of its neighbors and cleans out defects that exist in one frame only.

Filtering → Vapoursynth → Artifacts

KillerSpots controls in Hybrid
KillerSpots controls in Hybrid

What it does

Motion vectors are searched forward and backward, and the previous and the next frame are compensated onto the current one. The three frames are cleaned together: by default with a plain temporal Clense (fastest), with Advanced by a RemoveDirt-based routine whose motion detection decides which blocks are cleaned. Detail that stays over time is kept; only the middle frame of each triple is returned.

Settings

Control Parameter Range / values Hybrid default Meaning
Advanced advanced on/off off Off: plain temporal Clense, as in the original KillerSpots. On: RemoveDirt-based cleaning whose strength is set by Limit.
Limit limit 1 – 100 10 Spot removal threshold (noise level of the motion detection); only with Advanced.
Tools: MV – mvgpu, mvutensils, mv mvgpu with a discrete GPU, else mvutensils Motion vector implementation; mvgpu ignores the search settings.
Tools: RG – zsmooth, neo_smo zsmooth Clense/RemoveGrain implementation.
Tools: RemoveDirt – removedirt removedirt RemoveDirt plugin (used only with Advanced).

Example

Default settings on a 10-bit YUV 4:2:0 source (machine with a discrete GPU):

# spot/dirt removal using KillerSpots
clip = killerspots.KillerSpots(clip, tools={'mv': 'mvgpu', 'rg': 'zsmooth', 'removedirt': 'removedirt'})

How Hybrid calls it

  • KillerSpots works on 8-, 10-, 12- and 16-bit integer YUV; other formats are converted first.
  • advanced=True is only written when Advanced is on; Limit only with Advanced and when it is not 10. The Tools choice is always written.
  • Limit is not scaled: RemoveDirt treats its noise value on the 8-bit scale at every bit depth.
  • KillerSpots also offers the common options (Masked, ApplyOnlyTo, Merge, OnRegion, Gimmick).

Background

The script

The idea comes from Didée (2010, "SpotRemover"); GMJCZP turned it into the AviSynth function KillerSpots 2.0, which the VapourSynth version follows. The motion search uses fixed values (block size 8, overlap 4, pel 2). Advanced is off by default for compatibility with the original behavior. The AviSynth function also has a side-by-side comparison option, which the port does not have.

Sources