-
Ram stops working in the middle of export
Hello, I’m on a 2x Quad Core Intel Mac pro with 32gb of ram, running After Effects CS4. I have multiprosessing enabled and I’m working in adaptive resolution. I do extremely heavy 2.5D comps. The system has been great so far but I’ve been having problems occasionally on my exports. I go through the render cue set all my settings to my likings and hit render and also enable caps lock for faster render.
Usually when I export it’s quick and fast with all 8 cores using 3gb or ram, when looking at the activity monitor you can see the ram is maxed out and everything is quick. But for more complex comps i’ve been finding that the export starts out quickhttps://i147.photobucket.com/albums/r291/Genesis_089/Picture7.png
[IMG]https://i147.photobucket.com/albums/r291/Genesis_089/Picture7.png[/IMG]with an estimated time of 10min lets say, and all cores utilizing the max amount of ram, then about a quarter into the export the estimated time shoots to like 30min to 40min and suddenly the ram usage suddenly drops almost completely.
https://i147.photobucket.com/albums/r291/Genesis_089/Picture11.png
[IMG]https://i147.photobucket.com/albums/r291/Genesis_089/Picture11.png[/IMG]to this
https://i147.photobucket.com/albums/r291/Genesis_089/Picture14.png
[IMG]https://i147.photobucket.com/albums/r291/Genesis_089/Picture14.png[/IMG]In other words it’s like the multiprosessing or cores stop working I guess.
Is their a reason for this to be happening, I’m trying to figure out if this is a software bug or if it’s a system thing, has anyone else had such things happen? It seems to happen for more complex and heavy comps.Many Thanks in advance.
-
4 Replies
-
i notice that the ‘adobe after effects 9.0’ cpu usage increases as your aeselflink processes decrease. i’ve seen this happen when an effect is used that does not allow multiprocessing is used forcing all the rendering to be done by the foreground process (the ‘adobe after effects 9.0’ process is the foreground process)… in my cases it’s been effects like cc time blend and particle playground.
here’s a page from the manual that talks about some of the things that can effect multiprocessing:
https://help.adobe.com/en_US/AfterEffects/9.0/WSDD65B476-971A-48e9-A5FD-D90E9A2B996E.htmlKevin Camp
Senior Designer
KCPQ, KMYQ & KRCW -
Thanks for the feedback, I have a follow up question,
Is their a reason why the comp is able to export in hallf resolution without multiprocessing shutting down but is unable to at full resolution?
-
are you using any effects that use opengl? it may be that opengl is only kicking in at full res, and when it does kick in it disables multiprocessing at that point…. but that’s just a guess… it does seem pretty odd that that would happen.
you might post on adobe’s ae forum and see what they have to say about that… i’m curious…
Kevin Camp
Senior Designer
KCPQ, KMYQ & KRCW -
Thanks for the responses, yea i posted on the adobe forum and a member told me this
You are using a large blur, glow or similar effect somewhere that dilates/ expands the buffer beyond what the RAM assigned to the background instances can hold. Since the BG instances are solely controlled by the AE process manager, they have no way of directly requesting more RAM (or disk swap memory) from the operating system and thus shut down. The single remaining instance of the main program doesn’t suffer from this limitation. At half resolution it naturally works, as the processing of the effect(s) that make everything go *poof* at full res is naturally also based just on teh half res version, hence it may be just enough.
It’s a little dissapointing to find out that the ram will not be getting utilized to it’s full potential when working in very heavy comps, i really do hope this issue gets resolved when CS5 is released.
Thanks again for the feedback
Cheers
Reply to this Discussion! Login or Sign Up