Remote Collaboration: Transferring DAW Projects and Delivering Stems.

Working remotely with someone fails at the handover rather than through lack of talent: a project arrives with silent tracks, stems beginning at different bars, a sample rate nobody agreed and an email asking “can you make it a little brighter?” Agreeing the exchange before sending prevents all of that.

This guide covers the full handover: golden rules for remote collaboration, transferring projects between different DAWs, agreed sample rate/bit depth as a technical contract, exporting compatible stems and stem delivery standards, plus package contents and checking that delivery works.

Remote Collaboration

Remote collaboration rests on three decisions made before the first transfer:

• What is shared. The native project, stems or both. Projects allow editing; stems allow mixing and reduce plugin arguments.
• What happens if environments differ. Who installs, who converts or, more simply, who exports to audio what the other cannot open.
• When each block closes. One date per delivery and an identified version; undated work gets discussed again.

Add two habits that prevent back-and-forth: always work on a copy of a received project and always reply using the same version identification you sent. Documentation of discussions and outstanding work is covered in Session Notes, Recall Sheets, Feedback and Approvals.

Transferring Projects Between DAWs

Transferring projects between DAWs has no single format solving everything. Three routes, in decreasing order of reliability:

1. Same DAW and version. Transfer the project as it stands, provided media are collected and plugins exist on the other machine.
2. Interchange format (AAF/OMF). Retains edits, cuts and positions, but not instruments or most effects. Media must accompany the file in the folder expected by the receiving system. Avid documents consolidated-media exchange and warns that Pro Tools does not support embedded media.
3. Audio per track. Export each track as WAV from the session start, dry and at the original rate and bit depth. It is more work and the only method that always works: the recipient does not need your plugins or libraries.

Three audio-export rules make the difference: duplicate the project before cleaning it, align every file at 0:00 even if a track first sounds at minute two, and add processed versions only when the effect is part of the sound. An editor can make an edit in Ableton, FL Studio or Logic and export again if necessary, but cannot invent missing audio.

MIDI is almost always forgotten. If the other person will change notes or arrangements, send those tracks’ MIDI with their audio: they can make corrections without recreating the sound, while you retain the original design. When sending MIDI and audio together, specify which file belongs to which track in the notes; without that correspondence, the package is a list of names requiring individual opening.

A warning about format conversion: moving a project is a poor time to change DAW version, system and plugins together. Change one variable per transfer; if it fails, you will know which one.

Agreed Sample Rate/Bit Depth

Agreed sample rate/bit depth is the collaboration’s technical contract: a sample rate and bit depth set by the recipient or agreed beforehand, respected by everyone on every export.

The reasons are auditory and practical. Converting sample rate during playback is not transparent: it degrades the signal and, when done on the fly, stacks conversions without improvement. Mixing samples with different rates within a project forces real-time conversion, adding load and artefacts; the sensible option is conversion beforehand in a separate process, or no conversion. Bit depth determines noise floor and working margin: 16 bits suffice for distribution, 24 bits are usual for production and delivery, and 32-bit floating point is some DAWs’ native mixing format.

Two quick checks before sending: every delivered file declares the same rate—check visible properties rather than merely assuming it—and nobody has applied dither twice. For details of why conversion is not neutral and what bit depth means, see Digital Audio: Sample Rate, Bit Depth and Dynamic Range.

Exporting Compatible Stems

Exporting compatible stems means files open, play and align on any equipment. The procedure:

1. Group by instrument, not preference: drums, bass, harmony, percussion, vocals, effects. Five to ten groups are usually more manageable than thirty separate tracks.
2. Decide whether effects are printed. For a mix delivery, print each group’s own effects into its stem; deliver the master separately, without global processing.
3. Mark everything from the same point. Select the entire timeline and export: different starting points make the recipient guess alignment.
4. The same rate and bit depth throughout, with no exceptions or intermediate conversions.
5. Name files with the information needed to use them: title, BPM, key, duration and role.

Exporters provide shortcuts, such as FL Studio’s option to output each mixer channel separately or routing tracks and groups in Ableton. One detail has ruined more deliveries than any bug: MP3 adds a small initial silence that misaligns the file. For stems and loops, always use WAV.

Stem Delivery

Stem delivery supplies those stems under the recipient’s conditions. Every company has its own specification, but the pattern repeats: uncompressed WAV, at least 24 bits, 48 kHz unless otherwise specified, grouped stems with printed effects, all matching the full mix’s length and exact names often including BPM, key and initials.

Three common mistakes: sending stems without a reference mix so the recipient has no direction; sending global effects as a separate stem so summing doubles reverb; and renaming files after listing their names in metadata, breaking the link between actual and documented files.

If delivery includes licensed material or third-party vocals, stems retain the same status and rights. Isolating a voice with stem separation and restoration tools grants no licence.

Delivery Package Contents

The complete package, in a folder using the project’s naming convention:

• 01_mix — the full WAV mix, plus a listening copy if requested.
• 02_stems — grouped, aligned stems at the agreed rate.
• 03_midi — editable tracks’ MIDI, where applicable.
• 04_reference — the reference track used during work.
• 05_notes — tempo, key, rate, bit depth, plugin list and relevant decisions.

That makes the package understandable without a prior call. If it also goes to a label or client with their own form, the final file and credentials list is expanded in Deliverables, Credits, Split Sheets and Professional Delivery.

Verifying Delivery

Before sending, three tests taking five minutes and preventing a day of corrections:

1. Open delivery from another path, with the original project closed and, if possible, on another machine.
2. Check alignment and rate: all stems at 0:00, all with the same sample rate and bit depth, and the sum approximating the reference mix.
3. Listen to everything at low volume and compare with the reference. If stems sound louder or quieter than the mix, the gain problem is already in the file.

Passing these three checks means delivery opens the same in your living room as in the recipient’s studio.

Next Step

The folder transfers well; now the conversation must do the same: what was requested, reviewed and approved, and by when. That protocol appears in Session Notes, Recall Sheets, Feedback and Approvals.