Multi-Frame Rendering is here! (AKA The multithreading you’ve been asking for)

[TeresaDemel]

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.

Check out the blog and FAQ post to learn the following:

• What is Multi-Frame Rendering?
• What factors influence performance?
• Which effects have been optimized for Multi-Frame Rendering?

Start Testing!
We want to hear from you! Share your thoughts and ideas in this forum.

• How much faster is Multi-Frame Rendering compared to Single-Frame Rendering with your comps on your machine?
• Does our benchmark project perform at the expected speed on your system?
• If you run into specific speed or quality issues with your project, share your project with us at mfrbeta@adobe.com.

Test Your Comps
Test your comps in Multi-Frame Render mode vs. Single-Frame Render

• Use Ae Render Queue to export your comp in Multi-Frame mode.
• Purge both the disk and memory cache, then
• Use Ae Render Queue to export your project in Single-Frame mode. Note: Use the same output module for Single-Frame and Multi-Frame mode. Go to Preferences -> Memory and Performance -> Enable Multi-Frame Rendering (beta) and uncheck the box to use Single-Frame Rendering Mode

Leave a comment and the following information in this forum:

• Your hardware specs: # cores in your CPU, GB of memory, GPU model and amount of VRAM
• Single-Frame render speed (Use “Render Time” noted in your status bar)
• Multi-Frame render speed

If you detect any problems with render speed or quality, submit your projects

• Open your After Effects project
• File -> Dependencies -> Collect Files -> Collect -> Save As (Name Your Folder)
• After Effects will store your .aep file, footage, and text report (file log)
• Zip up your project and send it to us at mfrbeta@adobe.com (or send a link to it hosted on your creative cloud storage if it’s too large to email).

Share the following information in your comment:

• Your hardware specs: # cores in your CPU, GB of memory, GPU model and amount of VRAM
• Single-Frame render speed (Use “Render Time” noted in your status bar)
• Multi-Frame render speed
• Mercury CPU or GPU Mode used

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:

• Download the benchmark project. 
• Use Ae Render Queue to export the benchmark project in Multi-Frame mode.
• Purge both the disk and memory cache, then
• Go to Preferences -> Memory and Performance -> Enable Multi-Frame Rendering (beta) and uncheck the box to use Single-Frame Rendering Mode
• Use Ae Render Queue to export the benchmark project in Single-Frame mode. Note: Use the same output module for Single-Frame and Multi-Frame mode.

Share the following information in this forum:

• Your hardware specs: # cores in your CPU, GB of memory, GPU model and amount of VRAM
• Single-Frame render speed
• Multi-Frame render speed

[skilled_friend0D44]

Installed the Beta update and made sure Windows Low power mode was off and now I'm getting better numbers:

Here's the result of the benchmark (export is pro res 422 HQ):

• AMD Ryzen Threadripper 3970x / 128gb ram / rtx3090 - 24gb vram / Windows 10 64bit
• Single frame : 11:50
• Multi-Frame : 3:50

[jimhowells]

Been waiting for this for so long! Thanks Adobe. The new Render Queue looks great and gives all info at a glance.

Rendering to Quicktime ProRess 422 HQ: 

• AMD Ryzen Threadripper 3960X 24 Cores, 64GB RAM, GTX 1080Ti 11GB VRAM
• Single Frame 12:05
• Mulit Frame 04:11

[danboon05]

iMac Pro (2017)

Catalina 10.15.7

3.2 GHz 8-Core Intel Xeon W

128 GB 2666 MHz DDR4

Radeon Pro Vega 64 16 GB

TLDR; I encountered an issue when attempting to use multithreaded rendering. AE was building a HUGE cache during rendering, filling my drive and leading to the render coming to a standstill.

I tried rendering a project I am currently working on, which resulted in the render progress coming to a standstill about midway through. AE didn't actually freeze or crash, it appeared to be working but the progress bar never moved and didn't respond when I tried to pause or cancel the render. Eventually I force quit AE. After the first attempt any attempts to start a render resulted in a similar situation immediately, AE appeared to be starting the render but no frames were ever completed.

I then noticed that I had very little space on my drive, after clearing some space I was able to start a render, but eventually ended up stalled out once again. I found what was causing the issue when purging AEs cache, I discovered the cache was 500GB in size which is why I had so little room on my drive (1 TB SSD). It seems that when rendering with multithreaded, AE was not clearing the cache properly, resulting in a HUGE cache and eventually rendering froze when there was no space left on the drive.

I sent the crash reports, but I'm not sure they would reveal what was happening with the storage.

[jenkmeister]

Thank you for the details. Definitely something there for us to look at futher.

Do you know which build of AE you were on that caused this? 

[danboon05]

Yes, AE (Beta) 18.1.0 (Build 22)

[jenkmeister]

Build 30 is now available. It has a number of fixes that I think might help with what you're seeing. If you have time tonight or tomorrow to try it out, that would be super helpful. 

[jenkmeister]

Mulit-Frame Rendering - March 18th Beta Update

Multi-Frame Rendering has been in public beta for a week now and it’s time to give you a short update on how things are going, the issues you’ve reported, bugs we’ve fixed, etc. Our goal is to do update you every 1-2 weeks as the MFR beta continues, though we will also remain active responding to posts and answering your questions day to day. 

Let’s start with some MFR stats for the first week: 

• Total MFR RQ Exports: 5354
• Unique Projects Exported: 1926
• Number of times the Benchmark Project has been exported: 431
• Fastest benchmark project export time (with empty caches): 3m 17s
• Largest (by frame) project exported with MFR: 23852 frames

Suffice to say we’ve been blown away by all of you trying this out, reporting your results, and spreading the word about MFR through social media posts, YouTube videos, blogs, etc. It’s been so exciting for the team to see. 

A number of people have reported projects that don’t complete rendering or are slower than expected. For those of you who have been able to send us your project, we send you a big THANK YOU! It’s incredibly useful for us to be able to reproduce the issues ourselves and identify what in the code is broken. If you have projects that won’t render or are slower, please send them to us at mfrbeta@adobe.com

Changes in MFR this week:

• For those of you having issues with renders not completing or pausing mid-render for a while, we believe we’ve identified the core issues causing that and have implemented fixes. Please download the latest beta build and try your projects again.
• When using Mercury GPU mode for rendering, we’ve made the initial number of concurrent rendering frames a little bit more conservative. This is in response to more people reporting GPU out of memory errors. For a 1920x1080 composition, expect to see one frame rendering per 1GB VRAM, up to a maximum of half your CPU Cores, capped at 8. As comp resolution goes up or down, expect to see the number of concurrent frames shift. 
• This change doesn’t affect Mercury Software rendering modes. The initial concurrent rendering frames remains at up-to half your CPU Cores, but currently capped at 8. 
• In the coming weeks, we’ll be introducing dynamic composition analysis that will allow the MFR engine to adjust the number of concurrent rendering threads based on the complexity of the frames being rendered. This will allow performance to scale to higher-end machines and avoid over-committing lower-end machines.
• Moving past the maximum frame rendering count of 8 is planned but requires completing the work that will remove the startup overhead you currently see when starting an export. We are working on that for a future update.
• While exporting, it was possible for the rendering stage of a frame to complete much faster than the write-to-disk stage (especially if frames are cached). In the worse-case, this meant AE was having to use additional memory to hold those frames that could be used for rendering frames more efficiently. We’ve made changes to address this issue and it should result in overall better performance. 
• Auto Color, Set Channels, Shift Channels, Key Cleaner, Median (Legacy) and Dust & Scratches are now supported by MFR. 
• I’m sure some of you are wondering why these and not others you might use. The primary reason is that some effects use features in After Effects that aren’t yet ready for MFR support. Until the core code is fixed, we can’t make the effects support MFR. The other main reason is time, it just takes a lot of it to migrate 290 effects. We are continuing to work on the effects and our goal remains 100% of AE’s built-in effects will be MFR supported by launch.
• Variable Frame Rate Footage, Footage with Alpha Channels
• There have been some edge cases identified with VFR and Alpha Layers in footage when used with MFR. These should now be fixed. If you see any issues with incorrect or green frames, please let us know.

Keep those rendering reports, bugs and issues coming. Thanks!!!

[adam s]

Running a personal project and the Beta locks up once it hits the first red giant plugin. I cant do anything but force quit. 

18.1.0 Build 30

windows 10

nvidia 2080ti  (461.92)

[jenkmeister]

Could you Enable Logging (Help -> Logging), render the personal project until it locks up, Restart AE, then grab the After Effects Log.txt file that should come up when choosing Help -> Reveal Log Files. Send that to us at mfrbeta@adobe.com and we'll take a look at what's going on. Thanks!

[adam s]

thanks it might be the plugin, but ill keep that in mind!

[chfilm]

amazing amazing amazing, keep up the good work! This is gonna be the most exciting AFX update in years! Especially once this applies to the actual ram preview, not just the final render. Clients are looking over my shoulder and I have crazy ram preview times on my 16 core mac pro... can't wait for those to be cut in half!!

[Nick2049]

THIS.

And if you combine that with the ability to create groups/organise layers into folders (and no, pre-comp'ing everything isnt a solution) then I will take back every bad word I've said about AE and probably give up and transitioning to an alternative 😄

[jenkmeister]

RAM Preview is coming... We are working on it right now. 🙂 

[DavidJackson]

Hey guys,

Not sure if this is related, but is anyone else having an issue when you playback (spacebar) I hit it and it plays my timeline, but i struggle to stop it playing. Escape nor space manage to. Eventually after hitting escape about 5 times it will stop, but very laggy playback too, the playhead jumps like it's catching up. 

Only really in the latest update: 18.1.0 (build 34)

[jenkmeister]

MFR isn't enabled for preview yet, so unlikely related. 

Are you on Windows? Do you have any monitor refresh software, like NVidia Gsync installed? We've heard some reports that Gsync is causing issues with playback lately.

[DavidJackson]

nope not on windows - on a mac.

[JohnColombo]

Hi @DavidJackson,

Sorry to see you are experiencing this issue. When you experience the playback being difficult to stop, what are the Resolution and Zoom settings of your Composition panel set to? Is the playback still difficult to stop if they are matched up e.g. Resolution is Full and Zoom is 100% or Resolution is Quarter and Zoom is 25%?

We have seen this behavior surfacing intermittently, seemingly relating to the GPU. What are your system specs and OS version?

Thanks for any further info,

- John, After Effects Engineering Team

[DavidJackson]

Res is half, scale is 25% as it's a pretty hefty project im on (4000x4000px) haven't tried playback at 100% and full res as it'd barely play at all for me.

Mac pro 7,1 16C 

192 GB 2933 MHz DDR4

AMD Radeon Pro Vega II 32 GB

[hellopaul4]

Out of interest (I'm speccing up a new system, but heavily constrained by CPU/GPU availibilty), which system achieved that fastest render of the benchmark project with an export time (with empty caches) of 3m 17s?

[jenkmeister]

AMD Ryzen Threadripper 3990X 64-Core Processor

256GB RAM

GeForce RTX 3090

[idkartist]

I can't find anything that specifically states it (since it's not in the "effects list"), but is the puppet tool supported by MFR? Also, sending all my love and support your guises' way - I'm absolutely overjoyed that this is finally happening! ❤

[jenkmeister]

It's not supported by MFR just yet. But it's on our internal list to get migrated, we have a test project in place so we don't forget and can track the improvement as we get it done. 

[idkartist]

Awesome, glad to hear! And thank you for the reply - very much appreciated!

[Valibean]

Really thrilled about this new feature. I tried it out, but can't get it to work properly. If I enable CUDA, I get this error:

with Mercury Software, I get this error:

Here's my system specifications

CPU: AMD Ryzen 9 5900X 12-Core

64GB RAM

GPU: Nvidia GeForce GTX 2080 Ti

Would love to get some help on this!

[jenkmeister]

The 10007 error should have been fixed in build x30. If you're on x30 or above and still seeing it, can you enabled Logging (Help -> Enable Logging), make the error happen, then use Help -> Reveal Log Files and email the After Effects Log.txt file to mfrbeta@adobe.com. We'd love to take a look at it.

If by chance you are able to send us the project to that same email address, we'd love to take a look at it for the software OOM as well. Thanks!