The AAF exported without an error, and the receiving app — Ableton Live, Pro Tools, whichever — shows offline clips, silence, or a timeline with holes in it. There are three usual causes, and they look almost identical.
Linked media that stayed behind. Resolve can write an AAF that references audio files instead of containing them. Move the AAF without its media folder and every clip goes offline — in any application, not just yours.
MXF wrapping. Resolve normally wraps exported audio in MXF. Pro Tools and Media Composer handle it; a lot of other software — Ableton Live included — cannot read MXF at all, so the timeline arrives complete but silent.
Retimed clips. Clips with a speed change applied are a known source of blank or partial AAF exports out of Resolve. The export itself reports success; the clip is simply not in it.
A one-hour reel exported embedded is large — hundreds of MB upwards. If your AAF is a few hundred KB, it’s linked, and the audio lives in a folder that has to travel with it.
If you see .mxf files, the audio is MXF-wrapped. That’s normal for Resolve — but it decides which applications can use this export directly.
On the Deliver page, use the Pro Tools preset rather than File → Export → AAF. It produces the most widely compatible AAF, and lets you choose embedded audio — one self-contained deliverable instead of a file plus a folder.
Any clip with a retime applied should be rendered or replaced before the export. This is the cause behind most “the export worked but that one clip is missing” reports.
Accented or special characters in clip and timeline names have been known to break AAF exports. Plain ASCII names cost nothing and remove the variable.
Import the AAF back into a fresh Resolve timeline, or open it in a tool that reports what it found. A converter that lists tracks, clips, markers and offline media before converting tells you in seconds whether the export is complete.
Once the export is sound, the remaining question is what the receiving application can read.
One honest limit that comes from Resolve itself: it doesn’t write pan or volume automation into its AAF exports. That data never leaves Resolve, so no tool downstream can recover it.
Use the Deliver page with the Pro Tools preset for anything leaving the building. It gives you control over embedded versus linked audio and produces the most compatible file.
Embedded if it’s going to someone else — one file, nothing to lose in transit. Linked is fine inside a facility where everyone sees the same storage.
Not if your target reads MXF (Pro Tools, Media Composer, Nuendo do). For Ableton Live you do — either by exporting WAVs from Resolve, or by using a converter that unwraps the MXF as part of the import.
Because Resolve doesn’t write pan or volume automation into AAF at all. It’s a limitation of Resolve’s export, not of the format or the receiving app — the data never leaves Resolve.
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