Full program multi-threaded support
After Effects would benefit greatly from being able to actually utilize all cores when rendering, rather than having to rely on a third party solution, like the excellent program Render Garden by Mekajiki.
(This post was co-authored by Tim Kurkoski (After Effects Product Owner), Andrew Cheyne (After Effects Engineering Manager), and Victoria Nece (After Effects Product Manager).)
This thread has been sitting here for quite a while without a response. To start, we want to apologize for that. We haven’t been ignoring you or your feedback – this is just a particularly complex topic. That said, it’s time for us to check in with you, clarify a few things, and give you an idea of what we’re looking at for the future of After Effects, especially when it comes to performance.
Before jumping into the specific request here (multi-threading AE), we should talk about how the AE team looks at performance in general. There are three areas:
- Rendering Performance: How fast can AE get pixels onto your screen?
- Interactive Performance: How fast does the UI respond to your actions?
- Workflow Performance: How fast can you complete a task in AE?
All three are important. All three impact how quickly you can make creative decisions and get your work done. This request and this discussion are focused on the first area, rendering, so we will focus on that, however we don’t want to lose sight of the bigger picture.
What have as the AE Team been doing? When we set out to tackle rendering performance, we looked at the potential improvement offered by different technical paths. And we set a high bar: we didn’t want to just have an incremental speed increase. We wanted a major leap forward in rendering power.
The obvious technology that would enable us to achieve that goal was leveraging the GPU. Because GPU processing power has leapfrogged the CPU — and is explicitly designed to handle this type of processing — the decision was made to invest in getting AE’s core rendering pipeline running on the GPU.
This is not a small task, and we’re not done yet. The most visible result of this effort has been the porting of individual effects to the GPU – more than 40 so far. Less visible is the work we’ve done getting the rest of the After Effects rendering pipeline on the GPU, such as layer transforms and motion blur or debayering RED raw R3D footage.
We still have further to go, as the real power of the GPU is unlocked when you don’t have to send a frame back and forth between CPU and GPU for different stages of rendering. As more links of the GPU chain come online, you can expect further rendering performance gains.
We do know what you’re thinking at this point. You want to know what we’re doing about multi-threading.
We all recognize that After Effects would benefit from additional general-purpose multi-threaded rendering. And while we can’t get into specifics here or make any promises about our future roadmap (that’s all confidential when you’re a publicly traded company), we are actively working on multi-threaded CPU rendering.
Ultimately, when it comes to achieving the best rendering speeds possible for AE, we know we’ll need a combination of GPU and CPU processing that maxes out all the resources on your machine.
We recently partnered with the folks at School of Motion and they did a fantastic video on how to get a more optimized system for After Effects: https://www.schoolofmotion.com/tutorials/after-effects-computer
Please keep posting and letting us know what you think. We’ll continue to watch this thread (and all the others on UserVoice). And we appreciate your patience with our response to this post.
Christopher Jeffries commented
Oh look! I built a new workstation! (Specs: https://pcpartpicker.com/user/Cx/saved/gWRk99 )
What's amazing: Cinebench scores are fantastic! Lowest rendering time (quickest!) of the many years I've been running the AE Total Benchmark scene! Everything else I run other than AE is much improved!
What's not amazing: AE previews are still slow and the UI is laggy. And there's seemingly nothing I can do about it.
PugetBench results: Overall score of 1156. (The School of Motion article listed in the response from Victoria Nece shows a score of 985.)
CPU-Z benchmark results: 16336 (multi thread) / 499 (single thread)
I am beyond frustrated at the state of this application. It is, without hyperbole, the greatest pain point in my professional life.
lol, It's been over 6 years, time for an update!
Ian Davies commented
@the dudes : I admire your optimism, I really do!
Carl Strand commented
👇🏼 what he said.
the dudes commented
@Victoria Neece: It's been exactly 1 year. Time for an update 💁♂️
Jenny Girl commented
Most shops are actually PC now due to the need for nvidia GPU rendering, I miss the mac, but ¯\_(ツ)_/¯
Peter Labrow commented
Don't get me started on the icons. "Let's make all the icons of similar apps the same colour. Because that's not a confusing mistake a day one UX student would make."
I'd imagine it may be faster to invent a time machine to go back in time and save Adobe from 2004, because they're clearly stuck in a time before multi-core CPUs were a thing. I've wasted so much of my time and life idling while AE renders one frame every 5 seconds on my $500 CPU. My work efficiency is utter trash, legitimately the majority of my time "working" is waiting. I would gladly chop off both of my legs, an ear, and a majority of my kidney for even a 20% increase in performance. I'll even let them keep the icons that make no sense and are objectively worse than the ones they're replacing.
Piero Glina commented
lol welcome to the party!
Hollow Earth commented
No multithreading? You're kidding me right?
I appreciate Adobe’s comment here but it says nothing about working on Macs! A huge percentage of the creative community uses Apple products whether Adobe likes it or not, and they need to be taken into consideration as well
Hahahahaha, the video is best comment ever!
Lol, that video is perfect. Freaky but perfect!
This video could not be any better at describing the current situation oml
I think that is what they have been doing for the last couple of years, working on ARM versions. **** they must be doing something, because there has been nothing good to happen to any of the products since I can remember.
Its going to be weird though, as they will release it and no doubt it will be buggy and slow. Then there will be double the products to maintain. Currently they can't maintain their x86 software.
Yaneev T commented
Would you suppose, that Apple's switch to arm processors will force Adobe to re-write AE for mac?
If Adobe ever does, would it take themeless than five years to accomplish that?
On the other hand, might that be the end of After Effects for mac?
(I'm not optimistic, yet hoping for surprises)
Christopher Jeffries commented
Michael Szalapski It's a scene that was created by Brian Maffitt, available here:
Over time, in my copy I've replaced the now obsolete effects with the updated equivalents which are, ostensibly, GPU accelerated. Attached is the original ZIP which does not include these changes.
Peter Labrow commented
Yep. Latest update - new icons. Best bit, they ignore one of the key principles of UI design and make groups of icons the same colour. So useful when looking for Premiere or After Effects in the same dock. Total kiddie mistake. Meanwhile, my Media Encoder says that all media is offline when it isn’t. Fun being an Adobe customer:
A year almost passed since Adobe commented on this and now they released new set of icons for their apps. Well done Adobe. AE feels much snappier since!
@Vanessa Even though AE supports GPU accelerated functions and Nvidia's CUDA cores, it's not known to have that much of an impact on performance outside of select filters & third party plugins. A year ago I went from a GTX 1080 to an RTX 2080Ti and I don't recall noticing that much of a difference in AE. I also doubt a Quadro will benefit you in AE.
In addition to Daniel's recommendation regarding RAM (32 minimum, 64+ recommended), I do suggest having a fast PCIe or M2 SSD for AE's cache/preview render files separate from the O.S./AE software drive.
There maybe some workflow considerations that can help, depending on what you're doing...