View Full Version : uggghh memory issues
cheezweezl
03-16-2008, 06:16 AM
i keep getting various errors popping up saying i need to lower my ram cache and enable disk cache. both of which have been done. my ram cache is at the minimum 10% and disk cache is set to a max of 15gb. i have 6gb ram. ae only sees 3gb so i know i'm not short on ram. i have tried different ram setting combinations, enabled multi-processing (i have an 8 core mac), trashed prefs, reinstalled, etc. when it happens i can't touch anything or it keeps popping up. if i purge cache and undo it goes away for a while. sometimes i get errors during rendering but i notice that every time it happens ae has gone past the 10% cache level i set for it and has reached 100%.
anybody else having similar issues? anybody have a fix?
oneinfiniteloop
03-16-2008, 09:55 AM
which version of AE?
EDIT: you mentioned enabling multi-processing, so you're obviously using CS3. There is a secret menu that purges every nth frame that others have said to be helpful. I don't see why it would do that, I have a MBP with 3GB of RAM, and I'm set at 60% and I have no problems. What update are you using?
seejay1031
03-16-2008, 10:49 AM
Set your ram cache back to 60%.
Holding the shift key go to Composition > Preferences > General
Preferences will pop up, use the pulldown menu and choose the new option "Secret"
There are 3 options here, leave Disable Layer Cache and Ignore Sequence Rendering Errors alone.
On the purge every ___ frames during make movie choose a number like 15 and see if that works, if it doesn't try again but with smaller numbers.
If this doesn't work, you might have to reapproach your rendering order. Say your project is high resolution (1080P) and you have multiple precomps within, all 3d with lights and shadows to render. You could try prerendering any precomps. If everything you need AE to do in a single frame takes more than memory available, you need to figure a more efficient way to animate the scene. And without looking at the project, its needs and the way its currently setup, its hard to give any specific advise.
cheezweezl
03-16-2008, 01:52 PM
Set your ram cache back to 60%.
Holding the shift key go to Composition > Preferences > General
Preferences will pop up, use the pulldown menu and choose the new option "Secret"
There are 3 options here, leave Disable Layer Cache and Ignore Sequence Rendering Errors alone.
On the purge every ___ frames during make movie choose a number like 15 and see if that works, if it doesn't try again but with smaller numbers.
If this doesn't work, you might have to reapproach your rendering order. Say your project is high resolution (1080P) and you have multiple precomps within, all 3d with lights and shadows to render. You could try prerendering any precomps. If everything you need AE to do in a single frame takes more than memory available, you need to figure a more efficient way to animate the scene. And without looking at the project, its needs and the way its currently setup, its hard to give any specific advise.
cool. thanks i will try this. and i wouldn't be griping if my comps were as complicated as you are talking about. right now i'm doing a 720p simple key with a gradient solid background. no 3d. no lights. no particles. nothing. keeps sh*tting on me...
cheezweezl
03-18-2008, 03:07 PM
the secret menu trick did it!!! thanks you guys. what would i do without this place????
graymachine
03-24-2008, 03:31 PM
You still might want to add some more RAM. While the application itself "sees" 3GB, clicking the multiprocessing button will launch am additional AE renderer in the background, one for each core.. and each wanting up to 2GB of RAM.
Plus, as I sit here typing... only running Firefox and my OS, I am using 1.9GB of RAM. It runs out very quickly!
But, the "secret" option will work, at the cost of speed. Just something to think about.
I dropped another 8GB in mine from Ramjet for around $400 and change. Considering the cost of the computer, it has been WELL worth it. I used to get these same frustrating errors in 720p comps. Since the new RAM, I've not had any.