Click Repair

Parameters

Sensitivity — Detection sensitivity, 0–10 (default 3). Higher = more clicks detected; lower = only the most obvious ones. Maps non-linearly onto the LPC residual threshold so the useful range (2–8) fills most of the knob travel:

• 3 (default) — conservative; catches obvious vinyl clicks / digital glitches without false positives.
• 5–6 — moderate; picks up softer clicks on noisier material.
• 8–10 — aggressive; will start flagging legitimate transients (kick attacks, plosives) as clicks. Combine with peak_preserve to protect them.
• 0 — detector effectively off (threshold pushed beyond reachable values).

Detection results are cached and shared with the scope’s CLICKS color mode — when sensitivity changes, the scope’s overlay updates to match.

Peak Preserve — Transient-protection strength, 0–1 (default 0.5). Routes events that look more like real transients than clicks through a parabolic (gentler) repair branch instead of full LPC erasure — protects drum hits, plosives, and other percussive content from being mistakenly smoothed away.

• 0 — gate disabled; every detected event gets full LPC repair (most aggressive cleanup, highest risk of damaging transients).
• 0.5 — default; balanced. Events with strong transient evidence are passed through gently; clear clicks get full repair.
• 1.0 — most protective; only events with very weak transient evidence get full repair. Use on percussive material (drums, transient-heavy recordings) where preservation matters more than total cleanup.

The label was deliberately chosen as “Peak Preserve” rather than “Transient Awareness” — describes what the user sees (peaks survive), not the algorithmic mechanism.

Additional controls

Event Markers — Interactive timeline of detected clicks below the knobs. Each marker = one detected event; height/color encodes detector confidence (taller / brighter = more confident click). Click a marker to toggle its accept/reject state — rejected events are skipped in the repair pass, so you can keep the detector aggressive but veto false positives one by one. The status line above shows “Clicks: N detected, M accepted”. Toggling re-runs only the repair pass, not detection — fast feedback. Per-event accept flags reset whenever sensitivity or peak_preserve changes (since the underlying event set may be different).

About Click Repair

Click Repair is K2K’s surviving spectral-repair node — the only one to come through the late April / early May phase-category retraction (PhasePlayground was the other survivor; everything else was deleted). Time-domain LPC residual detection finds clicks; LPC forward+backward interpolation rebuilds the damaged samples; an optional STFT-based gate (driven by peak_preserve) routes likely-transient events through a gentler parabolic branch to keep drum hits intact. Use for: vinyl rip cleanup, fixing digital glitches in recordings, removing pops from speech / vocals. The per-event marker UI is the killer feature — set sensitivity high enough to catch everything, then audition and reject false positives interactively rather than tweaking thresholds blindly. The detection cache is shared with the spectral scope’s CLICKS color mode (open the scope and pick CLICKS to visualize what the detector found in the spectral domain). Compare with the (now-deleted) phase-coherence repair nodes — those addressed a problem that turned out not to need addressing on real material; ClickRepair addresses an actual common problem with audible failure mode and audible success.

Generated 2026-05-05 from K2K_Dev@96730bdc by scripts/gen_lexique.py. Edit _intros/ or _overrides/, not this file.