Skip to main content
Inspiring
December 4, 2017
Question

Media Encoder CC 2018 Very Slow

  • December 4, 2017
  • 11 replies
  • 11277 views

I'm having the same issue since upgrading to Media Encoder CC 2018 a few days ago. Previously my 10 to 20 second videos were rendering in no time. Now the exact same videos are taking ages to render or not rendering at all.

For me the main issue is that they take 5 minutes to begin rendering, and I frequently get 'Cannot read from source' errors, or Media Encoder just hangs. Prior to updating the software I had no issues.

Software only or GPU Acceleration makes no difference.

MacBook Pro (Retina, 15-inch, Mid 2014)
Processor: 2.5 GHz Intel Core i7

Memory: 16 GB 1600 MHz DDR3

Graphics: NVIDIA GeForce GT 750M 2048 MB

Intel Iris Pro 1536 MB


Adobe Media Encoder CC 2018
Comps created in After Effects CC 2018, which I updated at the same time.


Any advice would be greatly appreciated.

This topic has been closed for replies.

11 replies

Inspiring
December 31, 2018

I'm having the same issue...

But I don't think it's with the Encoder solely.  I have a 4k project that is 25 min and it was taking 17 hours to render until I removed the Red Giant effects from my footage. Now it's taking 2.5 hours to render. 

Participant
June 16, 2018

I have that issue too. I encode h.264 files which took about 30 min with media encode cc 2017 now take around 2 hours to get done. pls fix this.

Participating Frequently
June 16, 2018

There is a fix. After months of investigation and literally NO help from Adobe, I found this:

https://www.youtube.com/watch?v=klV_OgFiX-A

http://www.focuspulling.com/cc2018/

Just follow the instructions and check if you have compatible Hardware. It fixed my issue completely.

Render time on a 2hour 55 minute timeline went from 3h20min to 1h40min rendering time.

On a mac Hardware acceleration should work out of the box, since its build into the os, I believe.

Best

Hendrik

Participant
September 26, 2018

We should NOT have to go through such processes.

I have been using premiere for years mainly because of the lightning fast encodes because I create many different output file versions.

I wish I never updated!

Editing/encoding is via my nvidia gtx970.

30 minute edits were encoded to various mp4 formats in around  10 minutes. Now the same takes upto 2 hours!!!

I cannot carry on like this, I will never complete my workload at this rate!

I also have a powerful laptop with dual gtx 980s.

Exactly the same problem, clips are now taking OVER 10 times longer to encode!!! All since updating a few days ago.

Since I have done nothing else to either machine, made no changes whatsoever, it is ridiculous for adobe to think that this issue does not exist due to their latest updates.

To start mucking around with bios and other settings is not the answer, especially for just 2 times increase? Using my nvidia gpu, it was upto 10 times faster than cpu (which is also no slouch latest i7)

I have a load of files to encode to mp4, something which I could complete within the day ... I have absolutely NO chance of fulfilling my requirements now thanks to this useless update.

Can anybody recommend any other fast encoders that use GPU ??

If this doesn't get sorted soon I may as well cancel my subscription (and I know a few other developers in the same situation, so it is not just my imagination

cheers

Andy

Participant
June 12, 2018

I too am having this issue. Latest Media Encoder Updates have turned encoding into a 7-16 hour deal.

Even 30 second clips can take 5-9 minutes.

I don't need to need to update any drivers, my rig is built with 64GB Ram and 32 2.9GHz Xeon Cores. Encoding SHOULD be fast.

I do edit 4k H264 files with proxies. Only the encoding the process has slowed.

There is something wrong with Media Encoder. A setting is wrong or Adobe has fouled up something to do with H264 files. I have tried the trick unchecking the box Import Sequesnces Native to see if that helps. I also see that some have good luck with a reboot and the first encode doing fine. I will test that too.

Jockw1234
Participant
May 31, 2018

I have the same problem! After a reboot of the computer the first render in the queue goes quick, then the next in the queue just goes extremely slow.

Before I could stay away from this shit called Media Encoder but now when Adobe REMOVED the option to render to H264 in AE I have to use it. I do H264s at the end of the work day to show progress to clients and this completely F**Ks up my work.

And this problem has existed for more than a year. Sigh...

After the subscription model Adobe has become, lazy, slow and dumb (as was to be expected).

Participant
May 31, 2018

Same issue here.  After upgrading, it takes minutes for a render from After Effects to appear in AME's queue.  Rendering also seems to be quite slow.  AME seems to often hang while rendering during the 'Connecting to Dynamic Link server' phase.  Very frustrating.

Participating Frequently
April 26, 2018

graphter  schrieb

I'm having the same issue since upgrading to Media Encoder CC 2018 a few days ago. Previously my 10 to 20 second videos were rendering in no time. Now the exact same videos are taking ages to render or not rendering at all.

For me the main issue is that they take 5 minutes to begin rendering, and I frequently get 'Cannot read from source' errors, or Media Encoder just hangs. Prior to updating the software I had no issues.

Software only or GPU Acceleration makes no difference.

MacBook Pro (Retina, 15-inch, Mid 2014)
Processor: 2.5 GHz Intel Core i7

Memory: 16 GB 1600 MHz DDR3

Graphics: NVIDIA GeForce GT 750M 2048 MB

Intel Iris Pro 1536 MB


Adobe Media Encoder CC 2018
Comps created in After Effects CC 2018, which I updated at the same time.


Any advice would be greatly appreciated.

It has nothing to do with accelerated effects. All 2018 Versions of premiere pro and AME have a bug, which does not let them use MPE on export. The ONLY possible solution is rolling back to cc 2017 or earlier. creative cloud desktop lets you do that. Scroll to your app and under "more" there is a link "other versions".

I've been dealing with this over the last two weeks. Spent hours on chats with adobe support (You get know a lot of indian names that way). Adobe is in complete denial of this.

Trust me. I rolled back this morning to cc2017  and everything works perfect. And although I haven't used Effects with are supported by MPE, I am now able to export a sequence in 40 min., which took 4 hours before.

Vidya Sagar
Adobe Employee
Adobe Employee
April 19, 2018

Hi All,

A new update for Media Encoder & Premiere Pro is available, 12.1.1. Please update and let us know the issue status.

Thanks,

Vidya

Participating Frequently
April 19, 2018

Can't test right now, but the issues addressed have nothing to do with our probs, or?

  • Fixed a crash on launch in some cases when loading Cool Type fonts (these fonts are prevented from loading.)
  • PNG files containing Alpha are correctly displayed with the default interpretation of Straight Alpha.
  • In some PNG frame sequence exports, frames no longer get mixed together (superimposed).
  • Application no longer hangs if you quit it after playback of Sony F5 RAW files.

I am talking about AME not using gpu for export although Mercury engine is activated in AME..

Regards

Hendrik

tomcantrell
Inspiring
March 15, 2018

Did you ever get this fixed?  I have the same problem and it's driving me crazy.  Took an hour to render a 30 second video!

Vidya Sagar
Adobe Employee
Adobe Employee
March 23, 2018

Hi laurad5078754, tomcantrell,

Sorry for the delay in response. Performance issue occurs mostly due to bad permissions or incompatible video drivers.

Please try the steps in the following articles:

fixing permissions problem that impedes start of Adobe applications | Creative Cloud blog by Adobe

Update the graphics driver | Windows 8, 7, Vista

Let us know the status.

Thanks,

Vidya

agm 123
Participating Frequently
April 16, 2018

Had the same issue... 8 minute render taking 2 hours.

I had an issue with Premiere Pro's latest update (April 2018), so I reverted back to version 12.0.01 but I didn't revert Media Encoder back.

When I reverted back Media Encoder to match Premiere Pro 12.0.01 my files rendered properly. (Only issue is I lost my presets)

Inspiring
January 20, 2018

I'm having this, too.

I note that other users are complaining about renders from AE and I'm talking Premiere Pro; I do think this is the right topic since both programs render in AME and the complaint is slow processing. If someone wants to move this feel free.

Granted I'm processing MP4s of 4K files but the times are WAY longer and the amount of processor and memory taken up WAY less.

My system is Windows 10 Pro, 32GB DDR-3 RAM, i7-4770K. Files are written to a 30TB RAID. Video is GTX 1050 Ti with 4GB.

I have all but 6GB allocated to Adobe. I notice that the system is using far fewer resources than it did in past versions.

RIght now, I'm outputting a 4K file at "high bitrate" of an opera I recorded this past weekend (i.e. brand new project) on my Sony FDR-AX100 camcorder. The file is 2 hours 6 minutes in length. I've done these where processing is between 4 and 6 hours; this one now predicts 17 hours. There's nothing new in my system architecture, the type of video I'm using (had the AX100 since it came out in 2014) or anything else I can imagine.

All software is CC 2018 completely up to date.

What could this possibly be?

Vidya Sagar
Adobe Employee
Adobe Employee
January 5, 2018

Hi Graphter,

Have you resolved the issue? Please let us know the status.

graphterAuthor
Inspiring
January 5, 2018

It happens with projects created in the old version of AE and the new version. It seems to happen when the composition contains an h264 movie file.

Participant
January 30, 2018

    If you're dealing with an H264 in a .mov container then Adobe is going to give you a lot of issues. This is because it's a 32 bit codec and at the end of this year all 32 bit codecs can't be used. I would recommend transcoding your h264 into a ProRes.

I ran into a problem similar to this where AME won't let me export to my server and can only export locally on a drive. It's really annoying.