Audialab Interloper [WiN]

• Product: Interloper
• Developer: Audialab
• Version: 1.0.31
• Format: Standalone, VST3, AAX
• Requirements: Windows 10 or later
• Source: audialab.com/products/interloper

Interloper is a MIDI-triggerable sample instrument built around a three-band interpolation engine that splits two loaded audio sources into low, mid, and high frequency regions at user-defined crossover points, then blends each band independently between the two sources via dedicated sliders. It sits in the instrument slot of a drum or sound design session, replacing a multiband split-and-route chain with a single plugin that recalls blend states and automates them over time. The primary differentiator is that blend ratios are MIDI-controllable and DAW-automatable parameters rather than static mix offsets, making the fusion itself a performable, morphable element. The plugin answers the query: how to layer two samples without phase cancellation or EQ rebuild every session.

Key Takeaway

Interloper is at work in sessions where a producer needs to recombine the sub weight of one kick with the transient snap of a second one, or fuse a library synth bass with a synthesized sub without fighting low-end phase cancellation — and needs that result as a playable, recallable instrument that morphs over time rather than a static printed bounce. It complements rather than displaces a full sample library by acting as a combination layer rather than a browser. The three-band architecture covers most sound design needs but does not allow sub-band resolution within the low or high regions; producers after spectral surgery below or above the crossover point will still need conventional EQ alongside it. Engineers who work exclusively in the mix bus domain processing full arrangements, rather than building at the sound or element level, have no use for it.

What the Crossover Points Actually Control

Interloper divides the frequency spectrum into three bands — low, mid, high — using two adjustable crossover points that the user sets before blending. These points determine where the plugin splits each source signal before the interpolation sliders apply. A crossover point placed at 120Hz and another at 3kHz creates three distinct regions; moving the low crossover up to 250Hz expands the mid band downward, giving the mid blend slider more control over the body register of a kick or bass. The crossover placement decision precedes the blend decision and defines what the sliders address.

On drum sounds with complex transient-to-body relationships — kick drums with a long sub bloom, for instance — placing the low crossover just above where the transient energy lives keeps the punch material inside the mid band, where it can be blended independently from the sub. That gives the blend sliders more useful granularity than a fixed low/mid boundary would. The crossover points do not move during playback in normal operation; they set the spectral topology of the split, and the blend sliders then sculpt within it. Automating crossover positions mid-session is not a documented feature of the current architecture — that level of spectral morphing requires external routing or a different tool.

Producers working on bass synthesis layering will find the crossover positioning critical: too broad a low band subsumes body-register harmonics that the mid blend could address, leaving the low slider to handle both sub and bark simultaneously. The approach of starting with the low crossover narrow — defining only the true sub region below 100Hz — and widening upward if more sub-band blend control is needed gives more precision than working from the default position outward.

The Blend Sliders as Automatable Mix Parameters

Each of the three bands carries an independent interpolation slider that continuously blends between Source A and Source B for that region. At one extreme the band outputs Source A exclusively; at the other, Source B only; at center, an equal mix of both. This is not a crossfade applied to the whole signal — it applies per band, so the low region can sit at 100% Source A while the mid sits at 60% Source B and the high at 40% Source A. The three sliders set three independent spectral identities that sum at the output.

All three sliders are exposed as DAW automation parameters, meaning blend states can move across the arrangement without any manual intervention. A kick that starts a build with the sub from Source A can smoothly transition to the sub from Source B over eight bars while its transient material stays fixed. On a snare, automating the high-band slider between two sources across a verse-to-chorus transition shifts the top-end texture — from a cleaner tail to a grittier one — without changing the body. This morphing behavior is the functionally distinct capability relative to any static layering setup; a multiband split with individual send levels could approximate the fixed blend states but cannot produce the smooth, recall-stable, MIDI-controllable morph in one instrument instance.

The sliders respond to MIDI CC messages, which means a controller mapped to the blend values can move them in real time during performance or recording — not just at edit time. That opens Interloper to live performance applications where the hybrid blend is an expressive variable rather than a production decision locked before mixdown. For studio-only use the automation workflow is sufficient; for live performance or live-to-tape production where blends shift in real time, MIDI CC mapping is the more direct path.

Offline AI Drum Generation Inside the Sampler Slots

Either of Interloper’s two sampler slots can generate a new drum sample on demand using a compressed version of Audialab’s generative drum model — the same underlying technology as Emergent Drums 2, running locally without an internet connection or token system. Selecting a drum type (kick, snare, hat, and related categories) and triggering generation produces a new audio file that loads directly into the slot and becomes one of the two sources for the interpolation engine. The generation step adds a randomized source that isn’t in any existing library, which changes the character of the available interpolation range.

The practical consequence of having generation embedded in Interloper’s slot is that the two-source architecture gains a third input mode: library sample paired with a generated sample, rather than two library samples. The generated sample doesn’t need to match any reference; it just needs to contribute a useful spectral region that the blend sliders can extract. A generated kick with an interesting sub character but a mediocre transient becomes the low-band source while a library kick provides the mid and high. Neither sample needs to be usable as a standalone hit for the combination to work.

The in-plugin generation is narrower in scope than the full Emergent Drums 2 experience — there’s no similarity slider, no multi-pad kit view, and no direct drag-to-DAW export from within Interloper’s generation mode. It provides a useful source-expansion function without replacing a dedicated generative drum workflow. Producers who want deep generation control, variation browsing, or full kit management from the same session should treat Emergent Drums 2 as a separate stage that feeds samples into Interloper, not as a function Interloper fully replicates.

Processing Chain Placement and the Convolver’s Ambient Function

Interloper’s processing chain includes ADSR, transient shaping, compression, mid/side processing, filters, a convolver, and a reverb, all available as sculpting tools applied after the interpolation engine produces the fused output. The chain sequence matters: shaping the transient of the blended result rather than shaping each source separately means the transient shaper sees the hybrid signal, not its components. A blend that combines two sources with misaligned attack envelopes will produce a composite attack that the onboard transient shaper can then sharpen or soften as a single element.

The convolver slot accepts impulse responses, which in Interloper’s context extends beyond reverb into body-shaping and tonal character. Loading a short room IR shapes the blended source’s spatial identity; loading an IR captured from a specific cabinet or hardware device imposes that device’s resonance profile on the output. Users on the Drum & Bass community forums noted the convolver as particularly useful for ambient sound design applications — using longer, non-drum samples as convolution sources adds a textural dimension that goes well past simple room simulation. The convolver accepts any IR file, so its range is defined by whatever IR library the user already maintains.

Mid/side processing in the chain allows the blended signal’s stereo width to be shaped before it exits the instrument. On a stereo blended source — two stereo samples loaded into the slots — MS processing gives independent control over the center and side content of the combined output. The practical use on drum sounds is narrowing the side content to keep a blended kick mono-compatible without losing any spatial width that the blend itself introduced through phase offset between the two sources. Mono compatibility after interpolation is not automatic; checking it and applying MS narrowing if needed is a step that belongs in the post-interpolation chain rather than assumed.

Recall Stability and the Drag-and-Drop Loading Model

Interloper loads samples via drag-and-drop directly from the OS file browser or a DAW’s sample browser, and saves the loaded source paths and blend states as part of the preset. When a session is recalled, the plugin re-references the source files from their saved paths. If source files have moved — a common occurrence in sample library reorganization or DAW template migration — the slot shows a missing-file state, and the blend state from the previous session is retained but produces silence until the file is relinked. Blend states are stable across recalls as long as source files remain at their original paths.

The real-time visual feedback during blending shows spectral content from each source and the combined output in the interface, which makes crossover placement and blend iteration faster than working by ear alone. Seeing where the spectral energy from each source lives relative to the crossover points guides initial placement: if Source A’s fundamental lands inside the mid band rather than the low band, the low crossover needs to shift. The visualization reduces the number of trial-and-error iterations before the blend behaves predictably, particularly on tonal sources with harmonic stacks that aren’t immediately audible at a specific band boundary.

MIDI triggering means the instrument responds to note input like a sampler — velocity sensitivity, note-on and note-off behavior, and polyphony settings apply. On a drum bus context the MIDI trigger input replaces a traditional one-shot sampler; on a sustained sound design context, held notes play through the full sample duration and the blend sliders’ automation shapes the output over time. The combination of MIDI playback and automatable blend creates a behavior that sits between a static sample and a synth parameter animation — the sound evolves not through oscillator movement but through spectral blend shifting.

Where Two Sources and Three Bands Run Out

Interloper’s architecture caps at two input sources and three frequency bands. There is no slot for a third source, no per-band source routing that would allow Source A at low and Source C at high with Source B at mid, and no sub-band division within any of the three regions. A producer who wants to layer three samples — say, a sub from one kick, a transient from a second, and a room tail from a third — cannot accomplish that within a single Interloper instance. Two instances with one output feeding the other’s slot as a file could approximate it, but that workaround introduces a pre-render step.

The three-band granularity is sufficient for the majority of drum layering and bass combination work. For tonal instruments with dense harmonic content — a synthesizer pad with distinct low, low-mid, upper-mid, and high character zones — the available three-band split may not provide enough spectral resolution to address all four regions independently. In those cases the blend between two sources in the mid band collapses two spectrally distinct regions into one slider, which limits the precision available. This is a structural ceiling of the current engine version, not a configuration problem.

Producers already running dedicated multiband routing chains in their DAW — a mature split-and-route setup with eight or more bands, individual compression and saturation per band, and complex cross-routing — will find Interloper’s architecture a simplification rather than an upgrade. Its efficiency advantage applies at the level of producers who currently reach for simple layering with gain staging and EQ and find that workflow iteratively slow. Engineers running fully articulated spectral processing chains have already solved the recall and auditioning problems Interloper addresses, and the two-source, three-band limit will arrive before their session complexity does.

FAQs