AAF back and foward - Premiere Pro

[matiaslaney]

Hi colleagues, I've been struggling a lot working with video editors exporting OMF and AAF files from Pro Tools to Premiere. I'm trying to export an AAF file for them to open on Premiere Pro and keep the same filenames. The AAF does not embed the audio files unless Pro Tools changes the name of every file to some random sequence of characters. I need the files to keep their original name. Is there a way to export a Pro Tools session for Premiere to open the audio files as an OMF or AAF should do?
Thank you

[Reckless Erik]

Quite simply no! Going from Premiere to ProTools is hard enough. Virtually impossible to go the other way using the AAF/OMF work flow. Better to send time stamped .WAV files for the editor to drag onto his timeline.

[trevora]

Unlikely to work straight away (even AAF PT->MC can be problematic). Might work via Resolve? (IE open AAF in Resolve and export an XML).

Reach out to Adobe for guidance? It's a bit niche but it would be useful at times to get AAF back from ProTools

[@tention]

It's a nightmare and it's not PT's fault.

Today we have tried to find why PT, Nuendo and EdiLoad will just see void instead of audio files in the timeline in AAFs we received at some point...until we tried to reopen the Premiere AAF....with Premiere. Guess what, even Premiere was incompatible to it's own AAF. In other words: it's buggy.

[trevora]

The 'void' is likely to be badly formed multicam sequences in Premiere Pro. They sound ok in the timeline but, in the process of making the AAF they are 'flattened' to constituent clips - which can result in incorrect clips or no clips, when the multicam hasn't been made correctly.

Picture editor can check in their timeline by flattening before creating AAF.

Exporting an OMF is one workaround.