Skip to content
Muratpaşa Mon⁠–⁠Fri 10:00⁠–⁠20:00 · Sat 10:00⁠–⁠16:00 info@artncraft.com.tr 0536 959 02 62
Stüdyoda ilk kayıt seansına nasıl hazırlanılır?

Studio Tips

Checklist Before Sending Stems to Mix

A technical checklist to run before sending files to a mixing studio: sample rate and bit depth, exporting from the same start point, clipping and levels, effect printing rules, naming, rough mix, reference and an import test before delivery. Special notes for MIDI, live drums and vocal layers are included.

8 min read
In this article
  1. Define the Terms: Multitrack, Stem and Rough Mix
  2. 1. Lock the Project Settings
  3. 2. Export Every Track From the Same Point
  4. 3. Level and Clip Check
  5. 4. Effects: What to Print and What Not
  6. 5. Editing and Cleanup
  7. 6. Naming and Folder Structure
  8. 7. Reference, Rough Mix and Notes
  9. Special Cases: MIDI, Live Drums and Vocal Layers
  10. 8. Test Before Sending: Import Into a New Session
  11. 9. Sending and Safety
  12. How Much Time Should Preparation Take?
  13. Final Checklist at a Glance
  14. Common Mistakes
  15. Conclusion

A mix engineer’s first hours often go not into mixing but into repairing incoming files: tracks of different lengths, drifting start points, clipping vocals, a guitar named “Audio 14”. All of these can be prevented at the sending end, and each one costs your budget and the quality of the result. This checklist covers the technical steps producers and musicians, in Antalya or elsewhere, should go through before sending files to a studio, for instance a mixing studio in Muratpaşa.

Define the Terms: Multitrack, Stem and Rough Mix

Three concepts are often confused, and many delivery mistakes come from that confusion:

  • Multitrack (raw tracks): every microphone or instrument source is a separate file: kick, snare, overheads, bass DI, guitar 1, lead vocal. The most flexible format for mixing.
  • Stem: tracks grouped and bounced into one file: drum stem, bass stem, vocal stem. Stems are typically used in electronic production, ready-made arrangements or stem mastering.
  • Rough mix: your own temporary mix. The studio uses it as the “target feel”, so always send one.

Ask the studio in advance which you should send. Most mix jobs ask for multitrack and rough mix together.

1. Lock the Project Settings

  • Sample rate: if the project is 44.1, 48 or 96 kHz, export every track at the same rate; mixed sample rates can cause import problems or pitch shifts.
  • Bit depth: 24⁠-⁠bit WAV is the standard. 32⁠-⁠bit float is also accepted and reduces clipping risk; do not reduce to 16⁠-⁠bit.
  • Tempo and tempo map: note the BPM, time signature and any tempo changes. For projects with a tempo map, a MIDI tempo file or screenshot helps.
  • Key: write down the song’s key, especially if vocal tuning or harmonies will be added.

2. Export Every Track From the Same Point

The most common mistake is exporting each track from its own start point, so the files begin at different times and the mix engineer spends time aligning them. The right method:

  1. Set the export range from the project start (0:00 or bar 1) to the end of the song, including effect tails (reverb, delay).
  2. Export all tracks over that range, including empty parts, at the same length.
  3. Export silent sections too; this lets the files auto-align when dragged into a session.
  4. Check that “solo” or “mute” states are not hiding any track.

3. Level and Clip Check

  • No clipping: no track should have a peak touching 0 dBFS. A clipped recording cannot be repaired digitally.
  • Sensible level: track peaks should sit between -12 and -3 dBFS. Avoid extremely low levels (-40 dBFS); you do not need to normalise everything, but check very quiet tracks.
  • Fader position: leaving faders at 0 dB before export keeps file levels consistent. The mix is built from raw files; show your own balance in the rough mix.
  • Master bus: switch off master-channel processing such as limiter, compressor and EQ during export.

4. Effects: What to Print and What Not

The rule is simple: anything the mix engineer should decide stays unprinted; anything that is the identity of the song gets printed.

  • Switch off: standard EQ, compression, reverb, delay and saturation. The mix engineer will do these.
  • Print: designed sounds: vocoder, bit crusher, synth source effects, deliberate distortion, amp simulation (unless the engineer may try a different amp), creative delay and filter automation.
  • Send both: when in doubt, send a processed (“wet”) and an unprocessed (“dry”) version and separate them by name.
  • Pitch correction: if applied, send the dry vocal and the tuned vocal separately.

5. Editing and Cleanup

  • Verify there are no clicks or pops at edit points; add crossfades.
  • Finish vocal comps and put alternate takes in a separate folder; the engineer can go back to them if needed.
  • If you notice unwanted noises (headphone bleed, air-conditioner hum, shoe sounds), add a note.
  • Say whether rhythm parts are quantised or unquantised.

6. Naming and Folder Structure

“Audio 14.wav” is heavy work for a mix engineer. A consistent naming system saves time:

  • Format: numbered and descriptive: 01_Kick_In.wav, 02_Kick_Out.wav, 03_Snare_Top.wav.
  • Groups: drums, bass, guitars, keys, vocals and effects folders.
  • Special characters: use ASCII and underscores instead of accented characters and spaces; some systems produce broken file names.
  • Version number: name the project folder with date and version: SongName_v2_2026-11-16.

7. Reference, Rough Mix and Notes

  1. Rough mix: send your own mix as WAV with the master limiter off and peaks around -6 dBFS. Prefer a lossless file over MP3.
  2. Reference track: one or two songs that show the sound you want; briefly say what you like (bass, vocal brightness, wide stereo).
  3. Notes file: BPM, key, elements to emphasise, deliberate flaws (“the distortion at 0:42 is intended”).
  4. Known problem spots: if there is a known problem (“bass and kick clash in the chorus”), write it down.

Special Cases: MIDI, Live Drums and Vocal Layers

MIDI and software instruments

The mixing studio may not have the same plugins and sound libraries as you. Bounce every MIDI track to audio. Also send the original MIDI file so the engineer can return to it if a note correction or sound change is wanted. Where possible, give synth tracks both as stereo and split into characteristic layers (pad, lead, bass).

Live drums and multi-microphone recordings

In multi-microphone recordings the phase relationship between tracks matters. If you applied alignment or polarity flips while recording, note them. Microphones bleed into each other; that is normal, and trimming or gating belongs in the mix stage. Put drum tracks in a separate folder with names showing mic position: Kick_In, Kick_Out, Snare_Top, Snare_Bottom, OH_L, OH_R, Room.

Vocal and harmony layers

Separate lead vocal, double, harmony and ad-lib tracks, and include section information in the names: LeadVox_Verse, LeadVox_Chorus, Harm_Chorus_High. If the arrangement is complex, a short text file with a section map (which vocal appears where) can be added. This small piece of information cuts the engineer’s guessing time considerably.

8. Test Before Sending: Import Into a New Session

The most reliable check is to import the files you exported into a new empty project and compare to the rough mix:

  • Drop all files at the same start point; are they all aligned?
  • With faders at 0 dB and pans centred, does the rough balance resemble your rough mix?
  • Is any track missing or silent? Are file sizes abnormally small?
  • If you compare a one- or two-second section against the rough mix with polarity inverted (a null test), is the difference minimal? If not, a plugin or process may have crept into the export.

9. Sending and Safety

  • Compress the files into a single ZIP, preserving the folder structure.
  • For large projects, use a cloud sharing link and check its expiry.
  • After sending, tell the studio the file count and total size so missing files are noticed early.
  • Keep the original project file and raw recordings backed up on your side.

How Much Time Should Preparation Take?

For a mid-sized song (24⁠–⁠48 tracks), file preparation usually takes 30⁠–⁠60 minutes; for dense, many-layered productions it can reach two hours. Build this time into the delivery date from the start. Also agree the song’s delivery day and first mix date with the mixing studio: an unprepared project can lose its slot in the studio calendar and shorten your revision time. To avoid the same problems next time, add this list to your project template and apply it in the same order on every song.

Final Checklist at a Glance

  • Sample rate and bit depth identical on all tracks (24⁠-⁠bit WAV).
  • All tracks from the same start, same length.
  • No clipping; master bus processing off.
  • Standard effects off, designed sounds printed.
  • Tracks named meaningfully and organised in folders.
  • Rough mix and reference track included.
  • BPM, key and notes written down.
  • Import test done in a new session.

Common Mistakes

  1. Sending MP3: without a lossless format the mix hits a quality ceiling.
  2. Mixing processed and unprocessed files: if both versions are not named clearly, the engineer has to guess.
  3. Not sending a rough mix: the studio has to guess the target feel.
  4. Changing files at the last minute: sending a new version after the mix has started means redoing part of the work.

Conclusion

File preparation may look dull, yet it is a half-hour investment that decides the speed and quality of the mix. Once you apply this list, the studio spends its first hour shaping the music instead of fixing files. Whether you work with a local studio in Antalya or remotely, asking a studio such as Art N Craft in Muratpaşa for its technical delivery spec in advance keeps the hand-off smooth.

Share