[Ron Davis]

Thanks for the responses, yea i posted on the adobe forum and a member told me this

You are using a large blur, glow or similar effect somewhere that dilates/ expands the buffer beyond what the RAM assigned to the background instances can hold. Since the BG instances are solely controlled by the AE process manager, they have no way of directly requesting more RAM (or disk swap memory) from the operating system and thus shut down. The single remaining instance of the main program doesn’t suffer from this limitation. At half resolution it naturally works, as the processing of the effect(s) that make everything go *poof* at full res is naturally also based just on teh half res version, hence it may be just enough.

It’s a little dissapointing to find out that the ram will not be getting utilized to it’s full potential when working in very heavy comps, i really do hope this issue gets resolved when CS5 is released.

Thanks again for the feedback
Cheers

[Ron Davis]

Thanks for the feedback, I have a follow up question,

Is their a reason why the comp is able to export in hallf resolution without multiprocessing shutting down but is unable to at full resolution?

[Ron Davis]

Many Thanks for the feedback everyone, i just wanted to be sure since the Certified Data Ram was a bit cheaper then the Kingston, I guess it’s just brand prestige.

Cheers

[Ron Davis]

Thanks for the feedback

Just to be sure, since i did the preference hack and changed the MaxNumberOfProcesses from 0 to 4 is it still recomended to also have multiprocessing enabled?

Many Thanks

[Ron Davis]

Thanks for all the great info.

You were right the first time, I do indeed have an 8core Mac, I accidentally typed quadcore when I should have put 2 x quadcore.

Anyhow I did the preference hack and changed the MaxNumberOfProcesses from 0 to 4. In my activity monitor I now have 4 multiprocessing engines instead of 8 and each one is giving me a CPU reading ranging from 0.5 to 0.8 while the main CPU ranges from 100 to 200. I’m thinking that’s pretty good, after doing allot of tweaking the speeds are getting a little better.

Does everything I did here sound correct?

Here’s a question I have, could it be that taking a consolidated AE7 project with dozens of HD layers and then converting it to CS3 could result in sluggish performance since the project wasn’t conceived in CS3. Could it be that if the project was created in CS3 from scratch then speeds would be better?

Many thanks in advance again.

[Ron Davis]

Thanks for the quick response.

I’m actually working of a RAID so the disk array hopefully shouldn’t be an issue. The thing is that I was expecting to get significant increases in speed on this new Mac but that hasn’t happened so far, so maybe I shouldn’t be expecting speeds to increase 10 folds.

Is their any chance that converting a complex project from AE 7 to AE CS3 can create slowdown since the project want conceived in CS3?

Anyhow thank you very much for the advice, I will try implementing everything you listed and see how it goes from their. I just really want to rule out the issue that the graphics card can be causing these issues? Are certain graphics cards that would be more recommended then others for AE CS3?

Many Thanks again