Copy link to clipboard
Multi-frame Rendering is here for After Effects beta users. Right now, you will have access to Multi-Frame Rendering for export only. Keep your eye on this forum, as we will be rolling out new features until we launch.
Internally, we have been testing a representative sample of projects with a suite of hardware configurations, and we are excited to finally put this feature in your hands and get your feedback. Test your unique projects on your own hardware so we can ensure that our performance updates benefit all of our customers and meet speed and quality metrics before we launch.
Beta testing of Multi-Frame Rendering will last a little longer than some of our other features because we currently do not support Multi-Frame Rendering in Preview, Motion Graphics templates, Dynamic Link, Adobe Media Encoder and AERender Command Line Interface.
We want to hear from you! Share your thoughts and ideas in this forum.
Test Your Comps
Test your comps in Multi-Frame Render mode vs. Single-Frame Render
Leave a comment and the following information in this forum:
If you detect any problems with render speed or quality, submit your projects
Share the following information in your comment:
Test our benchmark project and see how your hardware compares
We would love to know how your hardware compares to the results we have gathered from our test suite:
To test the benchmark project on your machine:
Share the following information in this forum:
Copy link to clipboard
AMD Threadripper 3990x 64core, 256GB Mem, NVidia 3090 FE 24GB
Multi-Frame = 3:45
Single = 12:45
Multi-Frame = 3:22
Single = 11:59
WOO HOO Great job Adobe!! This made my week. It's so nice to be able to finally stretch my CPU legs in AE. I'll try some of my other projects in this new version. Hopefully I'll have the same results.
Mac Pro 7,1. 12 cores 96gb Ram Here , Radeon w5700x 16GB
Was excited to heard about this feature but AE only using only 13% of the cpu during the whole proccess...
Have you guys at Adobe thought about buying and implenting rendergarden from toolfarm as an standard render technology native to after effects? If you havent you should since that solution really works.
That doesn't seem right. We have 30,000 MFR renders happening in Beta per day with much improved performance. Can you a) confirm that MFR is enabled in Preferences -> Memory & Performance and b) tell me more about the project you were rendering?
I get the same. All my footage and caches are on 3,500 mb/s NVMe drives, have 64GB ram and my 64 core 3950x maxes out at maybe 25-35% utilization. In app RAM preview does maybe 2-4 simul frames max.
I'm only getting about 20% usage from my CPU in real world projects too, even though AE is concurrently rendering between 8 and 15 frames. I did do a comparison the other day, and having MFR turned on is indeed a big boost compared to switched off, but it still seems odd that AE isn't taking full advantage of my CPU.
Looking at the Render Time stats in my comp, CC Wide Time seems to be the culprit, taking 759ms per frame; all other layers/effects are 0ms - 2ms, with one other layer taking 38ms.
AMD Ryzen 9 5950X 16-core
Nvidia RTX3090 24GB VRAM
System, project & cache drives are all Samsung M.2 980 PRO or EVO.
Windows 10, updated yesterday, Nvidia drivers updated today
Having implemented parallel processing on projects before, the bottleneck comes from the BUS getting data to each thread. So for me UHD source and comps has to shove a lot of data into each frame/thread. I'm just guessing that's the bottleneck here. I'm not doing super heavy effects, either.
Are there effects in your project not optimized for MFR? (Look for the yellow warning icon in the effects panel). If so MFR needs to wait for those effects for each frame to safely complete which impacts the performance of MFR.
Also note that AE overall cannot address more than 64 cores so if you are using a CPU with 64 cores, meaning 128 with hyper threading, AE will only be able to utilize the first 64 cores but task manager is showing a percentage relative to 128 cores. So ~40% is effectively 55 or so cores.
We are working on extending AE to be able to use more than 64 cores for a future update.
If you click on the warning icon, it should tell you if it's MFR enabled or if the problem is that it doesn't support the bit depth you're working in. If it's the MFR issue, check to make sure you have the up to date version of it.
I get the non-MFR message:
"This effect may slow down Preview and Export as it is not optimized for Multi-Frame Rendering."
I just saw your post on the aescripts. Looks like the last update to the effect was back in mid-March and we had to make a change in late March for MFR that meant all MFR effects needed to be rebuilt with a newer SDK. I'm going to guess that hasn't happened as yet which is why you're seeing the warning icon.
Thanks thats great to know. I'm running a 3990 threadripper and kept the stock AE setting "10%" reserved for other apps. From what your saying I can set to "0%" and have it run on all cores(aka 64 of the 128) and not have to worry about locking up other apps). If we are really limited to 64 cores and I get this much of a performance boost. I'm looking forward to the day when you open it up for all 128.
I LOVE the beta version. I ran the PugetSystems Bench and before the beta install I was getting scores of about 950 to 980 and now I'm getting bench scores of 1748 what an amazing boost. It's making me what to create more.
Awesome, yes, set that to 0% and you should be just fine! 🙂
Thanks you ROCK Jenkmeister!!! Looking forward to more to come.
Copy link to clipboard
I was testing out one of my projects and noticed that Rendering was stalling at a particular point in my timeline. Using the Frame Render Time column I isolated the issue to a nested comp that had several text layers with animation expressions applied. Turning these text layers off changes the render time from several seconds down to a few miliseconds - quite dramatic.
Do you think there might be something going on with how expressions are being handled? Or maybe there's an issue with expression I'm using (I didn't write it)?
Yes. I've found that text layers with expressions seem to cause dramatic slowdowns and non-redraws.
It's frustrating because to do the text anmiations manually, although it would solve all the preview and render delay problems, would take significantly more time upfront and wouldn't be editable, as adjustable or as iterative - especially on multiple lines of text, and more signifanty if you wanted to try different fonts!
It would be nice to know if there are going to be any improvements to expression performance on text layers or if I just need to suck it up and accept the hit! 🙂
Are you able to provide the project(s) to us? Given how much expressions can do, it's very hard to isolate what might be the issue without seeing either the expression or the project.
I'll try to get a project over to you today.
On another note - if I've got some AE comps dynamically linked in a PPro timeline, will AE/PPro ever render those using MFR? I'm currenlty rendering out a timeline from PPro that's almost 100% DL comps, and my processor is sitting at around 5% usage (16 cores, varying between 1% and about 20%). I now have MFR turned on in AE (I turned it off earlier to avoid issues).
RE: Dynamic Link w/ MFR. Yes, we are currently working on adding the support for dynamic link and motion graphic templates built in AE rendering with MFR when in Premiere Pro. Should be in to beta in the next week or two.
Copy link to clipboard
is it possible for me to jump on the beta team? Thanks!
Yep, the beta builds are availabe in the Creative Cloud Desktop app. Just look for the "Beta" section on the left.
Copy link to clipboard
I ran into a new issue in the very latest beta version. Scrubbing the timeline has become awfully slow and sluggish.
This is even in a completely empty timeline. Notice the lag of the playhead behind the cursor:
It never was great, but in the regular after effects release it's way better than that:
It might be worth noting that I'm on an Apple XDR display, and not a single Adobe App except maybe Lightroom CC seems to like this huge resolution when it comes to UI responsiveness. After effects, Premiere and Lightroom Classic have always been the worst, to the point that I have to run premiere in 1/2 res UI mode.
But this super laggy scrolling behavior in the latest beta wasn't there before, so please look into that.
Ah one more thing, it also has become suuper slow to respond to a space bar press to stop a current playback!
Thanks for the reports. I'm not aware of any changes happening in AE itself that would be changing either the UI responsiveness or stopping playback in any of the recent beta updates. Can you confirm you're on 22.1x50? Have you made any changes to your OS or your hardware otherwise?