Skip to main content
mikhailm18748305
Participant
Nov 5, 2018 9:25 PM UTC
Question

Adobe Media Encoder 2019 very slow

Export times have quadrupled.

I have tested on 3 different iMacs, all with slow render times compared to 2018 Media Encoder.

macOS Sierra Version 10.12.6

iMac (27-inch, Late 2013)

3.5 GHz Intel Core i7

24 GB 1600 MHz DDR3

NVIDIA GeForce GTX 780M 4096 MB

This topic is closed to new replies. Start a new post to keep the conversation going.

51 replies

Participant
May 24, 2019 9:25 PM UTC

Windows 10 PC, Intel i7 quad core, 64GB RAM, in 2018 AME ran with acceptable times.Maybe 10 minutes to encode an 8-12 minute video.

Today, I finished a 6:41 video, sent it to the AME queue, and it took MORE THAN SIX HOURS to render.

This is not acceptable.

Translate
Participant
May 24, 2019 6:41 PM UTC

Open Media Encoder 2019 on a Mac Pro (OS 10.13.6) with 64 GB of RAM and 2 AMD Firepro D300 2048 MB graphics cards.

Beach ball for 1 minute before it even begins loading it's plugins.  Load Plugin for 30 seconds, beach ball for another 45 seconds.

The program opens.  Click on a hard drive in the media browser window.  2 minute beach ball.  Hard drive opens.  Try to open a folder in the hard drive.  2 minute beach ball.  Folder opens.  Drag a file to the queue.  2 minute beach ball.  File shows up in queue.  Click to set compression settings... 2 minute beach ball.  Set compression settings.  Click to set the destination for the new file.  2 minute beach ball.  Choose destination.

That took 10 minutes.  6 more files to go before I can start rendering a queue of files....

This is after setting the Renderer to "Open CL"

Infuriating.

Translate
Participant
May 9, 2019 10:52 AM UTC

Yeah this is really really bad. I generally do 3-4 minute clips that I render in 1080p. Usually it takes less than 1 minute to render but now it's saying over 1 hour in AME. I took some of the advice in the thread and rendered directly in Premiere. It rendered in less than a minute like I expected. This is extremely poor and is making me think of going to resolve. Also when I send an item to AME from premiere or after effects, AME opens but nothing goes into the queue. I have to close AME and re-open it and everything appears. I really don't understand how Adobe can keep adding these bugs to their software.

Translate
SpaceCherryFilms
Inspiring
May 1, 2019 9:38 PM UTC

Same problem here.  The previous version (cc2019) worked great. Now with version 2019.1 rendering is miserable.  I have been using Premiere since version CS4.   I bout had it.  I guess it’s time to cancel this and move on to Resolve 16. 

Translate
Participant
May 2, 2019 1:33 AM UTC

And they really don´t change the way they treat costumers and how things works. They´re giving a shit about this problem.

Translate
Participating Frequently
Apr 25, 2019 9:07 PM UTC

This problem is frustrating. I have a project that rendered in an earlier version of AME in 1.5 hours. Now it shows 51 hours, and the estimated time only goes up, never down.

I unchecked "import sequences natively" in AME.

I completely uninstalled NVIDIA drivers and did a new install.

Uninstalled and reinstalled PP and AME.

Adobe has often rolled out "upgrades" that make render times impossible to deal with.

Translate
Participant
Apr 20, 2019 9:53 AM UTC

Same problem here. My ´´solution´´ is rendering inside premiere pro. I´m just not using AME. And of course, that´s a shame because in a lot of ways, slow down my entire workflow and therefore, I lose money. These type of bugs are really getting boring over the time (I´m a very old Adobe user)...

Translate
Participating Frequently
Apr 18, 2019 4:44 PM UTC

Same issue here. I do short (3-8min) and long (2+ hours) exports in h.264. Before the latest update, I had standard times and a reliable queue.

Latest 2+hour video (2:17:00) -- it takes around 7 minutes to simply return a 'time remaining' and then says 80 hours remaining. After stalling, the time remaining will show a flurry of activity and then go up, climbing to 90 hours, 100 hours. It's absurd.

Exporting directly from Premiere showed similar delay. I updated Nvidia drivers (GTX 1070) and tried exporting with CUDA, OpenCL and software only. No changes. I updated the onboard intel graphics driver. No fix. I relocated assets to different hard drives, all SSDs. Nothing. Finally I got it to work directly from Premiere but AME is still a no go. I deactivated Intel graphics driver. I tried changing the mercury render engine in project settings. No help.

Watching the the component utilization in task manager, I noticed something weird:

When it works (directly from Premiere): CPU usage -- 80+ percent solid; Intel graphics (GPU 0): 30-50% solid; GTX 1070 (GPU 1): 50-60% solid. It works!

When "exporting" from AME:  CPU at 17% with brief activity spikes at regular intervals, GPU 0 total flatline, GPU 1 6% with similar activity spikes to the CPU.

Adobe, you broke the ability to create videos. How about -- just spitballin' here -- shifting some resources from new features nobody uses and working on the ability export videos in less than 4 days? I know, CRAZY idea. (seriously, release a version whose primary feature is stability and have a beta program for people willing to risk this kind of nonsense)

I don't care how many bells and whistles it has, if it doesn't drive, it's not a car. Right now, you're selling lemons.

Machine:

32gb ram, gtx 1070, i7 4790K, Windows 10 - over 10 years editing experience on PC and Mac.

Translate
Participant
Apr 19, 2019 11:17 AM UTC

Dear Adobe,

Will you respond to that ?

Will you tell us - your customers when we wil have the ability to use our Xeon machines to render with multiple CPUs again in AE/AME?

Translate
EaDEditor
Participant
Apr 17, 2019 7:20 PM UTC

I'm having the same problem after the April update.

In a simple video conversion, the same file with the same settings went from 15 minutes to 8 HOURS !!!

The processor does not exceed 10% of use during coding. Previously it was 100%.

It is not a video driver problem or any conflict. By Premiere the rendering works normally.

Just like the bugs I reported in the previous version Adobe will not fix until the following year.

Translate
Zellu
Participant
Apr 17, 2019 8:42 AM UTC

Hello,

I've never used the AME, installed it right now to test it and... omg what's wrong with this program?

Importing 6 animations coded in h264 took like 4 minutes, changing an encoding preset takes 10-15 seconds, opening the dialog box takes 30 seconds... Should I change some settings?

I have surface book 2, with Intel Core i7-8650U, nvidia GTX 1050 and 8g ram and this program is just not working at all. I took mi like 10 minutes to change encoding presets of 6 files, Rendering however isn't that bad, it gone somehow fast.

But even so, I used free prism to encode my 6 videos and I've checked 6 presetes with it, when trying to use AME I havent finished one yet.

Translate
Participant
Apr 15, 2019 1:54 PM UTC

Unfortunately same here.  AME is very slow on rendering premiere projects with h.264 *.mp4 files on timeline. Or rather "re-rendering"

cause rendering to mp4 h264 is fine, just rendering to timelines with mp4 files on them is very slow.

My typical project is made of ~30 second h264 mp4 file intro, then few minutes of mxf files and then 10-15 seconds h.264 mp4 outro.

Before latest update I would render entire timeline in about 3-4 minutes.

Now using AME 13.1, April version it takes about 12-14 minutes to render mp4 intro, 2-4 minutes to render mxf files and another ~10 minutes to render mp4 outro.

Just finished rendering a FHD, 25 fps, 3:13 long movie with hardware rendering in 27 minutes!

Translate