Is it just that Media Encoder is utterly RUBBISH?

Question

So is Media Encoder rubbish?Scenario 1) I've just exported a timeline to Media Encoder to render out an .mp4. Scenario 2) I then decided to export the same from AE a .mov prores422 file using AE's inbuilt renderer, brought the .mov into Premiere, and exported as .mp4. Both resulted in .mp4 files and both have similar file size.However, Scenario 1 took 90 mins, Scenario 2 took 30mins.  Am I missing something? Or is Media Encoder just rubbish?

ShiveringCactus · Accepted Answer

Wow, that's a really big time difference. One trick I stumbled upon recently when AME was failing was to go into Task Manager and End Task After Effects. It pops straight back, but at a lower RAM usage. I wonder if the same trick would work here.

For now, until that next update Mylenium mentions.

Mylenium · Answer

It#s not media encoder, it's the memory management. Encoding files directly uses DynamicLink, after all, and this gobbles up tons of extra RAM and limits the transfer bandwidths plus there's of course a ton of internal communication overhead whn AME requests to render a frame, the virtualized AE instance renders a buffer and then AME appends it to the stream or caches it for encoding larger chunks. It's just how it works and as you already found out, there can be a lot of sense in rendering intermediate files. The situation should improve once you can render H.264 directly from AE again in the next big update.

Mylenium

Sign up

To post, reply, or follow discussions, please sign in with your Adobe ID.

Sign in to Adobe Community

To post, reply, or follow discussions, please sign in with your Adobe ID.

Scanning file for viruses.

This file cannot be downloaded