Skip to main content
Participant
January 22, 2020
Question

Adobe Media Encoder doesn't start

  • January 22, 2020
  • 2 replies
  • 996 views

Grumpy hi...

 

Everything was running smoothly, but AME doesn't start anymore.

Neither when I try from After Effects nor from the Adobe creative cloud.

This extends aswell to Premiere Pro which won't start aswell!

 

All I get is the starting loading square... which then disappears.

I've uninstalled and reinstalled every softwares, cleaned my registry, still not working...

 

Anyone having the same issue?

This topic has been closed for replies.

2 replies

gupta shivangi
Legend
January 24, 2020

Hi there,

 

I understand AME does not launch. Could you share more details? We're here to help.

  • Which version of AME are you using?
  • Which Operating System are you using?
  • Has it ever worked fine before?

Looking forward to your response.

Thanks,

Shivangi

Participant
January 30, 2020

Hello Shivangi,

 

- I'm using the latest version of AME (and i tried to make it work with a previous version, v 13.1.5, without success).

- I'm on Windows 10.

- It was working great.

 

Thank you for your answer,

Armand

gupta shivangi
Legend
January 30, 2020

Thanks for the information. Could you follow the steps below and share the log file that will help our engineers identify where AE fails to send the comp to AME?

 

  1. Quit all Adobe apps
  2.  Press Windows + R, type appdata and click OK
  3. Navigate to Roaming > Adobe > After Effects > 17.0 > logs
  4. Create a blank .txt file named LiveLink Log.txt and save it (must be exactly this, with a space between LiveLink and Log).
  5. Now launch AE and send your composition to Media Encoder
  6. Navigate to the logs folder again. You should see two files in that folder now. If you do, share the LiveLink Log.txt with us. That will help our engineers identify where AE fails to send the comp to AME.

 

Thanks.

Shivangi

Participating Frequently
January 23, 2020

Whoops. Just realized I misunderstood the issue you were having. Disregard my response. The only possible solution I can think of to your problem is to make sure your drivers are up to date.