I’ve been to the mountain: Adobe. Answers. One question.

[Itamar Kool]

Hi Eric, Thanks for your remarks. The 9 gig resulted from buying 8 gig extra on a machine that had standard 1 gig of RAM. I know for sure that the 8 gigs were divided in 4 modules. The 1 gig was divided in 2 (512MB each). I don’t know nothing about this 256-bit memory access mode. How do I get there??
Thanks in advance

Kool En De Anderen
MAC Pro 8 core/OS 10.4.11/Kona LHe/Apple FCS 2/Adobe PPCS3/Huge fibrechannel
http://www.koolendeanderen.nl

[Eric Berna]

Kool,

Apple has thorough instructions at:

https://manuals.info.apple.com/en_US/MacPro_Early2008_MemoryDIMM_DIY.pdf

Just use your four 2GB modules, without the Apple memory.

Eric Berna

[Itamar Kool]

Thank you Eric!

Kool En De Anderen
MAC Pro 8 core/OS 10.4.11/Kona LHe/Apple FCS 2/Adobe PPCS3/Huge fibrechannel
http://www.koolendeanderen.nl

[Chris Poisson]

Hi Steve,

I never knew about the multiprocessor thing in CS3, will that help or compete with Nucleo Pro? I rendered a file this morning with Nucleo Pro 2 which took about 25 minutes, and while it was rendering I read this thread. When it was done, I enabled multiprocessing and rendered the same file again without Nucleo, it looked like it was going to take less than half the time, but it locked up half way through. So what’s happening here?

Have a wonderful day.

[Itamar Kool]

One thing is for sure: you can’t do both at the same time. You have to disable Nucleo Pro 2 when you use Adobe multiprocessing and the toher way round. I disabled NP myself. Just didn’t feel stable enough

Kool En De Anderen
MAC Pro 8 core/OS 10.4.11/Kona LHe/Apple FCS 2/Adobe PPCS3/Huge fibrechannel
http://www.koolendeanderen.nl

[Steve Forde]

Multiprocessing in CS3 is identical in nature to Nucleo standard. In other words – the features of fast-render and fast-preview found in both Nucleo Pro and Nucleo are what you get in CS3. They behave almost identically – and for the most part achieve the same result.

Nucleo Pro does things like Background Render, Spec Preview / Render, Commit to Disk, Pre-comp proxies etc., which neither Nucleo standard nor Multiprocessing provide. Since Nucleo Pro maxes out CPU in all features – CS3 multiprocessing must be disabled when using NP2.

As for what could be locking up Multiprocessing and not locking up NP2 – unfortunately is difficult to track as they both use different architecture yet similar approach. Some users have reported that NP2 is slightly faster than Multiprocessing but both are designed to achieve max performance.

Steve
GridIron Software Inc.