Re: Is 'incompatible effect/MP off' temporary?

Well, that is a bit pants really then isn't it!

I am starting to really crave AE7 Pro + Nucleo at the moment....I have noticed loads of memory/multiprocessing glitches since we upgraded to CS4, on ALL of our VFX macs.

A few off the top of my head (in addition to the aforementioned fairly major one): -

- RAM Previews take an age to start up when MP is switched on (this is compared to Nucleo firing up the same amount of cores alot quicker)

- Instigating a RAM preview with MP on often results in a crash. AE says it is saving project just before making the RAM preview, but that save point isn't reflected in the file (where does that process save to?)

- In CS4, with MP switched on OR off often I will lose all my RAM cached frames (the green line) totally randomly. Sometimes if I have made a RAM Preview, if I then hit '0' again to play it again the green line disappears and it has to start building from scratch again. Or I could be scrubbing within that green line and suddenly it just disappears!?

- When rendering with MP switched on and 'skip frames' on more than one machine (network rendering TGAs to a central destination folder) the machine that starts second, or is 'behind' will take almost as long to check and skip already rendered frames as it would take to just render them from scratch!! AE definitely says it is skipping them, but takes several minutes per frame to decide if it's been done or not. Doing the same thing in Nucleo with several machines works a dream.

- In CS4, despite alot of tweaking of the MP prefs, no matter how many processors/RAM I leave for other apps, AE totally takes over the mac and hogs all available power by the looks of it. Even surfing Safari is painful. Again, with Nucleo it uses as much as it can but still leave the mac useable for light work at the same time.

- In CS4 (w/MP on) the activity monitor almost NEVER says it is using the CPUs to full capacity. In Nucleo it regularly states 100% CPU activity across the board.


I'm slighty confused by all this, as I was under the impression that CS4 merely used the code from Nucleo under the hood anyway?

Sorry for the rant, but apart from a few nice new tools CS4 has been a living nightmare for us! And of course, any work you've done in it cannot be back tracked to CS3 or AE7!

Fantastic.

Please let me know if there is somewhere else I should be listing these bugs. Cheers.

Production Premium CS4 - Mocha v1.5 - FCP 5.1.4
MacPro Quad 3GHz / ATI 1900XT / 8GB RAM / OSX 10.4.11
30" ACD / Decklink SP / SONY PVM-20M4E/ Wacom Intuos 3 A4 / XServe / United Digital RAID
---------------------------------
Production Premium CS2 - Combustion 3 - Mocha v1.0.1
Win XP Pro 32 / Dell Precision T3400 Q6600 / 4GB RAM / NVidia Quadro570 / DeckLink Pro / Roland DS-5s / Sony BVM-20G1E / 2 x Dell 2007FP / Wacom Intuos 3 A4