How to share a music project without losing its sounds

Ask what the other person needs to change

A collaborator asks you to send the song. SODIUM COLLAB is a browser music studio that keeps recordings, MIDI, sounds and shared projects together. First decide whether to invite them into the project or export material for their next task. A singer needs a backing track and a clear recording start. A mixer may need separate audio parts. A co-writer needs editable notes. Choose the handoff around what they intend to do.

Use a simple handoff brief: the current version, the requested contribution and the material that must remain unchanged. For example, 'Add a lead vocal to the second verse; keep the chorus melody and drum sound.' In SODIUM COLLAB, inviting a person into the current project can keep the session, sounds and discussion together. Choose their role for the task, and confirm they can open the intended project before the deadline.

Keep three different deliverables straight

Often the best handoff includes more than one. Keep a listening mix so the recipient knows what the session should sound like. Keep editable material for the part they need to change. Render important sound choices when reproducing them would otherwise depend on your machine. Label those versions clearly, so nobody accidentally plays a reference mix on top of all its component parts.

Make the required recordings available

Samples can live outside the folder you think of as the song. A vocal might be in Downloads, a drum hit on an external drive and a guitar take in yesterday's project. Keep a clear collection of the recordings used in the arrangement, including the actual audio a partner needs. If you bring a song into SODIUM COLLAB from another studio, gather the required media before importing it. Start with one representative part and confirm its sound and placement.

In a SODIUM COLLAB collaboration, check that the required audio has finished uploading before handing over. A waveform on your screen is not enough to establish that a partner can hear the file. For a portable project export, retain the audio assets it requires and test the imported copy. Keep the working session until that test succeeds. This check is especially useful before changing computers or reorganizing your original recordings.

Render sounds that depend on your setup

If the song depends on a particular instrument library, unusual effect chain or hardware recording, include audio that preserves that choice. A matching instrument name on another computer does not prove the preset and library are identical. Keep the notes too when a collaborator needs to change the performance. Think of the audio as the sound reference and the MIDI as the musical material, with different jobs.

For example, send a synth bass as a rendered audio part and as MIDI when the producer may rewrite its rhythm. Write 'Audio is the intended bass sound; MIDI is for note edits.' If the bass returns as a different instrument, that is an informed musical choice rather than a surprise. SODIUM COLLAB's installed-instrument workflow also relies on the relevant computer and sounds, so confirm the rendered part is available to collaborators who need to hear it.

Keep separate audio parts aligned

For a cross-application mix handoff, export every separate part from the same song start. Keep the silent space before a late entrance. Otherwise a guitar that begins in the second verse might land at the opening when the recipient imports its file. Leave enough ending for sustained notes and effect tails, and give the recipient the tempo and meter used for the arrangement.

• Name the files by role: LeadVocal, Bass, Drums or GuitarHarmony, with a shared version name.
• State whether effects are printed into each file and whether an alternate dry version is included.
• Include a reference mix, clearly marked for comparison rather than simultaneous playback.
• If shared effects are exported separately, identify them so they are not added twice.
• Check a late section as well as the first downbeat; a start that aligns can still hide later timing drift.

In SODIUM COLLAB's audio export settings, choose the intended output and shared range. Full mixes, individual tracks, group buses and return effects serve different purposes. Check the export choices rather than assuming every part includes the same processing. Download the result and listen to the actual files you are about to send.

Write a handoff note someone can act on

A useful note can fit in a few sentences: 'Night Walk, version 3, 96 BPM, 4/4. All audio starts at the song beginning. Lead vocal is dry; guitars include their effects. Reference mix is for comparison. Please keep the drum arrangement and balance the vocal against it.' This gives a mixer a starting point without requiring them to decode the whole session.

For a shared SODIUM COLLAB project, use project chat to identify the track, marker or bar range that needs attention. If you create a separate variation, tell everyone which project is now current. A copy does not move collaborators automatically. Avoid having one person revise the original and another revise a copy while both assume their version is the final song.

Test before declaring the handoff complete

Ask the recipient to play the beginning, one dense passage and the ending. Check the bass sound, drum mapping, vocal timing and long tails. Ask them to describe any missing or different part before they start making changes. If they are importing files, confirm the files all start in the right place and that the reference mix is muted while the separate parts play.

Keep your original editable session and a verified backup. You do not need to save every experimental export forever, but do keep the agreed handoff and enough source material to revise it. Good collaboration depends on musical trust; a dependable package helps that trust survive the ordinary differences between computers, working hours and production setups.