Should library stems include master bus plug-ins? What to send, and why summed stems don't null

Leave the master bus plug-ins off your library stems unless the library says otherwise. Stems that pass through a limiter or bus compressor will not add back up to the mastered mix, and most libraries and mix engineers want unmastered stems for that reason. If a spec sheet says "mastered stems", ask what they mean, then export both sets. In Logic Pro, File > Export > All Tracks as Audio Files already skips the Stereo Out chain. Soloing groups and using File > Bounce > Project or Section does not, so bypass the Stereo Out plug-ins first.

I write for Extreme Music and have delivered to many other libraries. This question comes up on every spec sheet, and composers argue about it on the TAXI forums. Here is the reasoning, and the workflow I use.

Why summed stems don't null against the master

A fader move or a clean EQ is linear. Process each stem, add them together, and you get the same result as processing the sum. A limiter, a bus compressor, a clipper, a saturation plug-in: none of those are linear. They react to whatever is at their input.

Think about the drum stem on its own. The limiter sees kick and snare transients with nothing underneath, so it does far less work than it does on the full mix. Now the keys stem. In the full mix, the bus compressor is triggered mostly by the kick, so it ducks the keys a little on every beat. Solo the keys and bounce, and that ducking is gone.

Add those stems back together and you have a mix that is louder than the master, with different dynamics and transients. Flip the polarity on the master and play both, and plenty is left over. On a heavily limited track, in my experience, the difference is several dB and some audible pumping. Stems processed individually cannot sum to a mix that was processed once.

What libraries and mix engineers actually want

Most libraries want unmastered stems and a mastered full mix. An editor pulls the vocal stem down 3 dB under dialogue, or drops the drums for a tender scene, and the library masters the result to match the catalog. If your stems already have a limiter printed on them, every rebalance stacks a second round of limiting on top. Mix engineers want the same thing, because they will put their own chain on the two-bus.

In my own deliveries the pattern has been consistent: stems clean, full mix and instrumental mastered, sometimes an unmastered full mix alongside. The full checklist is in what libraries ask for in a stem delivery.

When a library asks for "mastered stems"

It usually means one of three things.

They want stems that sound finished. The spec writer is using "mastered" to mean "final, not a rough". They want clean stems at a sensible level.

They want the master bus colour without the limiter. Some composers run bus EQ or tape emulation on the Stereo Out, and the library likes that sound. Bypass the limiter, keep the rest.

They want loud stems for a quick preview. Occasionally an editor wants stems that sit near commercial loudness without touching a fader. These will not null against the master, and the library knows that.

You cannot tell which from the spec sheet, so ask. The line I send is: "Do you want the stems to sum back to the mastered full mix, or do you want each stem to pass through my master chain? I can send either, or both." Nine times out of ten the answer is the first option.

The safe workflow: ask, then export both sets

When in doubt, I export both and label them clearly. It costs a few minutes and saves a re-delivery.

1. Prepare the session. Name every track. Make sure the project end sits past the last reverb tail. Decide your stem groups: drums, bass, guitars, keys, synths, vocals, FX, or whatever the spec names.

2. Export the unmastered set with Export All Tracks. Choose File > Export > All Tracks as Audio Files (Shift-Command-E). Set WAV, 24-bit, at the project sample rate. Normalize Off. Leave Bypass Effect Plug-ins unchecked so your channel inserts stay in. Check Include Audio Tail and Include Volume/Pan Automation. Export writes one file per track from the project start, and in my experience it ignores whatever is on the Stereo Out. Your limiter is not on these files whether you bypass it or not. For the pitfalls around sends and track stacks, see how to export stems from Logic Pro.

3. If you solo-and-bounce instead, bypass the Stereo Out first. Soloing a group and using File > Bounce > Project or Section (Command-B) captures sends and bus processing as the mix hears them, but that path runs through the Stereo Out. Open the Mixer (X), click the Stereo Out channel strip, and bypass each insert you do not want on the stems. The bypass control sits on each insert slot in the Mixer. Then solo each group and bounce in Offline mode, PCM WAV, 24-bit, Normalize Off, Include Audio Tail on, same start and end for every stem.

4. If the library also wants the mastered set, re-enable the chain and bounce the same groups again. Same locators, same groups. Put Mastered in each file name and keep the sets in separate folders:

Midnight_Run_Stem_Drums.wav
Midnight_Run_Stem_Drums_Mastered.wav

5. Check the unmastered set. In a fresh project at the same sample rate, import the unmastered stems at bar 1 along with an unmastered full mix bounced with the Stereo Out bypassed. Put Gain with Phase Invert on the mix and play. It should go to silence. If not, a send return or a pre-fader send is outside your groups. The mastered set will not null, and that is expected. The same bypass routine covers the instrumental and unmastered mixes most libraries ask for alongside the stems.

Where QuickStem fits

I built QuickStem because steps 3 and 4 ate my evenings. It scans the Logic session's mixer and routing to find the stem structure. I review what it found, keep the groups or combine channels into custom stems, and pick the mix versions: Full Mix, Instrumental, Unmastered Full Mix, Unmastered Instrumental, and any custom mixes.

For the unmastered versions, I tell it which Stereo Out plug-ins to bypass. On most of my sessions the limiter goes and the bus EQ stays. The Full Mix keeps the whole chain. That choice, the stem groups and the naming convention are saved as a template, one per library, so the decision is made once.

Bounce All then drives Logic through Apple's Accessibility API, soloing, muting and bouncing one deliverable at a time the way I would by hand. It never touches audio files directly, and it verifies the session is unchanged afterward. Output lands in STEMS, MIX DELIVERABLES and DOCUMENTS folders, and several sessions can queue for an overnight batch.

QuickStem runs on macOS 14 or later with Logic Pro 11 or later (verified on Logic Pro 12). It is signed and notarized, and one licence covers two Macs. Details are on the QuickStem product page. You can buy QuickStem for $49 or QuickStem Plus for $79 before the opening sale ends November 30, 2026. Every purchase includes one free Soundwall master. Ableton Live and Pro Tools versions are coming.

FAQ

Should stems have the limiter on or off?
Off, unless the library asks for processed stems. A limiter reacts differently to each stem than to the full mix, so limited stems will not sum back to the master.

Does Export All Tracks in Logic Pro include the master bus?
In my experience, no. Each track renders before the Stereo Out, so its inserts are not printed. Solo-and-bounce with Command-B does include them.

What does "mastered stems" mean on a spec sheet?
Usually "finished stems at a good level", sometimes "master bus colour but no limiter", occasionally "loud stems for previews". Ask, and offer both sets.

Can QuickStem bypass only some of my master bus plug-ins?
Yes. For the unmastered versions you choose which Stereo Out plug-ins to bypass, so you can drop the limiter and keep the bus EQ.

Author: John Coggins is the founder of Soundwall Studios in Westlake Village, CA, and the creator of QuickStem. He's a songwriter and producer with over 1,000 works registered with ASCAP and a long-time writer for Extreme Music.

Previous
Previous

How to make 60, 30 and 15 second edits of a library track in Logic Pro

Next
Next

Why Logic Pro exports mono tracks as stereo files (and how to get true mono stems)