Session Setup and Organization

Starting a Session

When you open a new session, resist the urge to start recording or importing immediately. Spend five minutes setting up the infrastructure:

Name the session descriptively. “Session 1” tells you nothing in three weeks. “Song Title - Mix v1 - 2026-03-06” tells you everything.

Set your sample rate and bit depth. Record at 24-bit. Sample rate depends on the destination — 44.1 kHz for music that will end up on streaming platforms, 48 kHz if video is involved. Pick one at the start and don’t change it mid-project. Converting sample rates degrades quality.

Create your buses and routing before you add content. Drum bus, vocal bus, instrument bus, effects returns — the structure from Chapter 11. If you have a template, open it. If you don’t, build one now and save it for next time.

Gain Staging in Practice

Chapter 7 introduced gain staging as a concept. Applying it starts at session setup.

The goal: every stage of the signal path operates at a healthy level — not too hot, not too quiet. In a 32-bit floating-point DAW, you technically can’t clip internally (the math handles it). But plugins — especially those that model analog hardware — respond differently depending on how much signal you feed them. Drive an analog-modeled compressor too hard and it behaves differently than the designer intended. Feed it too little and you’re below the effective range.

Start with unity gain. Set every fader to 0 dB (unity). If your raw tracks are peaking well above -6 dBFS, use clip gain or input trim to bring them down before they hit the fader. The fader should be a mixing tool, not a damage-control tool.

Check the master bus. With all faders at unity, look at the master bus peak. If it’s slamming 0 dBFS, your individual tracks are too hot. Trim them down. You want the master bus peaking around -6 to -3 dBFS before you start mixing — this gives you headroom for processing.

Watch your plugin levels. Every time you add an EQ boost or a compressor with makeup gain, you’re adding level. Check the signal after each plugin. If a 3 dB EQ boost pushed your signal up 3 dB, either reduce the plugin’s output or adjust your gain structure to compensate. Small boosts accumulate across a mix.

Color-Coding and Naming

Color-code by instrument group. All drum tracks one color, all vocals another, all synths another. Every DAW supports this. It sounds trivial until you’re staring at forty tracks in a deadline session and need to find the background vocal stack immediately.

Name every track clearly. “Audio 7” means nothing. “Vox Lead” means everything. Use consistent abbreviations: Vox, Gtr, Bass, Drums, Synth, FX. If you have multiple microphones on one source, include the mic or position: “Kick In,” “Kick Out,” “Gtr Amp 57,” “Gtr DI.”

Versioning

Save versions as you work. “Mix v1” on Monday, “Mix v2” after Tuesday’s revisions, “Mix v3 after client feedback.” Never overwrite a previous version — you will want to go back at some point, and when you do, you’ll be glad the file is still there.

Some DAWs support versioning natively (Pro Tools playlists, Logic alternatives). If yours doesn’t, Save As with a new name. Disk space is cheap. Regret is expensive.

Future-Proofing

Sessions have a shelf life. Plugins get discontinued. Operating systems change. DAW versions advance. A session you can open today might not open cleanly in five years.

The best insurance: collect all files into the session folder (every DAW has a “Save a Copy” or “Collect All and Save” function that gathers audio, samples, and presets into one folder), and export stems. The session file might become unreadable. The stems — plain audio files — will play on any system, forever.

Exporting Stems

Stems are submixed audio files — one file for the drums, one for the vocals, one for the bass, and so on. They’re your insurance policy and your collaboration format.

Why stems matter:

• If your session file corrupts, stems let you rebuild the mix
• If you need to send the project to a collaborator using a different DAW, stems translate universally
• If you hire a mastering engineer, stems give them more control than a single stereo mix
• If you need to remix or rearrange the song later, stems give you a starting point without reprocessing everything

How to export stems: Solo each bus, bounce to a new audio file. Or use your DAW’s batch export feature — most modern DAWs can export all buses simultaneously. Match the sample rate and bit depth of your session. Use lossless formats (WAV or AIFF), not MP3.

Export a stereo mix too. In addition to stems, always bounce a full stereo mix at the same time. Label it clearly with the date and version number.

What to Practice

1. Build a template. Create a session template with buses, color-coding, sends, and a reference track input. Save it. Use it for your next three projects and refine it each time.
2. Practice gain staging. Open a session with raw tracks. Set all faders to unity. Use clip gain to bring hot tracks down so the master bus peaks at -6 dBFS. Notice how much headroom you have for mixing moves.
3. Export stems from a finished project. Solo each bus, bounce, and save into a “Stems” folder alongside the session. Verify the stems by importing them into a new session — they should sum to a mix identical to your original.