Rapid-fire bass transient engine.
9 parameters, generated from the parameter registry and checked against the plugin on every build — so this page and the software cannot describe different instruments. It says what each control does, not what it sounds like.
Version 0.9.1 · Windows x64 · VST3, CLAP and standalone · offline activation, no account, no telemetry.
Cadenced bass bursts with recoil, pause and rumble completion. Bass as an event with a rhythm of its own rather than a sustained tone. One MIDI note fires a burst of up to eight synthesised hits, a rumble tail, then a pause.
How often a held note re-fires the burst, 8 s down to 0.5 s. Also sets each hit's length.
Used for: machine gun, sparse artillery.
How many hits per burst, 1 to 8.
Used for: single kick, roll, flam.
The gap between hits inside a burst, 5 ms to 200 ms.
Used for: fused texture, audible roll.
Refuses retriggers until it expires. Decides how fast the instrument can be played, not how it sounds.
Used for: rhythmic limiting.
The low resonant tail after the last hit, 20 ms to 2 s.
Used for: dry percussion, overlapping density.
Pitch drop, click, saturation drive and level together. The control to reach for first.
Used for: soft thud, hard crack.
How much octave-down sine is mixed in. Always mono.
Used for: club weight, phone speaker survival.
Symmetric detune in the hit; grit correlation in the tail. Never shifts the pitch centre.
Used for: stereo width, mono safe low end.
A hard output clamp applied last. A clamp, not a limiter.
Used for: guard rail, deliberate squaring.
Every parameter above comes from metadata/gatling-bass.yaml, the
single definition of this instrument. The build refuses to publish if the
C++ registrations, that file and this reference describe different
instruments — and it refuses if any declared parameter fails to change the
output, because a control that does nothing is the failure that passes
every other test.