Skip to main content
hellopaul4
Inspiring
August 21, 2025
Question

Rendering two comps - one in AE, one in AME at the same time, or sequentially?

  • August 21, 2025
  • 1 reply
  • 112 views

A performance question:

If I have two comps I'm in a hurry to render, is it generally quicker to send one to Media Encoder, and render the other directly in AE simultaneously, or wait for one to finish then start the other? I'm sure the answer would be "it depends", but is there a general guidance? Does AME and AE share the same background task when rendering, and just divvy up its performance between the two apps, or is it more efficient than that?

 

If I have plenty of RAM (128GB), 16 cores on my 4.6GHz processor and 24GB VRAM, does AE+AME use these efficiently(ish) when both rendering? Like many other users, I'm often frustrated when I send something to render, and see that AE or AME is only using a small fraction of my PC's capabilities, so it stands to reason that if I set more than one thing rendering, AE could use 10% of my CPU while AME also used 10% (and I'd still have 80% left over for writing this long post! With AE+AME currently rendering, my CPU usage is around 21%, RAM is at 88% and GPU varies from 13%-79%, so even with two things rendering, it's taking a lot longer than it should).

1 reply

Shebbe
Community Expert
Community Expert
August 24, 2025

When it comes to AME. The way I understand it works is that the app creates a single copy of the project for each comp you send to it to render. These get placed next to the project in the [projectname]AME folder. This is for redudnancy sake to prevent file changes while rendering. The process it renders on is separate from AE so you can do both at the same time.

 

AFAIK, AME does not take your cache data along with it. So if you have a lot of data chached already inside AE, rendering out of AE will always be faster.

 

If you have multiple comps that take data from the same precomps (think different ratio edits of the same asset for example) this data is reused when rendering them both in AE. This does not happen in AME I believe because each comp was send to queue via a separate project file.

 

So depending on the context, AME can be a lot slower in general compared to AE, but does have the flexibility of keeping AE free to continue work. However with heavy renders this is meaningless because your computer will run slow anyway.