Creative Communities of the World Forums

The peer to peer support community for media production professionals.

Activity Forums Adobe Premiere Pro AAF from Premiere Pro to Logic Pro X

  • AAF from Premiere Pro to Logic Pro X

    Posted by Oliver Peters on August 18, 2015 at 11:57 pm

    I sent audio to the mixer today from Premiere Pro CC 2015. He’s using Logic Pro X. I first tried an OMF and Logic couldn’t open any of the embedded audio files. AAF was fine, but we encountered a shift at every point where I’d placed an audio dissolve.

    When I edit dialogue in PProCC, I place short audio dissolves across the cuts. In Logic, these dissolves were gone and gaps were left. However, the full media clips was there. This resulted in the dialogue going further out of sync at each new clip.

    When I deleted all audio dissolves from the Premiere Pro timeline and exported a new AAF, everything was fine in Logic.

    I don’t know if this is an issue with other DAWs like ProTools or if it’s specific to Logic. IOW, it could be a Premiere AAF-creation problem or it could be how Logic interprets that AAF.

    – Oliver

    Oliver Peters Post Production Services, LLC
    Orlando, FL

    Kris Strobeck replied 6 months, 2 weeks ago 3 Members · 2 Replies
  • 2 Replies
  • Olivier Aubut

    August 19, 2015 at 4:32 pm

    I’m seeing the exact same problems. AAF from Premiere to Pro-Tools shifts certain clips with cross-dissolves.

    We ended up sending sequence to Audition (right-click in project window). Then in Audition, exporting an OMF. There are still issues where the volume goes way up at the beginning of certain clips (mostly music but some dialogue) then follows the keyframes correctly.

    I really wonder why this hasn’t been fixed even with third party applications (like the late automatic duck for fcp7). This is a major slow-down for our workflow.


  • Kris Strobeck

    September 27, 2023 at 8:47 pm

    Hey all. Just wanted to post this solution. An AAF from Premiere Pro to Logic Pro X is working well for me. There are a few things to note. If you have clip volume levels, they will translate (but there are caveats)! They don’t come to Logic Pro X as clip gain but as automation in the track. Awesome!

    You’ll probably need to show the automation and then select “volume” since it may default to “display off”. You should then see levels. If there are no level changes on clips in a given track in premiere, the automation in Logic Pro X should be at 0db.

    If you have any audio clips with automation in a track, as I said, those should come across. But… if you have additional clips later in the timeline without any changes, you will not see the automation go back to zero unless you add at least one keyframe on the clip in premiere. Then it will change the automation back to zero. You may need to do this to any clips that don’t have any automation change.

    In the second paragraph, I say “probably” and “maybe” because I found a great workaround for a project with a lot of tracks to have the volume automation display come across set to on. So, it’s a weird bug, but if you add a keyframe to a clip after clips with automation in a given track, voila, when you import the AAF into logic and toggle on the automation view, ALL tracks should be already set to volume and display automation changes.

    Please feel free to ask questions. I just figured these couple of things out today and was so happy to see that editor audio clip levels can come across and I can work from there. I also have any audio effects coming across burned into the audio with the same audio un-affected as well. See “Render audio clip effects” and “Include clip copies without effects” here:

We use anonymous cookies to give you the best experience we can.
Our Privacy policy | GDPR Policy