Bouncing & Stem Export

Bouncing — also called rendering, exporting, or printing — is the process of turning your DAW session into a single audio file (or a set of audio files) that exists outside the project.

It sounds simple. It's where most production mistakes get baked in.

Why Bounce

• Final delivery. A streaming-ready WAV or AIFF for a label, distributor, or client.
• Mastering. The mastering engineer needs a stereo bounce of your mix.
• Stems. Separated bus exports for re-mixing, remixing, or sync use.
• CPU relief. Bouncing a heavy plugin chain to audio frees the CPU for other work.
• Archiving. A mixdown saved alongside the project so you can hear it years later without needing every plugin still installed.

Bounce Settings That Matter

Sample rate. Match the project's sample rate. A 96 kHz session bounced at 44.1 kHz forces a sample rate conversion that not every DAW does well.

Bit depth.

• Mastering delivery: 24-bit minimum, 32-bit float ideal.
• Streaming/CD delivery: 16-bit (after dithering).
• Working masters: 24-bit float.

Never deliver a 16-bit master to a mastering engineer. They need the headroom that 24-bit gives.

File format.

• WAV — the universal standard.
• AIFF — Apple's equivalent, identical content.
• FLAC — lossless compressed. Good for archiving.
• MP3 / AAC — lossy. Never deliver these as a master; only as a final post-master output.

Dither. When reducing bit depth (24-bit → 16-bit), apply dither. Most DAWs include it as an option in the bounce dialogue.

The Three Bounces You Need

For any mix, plan to deliver three things:

1. Stereo mixdown. Single 24-bit WAV at the project's sample rate. With your master bus processing applied. This is what the mastering engineer or distributor receives.
2. Stems. Separated bounces of your major bus groups: drums, bass, vocals, music. Useful for remixing and post-production.
3. Reference master. A final 16-bit dithered version with mastering applied (loudness-normalised). What you put on streaming services.

Stem Export Workflow

Each stem is a bounce with everything except the relevant tracks muted. The standard set:

• Drums (kick, snare, hats, percussion, drum bus processing)
• Bass (bass tracks, sub layers)
• Music (synths, guitars, keys, samples)
• Lead vocal (the main vocal performance)
• Backing vocals (harmonies, doubles, adlibs)
• FX (returns, reverbs, delays)

Each stem starts at the same time (sample-aligned to the project start), even if it's silent for the first 30 seconds. This is critical — stems that don't time-align force the next engineer to manually slip them.

Common Mistakes

Clipping the master. Bouncing a mix where the loudest peak hits 0 dBFS leaves no room for mastering. Aim for the master peak to land at −6 dBFS at most.

Forgetting to disable mute. A muted track stays muted in the bounce. Surprisingly common gotcha.

Inconsistent sample rates. Project at 48 kHz, bounce at 44.1 kHz. The DAW silently down-samples — and not always cleanly. Always match.

Skipping dither when reducing bit depth. Going 32-bit → 16-bit without dither introduces low-level distortion. Most DAWs default to "no dither" for safety; remember to enable it on the final delivery bounce.

Stems that don't time-align. Each stem must include silence at the start so all stems begin at the same DAW timecode. Otherwise stems played together drift apart.

Real-Time vs Offline Bouncing

Most DAWs offer both:

• Offline (faster than real-time) — typically faster, generally fine for plain audio + native plugins.
• Real-time — required for any external hardware (outboard compressors, hardware synths) or some plugins that don't render correctly offline.

If a bounce sounds different from playback, try real-time mode. Some plugins (especially older or modulating ones) only behave correctly in real-time render.

Reference Mastering Plugins

If you're doing your own light mastering for streaming delivery:

Further Reading

• iZotope Ozone Page
• FabFilter Pro-L 2 Page