You have an AAF from an editor, and Live simply won’t take it. Before you hunt for a setting: there isn’t one.
File → Open won’t list the file, drag-and-drop does nothing, and no preference or plug-in enables it. So a failed import usually means nothing is wrong with your AAF — it means Live can’t read that format at all. Below: how to confirm your file is sound, the free routes, and the direct one.AAF (Advanced Authoring Format) is the interchange format audio post runs on: DaVinci Resolve, Pro Tools, Media Composer, Nuendo and Premiere Pro all write it. Ableton Live is the one seat in that chain that never learned to read it — there is no import, no export, no hidden preference, and no plug-in that can add it, because Live has no API for opening session formats from the inside.
That means the usual debugging instinct — re-export, try another
setting, update Live — can’t work. The file has to be
converted outside Live into something Live does read: an
.als Live Set.
An AAF comes in two shapes. Embedded: one large file (often hundreds of MB or several GB) that contains the audio. Linked: a small file (a few hundred KB) that points at a media folder sitting next to it. If you got a small AAF on its own, the audio was never included — ask for the media, or for an embedded export.
There is no AAF entry under File, no Pack, no plug-in. This is worth stating plainly because a lot of time gets lost here: Live 10, 11 and 12 all behave the same way.
Resolve and Avid usually wrap audio in MXF. Live can’t read MXF either — not inside an AAF and not as loose files. If you see .mxf next to the AAF, that’s a second wall behind the first one.
Open the AAF in whatever app is at hand — Resolve imports AAF, and so does Pro Tools. If it opens there with audio, the file is fine and Live is the limitation. If it’s empty there too, ask the editor to re-export (in Resolve, clips with speed changes are a common cause of blank exports).
Since Live can’t read the format, the file has to become an .als before Live ever sees it — see below. The free demo converts the first 120 seconds of any timeline, so you can confirm the result on your own file first.
AAF Bridge reads the AAF outside
Live and writes a real .als project: clips sample-accurate at
their timeline positions, fades and crossfades, clip gain, markers as
locators, the picture cut on its own muted video track — and any
MXF-wrapped audio converted to WAV on the way, with nothing to install.
Every conversion also writes a plain-text report next to the project, listing what transferred and what the format couldn’t carry: AAF is audio-only, so MIDI, plugins and bus routing never travel, and time-stretched clips are flagged for consolidation rather than silently rendered.
It works in both directions — when the session is finished, the Live Set is written back out as AAF or XML for the picture edit, so the hand-off closes the same way it opened.
No. Live has no API for opening session formats from inside the application, so no Max for Live device or plug-in can add AAF import. The conversion has to happen outside Live, producing an .als that Live then opens normally.
No — that’s the expected result. Pro Tools, Resolve, Media Composer and Nuendo all read AAF; Live doesn’t. A file that opens elsewhere is a healthy file.
No. An AAF isn’t audio — it’s a structured container describing a timeline, with the audio embedded or referenced inside it. Renaming it produces a file no application can play.
The AAF was the linked kind and its media didn’t travel with it. Get the media folder from the editor and keep it next to the AAF, ask for an embedded export instead, or convert with Collect media enabled so a self-contained project folder is written.
The free demo is the full app — it converts the first 120 seconds of any timeline, so you can check the result before spending anything. $49 one-time, no subscription, runs offline. macOS & Windows.
Download the free demo Back to the overview