Skip to main content
N
Nitram56
Participant
November 23, 2017
Answered

Unable to export AAF - Error "AAFRESULT_INSUFF_TRAN_MATERIAL"

  • November 23, 2017
  • 11 replies
  • 21238 views

Hi All,

I've been trying for days to export an AAF for our audio studio but for some reason I'm not able to.

I get 2 kinds of errors while exporting. The first few errors say:

Cannot export video effect "AE.ADBE Text" (Sequence: <name>, Video Track: "Video 1 (#25), Position 26741, Time: 00;14;52;07) because it is not supported. Effect was ignored.

I get a few of these error messages with different timecodes but when I go to each timecode to check in the timeline there are no effects applied to the video layer at all so I have no idea what effect it is referring to and then right after that, the export fails saying "AAFRESULT_INSUFF_TRAN_MATERIAL"

My next idea was to delete all video and just place a layer of black video on Track 1. This got rid of the "AE.ADBE Text" errors but I still get the "AARESULT_INSUF_TRAN_MATERIAL" error and the export fails.

I then tried to get rid of all effects and cross fades in the audio clips and this time the file finished exporting but when our guy at the audio studio opens it up the audio is all messed up. He says there are multiple layers of dialogue happening at once almost as if two different sequences are being exported at the same time on top of each other, which makes no sense because I only have one sequence in my project.

I've also tried deleting caches, preferences, reinstalling, etc. My last attempt was to switch to a different computer to see if that was the issue but I'm still not able to export the AAF successfully.

I'm not sure what else to try since I'm not too familiar with AAF files and I'm desperate now since I've got a deadline looming. I'm hoping someone can suggest something that I haven't thought of.

Thanks in advance for any help!

This topic has been closed for replies.
Correct answer Nitram56

I managed to find a workaround so I'm posting an update hoping to help the next person with this issue.

I had been working with the Premiere 2018 version so I decided to try going back to the 2017 version and the AAF exported no problem so there's definitely something wonky going on with the newest version of Premiere.

In order to get around the whole "you-can't-open-a-newer-version-project-in-an-older-version-of-premiere" deal I exported an XML out of my 2018 project and then imported it into the 2017 version. Worked great!

11 replies

Miguel437
Miguel437
Participant
December 23, 2018

Similar issue. Not sure why. Using version 13.0.2 (Build 3B) @Adobe please help. A feature we are trying to send off to ProTools.

@

    ProwlaMan
    ProwlaMan
    Participant
    December 23, 2018

    I was getting this error in my version 12.1.1 and I figured out this workaround.

    (Duplicate your sequence just to have a backup copy). In the sequence, delete all your video and export to AAF. Press undo to get you video back. The AAF file should now open in your DAW. However, I'm not seeing my volume changes in my DAW but that's not a huge problem with me.

    D
    Adobe Employee
    devinstone
    Adobe Employee
    May 18, 2018

    Hi all. Has anyone tried this in Premiere 12.1? I believe it has been fixed, but please let us know if anyone is still seeing this error.

    J
    jpdirector
    Known Participant
    May 18, 2018

    I have heard from one person, Colin Smith who is a well known Premiere expert, that his friend said the update has fixed the AAF issue. But, I heard directly from an editor I work with that it didn't fix it for him. I have called this in days ago and still have not received my call back even though my case has been "elevated" and a Sr. Tech promised to call back. They have not.

    I would be willing to try the update of 12.1.1 if I could go into "advanced settings" and uncheck "remove old versions" just in case, as doing an update of this nature with a feature film that has the edit locked is too risky, (other changes in the update will damage our project). Do you know if I can do the update without loosing my old 2018 version that I used to do the edit?

    Bottom line is hearing things like "I believe" "should" when it comes to a fix like this is too unsettling as an answer.

    I will just add that any professional editor who has a feature heading for theaters, or netflix, or Amazon for that matter will have to export an AAF for final sound design, so someone has to know the answer. As we can see from this thread alone the problem has existed for a long time.

    Thank you. If you could advise us what to do we would be so grateful.

    D
    Adobe Employee
    devinstone
    Adobe Employee
    May 18, 2018

    Colin forwarded your email to us. I'll reach out directly.

    Just to clarify, when I say "believe" and "should", it's because I'm not sure whether the issue we fixed is the same one you are experiencing. The same AAF transition error could theoretically be displayed for many different reasons. I am sure that we fixed one issue that caused this error to be displayed which was affecting several customers. Hopefully yours is the same one.

    J
    jpdirector
    Known Participant
    May 15, 2018

    I am having the same problem. I am in the final phases of a feature film that was shot on a RED in 8K. The file sizes are huge, the project has over 15TB of media, obviously the edit is complex, so any "work around" is not acceptable at this point. Every major project in the industry has to go into Pro Tools or the like for final sound design and mix. Adobe please help? The film is hanging in the balance.

    D
    daniela29930487
    Participant
    March 5, 2018

    Hey Adobe! Please fix this!!! IT'S BEEN OVER 3 MONTHS!!! We have to kick out 22 episodes with 100 audio tracks!!!!

      Zesty_Wonderland154A
      Zesty_Wonderland154A
      Participating Frequently
      March 9, 2018

      Same here. We are about to lose the job if there is no fix!!

      alanp47544855
      alanp47544855
      Participant
      May 18, 2022

      Did you ever figure a solution to this?

      florianlippke.tv
      florianlippke.tv
      Participant
      March 1, 2018

      I'm having the same problem! Always new versions with major bugs! In a professional workaround is this an absolute "no go"!

      robertstonefilm
      robertstonefilm
      Known Participant
      February 8, 2018

      I'm having the same problem. Finding a way to revert to 2017 is not an acceptable solution. Adobe must fix this!  Please everyone submit a bug report:

      A
      awaterslideaway
      Participant
      January 17, 2018

      NO. This is not okay. PLEASE FIX adobe. Slowing down professional workflow on seven figure feature film!

      miciad91746869
      miciad91746869
      Participant
      January 11, 2018

      Hi

      I tried this, and the xml export worked, but now the entire audio file for the AAF export is in one clip and the different channels aren't being picked up. Any way around this?

      K
      keitht67126583
      Participant
      December 4, 2017

      Hi

      I'm getting this error now

      AAFRESULT_INSUFF_TRAN_MATERIAL

      how would I revert to an earlier version as you did. I found some instructions

      Install a previous version of any Creative Cloud application

      but there does not seem to be a "Find Additional Apps section" in the creative cloud.

      Will try OMF and get back to you with result.

      N
      Nitram56Author
      Participant
      December 6, 2017

      Hi Keith,

      In the Creative Cloud manager app, under the Apps tab. Click on the drop down arrow next to Premiere and choose "Other Versions." There you will be able to choose an older version of Premiere.

      K
      keitht67126583
      Participant
      December 7, 2017

      Thanks for that, I got the previous version which worked ok. Maybe someone from Adobe might check this and say when it’s ok to upgrade.

      P
      pallavis
      Participant
      December 1, 2017

      I too faced the similar issue! AAFRESULT_ADJACENT_TRAN (project conversion error). However this error occurred only with one version of my edit, the other versions of the same edit were exported successfully. So the clips and transition effects were almost same on all versions. Then why did this error occurred only with one particular version, is beyond my comprehension. Secondly, when the sound guy (using pro tools) tried importing the AAF, few of the tracks out of 10 were not in synch. We were clueless!!! Finally we had to export omf. Definitely there is something which needs to be tackled by adobe. I hope they are reading this.

      I am using adobe premiere pro 2018. iMac 27" 5k retina display 3.3 ghz intel i5, 16gb ram 1600 MHz DDR3, Macintosh HD 10.8.5,

      AMD Radeon R9 M290 2048 MB

      Adobe, kindly reply!

        robertstonefilm
        robertstonefilm
        Known Participant
        February 1, 2018

        I'm having the exact same problem. Premier 2018 is so full of bugs it's basically a Beta version sent out as a finished product. This one is incredibly annoying.  PLEASE FIX THIS ADOBE!!!

        Show more replies
        Terms & ConditionsAccessibility statement
        Using the community Terms of use Privacy Cookie preferences Do not sell or share my personal information ad choicesAdChoices