This content has been marked as final. Show 6 replies
More ram will only let you have faster renders, if you configure ae carefully. For the actual time when you are working on the project the only way to reduce freezes is to be very careful with the files you use and to organize tightly the project: use all the tweaks given by ae: pre- composing when necessary, use proxies, reduce input file size when possible. Freezes are probably due to ae needing time to gather the data from the disks for the elements you are displaying on the frame. The smaller the files, the faster ae will fetch them. Sometimes it's a tiresome job of recompressing hd movies that you really don't need in hd resolution, or converting huge psd files in smaller versions, if you don't need the size or the layers, but it definitely changes things. Even your render times will benefit. A while ago I had to use a 2500x1500 pixels psd layered file, but I really didnt need the layers, so I just converted it to a jpg at maximum quality and render time fell from 2hrs and a half to less than one hour.
I'm working on fairly complex projects and I noticed that for me a LOT of the freezes and crashes (that on my mac are spinning beachballs) are directly related to how ae handles audio (=awfully). if you got audio on your projects, try to disable audio preview in the ram preview pane (just disabling the sound from the audio track won't work). I found that a lot of freezes when pressing 0 to preview the comps simply go away if i shut audio preview.
I have an 8 core Mac Pro with 10 gb of ram.
Ah, it's good to know I'm not the only one having problems. And interesting the problems don't stop even on a powerful machine. Do you just use AE on its own or do you have other apps running while you're working?
Audio is a good point... thinking about it most of the problems I've had are to do with projects which either feature audio, or DV video (as opposed to stills or layered PS files). I think I'll leave the memory for now as it was going to cost about £500 anyway :O
Check to see if your laptop can be configured with more than 4gig before you consider purchasing it.
>> Do you just use AE on its own or do you have other apps running while you're working?
having other apps running doesn't change things, because ae cs3 on the mac can use a maximum of 3 gb of ram, so that leaves my other 7 for the system and other apps, which usually is enough.
The rest of the ram comes handy if you render with multiprocessing on, so that each process can use one or more gb. in the end the problems are caused by ae - wich probably needs a rewrite from scratch since it feels like it's built on a structure that is not optimized for huge amounts of data and is not capable of using all the resources of the multicore systems of today.
>>Audio is a good point... thinking about it most of the problems I've had are to do with projects which either feature audio
I don't work often with dv video, but I use a LOT of layered psd files and I can tell you that in this case - as I wrote - using 'flat' versions when possible speeds things up a lot. mayve a 60 megs psd file can be replaced by a 2 megs hi def jpg if you don't need the layers... ae will be really really happy.
do a little experimenting: try to discover what causes the freezes, try different ways of organizing your comps. for example I discovered a weird situation in which the same contents subdivided in 8 sub comps caused a delay in the audio preview. audio disabled: no delay. then i pasted all the layers from each subcomp in one main comp and the audio preview was without delay again.
all in all, though, the problems get worse together with the complexity of your composition.
Each 32-bit application can only address a maximum of 4 GB of RAM under Vista 64, but AE's "Render Multiple Frames Simultaneously" will start hidden background-copies of AE, each using up to 4 GB of RAM. Adding more RAM will let you use more processors for this kind of multi-processing, plus it will let you run other programs in the additional amount of RAM.
Audio problems often stem from people using weird codecs or highly compressed formats such as MP3. If you are having problems, an easy fix is to use something like Audacity, Adobe Soundbooth or QuickTime Player Pro to transcode (re-save) into common formats such as WAV or AIFF.
- Jonas Hummelstrand
(4-processor Mac Pro with 16 GB of RAM)
>> Audio problems often stem from people using weird codecs or highly compressed formats such as MP3. If you are having problems, an easy fix is to use something like Audacity, Adobe Soundbooth or QuickTime Player Pro to transcode (re-save) into common formats such as WAV or AIFF.
it may be helpful to note that the behaviour I described is showing using only uncompressed 44.1khz, 16 bit wav or aiff files