View Full Version : AE7.0 render stoped error?
ph2003 07-06-2006, 06:49 AM hi all,
well im running AE7 on Win2000 duoXeon3.0 2gb ram (lol, i know its not recomended.)
ive tried it on a heavy comp project so far.... likes 70ish levels involed.
when i render it... it will just stoped after the rendering done like 50%.... (only once... it done the rendering in all my rerender so far... otherwise it just stop at somewhere else..)
so i have to do another few more renders later to complete all the frames i have.
im render for uncompres .tga files (450 frames)
some plugin r used (shine, blurs, lenflares, etc)
any1 having this probelms with AE7 too?
or it just the OS problems.... idk but AE7 is working fine after i copied a .dll files from XP lol.
thx.
|
|
beenyweenies
07-06-2006, 08:25 AM
hi all,
well im running AE7 on Win2000 duoXeon3.0 2gb ram (lol, i know its not recomended.)
ive tried it on a heavy comp project so far.... likes 70ish levels involed.
when i render it... it will just stoped after the rendering done like 50%.... (only once... it done the rendering in all my rerender so far... otherwise it just stop at somewhere else..)
so i have to do another few more renders later to complete all the frames i have.
im render for uncompres .tga files (450 frames)
some plugin r used (shine, blurs, lenflares, etc)
any1 having this probelms with AE7 too?
or it just the OS problems.... idk but AE7 is working fine after i copied a .dll files from XP lol.
thx.
Try to pin down which frame # the render fails on, then look in your comp and see what is happening at that frame. If a new layer starts on this frame, it is suspect - could be a bad image file, plugin issues, etc. I doubt this is it, but is one of your plugins accidentally running in Trial Mode where it only allows you to render x number of frames?
Also, how much hard drive space do you have available? Goes without saying that if you don't have enough space, the render will die when it runs out of HD room. You should look at all of these variables, because I doubt it is After Effects that is causing the problem.
One last thing - 2Gb RAM is not much of a problem, since AE can only use 3GB anyway. Sure, if you frequently have multiple apps running at once adding more RAM can be useful, but for the most part I wouldn't be too concerned.
suztv
07-08-2006, 06:29 PM
I have had the same problems with AE7 crashing on both Macintosh G5 quad with 4G of RAM and PC Platforms with dual core processors and 2G of RAM. What I have found is that if your images are very large and unwieldly and used several times throughout your composition(s) - you will get out of memory errors or unable to render image at 2225 by 3000 (or whatever size the giant image is).
My best advice is to find the offending image and see exactly what size it is needed - then resize the image to that. If you have an image that at it's largest instance in the comp is only 1200 pixels by 800 pixels - but the original image is 3000 by 2000 then take it into Photoshop and pare it down.
After that reload or replace it in your project window. Of course you might end up having to re-animate or re-do some of your animation since the size won't be the same.
Also look at your memory cache settings - you do not want AfterEffects to use more than 70% of your RAM. That seems to be the magic number as far as preventing the program from having continual image rendering errors - that is just from personal experience and I have no idea if this holds true for other people.
I hope that this answers your question to some extent. Good luck on your project.
gmask
07-10-2006, 01:57 AM
On W2k or XP if you only have 2GB of ram then AE can really only use about 1.3 GB or ram so try setting the memeory cache in the prefs to 1.3 or less.
Kargokultti
07-10-2006, 10:12 AM
After that reload or replace it in your project window. Of course you might end up having to re-animate or re-do some of your animation since the size won't be the same.
Or you could copy-paste the transforms on the resized layer to a null layer > erase them from the original layer > see what it's scale is (remember to remove parenting for this) > go to Photoshop and Image size to e.g. 40% and save (saving the original by another name could also come in handy later on) > go to AE and set scale to 100% > parent it to the null layer, and the original animation ought to work.
(Sorry for the nitpick: coffee break + no life = nitpicks)
ph2003
07-13-2006, 08:30 AM
Try to pin down which frame # the render fails on, then look in your comp and see what is happening at that frame. If a new layer starts on this frame, it is suspect - could be a bad image file, plugin issues, etc. I doubt this is it, but is one of your plugins accidentally running in Trial Mode where it only allows you to render x number of frames?
Also, how much hard drive space do you have available? Goes without saying that if you don't have enough space, the render will die when it runs out of HD room. You should look at all of these variables, because I doubt it is After Effects that is causing the problem.
One last thing - 2Gb RAM is not much of a problem, since AE can only use 3GB anyway. Sure, if you frequently have multiple apps running at once adding more RAM can be useful, but for the most part I wouldn't be too concerned.
Hi. and thx for reply,
-ive tried to pin the number fails. but it wont work at all ( coz its stoped at random frame#) ><
-theres no bad frame images/ HD space problems here (30GB open space)
-the plugins i used r regeisted version not trail mode.
my proj was 1920 HD size (orriginal)
and resize down to 1024 (half HD size at final)
CGTalk Moderation
07-13-2006, 08:30 AM
This thread has been automatically closed as it remained inactive for 12 months. If you wish to continue the discussion, please create a new thread in the appropriate forum.
vBulletin v3.0.5, Copyright ©2000-2012, Jelsoft Enterprises Ltd.