← Back to blog

Why your exported stems don't line up (and how to check before you send them)

· Dave Nunes

workflowmixingexport

A session sounds right in your DAW, every stem lines up, the mix is solid, and then the exported files land somewhere else (a mix engineer's session, a collaborator's DAW, a mastering chain) slightly out of time with each other. Nothing was moved. The stems just don't line up anymore. This happens more often than most producers realize, and it's almost never a mistake you made while arranging.

Where the misalignment actually comes from

Every DAW delays some tracks to keep everything in sync when a plugin introduces real processing latency, things like linear-phase EQ, certain limiters, and lookahead compressors don't respond instantly, so the DAW reports that plugin's delay and nudges other tracks to compensate. This is called plugin delay compensation, or PDC. It works well inside a single session. It becomes a problem the moment stems get exported separately, because how consistently PDC gets applied across every exported file is not guaranteed, and it varies by DAW, by plugin, and by exactly how the export happened.

  • Inconsistent PDC across stems. If some stems pass through a bus with a latency-inducing plugin and others don't, or if a plugin misreports its own latency (this happens more than manufacturers admit), the stems that went through it can land a few milliseconds to a few dozen milliseconds off from the ones that didn't.
  • Freeze versus render. Freezing a track and bouncing it down don't always apply delay compensation identically. A frozen track can render at a slightly different offset than the same track exported through a normal bounce, depending on the DAW.
  • Warped or time-stretched audio. If a region was stretched or quantized to fit a tempo grid, the exported file needs to render from the true, sample-accurate stretched position, not the original unstretched audio's timing. A warp engine that doesn't commit cleanly at export time can leave a small offset at the very start of the file.
  • Group bus processing applied unevenly. A lookahead limiter or compressor on a group bus adds real delay to everything routed through it. If you export some stems pre-bus and others post-bus, they were never going to line up in the first place.

None of these are bugs, exactly. They're all reasonable behavior for a DAW handling one session internally. The problem only shows up once files leave that session and get played back somewhere that doesn't know what compensation was applied where.

A DAW-agnostic way to check before you send stems anywhere

You don't need to understand every DAW's internal PDC implementation to catch this. You need one check that works regardless of what you exported from: does the sum of your stems match your original mix, sample for sample.

  1. Import every exported stem into a fresh session, all starting at the same timeline position they were exported from (usually bar 1, or whatever absolute position your export started at).
  2. Bring in your final full mix on its own track, at that same starting position.
  3. Invert the phase on the summed stems (most DAWs have a phase or polarity flip on every channel) and play the inverted sum against the full mix at the same time.
  4. If every stem lines up, the two should cancel almost completely, close to silence, not exact silence, since a limiter or bus processing on the master will never null perfectly against un-summed stems, but close enough that nothing rhythmic or tonal is audibly left over. If you hear a smeared, phasey, or comb-filtered version of your mix instead of near-silence, something is offset.

If the null test flags a problem, the fastest way to isolate it is by elimination. Solo pairs of stems and check whether transient hits (a kick, a clap, anything with a sharp attack) land on the exact same sample across both. The stem that's off is almost always the one that passed through the most processing, a bus insert, a frozen track, a heavily warped region, before export.

What to do once your exports are actually aligned

Alignment is a separate problem from organization, but they show up together in practice. A batch of correctly-aligned stems that are also named kick (3) FINAL_v2.wav, with no tempo or key attached, is still a batch someone has to sort through by hand before they can use it.StemStash handles that second half: it classifies each stem by instrument, tags the project's BPM and key, and sorts everything into consistent group folders. It doesn't check timing alignment, that's a property of the export itself, not something a naming and classification pass after the fact can fix or detect. Get the export right first with the null test above, then let the organizing be the part you don't have to think about.

The free Hobby tier includes 10 credits, no card required. Get started once your next export is one you trust.