Pro Tools and Live don’t open each other’s sessions. The exchange format both understand is AAF — here’s how to move the edit across cleanly.
Neither app opens the other’s session file. AAF is the common ground — Pro Tools writes one, and AAF Bridge turns it into a native Live Set with the clips where they belong.
Because AAF carries audio and its edit, not the mixer, anything that lives in plugins or routing won’t travel. Commit or print those before exporting if they need to be heard.
File → Export → Selected Tracks as New AAF/OMF. Choose AAF, consolidate the audio, and add handles if you want trim room. Commit any real-time / elastic-audio processing first.
The free demo converts the first 120 seconds of any session, enough to check the result.
Set the project tempo and time signature — AAF doesn’t carry them, even from a tempo-mapped Pro Tools session.
A complete Live project folder and a plain-text report are written next to the AAF.
Clips land sample-accurately with their handles, fades and clip gain; track names carry over.
Prefer AAF — it’s the modern, richer format and the one AAF Bridge tests hardest. OMF is older and more limited; if you only have OMF, ask for an AAF instead.
No — AAF is an audio-only exchange format; no DAW carries plugin chains or bus routing through it. Print or commit anything that must be heard, and recreate routing in Live.
Neutral clips convert perfectly. Truly stretched clips are flagged before conversion so you can commit them in Pro Tools first — AAF Bridge never renders the stretch behind your back.
The free demo is the full app — it converts the first 120 seconds of any timeline, so you can open the result in Live before spending anything. $49 one-time, no subscription, runs offline. macOS.
Download the free demo Back to the overview