Back to Blog
    slingshot
    reverse delay
    production technique
    ableton live
    bass production

    Slingshot's TARGET Now Knows the Difference Between Your Kick and Snare

    October 25, 20266 min read

    Reverse delay only earns its place in a mix when the echoes are building toward something specific. Point Slingshot at a full drum loop with no filtering and the reversed echoes pile up in front of the kick, the snare, and the hat at the same time, and all three smear into one rising wash with no single moment to land on. Low End Candy's October 2026 updates to Slingshot went straight at that problem: TARGET now knows which drum it's listening to, and it remembers.

    What Changed in the Last Two Updates

    Two Slingshot releases landed ten days apart this month. The October 11 update (v2.0.0) dropped the plugin's demo mode and license key entirely. Slingshot is now sold as a complete one-time purchase, backed by a 14-day money-back guarantee, with nothing to activate. That same release introduced the first version of TARGET: pick KICK, SNARE, or HAT, or click a transient by hand, and only that drum feeds the reverse echoes. A new MATCH control sets how strict the detection runs, and the preset count grew from 33 to 73, including a Loop Target group that switches TARGET on automatically.

    The October 21 update (v2.1.0) sharpened all of it. TARGET now locks onto the loop's bar grid at 1, 2, 4, or 8 bars and holds that lock across every pass, instead of recalculating each time. Clicking a transient sticks, and clicking it again removes it cleanly. KICK, SNARE, and HAT detection got measurably better at telling the three apart on busier loops. The TARGET view itself picked up a bar.beat ruler and a waveform colored by what it's reading, and picks plus loop length now save with the project rather than resetting every time you reopen the session.

    None of this touches Slingshot's six delay characters (Clean, Tape, Analog, Diffuse, Ping-Pong, Filtered) or the core swell engine behind them. Those are unchanged. What changed is which part of a loop gets the reverse treatment in the first place, and that turns out to matter more than any new character would.

    Why Targeting One Drum Beats Processing the Whole Loop

    The reason reverse delay across a full loop tends to sound messy is straightforward: every transient gets its own buildup, and on a busy pattern those buildups overlap constantly. A kick on every beat plus a closed hat on every eighth note means eight to sixteen small reverse swells per bar, stacking into a blur that never resolves to a clear moment.

    TARGET fixes this by letting the reverse echoes care about exactly one source. Set it to KICK and Slingshot ignores the snare and hat completely, on every pass, not just the one transient you happened to click first. A loop-wide blur becomes a single, repeatable buildup pattern that lines up with the one part of the beat you actually want the listener anticipating.

    Before TARGET existed, getting this result meant manually printing a reverse swell off an isolated kick stem on its own track, which worked but cost a routing step every time the pattern changed. TARGET collapses that into a setting inside the plugin itself, which is also why the project-save behavior added in 2.1.0 matters: the setup now survives a session reopen instead of needing to be rebuilt.

    Why This Matters More on Bass-Heavy Tracks

    A kick and a sub bass line usually share the same frequency range, and a reverse swell layered under both at once muddies exactly the register a bass-focused track depends on staying clean. Targeting the kick alone keeps the buildup confined to the low end on a predictable schedule, then gets out of the way before the bass note underneath has to carry the groove on its own.

    This also means the reverse swell can sit lower in level than it would need to on a full mix, since it's no longer fighting the snare and hat for the same two or three seconds of attention. A kick-only TARGET build can run louder in isolation and still sit under a bass line without clouding it, because nothing else in the loop is competing for the same transient window.

    Setting Up a Kick-Only Build in Ableton Live

    1. Drop Slingshot on the drum bus, or on a dedicated kick channel if the kick is already split out from the rest of the kit.
    2. Open the TARGET view and select KICK. On a loop with a clear low-end transient, detection should catch every kick without any manual clicking.
    3. If TARGET is grabbing ghost notes or missing softer kicks, adjust MATCH. Tightening it toward strict cuts false positives from bleed or layered percussion. Loosening it catches quieter or more varied kicks, at the cost of occasionally grabbing snare bleed too.
    4. Set the bar-grid lock to match the loop length: 1 bar for a steady four-on-the-floor pattern, 2 or 4 bars if the kick pattern changes across a longer phrase. This keeps TARGET's picks stable from pass to pass instead of recalculating.
    5. Dial in Time, Feedback, Shape, and Tone the way you would on any Slingshot swell, then pick a delay character. Filtered or Analog tends to sit better under a kick-focused build, since both keep the top end out of the way of the transient itself.
    6. Arm Capture, play the section once, and drag the printed WAV into the session. Nudge it onto the grid if needed, though the bar lock added in 2.1.0 usually lands it close on the first try.

    MATCH and the ALIGNED Mode Trade-Off

    MATCH is worth sitting with before committing to a full build. It governs how much evidence Slingshot needs before deciding a transient belongs to the drum selected in TARGET. A kick pattern with consistent velocity and no competing low-end percussion can run MATCH tight with nothing missed. A kick pattern that swings between a hard four-on-the-floor strike and a softer ghost note needs MATCH loosened, otherwise TARGET quietly drops the softer ones and the reverse build skips a beat for no obvious reason.

    ALIGNED mode, which keeps Slingshot's output locked precisely to the grid rather than running free, now reports 32 milliseconds more latency than it did before the 2.0.0 update. A DAW's automatic latency compensation handles this during playback, so it's not something to chase manually, but it's worth knowing about if a timing issue shows up elsewhere in a session and other causes need ruling out first.

    A Snare-Led Build Works the Same Way

    The same workflow runs in reverse for arrangement purposes. Set TARGET to SNARE instead of KICK, and the reverse build leads into the snare that opens a chorus or caps a fill, while the kick and hat underneath stay completely dry. Because picks now save with the project, switching between a kick-targeted build before a drop and a snare-targeted build for a chorus doesn't mean re-clicking transients every time the session reopens. Set up each section's TARGET once and it stays put.

    The Takeaway

    The real change across Slingshot's last two updates isn't a new delay character or a longer preset list. It's that TARGET finally treats a drum loop as separate instruments instead of one undifferentiated stream of transients. On a bass-heavy track, that distinction is what keeps a reverse-delay buildup from smearing into the low end the track depends on. Slingshot runs $49 on its own, or $70 paired with Preverb, as a one-time purchase on Mac and Windows (VST3 and AU, macOS 11 or later, Windows 10 or later, 64-bit), with a 14-day money-back guarantee either way. Full details on the current feature set are on the Slingshot page, alongside Preverb if the goal is a matching build-and-release pair across the same transition.