Multi-Output Instruments in Logic Pro: Separate Drums and Mix Each Output

A multi-output instrument lets one Logic Pro software instrument feed separate mixer channels. Leave the kick on the instrument’s main stereo pair, send the snare to 3–4 and the hats to 5–6, create the matching aux channel strips, and then mix each output as if it were a track of its own.

It's the tidy way to keep a sampled kit in one piece while the parts that matter get their own EQ, compression, sends and automation in a wider Logic Pro mixing workflow. You don't need a separate Sampler instance for every drum sound, and you don't have to bounce every internal sound to audio before you can balance it.

What multi-output means in Logic Pro

A multi-output instrument is one plug-in instance with more than one output pair. The instrument channel strip carries the first stereo pair, and the extra pairs (3–4, 5–6, 7–8 and so on) show up through aux channel strips in the Mixer. Apple’s Logic Pro multi-output guide describes the same model: route individual sounds inside the plug-in, then use aux strips to isolate them for processing.

A kit full of samples won't give you extra channels on its own. The plug-in has to offer a multi-output configuration, and the sounds have to be assigned to outputs other than Main. If every zone stays on Main, adding aux strips just gives you more faders with nothing separated on them.

Load Sampler as a multi-output instrument

The example uses Sampler because its zones make the routing easy to see. Any other instrument works the same way when its plug-in menu offers a multi-output option.

1. Select the software instrument track that should host the kit.
2. Click the Instrument slot in the channel strip.
3. Choose Sampler, then choose Multi-Output.
4. Open the Sampler window and check that the zones or samples you expect are loaded.
5. Keep the main stereo pair free for the sound you want to stay on the instrument strip. That's often the kick, or the full kit as a reference.

Resist creating every possible aux channel up front. Decide first which sounds actually need their own treatment. A small kit may only need snare and hats pulled off the main output, while a bigger kit can justify toms, percussion or a room layer too.

Route Kick, Snare and Hats to different outputs

In Sampler, open Mapping and switch to Group view, then assign each drum group in the Mixer > Output column. Apple’s Sampler Group view guide shows that column and its output menu. If your kit assigns outputs by zone, use the zone output control instead. In this example, choose Main for the instrument strip, then 3–4 and 5–6 for the two separated sounds.

• Kick → Main keeps the low-end anchor on the instrument channel.
• Snare → 3–4 gives the backbeat its own insert chain and send balance.
• Closed hats → 5–6 keeps high-frequency control off the kick and snare path.

The output number leaves the sample itself alone. It only changes where the signal shows up in the mixer after it leaves Sampler. A zone left on Main keeps riding the main instrument fader even after you've created aux strips.

Create the matching aux channel strips

Go back to the Mixer and find the channel strip holding the multi-output Sampler. Click the small + button at the bottom of the strip, and Logic Pro creates an aux channel strip for the next available output pair. Click again for every output pair you actually used.

For the example above, that means two aux strips, one for 3–4 and one for 5–6. The main Sampler strip carries Main and the new strips carry the extra pairs. Apple notes that the Add button lives on multi-output instrument strips and that the aux appears next to the instrument strip, and it recommends creating only as many aux strips as the outputs you're using.

Aux output versus bus: keep the routing clear

The aux strips a multi-output instrument creates are output paths. In this example they pick up whatever Sampler sends to 3–4 or 5–6, and you add 7–8 when you need a third independent output. A bus is something else: a routing destination for grouping several channels, building a parallel effect or feeding another processing chain.

So a bus can't stand in for the Add button here. Sending the whole Sampler channel to a bus won't split Kick, Snare and Hats into separate sources. Start with the multi-output aux strips, and then send those strips to a drum bus if you want shared glue compression or a common room effect. Our guide to buses, sends and aux channels covers that second stage.

Mix each drum output independently

Once the signal is split, treat each aux like any other mixer channel. Rename them straight away, Snare and Hats, so you don't end up adjusting the wrong pair later in a busy session.

Now the usual decisions get easy:

• Take a small EQ cut on Hats when the top end crowds a vocal or cymbal.
• Compress Snare without flattening the kick or the rest of the kit.
• Give Hats less room than Snare when the groove needs a tighter image.
• Automate the Snare aux for a fill, and skip drawing volume changes across every MIDI zone.
• Route all the drum auxes to a shared drum bus once their individual balances have settled.

Keep the Sampler instrument strip in view while you mix. If Main still carries several sounds, moving that fader can change more than the part you meant to touch. The cleanest setup keeps the low-end anchor and any deliberately combined sounds on Main, and puts every sound that needs its own treatment on a named aux.

Check the signal when an aux is silent

A silent aux almost always means a routing mismatch. The instrument is rarely broken. Trace the signal in this order:

1. Play the exact MIDI note or pad that should trigger the sound.
2. Watch the Sampler instrument meter. If it's silent, the problem sits before the output assignment: wrong note, unloaded zone, mute or MIDI routing.
3. If Main moves and the expected aux doesn't, reopen the zone and check its output pair.
4. If the aux meter moves and you still hear nothing, check the aux fader, mute, solo, output destination and plug-in chain.
5. Make sure the aux belongs to the same multi-output instrument. A bus with a similar name won't pick up Sampler’s 3–4 signal by itself.

Don't add another aux until you know which stage is silent. Extra strips can bury the real problem and make the Mixer harder to read.

Export separate drum files

Keep the kit as MIDI while you mix through the instrument’s aux outputs. When another session needs audio files, select the Sampler software instrument track and choose File > Export > 1 Track as Audio File. In the export dialog, pick One File per Channel Strip under Multi-Output Software Instruments. Apple’s track export instructions explain that this option writes extra files for the aux channel strips fed by the selected instrument’s outputs, while One File per Track folds those outputs into Main as a single file.

Set the range and starting point for the delivery. Choose Include Audio Tail if releases, reverb or delay have to ring on past the last event. Set Bypass Effect Plug-ins and Include Volume/Pan Automation depending on whether the recipient needs your processing and fader moves printed into the audio, and don't assume any of it is included automatically. Keep the MIDI project for later edits, and check the resulting files by name, length and drum part. For wider delivery choices, see the Logic Pro stem export guide.

If one combined drum file is all you need, One File per Track is the simpler choice for this instrument. A separate drum bus can still help in the mix, but how you route it has nothing to do with the channel-strip export setting.

Multi-output Sampler versus Drum Machine Designer

Drum Machine Designer is built around pads, cells and a dedicated drum interface, and Apple’s Drum Machine Designer overview describes that pad-based workflow. A Sampler multi-output setup starts from one instrument instance and exposes its extra output pairs through aux strips.

Go with Sampler multi-output when the kit already lives in one Sampler and you want to keep its zone mapping. Go with Drum Machine Designer when you want every pad to act as an obvious drum slot with its own pad-level controls and channel strip. Neither is better across the board. It comes down to where you'll want to make edits later.

If you're building a kit from individual samples, compare this workflow with our Drum Machine Designer guide. If you're still choosing a sampler, read the Sampler versus Quick Sampler comparison before you load anything.

Troubleshoot common multi-output problems

The Multi-Output choice is missing

The instrument may not offer multiple outputs in the plug-in format you picked, or you may be looking at a menu other than the channel strip’s Instrument slot. Check which configurations the plug-in offers and make sure you selected the instrument itself. An audio effect slot won't show the option.

The aux exists but receives no drum sound

Open the instrument and look at the zone’s output assignment, because a zone on Main won't show up on 3–4. Also make sure you created the aux from that same multi-output instrument strip. A generic aux or bus added elsewhere in the Mixer won't receive it.

Several drum sounds still move together

That's normal while those sounds share Main or the same output pair. Give the sound that needs independent processing its own pair, create the matching aux, and only keep related sounds together when that helps the music.

The exported stem is empty

Select the software instrument track hosting the multi-output Sampler, choose One File per Channel Strip in the track export dialog, and make sure the relevant aux is getting signal from the instrument output. Check the export range and any mute or solo state too. An output pair nothing is routed to won't give you the drum part you expected.

The Mixer is full of unused auxes

Delete aux strips you created for output pairs you no longer use. A smaller Mixer makes the live signal path easier to check and cuts the chance of editing a stale channel.

A clean multi-output pass

• Load the instrument in a Multi-Output configuration.
• Keep Main for the sound or group that should stay on the instrument strip.
• Assign only the sounds that need separate treatment to 3–4, 5–6 or later pairs.
• Click Add once for each output pair you really use.
• Rename each aux by sound or drum role.
• Check the meters before you change plug-ins or add more routing.
• Send the separated auxes to a drum bus only once each individual path is clear.
• For separate audio files, export the Sampler track with One File per Channel Strip and keep a MIDI copy for later edits.

Multi-output routing is worth the setup when it takes a repeated job out of the mix. Keep the instrument in one piece, split off only the sounds that need their own decisions, and let the auxes show those decisions in a Mixer you can read.