Mastering & delivery
Stems vs multitracks: what to export for a useful collaboration
Choose grouped stems or individual tracks, preserve timing and avoid losing shared effects or bus processing in the handoff.
Stems are grouped renders such as drums, bass and vocals. Multitracks are the individual parts. Because collaborators sometimes call every exported track a stem, ask what they need to control. A grouped kit is useful for live playback but may block a mixer who needs to rebalance kick and snare.
By Spectraforge Audio3 min read
Published
Guide review: Captum Records and AS Mastering. AI-assisted writing and source checks. How these guides are made.
Choose the separation the next person needs
Agree whether processing and automation should be printed, which wet/dry alternatives are needed, and whether the sum should approximate the approved mix. This prevents a correct-looking folder from giving the recipient the wrong amount of freedom.
Keep one shared timeline start
Export every part from the same timeline position, retaining silence before a later entry. Use the agreed rate and representation, and include complete tails. A common end simplifies import but a tail may legitimately extend farther; document any difference rather than cropping a useful decay.
Disable independent normalisation when preserving relative balances. Decide whether volume and pan automation should be included. Logic’s documented track export exposes those choices, along with range and audio-tail settings; check the equivalent controls in your own host. Include tempo changes as a map or clear notes.
Assign shared effects once
Choose whether a shared reverb belongs in an FX stem or inside a group. Include it once. If two isolated vocal stems each contain the full shared return, adding them can duplicate the reverb. Likewise, do not play a “dry alternative” and its “processed alternative” together unless they are deliberate layers.
Suggested routing check: export a dry lead, a backing-vocal group and one shared vocal FX return. Re-import them on clean tracks at the common start. Solo the FX return to check that it is effects only, then sum all three. A dry result points toward a missing send or return; an overly wet result points toward duplication or altered levels.
Explain why nonlinear bus processing may not reconstruct
A compressor responding to the whole kit behaves differently when each drum is sent through it alone. The same problem applies to isolated stems through a master limiter. Summing such renders is not generally identical to processing their combined signal once.
If exact reconstruction matters, agree how to handle these shared stages before printing. A full approved mix is the reference. You might deliver groups before master processing and describe the master chain, or print the combined group where its bus behaviour defines the sound. Do not promise independent tracks and exact nonlinear reconstruction without testing that specific route.
Rebuild before packaging
Import the complete delivery into a blank session at its shared start. Compare its musical balance with the rough mix and check transitions and ending. A perfect null may be inappropriate for time-varying effects, but missing tracks, shifted starts and doubled returns are still defects you can catch.
Use role names, mark alternatives and include a short routing note. A receiver should know which files play together, which replace one another, what was printed and which rough mix is authoritative. That information is more useful than adding another unexplained set of renders.
Technical references
- Apple Logic Pro 10.7: track export, automation and audio-tail options
- Ableton: stems, multitracks and common export ranges
Listening exercises are proposed practice routines. Worked examples illustrate the stated setup; they are not reports of our listening tests. Editorial process and corrections.