-
AE freezes during render
Afetr trying multiple times and formats, and searching the web extensivly, I can’t seem to get my sequence rendered out. I have a new mac pro, with 10gb ram and blackmagic decklink extreme card, the sequence is about 30seconds, and freezes around half way everytime. I have exported as a image sequence and it worked fine, but exporting as a movie/animation of any sort freezes the render, and if I stop the render, AE freezes. Any suggestions? I thought I might have a corrupt file, but if I render each layer out individually, they all render fine.
-
7 Replies
-
are you running a mac with osx 10.5 and quicktime 7.6…? i’m just wondering be cause i’ve been seeing several posts over the last few weeks with issues with apple codecs, and most of them have been running a version 10.5 and quicktime 7.6…
anyway, you may have an older codec that is interfering with apple’s animation codec. if you have a mac, try dragging all the files in the library/quicktime to a folder on the desktop. do the same for the files in users/username/library/quicktime. leave the system/library/quicktime folders alone, unless you know you installed third-party codecs (quicktime components) there.
then try restarting ae and see if you can render a lossless animation mov.
this may help in windows too, but i don’t know where windows puts quicktime components.
Kevin Camp
Senior Designer
KCPQ, KMYQ & KRCW -
Hmm, well I am running quicktime 7.6, but running Leopard, and this is CS4 After Effects. I just tried rendering out a Targa sequence and it froze again in the same spot. I’ll try this out and see what happens, but every codec I have tried has froze in the same area.
-
[Kevin Matluk] “I just tried rendering out a Targa sequence and it froze again in the same spot.”
sorry, i thought you had said that you had been able to render an image sequence… i was thinking that if the image sequence worked, but a quicktime failed, then it may be a problem with quicktime…
but if the image sequence is failing at the same point, i may be an effect that happening/changing at the point in the comp… can you identify any changes that occur at that point? it’s usually pretty easy, move the time cursor to that frame, select all the layers in the comp and hit ‘uu’ (that’s 2 letter u’s) to reveal all keyframed properties. look for any layers that start at the point, or any effects that have keyframes at that point.
you can try hiding layers that may be causing the problem until you find the one that is bad. then you’ll need to figure out how to deal with it… live without it, find an updated effect, find another way to do what you are trying to do at that point…
also, you’ll need to do this for any nested comp’s within the main comp…
Kevin Camp
Senior Designer
KCPQ, KMYQ & KRCW -
Well I tried file > export > image sequence and it worked, but if I try > composition > make movie, none of the codec’s have worked so far, The problem is the comp does not freeze in the exact same spot, but the same area (within 10frames) so its hard to tell exactly where the problem is. the whole comp is made up of about 15 other pre-comps so I have an idea of which I’m having trouble with, just not an exact frame. I’ll keep trying to diagnose the problem, thanks for the quick reply….
-
since file>export works, but the render queue doesn’t, it may be an issue with multiprocessing or the ram cache not clearing.
to disable multiprocessing, choose preferences>multiprocessing and disable ‘render multiple frames simultaneously’.
if it’s the cache, you’ll usually see the ‘ram’ value in the render queue hit the max ram cache value that is set in preferences>memory & cache (default is 60%). if you think that is the problem, then you can force ae to clear the cache at specified intervals…
to do this you need the secret pref…. hold shift while select any preference in ae (make sure you hold the mouse button down the entire time too). from the pereference window, click the pref dropdown and at the bottom should be one called ‘secret’. select it, then enter a value in the ‘purge every xx frames’ to a number of frames that is less than where the crash usually happens. so if it crashes at frame 100, try a value of 80 or 90.
note that when using the purge frames option, you want to make sure that you set it back to 0 when you are finished… there is a reason why adobe keeps it ‘secret’, it has some negative effects, namely decreased performance, and should only be used to get through a render that is giving you problems like this.
Kevin Camp
Senior Designer
KCPQ, KMYQ & KRCW -
Kevin,
I was just having the same exact problem trying to render a 720P composition in CS4. I’m using a worn out old P4 on XP-PRO (I know – I know -I’m building a new quad core) and it would freeze somewhere in the 47-60 second range no matter what codec I tried. I used the ‘secret’ tab and set it to 40 frames and got a successful render – THANK YOU!!
Jack
Jack Donnelly
Ball Ground Video Productions -
Found this thread on Google because I was having a similar problem. Disabling multi-processing did the trick! Thanks so much for the help.
Reply to this Discussion! Login or Sign Up