How I Fix Cross-DAW Collaboration in 2026 with the Dry MIDI + Wet Stem Protocol

Horia Stan is music producer and sound engineer at The One Records, Bucharest.

Why cross-DAW collaboration still breaks records

Remote collaboration is the norm in 2026. Teams use different DAWs. They use different plugin formats and OSes. That creates two problems I see daily: lost creativity and time spent fixing sessions. I do not accept that. I set rules. Clean rules speed up decisions.

I work in Logic Pro on an Audient iD14 MkII. My chains are FabFilter Pro-Q 4, Waves SSL-style buss compression, and Keyscape for piano beds. My collaborators use Ableton, FL Studio, or Motion DAW. They also use different plugin lists. You cannot send a full Logic session and expect the other side to open it with perfect recall. That is naive.

I use a protocol I call Dry MIDI + Wet Stem. It is simple. It preserves playability. It preserves my sound. It avoids format fights.

The Dry MIDI + Wet Stem protocol - what it is

Short version: send editable MIDI and instrument presets, plus rendered stems with my sound. The collaborator can change arrangement and performance using MIDI. They cannot unintentionally alter the main sound I engineered. I get to keep the production decision where it matters.

Longer version:

• Dry MIDI: fully editable MIDI files with articulation CC lanes, a tempo map, and a one-bar pre-roll alignment. No embedded instrument audio. Sends the note info. Use 24 PPQ or higher when exporting from Logic's MIDI. Include track names like 'LeadPad_MIDI_v01'.
• Instrument presets: export the plugin preset or program for the instrument used. For AU plugins like Keyscape or FabFilter, save the preset from the plugin UI and include it. For Logic's Sampler, save the instrument as a Channel Strip Setting. For Kontakt or other third-party samplers, export the instrument patch.
• Wet stems: stereo audio stems that contain all processing I want glued to the sound - reverb, saturation, convolution tails. Stems are meant to reproduce my tone instantly in any DAW.

This split forces a decision. If the collaborator alters the performance, they work from MIDI. If they want my tone, they import the wet stem. Both are usable. Neither breaks the session.

Technical settings I enforce

I set these numbers every time. They remove guesswork.

• Sample rate: 48 kHz. It balances CPU and quality for hybrid workflows.
• Bit depth: 24-bit.
• Stem headroom: peak ceiling -1 dBTP.
• LUFS for rendered stems: aim for integrated -16 to -18 LUFS. That leaves mix headroom while still translating loudness.
• Naming: TrackName_BPM_v01_48k_24b.wav.

Packaging presets and plugin metadata

Plugins kill compatibility. I accept that. So I remove the guesswork.

1. Save every plugin preset you used. FabFilter Pro-Q 4 has a Save Preset option. I export the preset file and include it. Keyscape lets you save programs. Waves presets are saved via the Waves menu. For Logic stock plugins save Channel Strip Setting.

2. Create transfer.txt. List plugin names and versions. Example: "FabFilter Pro-Q 4 v4.11.0, Waves SSL G-Master v12.3, Keyscape v1.8.2." Do not assume they can load a plugin. This list helps the other producer recreate or find substitutes.

3. If a plugin is crucial and cross-platform incompatible, render an extra stem labelled _FXFREE. That stem is the dry instrument with minimal processing. The collaborator can reinstate their own effects.

Automation, tempo maps, and alignment

Tempo and start time break sessions fast. Fix them.

• Set bar 1 to start at 1.1.1 in Logic. Put performance material after a one-bar pre-roll. This ensures DAW imports align without sample drift.
• Export tempo map from Logic: File > Export > Tempo, Key, and Time Signature. Include it in the zip.
• Export MIDI with controller lanes: CC1 for modulation, CC11 for expression, and CC64 for sustain. Name them logically.

If you send MIDI only, the collaborator can change phrasing. If you send wet stems only, you keep sonic identity. If you send both, you give maximum flexibility while protecting decisions.

Versioning and communication rules I enforce

Collaboration is a human problem first. Technical rules help.

• One master transfer.zip per delivery. No scattered files.
• Semantic versioning: v01, v02, etc. Always include date and BPM.
• Change-log.txt with bullet points. One-line summary per change.
• If someone wants to replace a sound, they must provide the MIDI change or a new wet stem. No silent edits.

This policy stops endless rework. It forces the creative decision to happen once.

Example: sending a vocal stack from Logic to an Ableton producer

I record in Logic. I comp and tune. I save a Channel Strip Setting that includes my FabFilter Pro-Q 4 corrective moves and Waves reverb send levels. I export the vocal MIDI (if any) and save the Keyscape patch for background piano.

I render two stems:

• Vocal_Wet_v01_48k_24b.wav (full chain, reverb tails included, -1 dBTP)
• Vocal_Dry_v01_48k_24b.wav (no reverb, only clip gain and pitch correction)

I export the Channel Strip Setting and include presets for FabFilter and Waves I used. I write transfer.txt with the plugin list and a one-line note: "Use Wet stem for reference glue. Use Dry stem if you need to re-embed your room or reverb." Then I zip and send.

The Ableton producer imports the wet stem for quick reference. They import MIDI and presets if they want to rebuild performance using Live's samplers. If Live cannot load Keyscape, they at least have my wet stem and the dry stem to build from. Everyone moves forward.

Why this is faster than "send project file"

Sending a project file assumes parity across DAWs and plugins. That is false. My protocol removes that assumption. It also reduces back-and-forth. You either change MIDI or accept my tone. Decisions happen. Deadlines get met.

This workflow also preserves my production stamps. I do not give up sounds I crafted for the sake of being perfectly editable. I give access where it matters.

Final takeaway

Start every remote session with one transfer.zip that contains: 48 kHz / 24-bit wet stems at -1 dBTP, editable MIDI with CC lanes and tempo map, exported plugin presets, and transfer.txt listing plugin names and versions. Use semantic versioning like v01_20260510_BPM120. Do that and you cut days of back-and-forth from every collaboration.