Archive for December, 2009

December 22, 2009

Performance tip: Don’t starve your software of RAM.

I find myself giving the same advice over and over on various forums, so I thought that I should say it here, too.

Give your software enough RAM to work.

This means making sure that you’ve allocated enough RAM for each process when using Render Multiple Frames Simultaneously multiprocessing, and it also means setting RAM To Leave For Other Applications to at least 2GB (preferably more, around 1/3 of installed RAM).

If you don’t set your Minimum Allocation Per CPU high enough, or if you don’t set RAM To Leave For Other Applications high enough, then you are going to experience the inevitable problems of multiple components both within and outside of After Effects fighting over memory, which slows things down. One of the things that can really kill your performance is essentially telling After Effects to fire up all eight cores in an eight-core machine and then starving those cores of RAM—which is what happens if you set your allocations too low and don’t have much RAM. And if you make the operating system swap RAM to the hard disk because you haven’t given enough RAM for other applications, then you’ve really thrown some serious speedbumps in the way.

It seems that a lot of people have machines with eight processor cores and far too little RAM to feed all of those cores. It is far better to leave some of those processors idle than to try to make them run and then have them shut down because they don’t each have enough RAM to render a frame.

Let’s take an example of a computer with eight processor cores and 24GB of RAM:

For HD, you want at least 2GB for each process; preferably 3GB. And you almost always want to leave at least 2GB for other applications (preferably more, around 1/3 of installed RAM). That leads to some relatively simple math. For an eight-core system with 24GB of RAM, leaving 8GB for other applications gets you down to 16GB. The foreground process takes 1.2 times the RAM allocated for background process, so that is 3.6GB in this case, leaving 12.4GB of RAM. That’s enough RAM for four background rendering processes at 3GB each.

(For RAM previews, there’s the extra detail that the foreground process has a RAM cache that it uses to hold rendered frames. In After Effects CS4, you can give more or less RAM to this cache with the Longer RAM Previews / Faster Rendering slider. If you drag that toward Longer RAM Previews, then you take RAM away from the background processes that do the rendering. In After Effects CS5, this is handled automatically.)

To get the most from After Effects CS4 out of your computer with eight processor cores and a 64-bit operating system, you would have 32GB of RAM. (For After Effects CS5, you can go higher.) If you don’t have that much RAM, then do yourself a favor and set the preferences that I’ve mentioned in this post so that you’re optimally using what you do have, rather than forcing your operating system and applications to fight over scarce resources and thus bog things down.

Here’s another tip: In some cases, performance is improved by using fewer than the maximum number of processors for Render Multiple Frames Simultaneously multiprocessing, even when you have enough RAM for all of the processors. See “Performance tip: Don’t overschedule your processors.”

Also, check out “Improve performance” for some additional tips on improving performance.

Of course, all of the numbers that I give here are just intended as a starting point. Every composition is different, and every computer system is different. The reason that there are Memory & Multiprocessing preferences is so that you can set things as appropriate for your work.

UPDATE: Here’s an updated page in which we recommend some memory settings for After Effects CS5 and ask for feedback:
“Please try recommended memory settings for After Effects CS5 and give feedback.”

9:17 AM Comments (0) Permalink
December 3, 2009

improved search for After Effects CS4 Help

I’ll spare you the gory details, but the quick version is that we just moved our “This Help System Only” searches to a new search platform—the same one that we’ve been using for the “All Community Content” searches.

The gist is that search results should be much better now when you’re just searching within our Help documents.

If you have any problems with searching After Effects CS4 Help, let me know. That includes telling me if you searched for something and couldn’t find it, as well as just not knowing what word to search for.

11:08 AM Comments (0) Permalink
December 2, 2009

ProRes 4444 colors and gamma shift when working with After Effects CS4 and Final Cut Pro

[For After Effects CS5, see "ProRes 4444 and ProRes 422 in After Effects CS5".]

If you use Apple’s new ProRes4444 codec with After Effects CS4 and Final Cut Pro, you may notice a gamma shift (i.e., colors will seem to have too much or too little contrast) when you bring the movies rendered and exported from After Effects back into Final Cut Pro.

To avoid this gamma shift, you’ll need to edit your After Effects CS4 QuickTime gamma rules XML file. This will add the appropriate gamma tag to your QuickTime files on output.

The XML file is found here:

[hard drive]/users/[user name]/Library/Application Support/Adobe/Common/MediacoreQTGammaRulesCS4.xml

Using textedit.app or a similar text editor, add the following line to your MediaCoreQTGammaRulesCS4.xml file:


<QTCodec codec='ap4h' vendor='****' platform='mactel' direction='encode' versionlow='0x00000' versionhigh='*' gammatag='true' />

‘ap4h’ is the 4cc code for ProRes4444. You’ll notice that the XML file already includes entries for ‘apcn’ and ‘apch’. These are the 4cc codes for the older flavors of the ProRes codec.

Once you’ve made this change, you should be able to round-trip ProRes4444 media between Final Cut Pro and After Effects without experiencing a gamma shift.

For more information on preventing color shifts when working with ProRes codecs, see this post:
“ProRes 422 colors in After Effects”

For more information on gamma shifts with QuickTime and Apple software, see this section:
“QuickTime and gamma in non-color-managed projects”

Here’s a thread on the MoGraph forum in which Dan presents the same solution.

(UPDATE: For After Effects CS3, see my response in the first comment below.)

1:17 PM Comments (0) Permalink

FAQ list for After Effects

On the Adobe After Effects user-to-user forum, we have a list of frequently asked questions. These are the questions that I (and others) on the forum answer many times each week, so it’s convenient to just be able to point someone to an answer instead of typing the same answer time and time again. We intend for this to be a resource for others to use as they answer questions, too—either for themselves or for other folks on other forums and such.

Do you have any suggestions for additions to this list? Do you have any additions to make to the answers? If so, come on over to the forum and let me know in the thread on this topic.

FAQ: Why doesn’t After Effects see and use all of my RAM?

FAQ: Why does RAM preview only play part of my composition?

FAQ: Why are my vector graphics (e.g., from Illustrator) jagged or soft?

FAQ: Why is there no audio (sound) in my output file?

FAQ: How can I play or preview sound (audio)?

FAQ: Why does my layer (camera) move back and forth between keyframes of equal value?

FAQ: Why won’t After Effects import my PSD file as a composition but flattens it?

FAQ: Why doesn’t AVI appear as an export format in the Render Queue?

FAQ: Why do FLV files with transparency from After Effects look bad in Flash?

FAQ: Why isn’t the anchor point centered in shape layers?

FAQ: What’s the difference between Make Movie and Add To Render Queue?

FAQ: How do I quickly center a layer in the Composition panel?

FAQ: How do I create a new composition that matches my source file(s) dimensions, duration, frame rate and pixel aspect?

FAQ: Why does only a section of a motion path appear in the Composition panel?

FAQ: How do I make fire, fog, smoke, or explosions?

8:54 AM Comments (0) Permalink