-
Time warp out of memory – How to prevent?
Well. I’m using XP. I’ve got 6GB but obviously can’t use all of it. I haven’t performed the 3GB switch trick because 1) Msconfig doesn’t seem to make it possible to add “/3GB” to the BOOT.INI, 2) BOOT.INI is nonexistent on my machine, and 3) in any event, I’ve read horror stories about how unstable it makes the OS.
But that’s not really the issue. The issue is that TimeWarp is trying to grab more memory than it’s supposed to. Adobe’s own troubleshooting info on this issue is really sort of shockingly nonchalant. It acknowledges the bug and recommends doing projects in pieces to get around it.
I’ve tried that. I painstakingly split my project into three-second chunks (that seems to be the rough limit) and added each to the render queue. But it seems that merely splitting the project up makes no difference. I have to literally quit AE between each chunk. And this means that rather than being able to render this piece overnight while I sleep, I’m going to have to set my alarm every 30 minutes so I can restart AE and move to the next piece.
This, my friends, is bollocks.
I tried turning the disk cache on. This made no difference. I don’t know what else to do. So suggestions are very welcome.
-
3 Replies
-
you may be able to use the secret pref to force ae to purge the ram cache at specific intevals (which is what ae seems to be having trouble doing on its own).
to get the secret pref, hold shift while selecting preferences>general. then, from the pref window, use the dropdown menu to select a pref, and at the bottom should be one called ‘secret’.
choose it and set the ‘purge every xx frames’ value to a value that is less than where the crash occurs… if the crash is ocurring at about 3 seconds and you are wokring in 29.97 fps, then a value less than 90 would be appropriate… maybe 65-75, just to be safe.
if this works, when you are done with this project, don’t forget to delete the purge value from the secret pref. while it can help you out in a situation like this, usually it is not necessary and it will often hurt performance to some degree.
Kevin Camp
Senior Designer
KCPQ, KMYQ & KRCW -
That’s a pretty amazing trick. Thanks for helping out.
I gave it a whirl, but it seems that whatever bit of ram Time Warp is illegally utilizing is not part of what AE is able to purge. I watched ram usage during the render. Sure enough, it freed up 500mb at one point, but it was all used up again within three or four frames.
This bug is some serious fun.
-
well you could set the purge value to 3-4 frames to se if that will get you through the render… i’ve gone as few as 10 frames to get through a render.
if you have ‘render multiple frames simultaneously’ enabled, you might try disabling it. you’ll sacrifice processing power for extra ram available for the render, but if it finishes the render, it’s worth while.
Kevin Camp
Senior Designer
KCPQ, KMYQ & KRCW
Reply to this Discussion! Login or Sign Up