At a glance: An AAF that imports into Pro Tools with named clips and no audio has one of four causes: the media was referenced rather than embedded and did not survive the journey, the file carries multichannel references Pro Tools refuses, the AAF and the Pro Tools version disagree, or the file itself is empty or damaged. All four are decided on the export side, all four are fixed by a re-export with one changed setting, and each leaves a different fingerprint, so a minute of diagnosis tells you exactly which re-export to ask for. This guide identifies each cause by its symptom, gives the fix, and covers the export habits that prevent all four.
The blocks are on the timeline. The names are right, the lengths are right, and nothing plays.
If you are the editor who exported the file, this is the complaint that comes back, and it is worth knowing that the diagnosis is fast and the fault is almost never in your edit. It is in one export setting, and which setting depends on which of four fingerprints the silent session shows. Getting the fingerprint identified before anyone re-exports is the difference between one round trip and three.
| Fingerprint on the Pro Tools side | Cause | The re-export to ask for |
|---|---|---|
| Clips present, marked Media Offline | Referenced media that moved or never travelled | Embedded audio, or copy complete files |
| Import refuses with the multichannel error | Multichannel audio references in the file | Breakout to Mono enabled |
| Import fails on a file from a newer NLE | Version mismatch between export and Pro Tools | Compatibility option enabled in the export |
| Import refuses, says nothing can be imported | Empty or damaged file | Fresh export, transitions removed first |
Case One: The Media Never Made the Trip
An AAF can carry its audio inside itself or point at files stored elsewhere. Referenced exports work only if every referenced file arrives alongside the AAF and sits where the AAF expects it. A renamed folder, a drive mounted under a different path, or a delivery that included the AAF and nothing else, and Pro Tools reads the structure perfectly and finds silence behind it.
The fingerprint is the gentlest of the four: the session opens, the clips are there, and they read Media Offline. The tell on your side is file size, visible before you ever send: a referenced AAF weighs a few megabytes while an embedded one weighs roughly what its audio weighs. The fix is embedding, or in Premiere's terms copying complete audio files, and Production Expert's guide to Pro Tools friendly AAFs adds that copying complete files is also the setting that preserves metadata flow, checked September 2026.
One nuance stops a false alarm: an embedded AAF that will not reimport into Premiere itself is not broken. Premiere cannot reopen its own embedded AAF exports, as an Adobe Community thread documents, checked September 2026, while the same file opens fine in Pro Tools. Test deliveries in the destination, not the origin.
Case Two: Pro Tools Refuses Multichannel References
This one announces itself with an error string rather than silence: "Pro Tools does not support import of AAF/OMF references to multi-channel audio files." The cause is almost always a Premiere export where stereo content left as interleaved multichannel references, which Pro Tools declines to read.
The fix is one checkbox: Breakout to Mono in Premiere's AAF export, which writes each channel as its own mono file. Sound editor April Tucker's reference on Premiere AAF issues, which documents this error and its fix, has been the standard citation since 2018, checked September 2026; note that her testing dates from that era and newer Pro Tools versions have improved multichannel handling, so the error is less universal than it was without being gone. The wider stereo story, including what split mono pairs do to a session even when the import succeeds, is in our Premiere export guide.
Case Three: The Export and Pro Tools Disagree About the Format
A file from a current Media Composer can fail to link its audio in an older Pro Tools, with the clips present and named and the audio unlinkable, which is exactly the symptom in a long running Gearspace thread on AAF imports that stopped working, checked September 2026. The reports there, secondhand from Avid support, put the floor for modern Media Composer AAFs at newer Pro Tools builds, and the practical remedy on the export side is Media Composer's Pro Tools compatibility option, which writes the older, more widely readable variant.
The fingerprint that separates this from case one: the media did travel, the file is big, and it still will not link. When the receiving side is on an older system, the compatibility flag is a thirty second courtesy that costs nothing when it is not needed.
Case Four: There Is Nothing in the File to Import
The bluntest fingerprint is the refusal our import guide covers in detail: the dialog that says the file does not contain data that can be imported. Pro Tools opened the AAF and found nothing usable inside. The usual causes are audio transitions that failed to translate and took the export down with them, or a render that stopped partway.
The tell on your side is again size, at the extreme end: a DaVinci Resolve export error can produce an AAF of just 76 bytes, a figure documented in Production Expert's Resolve export guide, checked September 2026, and a failed export in the tens of kilobytes is the same story. Resolve deserves its own sentence here, because Production Expert calls it the hardest NLE to extract a Pro Tools friendly AAF from, checked September 2026, and its audio settings live in unexpected places on the Deliver page; our Resolve export guide walks the working path. The fix for a dead file is always the same: strip the audio transitions, re-export fresh, and if the NLE offers two AAF presets, try the other one.
Preventing All Four in One Pass
Every cause above is visible before the file leaves your machine, which is the actual point of this article.
The file size catches cases one and four in five seconds. The two export settings, embedding and Breakout to Mono, close cases one and two permanently once they are in your preset. The compatibility flag closes case three whenever the receiving side runs older software, which is a one line question in the delivery thread. And a validator closes the residual doubt: the free AAF Checker reads the file and reports whether its media is present and readable and whether the structure is intact, before Pro Tools tests the same things for real. The two minute pre-send check puts all of this in order, and the full delivery specification covers everything beyond it.
On the receiving side, the same class of failure gets closed structurally rather than per delivery: fPost copies media into the session it builds and preserves a backup of the original AAF, so a session it prepares is self contained rather than pointing at files that might move. What no tool on either side can do is put audio into a file that was exported without it, which is why the five second size check remains the highest value habit in this entire article.
The diagnostic from the mixer's chair, covering these failures and the ones beyond them, is in our guide to why an AAF will not import cleanly.
Frequently Asked Questions
Why does my AAF import into Pro Tools with no sound?
Four causes: the media was referenced rather than embedded and did not travel, the file carries multichannel references Pro Tools refuses, the AAF format and the Pro Tools version disagree, or the file is empty or damaged. Each leaves a different fingerprint, and the fingerprint tells you which single setting to change on re-export.
What does Media Offline mean on an imported AAF?
Pro Tools read the timeline structure but cannot find the audio the clips point to, which means the AAF referenced external files that moved or were never delivered. The permanent fix is exporting with embedded audio, so the file carries its own media.
Why is Pro Tools saying it cannot import multichannel audio files?
The AAF, usually from Premiere, contains interleaved multichannel references. Re-export with Breakout to Mono enabled so each channel arrives as its own mono file, and the import proceeds normally.
Can the audio team fix a silent AAF on their side?
Only sometimes. Referenced media can be relinked if the files exist somewhere in the delivery, and a version mismatch can occasionally be worked around. Multichannel refusals and empty files can only be fixed by a re-export, which is why identifying the case first saves the pointless round trips.
How do I know before sending whether my AAF has its audio inside?
Check the file size. An embedded AAF weighs roughly what its audio weighs; a referenced or failed one is a few megabytes or less. A free validator like the AAF Checker then confirms the media is present and readable in about thirty seconds.
Does this happen with every NLE?
The causes differ by application. Premiere accounts for most multichannel refusals and split stereo, DaVinci Resolve is the least consistent AAF exporter and the usual source of empty files, Media Composer is the most reliable but carries the version mismatch case, and Final Cut Pro goes through a bridge tool with its own settings.
fPost turns an AAF into an organised Pro Tools session, copying media in and keeping a backup of the original so the session it builds is self contained. Details at forte-ai.com/fpost.
