Participant

Question

Premiere Pro not sending to Adobe Media Encoder

Forum|Forum|6 years ago
July 4, 2019
6 replies
12157 views

Hi,

Starting this week when I send items to the render queue or try to create a proxy from within Premiere Pro nothing shows up in Media Encoder.

Media Encoder opens and the dialogues in Premiere all show up as expected but nothing is added to the queue.

However from After Effects selecting Export > Add to Adobe Media Encoder Queue... the selected composition is added to the the queue.

I can add to the queue directly from AME by Adding Source or Adding Premiere Pro Sequence, I just can't add to the queue, either as an export or create proxies, from within Premiere Pro.

This is very frustrating. The only thing I've found in these forums which seems to describe my issue says, 'after a time it fixed itself' which is extremely unhelpful.

I've tried clearing all the caches, uninstalling (from the CC app) individual applications, restarting, and reinstalling. I've tried uninstalling the whole CC suite and reinstalling, to no avail.

If anyone has any ideas I'd welcome them,

Thanks.

Versions

Adobe Media Encoder: 13.1 (Build 179)
Premiere Pro: 13.1.2 (Build 9)
After Effects: 16.1.2 (Build 55)

System

Win10 Pro
16GB RAM
Core i7

S

Speex25090918hoy1

Participant

Deleting the media cache in Premiere Pro and restarting the computer resolved my issue. Note that I wasn't able to export the video in Premiere Pro either, as the rendering was stuck at 0%. I also copied the footage to a new project before deleting the media cache and restarting the computer.

martins73850577

Participating Frequently

I've got the same problem for years on and off, again and again. Now it's there again. Premiere simply does nothing (!!) after I request sending to ME or also direct export.... no reaction or after 10 minutes of waiting it goes to the export window, then every click needs another 10 minutes, when finally I managed to send it from there to ME, rendering is impossible: "failed".

I deleted the user-folders of both programs.

I deleted the AMERequestDB of premiere.

Both helps nothing.

I updated both programs to the newest version. Does not help.

That's so unprofessional, simply not worth the money, as all my work is stuck in premiere. For years (!!!) adobe is not solving the issue.

macOS Sonoma

macBook Pro 13" M1 2020

Premiere 24.5.0

ME 23.6

Kevin-Monahan

Community Manager

Please try updating Media Encoder. The apps need to be on the same branch to interact as part of best practices. I hope the advice helps, @martins73850577.

Thanks,
Kevin

Kevin Monahan - Sr. Community and Engagement Strategist – Adobe Pro Video and Audio

C

Crirus74

Participant

Go to C:\Users\[user]\Documents\Adobe\Premiere Pro\[version] and delete AMERequestDB.

It got corrupted on me and deleting it solved the communication issue with AME

D

DanMaxCro_Dartmouth

Participant

Just had this issue come up today and deleting the AMEReguestDB did the trick. Everything is working again...Thanks Crirus!

-d

E

excited_Genie16B8

Legend

Couple things you can try are Steps 3D and 4D below.

Unofficial Premiere Pro Troubleshooting Guide

S

Sumeet Kumar Choubey

Community Manager

Hi PhillUpNorth,

Sorry to hear that you are facing this issue. Please try resetting app preferences (https://forums.adobe.com/thread/2126506) for Premiere Pro and Media Encoder and check if it's working properly. Some times corrupt preferences may cause the applications to misbehave. If you are still facing the issue then try these steps and check if it helps:

Go to \Users\<username>\Documents\Adobe\Adobe Media Encoder\13.0 and rename the folder name 13.0 to old13.0.
Go to \Users\<username>\Documents\Adobe\Premiere Pro\13.0 and rename the folder named 13.0 to old13.0.

(Doing this will cause Premiere Pro and Media Encoder to rebuild the default preferences, you may lose custom preferences and recent history of the projects)

Once done then launch Premiere Pro, create a new test project and check if you are able to queue to Media Encoder.

Let us know if it helps.

Thanks,

Sumeet