Stems vs. multitracks: what to send, and how to check it

What does the next person need to change?

“Can you send the stems?” sounds like a complete request. Then the mixing engineer receives a stereo drum group when they needed the individual microphones. Or a performer receives every drum microphone when they needed one backing-track file.

People use the word differently, so ask what should be inside the package. In a common production setup, stems combine musical groups, such as drums or backing vocals. Multitracks contain individual parts. A stereo mix combines the whole production into its listening version.

A live show may suit grouped stems. Mixing may require separate parts. Mastering may require only the stereo mix unless you have arranged otherwise. The right choice depends on what someone needs to control next.

Ask a few practical questions

Before exporting, agree on format, sample rate, bit depth, start point and ending. Then talk about the sound. Does the recipient want your processed choices, unprocessed sources or both?

A distorted synth may owe its entire personality to its effects. A vocal being mixed somewhere else may need a dry version as well as the version everybody already likes. There is no single “professional” answer that fits both situations.

Shared effects deserve a sentence of their own. If the lead vocal is dry and its reverb lives in another file, name that clearly. If the reverb is already printed into the lead, say so. Accidentally adding the same effect twice rarely improves anyone’s confidence in the delivery.

Give every part the same starting line

For a straightforward transfer, export from a common agreed start. Keep the silence before a late entrance. That second-verse guitar should land in the second verse when its file is imported, without someone dragging it around until it sounds vaguely familiar.

Include tempo and meter information. If the tempo changes, a single BPM in a filename will not tell the whole story. Explain the change or provide the information your collaborator requests.

Ableton’s All Individual Tracks export produces equal-length files, which helps alignment. Its manual also notes that group and return tracks are included. Check the list before sending everything: playing a group alongside all its individual parts can double material that was meant to appear only once.

Keep the reference mix nearby

Separate files do not always add up to an exact copy of the approved mix. Groups may interact through compression, saturation, sidechains and shared effects. Exporting each group alone can change how those processes respond.

That is worth discussing before someone spends an hour trying to rebuild a mix that the files cannot reproduce identically. Is the goal faithful playback, or enough freedom to mix the song differently?

Apple’s Logic Pro export guidance distinguishes effects, automation and tail options. Check the equivalent choices deliberately in your DAW. When a creative sound matters, a clearly labeled printed version can preserve it. Optional dry files should look optional, so the next person does not accidentally use both versions together.

Try opening your own delivery

A clean test session is an excellent place to find mistakes. Import the files at the agreed start and listen through the early hits, late entrances and ending. A silent export is much less embarrassing when you discover it first.

Compare the result with the reference mix. Check for missing instruments, doubled parts and cut-off tails, while keeping any expected differences in mind. For drums, verify that the microphones and layers remain aligned.

Vocals deserve a careful check too. Is this the approved comp, with the intended tuning treatment and doubles? The word lead in a filename cannot answer that. Listen to what you actually exported, even if you are quite sure which tracks were selected.

• Name each part or group in plain language.
• State the shared start point and any offset.
• Include the approved stereo reference.
• Identify printed effects and optional dry alternatives.
• List intentional omissions and expected mix differences.

Include a small map of the song

A useful note might say: “All files start at bar 1; the song begins at bar 5. Drums and music include their group processing. Vocal reverb is separate. The reference has additional stereo-bus processing.” Adjust the details to match your actual session.

That is enough to answer several questions before they interrupt somebody’s work. Add any intentional omissions and explain whether alternate files should replace, rather than accompany, another part.

Ask the recipient to confirm that the package opens and aligns before you put the session away. Fixing an export while the project is still fresh is far easier than reopening it a week later and wondering which of your many nearly identical alternatives you used.