[Michael Uman]

i watched a few of there tutorials this morning and the work flow stuff seems very usefull…It sounds like for the basic program though you get the same preview and render boost that you would get from cs3 rendering on all the cores.
M

[Michael Uman]

from what i’d been reading on this forum i thought i could get away with ten gigs of ram (8 gigs to ae) and add the extra later on… Since I’m considering not building the array i can afford the extra ram.

Smart work flow also depends on the animator and there knowledge of AE…I rarely touch AE anymore (I’m a creative director/partner) but came up very hands on using it from 1.0 when it was still owned by Cosa…I still have the box and dongle to prove it. Since computers have become so much faster i find a lot of younger animators have pretty bad work flow habits since they didn’t come up when you had to understand what good work flow was.lol. Kids these days.Of course HD changes all of this and we are now back in the stone age of renders that take hours instead of minutes again…thus me trying to set up the zippiest system i can for those HD projects.
I find myself often in the role of explaining and educating my hires in the benefits of good work flow…All of what you have listed is vital in render pig projects. 🙂
cheers
M

[Michael Uman]

Thanks for the suggestions…We’re definitely going to need disk caching since there’s going to be a lot of previewing…I had forgotten about the whole bus load issues. An external firewire 800 drive is a very affordable solution to that problem as well… I may even have a few lying around that i can run some tests before having to buy a dedicated one.

My initial excitement about the internal Caldigit solution is fading since i have discovered if i want to use external drives as well they only work with the caldigit element drives…it still sounds like a great internal solution though…just not as expandable(for a reasonable price) as i had originally thought.
cheers
M