Best Controller for Multipass (2026)
Multipass by Kilohearts is built on one deceptively simple idea: split your signal into up to five frequency bands, then load any Kilohearts snapin into any band. That single concept covers multiband saturation, band-split chorus, frequency-selective delays, OTT-style dynamics, and plenty of sound design tricks that don't have names yet. If you've gone searching for the best controller for Multipass, you've probably discovered the catch. A plugin this modular lives and dies by constant adjustment, nudging a crossover point, riding the drive on the low band, morphing a macro during a drop, and a mouse only lets you touch one of those things at a time. Every tweak means finding the right lane in the interface, clicking into the right snapin, and dragging the right control, all while your ears wait for your hands to catch up. Below, I'll break down why Multipass is uniquely awkward to drive with a mouse, which parameters come alive on hardware, and what a controller actually needs to keep up with a multiband modular host.
The typical controller setup for Multipass
If you already have a MIDI controller on your desk, here's what getting it working with Multipass usually looks like.
Multipass exposes its macros, crossover frequencies, band gains, and every parameter of every loaded snapin to your DAW. So you start the usual ritual: enter MIDI learn in your DAW or the plugin, click the Macro 1 knob, twist an encoder. Repeat for Macro 2. Then the low crossover, then the drive on the saturator you dropped into band one, then the rate on the chorus in band three. Ten minutes later you have eight assignments and you can finally start working.
Then you load your next patch, and everything falls apart. That patch had a saturator in the low band; this one has a compressor there and a phaser on the highs. Half your mappings now point at parameters that no longer exist, and the other half control the wrong thing. You either remap from scratch every time or accept a controller that only works with one patch.
And even when the mapping is fresh, the hardware itself is silent. Is encoder 4 the mid band gain or the delay feedback in band two? There's no label, so you check the screen, which is exactly what you were trying to stop doing.
The Auriteq Flow handles this differently, with mappings that follow the plugin and displays that follow the mappings. More on that later.
How to control Multipass with hardware
The short version: you map Multipass's most-used parameters, the macros, crossover points, band gains, and the key snapin controls, to physical knobs so you can shape the whole multiband patch in real time instead of clicking one lane at a time. The interesting question with Multipass is which parameters earn a spot on the hardware, so let's get specific.
Multipass parameters that transform with hands-on control
Here are the Multipass parameters I'd put on hardware first, and why each one rewards a real knob:
Macro 1 - Kilohearts designed Multipass around its macros for a reason. One macro can be routed to a dozen destinations at once, drive on the lows, mix on the highs, feedback in the mids, so a single knob morphs the entire patch. This is the most performable control in the plugin, and it belongs under a finger, not a mouse pointer.
Macro 2 - The second axis of movement. A common setup uses Macro 1 for intensity and Macro 2 for tone or space. With both on adjacent encoders you can play the patch with two hands, which is where Multipass stops feeling like a processor and starts feeling like an instrument.
Crossover 1 Frequency - The split point between your low and mid bands decides what your low-band snapins actually chew on. Sweeping it while a bass loop plays lets you hear exactly where the saturation should stop and the clean mids should begin. Clicking and dragging a thin crossover handle does the same job at a fraction of the speed.
Crossover 2 Frequency - The upper split. Moving both crossovers by hand, one per hand, reshapes the whole frequency structure of the effect in seconds, something that's simply not possible one drag at a time.
Band Gain (Low) - Each band has its own output gain, which makes Multipass a tone-shaping tool on top of everything else. Riding the low band gain against the others is how you balance a multiband patch by ear.
Snapin Drive - Whatever distortion or saturation snapin you've loaded, its drive amount is the character control for that band. Pushing drive into the low mids while listening in context beats setting a number and hoping.
LFO 1 Rate - Multipass's modulation system can route LFOs to nearly anything. With the rate on a knob you can pull a wobble from a slow drift to a rhythmic flutter and lock it to the track's energy by feel.
Mix (Wet/Dry) - The master blend decides how forward the whole effect sits. Easing it up into a chorus and back down for the verse, live, keeps Multipass musical without drawing an automation curve for every section.
A better multi-effect workflow for Multipass
Here's a real scenario: you're designing a multiband bass patch. With a mouse, you load Multipass, drop a saturator on the low band, and drag its drive up. Too much. You drag it back. Now the mids feel thin, so you scroll to the mid lane, click into the chorus, nudge the rate. Now the crossover feels wrong, so you grab the split handle and drag it down 80 Hz. Each move is a separate hunt: find the lane, find the snapin, find the control, drag, listen, repeat. The sound you're chasing lives in the relationship between five parameters, and you can only ever touch one.
With a controller, the same session runs differently. The track plays, your left hand sits on the low crossover, your right on the saturator drive. You sweep the crossover down while easing the drive up and hear the exact point where the low end gets thick without swallowing the mids. Then one hand moves to the band gain, the other to the chorus rate, and you balance the bands against each other in real time. What took twenty interactions takes one continuous gesture, and it gets captured as automation in a single take.
The deeper change is where your attention goes. Multipass's interface is dense, lanes, snapins, modulation routings, and mouse-driven work keeps your eyes pinned to it. Hardware control flips that: you make decisions with your ears while your hands do the navigating. For a plugin whose whole point is the interaction between bands, hearing those interactions as you shape them is the difference between finding a sound and settling for one.
Why Auriteq Flow is one of the best controllers for Multipass
A multiband modular host is a moving target for any controller: the parameters change with every patch, and the good sounds live in several controls moving at once. Here's how the Auriteq Flow is built for exactly that.
Pre-mapped out of the box. Load Multipass on any track in Ableton, Logic, or FL Studio and the Flow's encoders are already assigned to the essentials: macros, crossover frequencies, band gains, and mix. No MIDI learn session, no template files. Select the plugin and the knobs are live.
Dynamic displays behind every encoder. Each knob has its own display showing the parameter name and current value. When your patch changes and encoder 4 goes from a band gain to a delay feedback, the display changes with it. On a plugin where no two patches share a layout, always knowing what you're holding is the whole game.
Touchscreen page navigation. Multipass patches can expose dozens of parameters across five bands of snapins plus the modulation system. The Flow's touchscreen lets you page between them: crossovers and band gains on one page, macros and modulation on another, snapin parameters beyond that. Everything is a tap away without opening the plugin window.
Custom mappings in seconds. If a particular patch leans on one control, say the feedback of a delay snapin in band two, you can pin it to any encoder in a couple of taps, and the layout is remembered.
Picture finishing a drop: the track is running, you page to the macros and ride Macro 1 up so the whole patch intensifies, then swipe to the band page and pull the high band gain back so the top end doesn't get harsh, then ease the master mix down as the section resolves. Three moves, all by ear, all on labeled hardware, captured in one pass.
Suggested Multipass mapping layout
| Encoder | Parameter | Why |
|---|---|---|
| 1 | Macro 1 | Patch-wide morph control |
| 2 | Macro 2 | Second performance axis |
| 3 | Crossover 1 Frequency | Low band split point |
| 4 | Crossover 2 Frequency | Mid/high split point |
| 5 | Low Band Gain | Band balance by ear |
| 6 | Snapin Drive | Per-band character |
| 7 | LFO 1 Rate | Modulation speed |
| 8 | Mix | Wet/dry blend |
The verdict
Multipass might be the most flexible effect host you can put on a channel, five bands, any snapin anywhere, macros and modulation tying it all together. That same flexibility is what makes it frustrating on a mouse: the sounds worth keeping come from several parameters interacting, and a pointer can only touch one at a time.
Hardware control closes that gap. The requirements are specific to how Multipass works: mappings that adapt when the patch architecture changes, labeling so you always know which band and which snapin a knob is touching, and page navigation deep enough to reach the modulation system. Auriteq Flow covers all three, with pre-mapped Multipass support, per-encoder displays, and touchscreen paging, and it works in Ableton Live, Logic Pro, and FL Studio out of the box.
If Multipass is part of your regular sound design or mixing toolkit, putting it under physical control is one of the most impactful workflow upgrades you can make.
Ready to shape every band of Multipass with your hands?
Auriteq Flow comes pre-mapped for Multipass and thousands of other plugins - no setup required.
Explore Auriteq Flow