Stem mastering has become the de facto standard for remote audio collaboration. Instead of bouncing a single stereo mix and hoping for the best, you send grouped stems — drums, bass, vocals, instruments, effects — giving the mastering engineer granular control over the final product.
For remote teams, this workflow eliminates the most painful bottleneck in audio production: the revision cycle.
What Is Stem Mastering?
Traditional mastering takes a finished stereo mix and applies final processing — EQ, compression, limiting, stereo enhancement — to prepare it for distribution. The mastering engineer works with a single file and has limited ability to fix issues baked into the mix.
Stem mastering changes this equation. By receiving individual grouped tracks (typically 4–8 stems), the mastering engineer can:
- Adjust the balance between instrument groups
- Apply targeted EQ to specific elements without affecting others
- Fix frequency masking issues that would require a remix in traditional mastering
- Make creative decisions about spatial placement and dynamics per stem
Setting Up Your Stem Session
The key to a smooth stem mastering session is consistency. Here's a checklist for preparing your stems:
File Format
Format: WAV or AIFF (never MP3)
Bit Depth: 24-bit minimum (32-bit float preferred)
Sample Rate: Match your session (44.1kHz, 48kHz, 96kHz)
Stem Groups
A typical stem split for a modern pop/rock production:
| Stem | Contents |
|---|---|
| Drums | Kick, snare, toms, overheads, room mics |
| Bass | Bass guitar, synth bass, sub layers |
| Vocals | Lead, backing, ad-libs, vocal effects |
| Instruments | Guitars, keys, synths, pads |
| FX | Reverbs, delays, risers, impacts |
Critical Rules
- All stems must start at the same timecode — bar 1, beat 1, with any pre-roll silence included
- Remove master bus processing — no limiter, no bus compression on the master output
- Label everything clearly —
01_Drums.wav,02_Bass.wav, notbounce_final_v3_FINAL.wav - Include a reference mix — a rough bounce of how you want it to sound, for context
Managing Feedback with Timestamped Comments
The biggest friction point in remote stem mastering isn't the audio — it's the communication. Vague feedback like "the chorus feels flat" or "can you make it louder" leads to multiple revision rounds and frustration on both sides.
Timestamped feedback solves this by anchoring every comment to a specific moment in the audio:
- "0:47 — vocal sibilance is too harsh after the de-esser" is actionable
- "The vocals sound weird" is not
When your mastering engineer can see exactly where an issue occurs, they can address it in a single revision instead of three.
Reducing Revision Cycles
The average stem mastering project goes through 2.4 revision rounds. Here's how to cut that down:
- Send reference tracks with your stems — commercial releases that represent your target sound
- Use timestamped comments instead of email threads
- Consolidate feedback — send all notes at once, not one at a time over a week
- Trust the process — give your mastering engineer context about the genre, audience, and distribution platforms (Spotify, Apple Music, vinyl) upfront
Delivery Formats
Your mastering engineer should deliver multiple formats from the same session:
Streaming: -14 LUFS (Spotify/Apple Music normalized)
CD: -9 to -12 LUFS (depending on genre)
Vinyl: Separate master with adjusted low-end and dynamics
Broadcast: -24 LUFS (EBU R128 for TV/film)
Each format has different loudness and dynamic range requirements. A good stem mastering session produces all of these without additional cost, since the stems are already separated.
Conclusion
Stem mastering for remote teams isn't just about audio quality — it's about workflow efficiency. By standardizing your stem preparation, using timestamped feedback, and consolidating your revision process, you can deliver broadcast-ready masters in fewer rounds with less friction.
The tools exist to make this seamless. The question is whether your workflow is set up to take advantage of them.