The AAF came from Resolve, Avid or Pro Tools, and Premiere greets it with an error or an empty sequence. There is a reason for that — and a clean way around it.
File → Import. It arrives as a native sequence with its tracks, transitions, constant clip gain and markers.Premiere Pro can write an AAF — that is its sample-accurate way out to audio post. Reading one that another application wrote is a different story: AAF is a large specification and every vendor writes its own dialect of it. Premiere accepts a narrow subset, and an AAF from Resolve, Avid or Pro Tools often lands outside it. The result is an import error, or a sequence with clips stacked at 00:00:00:00.
The format Premiere reads dependably is XML — the Final Cut 7 dialect it has supported for years. So the route in is AAF out, XML in.
File → Export → AAF) — that is its
sample-accurate route to audio post. XML is the way into
Premiere, not out of it.Drop the .aaf in, or click Choose. Several reels at once is fine — they convert as one batch.
.xml and the sequence frame rateUnder Output pick .xml — Premiere Pro. Set the frame rate to the one the cut was made at: unlike AAF and FCPXML, Premiere’s XML counts in frames, so this is the grid everything lands on.
Collect next to output is the safer choice when the AAF came from another machine: the XML and every referenced file end up in one folder. MXF audio — typical for Resolve and Avid deliveries — becomes WAV automatically.
Convert, and read the report that lands next to the output — it names anything the XML format could not take with it.
File → Import and select the .xml. The timeline appears as a native sequence in the project panel — not as a nested mystery clip.
Where Premiere XML stops: it is frame-quantised, because the format itself counts in frames — the only one of the four that does. And moving volume automation is left out rather than averaged into an invented level; constant clip gain travels, a rising curve does not. If the automation has to survive, convert to FCPXML or keep the AAF for audio post.
Usually not. It is far more often a dialect Premiere does not accept. The same file normally converts without complaint — try the demo on it.
That is the other common symptom of a dialect mismatch: the structure was read, the positions were not. The XML route avoids it.
AAF. File → Export → AAF is Premiere’s sample-accurate way out for audio. XML is the way in.
Yes, the picture tracks travel with the cut, including several layers.
The demo is the complete app with unlimited conversions — each output covers the first 120 seconds with the full track layout. If your file converts the way you need, buy a license.
Download the free demo Buy — $79