“not enough memory to create cachet…”

[Kevin Camp]

512mb of ram is pretty limiting for ae, most people are using 5-10 times that amount, although ae can only use 2-3gb of ram, having more allows the os and other apps to not take it away from ae.

that being said, i do think that enabling disk cache in the memory prefs would be a good idea. it’s not going to hurt anything, it just allows ae to use some disk space when it runs out of ram. additionally, you may want to use the secret pref by holding down the shift key while selecting any pref, then, at the bottom of the pref pulldown will be ‘secret.’ select that and enter a value for the purge every xx frames to about the frame number that your systme is crashing (if it crashes at 13 frames, set purge to 10 frames). all this does is tell ae to clear ram at designated intervals, it may increase render time, but it won’t hurt anything.

i would also suggest, rendering via the add to render queue function from the compostion menu. this will put your render in the render queue, which, aside from giving you many more render options, will allow you to continue a render where the last render failed. so if your first render quit on frame 13, ae will create a new render in the queue that starts at frame 13. you can then edit your renders at the end and render out a complete animation.

you may also want to set up pre-comps of some of the layers in your comp. you can then pre-render those pre-comps, and throught render queue, you can set up post render actions (twirl down the output module to find) that will import and replace usage of the pre-comps (it won’t delete the pre-comps, just replace them in you main comp). that should allow your final comp to render much easier.

Kevin Camp
Designer – KCPQ, KMYQ & KRCW