Error when exporting to AME from Premiere

[Scott_at_RLA]

Everytime I export from Premiere to Media Encoder  i get this:

[/Pr12.1/releases/2018.02/shared/adobe/MediaCore/Backend/Src/Content/AudioMediaContent.cpp-570]

what gives?

[Vidya Sagar]

Hi Scott at RLA,

Sorry for the issue. Please check if both the applications are updated to the same version or not.

Here are the steps: FAQ: How to find the exact version of Premiere Pro you're using?

There is a new update for Premiere Pro & Media Encoder 12.1.1. Update the apps & let us know the issue persists.

Thanks,

Vidya

[Emanuel Constantin]

Exporting to AME worked fine a couple of hours ago. Suddenly the same issue arose. Both Premiere and Encoder are 12.1.0

Unforatunately I'm in the middle of a project, I can't take the risk of updating my software.

Is there a way to workaround?

(has it something to do with audio?)

[R Neil Haugen]

One thing to quick try ... in AME, Edit/Preferences, un-check "import sequences natviely" ... no clue what that does, but un-checking it solves a ton of odd issues.

Neil

[Emanuel Constantin]

Thanks for the tip. Unfortunately this does not solve the issue.

I have now also update both premiere and AME to the latest versions, but the issue persists.

[Carlos Ziade]

clean media cache and project previews of both, there might be something stuck

try if this helps and let us know please

[Emanuel Constantin · Accepted solution]

Thanks for the tip.
It did not solve the issue.

But I now assume it has something to with dynamic link to after effects. The timeline consisted almost exclusively of linked AE files.

I have now exported all linked clips natively in AE and replaced them in premiere - now the export to AME works fine again.

(plus other projects I tested worked fine too).

I guess it was something with this specific project related to the AE-link.

All good again 😃

[Vidya Sagar]

Hi manuel Büchler,

As you mentioned, it is an issue with AE files. There is a known issue with Dynamic Link between Premiere Pro & After Effects.

Engineering is working on a fix. Hopefully, it will get fixed in the next update.

Thanks,

Vidya