-
Multiprocessing disabled – limited to just precomp?
Hi all (mainly Todd if you’re about?)
I’m having more problems with multiprocessing being ‘rendered’ useless in my project and I’m trying to fully understand the rules/laws of AE’s management of when it disables multiproc…
Basically I have a giant project, which is 30+ minutes long. The main comp I am rendering has no effects applied DIRECTLY in it, however some of the nested comps (or rather comps nested within other comps) do have some temporal effects. (Twitch, pixel motion, twixtor)
What I want to know is, if I know roughly where the offending effects are and I position my work areas so as not to include these for my multi-proc renders, should AE render these non-offending parts of my comp with MP switched on? i.e: does it switch off if there are any of these effects present ANYWHERE in my main or nested comps, or should it only switch off if it needs to actually render those parts?
I hope that makes sense! I can’t seem to find a way of getting around this and I’m having to resort to pinching everyone’s workstations on skip frames to get this job done, when I should be only using 8 processors on ONE workstation! Not good for productivity..
The thing that bugs me the most about this is that in AE7 using Nucleo this very same project would whizz through like butter on all procs and now that I have used CS4 to update it I can’t go back and it’s at a crawl.
HELP!