How to hand a Premiere Pro edit to Avid Media Composer as AAF

An Avid Media Composer editor cannot open a Premiere Pro project. The handoff format between them is AAF, and the usual way to get one is to open the project in Premiere and export it. When Premiere is not installed, the licence has lapsed, or the .prproj is newer than the copy you have, the alternative is to convert the .prproj to a picture/audio AAF directly. The converter reads the project file itself, writes an AAF that references your original media, and tells you which parts of the edit did not make the trip. This guide is the route, what an AAF carries, and what to check on import.

What an AAF is, and what this one contains

AAF (Advanced Authoring Format) is the interchange container Avid reads natively. It describes a sequence: tracks, clips, source in and out points, and references to media. The AAF written here is external-reference: it points at your media files by path and embeds nothing, so the file stays small and your footage stays where it is. There is no rendered picture or audio inside it.

The route: .prproj to AAF without Premiere

1. Drop the .prproj on the Premiere to AAF converter. Use the saved project file, no export needed. It is read in your browser and nothing is uploaded. You see each sequence with its tracks and clips before anything is written.
2. Choose the sequence to transfer and press Convert. The converter writes one AAF per sequence and a conversion report.
3. Read the report. Every omitted clip and every piece of processing it could not carry is listed by name. This is the part to keep next to you at the Avid.
4. Import in Media Composer. Import the AAF into a bin, then relink to the original media. Compare the edit against the report before cutting further.

A project above the free cap is $7 and converts to any format for 24 hours, or is covered by Pro ($9/month or $39/year, files up to 50 MB) and Studio ($19/month or $79/year, files up to 500 MB).

What carries over

Carried: normal-speed picture cuts at the sequence frame rate, with their placement and source trims; sources at a different frame rate from the sequence; standard constant-speed changes in the positive direction; static rectangular crops; supported audio edits with clip gain, independent gain envelopes and the source channels the clip used; sequence markers; clip names and media paths.

Written with a change: constant gain steps become separate audio clip sections rather than automation points. Visible picture and audio nests are flattened into ordinary media clips, so the nest's identity is gone but its contents cut correctly.

Not carried, and warned about: curved, reverse and variable speed changes, retimes beyond the constant positive case, mixed-rate picture that the AAF cannot express, and proprietary effects, colour, titles and mattes. Track automation, mute and solo states, and linear fades are qualified in the report: check them on import rather than assuming either way.

The same edit into Resolve is a different handoff with a different set of carried features. It is described in the Premiere to Resolve handoff, and every route is listed pair by pair in the capability table.

Where this stands with Media Composer

Plainly: this AAF has been imported and checked in DaVinci Resolve, which reads AAF. Native acceptance in Avid Media Composer has not been established. The file follows the AAF structure Avid documents, but until a real Media Composer import has been verified, treat the first import as a test: import into a scratch bin, relink, and step through the cuts against the report before you rely on it. If Media Composer rejects the file or drops something the report said was carried, the about page is the place to send it.

FAQ

How do I get a Premiere project into Avid Media Composer without Premiere? Convert the .prproj file directly to a picture/audio AAF, import the AAF into a Media Composer bin and relink to the original media. The converter reads the project file, so Premiere does not need to be installed.

Is media embedded in the AAF? No. The AAF references your original media files by path. Your project and footage stay on your computer, and the AAF is small enough to send alongside them.

Is this full Avid compatibility? No. Native Media Composer acceptance has not been established. It is a limited picture and audio interchange with explicit conversion warnings; import into a scratch bin first and check the edit against the report.

What happens to nested sequences, speed changes and effects? Visible nests are flattened into ordinary clips. Constant positive speed changes carry; curved, reverse and variable ones are warned and need rebuilding. Effects, colour, titles and mattes are not converted and are listed in the report by name.

Can I check the AAF before Avid? Yes. DaVinci Resolve imports AAF, and the converter's output has been tested there. Importing into free Resolve is a quick way to see the cuts land before the file reaches the Avid.