What's up Adobe? Why so slow (After effects)

[Stefan Scherperel]

For the last few months i have been using the following workflow.
Premiere 4K timeline
Cut Project in Premiere
Impot Premiere footage into AE - Not dynamic link so i can have access to individual clips
Color correct, composite, effects.
Render 1080P at full or half depending on project and footage used
Use multi-core rendering when available, not always.
Have a 3 - 8 hour render for 3-4 minute projects (8 hours for full - no multicore becasue of certain effects.)

Now even though I have a fairly new Core i7, overclocked, 12GB of ram, I have always had problems with multi core rendering, usually having to use only 2 processors of 4 becasue it eats too much RAM. And some effects don't allow multi processing (Yay 8 hour render)

Today I was just sick of it and decided to try somethin new. I found that if I set my Premiere timeline to my output size (1080P) not only could I get much better realtime performance, but when I render from premiere with Adobe media encoder I use all 4 processors, 8 cores EVERY SINGLE TIME!
I just rendered out a clip from premiere using all the same color correction that I did in AE for the same clip, including some effects that don't allow multi processing and guess what, at 1080P It renderd the clip 6 times as fast.

If Adobe media encoder can use RAM so effeciently as to use all of my cores all of the time, and with effects that AE says can't use multi core rendering, then what has the AE team been doing. I have nothing but headaches trying to render from AE, and with Premiere the end result looks exactly the same.

Hmmm, I think I have a new workflow emerging.

 

[Pietro Impagliazzo]

AE is a resource hog... And I really don't know why so.

The RAM that multi-processing needs really is absurd.

Ok, but what you saying is that the same effects that can't be calculated by multiple processors on AE do can on Premiere?

 

[BigLu]

I have stopped using AE and Premiere do to its horribly slow issues.
If i go to AE i take transcoded martial at 1080p so i can get my projects done.

Its just too problematic and troublesome , not to forget the new color science is not in AE adobe yet.
I switched back to FCP working with transcoded ProRes files.

This is working with an 8core 3gig processors intel nehalem mac with 16gb of RAM
still way too slow.

good luck.

 

[Stefan Scherperel]

I'm still going to wait it out and hope that Adobe updates to allow use of build 20- 21. While I agree that AE is really slow to render, I have found that now working with RED footage natively in Premiere is almost as fast a workflow as working with standard 1080P footage from a Canon A1 or EX1. Plus I still love the fact that I'm working directly with the RAW files in Premiere, and able to adjust on the fly.
We do alot of Rapidly produced content for Microsoft (Not the most fun, but pays the bills and allows us to do the fun stuff) and with this current workflow, RED is now a big option that we have. I'm holding out for you Adobe, please don't prove me wrong .

 

[Stefan Scherperel]

To Pietro:
Yes, the effects that AE and Premiere share that requires AE to slow to one processor, Premiere does with multiple. While I don't use this effect very often as it is not 32 bit, highlight shadow is one of these effects. Use it in AE and it's down to 1 proc. Use it in Premiere and it uses them all.