Media Encoder Fails more often than Renders

[Juniperf]

Unsure if this is a shared experience beyond me and some colleagues, but we've noticed that Media Encoder has been steadily failing more often than it succeeds in any job (whether Dynamic Link or not).

After Effects & Premeire can render such projects just fine, but the one advantage to Media Encoder is that you can continue working on projects while the render is happening. So it's unfortunate that, at this point, I can only reliably render in software and not in Media Encoder.

[Mandee241926717z95 · Accepted solution]

Hello @JohnColombo I wanted to provide an update for you. Last week I updated my Macbook Pro to the new OS Sonoma 14.0, and since then my Adobe products seem to be making the correct connection. So far the projects I've worked on ARE CORRECTLY sending directly to Media Encoder from Adobe After Effects! I have not tested all of my various types of projects but I wanted to let you know that this OS change could possibly have corrected the issue for me.

[Juniperf]

Thank you for the help! 

Dragging a project into AME, or trying Dynamic Link from the AME menu actually results in the program stalling until I have to force quit. The only way to reliably get a project to appear in AME is by adding the project to the AME queue via Premiere / AE 

My error logs tend to have lots of "Operation Interrupted by User" or "Could not read from the source. Please check if it has moved or been deleted." (the source has not been moved or deleted)

[eckiAMETeam]

Can you please try the following:

1. Make sure that versions of all apps match (required for DynamicLinkManager to work correctly).
2. Verify your own AntiVirus / GateKepper setup. If applicable, deactivate temporarily to verify.
3. Quit all DVA apps.
4. Use Activity Monitor / Task Manager to kill DynamicLinkManager if it still runs. (On Windows, you need to open the Details tab to see dynamiclingmanager.exe in TaskManager.)
5. Launch AME first.
6. Open & export the project again.

Please let me know if this workaround works for you.