A reactive visual parameter that spends most of its time pinned at its min or max fails the sanity check and needs its base, gain, or scale retuned

A common failure of a reactive patch is a parameter whose transfer function keeps it stuck at an extreme — a permanently black or blown-out white frame, or undifferentiated noise. If a parameter spends most of its time pinned at its minimum or maximum, the coupling is not actually conveying the audio’s dynamics: it reads as broken rather than reactive. The fix is to retune the transfer so the parameter uses its usable range — adjust the base (floor), the gain (sensitivity), or the global a.setScale, so the value moves through the middle of its range as the band varies. Reacting is not the same as reacting legibly.

Examples

blend(() => a.fft[0]*5) may sit at fully white the whole set (pinned max). Lowering the gain and adding a clamp brings it back into a moving mid-range. A rotation gain so small the image looks static is the min-pinned version of the same failure.

Assessment

A brightness parameter is white almost all the time during a loud set. Explain which sanity check it fails and name three tuning controls you could adjust to fix it.