The project file won't open. Now what?
A collaborator sends a session you can't open: wrong DAW, missing plugins, a version that's too new. Here's how to get the audio out without asking them to do the whole thing again.
The email says "here's the session, can't wait to hear what you do with it." You double-click. Nothing. Or worse, it opens and every track is a red rectangle labeled "plugin not found." The collaboration has not started and already you're negotiating with software.
First, identify which failure you have
There are three, and they need different fixes. One: you don't own the DAW. Two: you own it but not the plugins. Three: you own both but the version is wrong — their session was saved in something newer than yours and won't open backward. Ask the collaborator which it is before you start guessing. A surprising number of these problems are solved by one sentence of clarification.
The version problem is the ugly one
Plugin mismatches are annoying but legible: you can buy, borrow, or substitute. Version mismatches are not. If they're on Ableton 12 and you're on 11, the file simply will not open, and no amount of clicking will change that. The fix is either you upgrade or they re-save in a compatible version. Neither is free. Decide who pays the cost — in money or in time — before you spend an evening troubleshooting.
The universal fallback: stems
When the session won't cooperate, ask for stems. Not the plugins, not the MIDI, not the automation curves — just the audio, one file per track, dry, from bar one, exported at the session's native sample rate. This is the lingua franca of collaboration. It works across every DAW ever made and it will still work in ten years when the plugin they used has been discontinued by a company that no longer exists.
Ask for 24-bit WAV, not MP3. Ask them to include the tempo and key in the file name or a text note. Ask for a rough mix reference alongside the stems so you know what they were hearing when they made the decisions.
What you lose, and whether it matters
Stems are a snapshot. You can't change the synth patch, can't retune the vocal, can't undo the compression on the drum bus. That matters enormously if you're supposed to be co-producing. It matters very little if you're mixing, remixing, or adding a part. Be honest about which job you've actually been hired for. The person who needs to edit the MIDI needs the session; the person who needs to make it sound good needs the audio.
The awkward ask
Sometimes the right move is to say no. If the collaborator's workflow is a black box — proprietary plugins, no exports, no documentation — that's a signal about what the rest of the project will feel like. Better to name it now than at the deadline. "I can work from stems but not from your session" is a professional sentence. It is not an insult.
Build the habit on your side
When you send a session, send it the way you'd want to receive it: freeze or bounce anything exotic, note the plugin list, include a rough mix, and put the tempo in the file name. It takes ten minutes and saves your collaborator an evening. The project file is a private document. The stems are the public one. Send the public one.