I see that this is a common problem and no one gets to any conclusions...
In short: Latest AE, latest AME, windows 10
Simple composition created in AE -> Add to AME queue. -> AME opens and hangs while displaying Reading XMP
Is there a solution for this?
We're sorry to hear that you are getting issues while exporting an After Effects project from AME via dynamic link. A few more details would be super helpful to troubleshoot the issue better.
Reinstall applications??Is that your advise? Will you pay me to do that?
Anyway, After effects 2020: It takes cca 20min to start to render, any sugestion? Come on Adobe, Im loosing my patience with you. EVERY update is problem!
Did you ever find a solution robert_s? I am having the same issue with the latest Adobe Media Encoder.
After Effects - Preferences - Media Disk Cache
What options do you have checked under XMP Metadata?
Media Encoder - Preferences - Metadata
What options are checked there?
I actually do not use After Effects and have the issue with Premiere Pro and Media Encoder.
The issue persisted after reinstalling (inclusive deleting settings).
It's present when I export H.265 and H.264.
My settings in Media Encoder - Preferences - Metadata:
Hey Chris!! I'm having the same problem as you on the same versions, buddy. I found that AME 14.1 gives me the XMP error, so I just downgraded to 14.0 and my problem was solved. Hopefully this can help you out while Adobe figures out their ish lol
What's your Win10 build number?
Workaround for this problem is to delete your sequence markers.
- Sequence Markers are not (my) problem.
- The version difference between 14.0.0 or 14.0.1 doesn't matter.
- Apparently it is just any custom plugin, I also noticed it with the AconDigital DeVerberate
- This does seem to affect all AU, VST, and VST3 plugins 🙈.
- Workaround for me: remove Loudness Meter before exporting with Media Encoder.
- Exporting with Premiere Pro itself does work no matter what.
Now, the long version:
I tested to remove my sequence markers and it didn't help with Media Encoder 14.0 (it goes further than the "Reading XMP" but still does not render fully).
Testing with 14.0.1 and a new project file it did export without markers (no markers, no effects, just a video file). I also tested it with an adjustment layer and some Lumetry settings and it still exported.
I tried adding markers to this new project file and it still exported.
Exporting stopped working with dpMeter4 and Youlean Loudness Meter 2 on any Channel (does not matter if it's on the master, submix channel - even if nothing is routed through the submix, or the audio channel itself). Even when the effect is 'disabled' it does not export. It only starts working again when I remove the effect from the audio mixer.
Interestingly, it all works perfectly when not using Media Encoder and just export directly inside Premiere Pro.
It also works with no issues if I remove both of these from the audio mixer.
I have messaged the developer of the Youlean plugin with the link to this topic and we'll see if it's something Adobe or the plugin developers can fix.
Current workaround: remove the Loudness Meter from the audio mixer and export.
Let's hope it's fixable either by Adobe or Youlean.
Cheers and have a great day,
Please start a new post regarding 3rd party plugin problem.
Also try updating Youlean Loudness 2 to version 2.3.2
We could not repro your this problem with that build.
I am using 2.3.2 of Youlean Loudness Meter 2.
I have created a new topic about custom VS3 plugins not working when exporting with AME:
Hope we can find the issue there, it's not just Youlean, it's also Fabfilter Audio Plugins, and dpMeter 4.
I tried many things. I hope an update will fix this.
Can confirm. Deleted all markers and it (almost) worked. Removed my Fab Filter plugins and then it exported from AME fine. What a headache, this has been plaguing me all year.
It was sequence markers for me. Thought I was alone in this. Thanks for confirming my suspicions that this was a known bug.
Thank god I found this thread!...was having same issues as others. Deleted the sequence markers and everything is working again. Thanks Adobe for making everyonre crazy....again
Can someone help I'm trying to export my video once I get to the Adobe Media Encoder I'm getting this Processing: Reading MXP...
How do I get pass this please
I found a solution: use another video editing program.
Until Adobe stops added the suffix of the year to every application (Premiere 2020, etc), this kind of problem will be constant. They roll out a new version in January; initial bugs until March; constant bugs through August. Bugs fixed in October. Holidays for two months. New bugs with the next version. That's 1 month out of 12 with expected functionality. Of course this isn't just Adobe, Apple also has this issue. What we've learned is there's no amount of money in the world for a software company to release a stable product within a calendar year.
I'm having the excact same issue! Trying to export a five minute timeline now, and it simply does not work!!! It worked perfectly in Premiere 2019 on the same project.
I've tried to use "export" in Premiere itself, and also as queue, neither work.
The solution was to use DaVinci resolve instead. Sorry, Adobe. 😞
After hours and hours of frustration, it finally worked. The solution was to remove ALL markers from the metadata and timeline. WHY Adobe, WHYYY???
Thank you. I found a solution right before you commented, and it was to remove the markers. However, I do need the markers on the export, but i'll add them in DaVinci instead for now.
Hope to see a fix from Adobe soon..
Please look at this post for how to resolve this issue and continue to use markers:
New markers created in PPRO 14.0.1 will work just fine.
There is also a way to update your existing markers by removing the guid_id which will fix the problem as well.
Also, the fix will be released soon...
Great to hear! 🙂
The fix will be in place soon? Neat... What's the definition of soon? 😄 Seriously - fix this... what's the point if you cannot export your hard work?
I had the same problem, which is fixed by removing all sound effects from the Essential Sound panel. Wasvery happy when I discovered it, but looks like it's quite buggy. Adobe? Whatchagonnadoaboutit?