[Brian Charles]

When it worked BG render with nucleo was seamless. You could continue to work in in After Effects with no noticeable performance hit, though RAM preview was out of the question. One great feature is Commit to disk.

I would highly recommend the product, download a trial an check it out.

[Brian Charles]

Kevin, many thanks for the response. I’ve recently upgraded from a 4 core to an 8 core with 10GB of RAM.

I’d been using Nucleo Pro but on the 8 core with Leopard it seems to make AFX CS3 unstable, AFX crashed several times a day until I removed Nucleo Pro entirely. Gridiron hasn’t responded to my posts yet so I’ve been looking for an alternative.

I now use Lloyd Alvarez’s BG render script which can invoke Multiprocessing but has no control over how many cores are employed for the render — an option available with Nucleo.

I’ve done the prefs edit and it seems to work: according to activity monitor 8 copies of aeselflink launch but only 4 gobble the available RAM.

[Brian Charles]

Waving the dead chicken over the keyboard produced no discernible results however removing Nucleo Pro from the Plug ins directory did.

I’m not certain where the conflict lies but I haven’t crashed once since removing Nucleo.

[Brian Charles]

If you’re intending to animate the covers in a similar fashion, you could animate one cover then duplicate the layer and use the valueAtTime expression to offset the other animations.

Something like this could work:

thisComp.layer(index-1).transform.position.valueAtTime(time-.25)

making sure the layer is below the controlling layer. The offset in time is controlled by the (time -) part of the expression so .25 is 1/4 second.

[Brian Charles]

Hmmm. Sounds like more troubleshooting for me.

I was running on first gen Mac Pro Quad using 10.4.1 before with no issues.

Thank you both for the replies. I do have Nucleo which I find indispensable. Perhaps I should chuck it.

I’ve repaired permissions, done Onyx cache cleaning etc. Next I’ll light some incense and wave a dead chicken over the keyboard…

[Brian Charles]

I have a similar problem when I try to rename any item in the project panel. If I’m too quick and click away before typing an new name I crash with an error message.

I’ve learned to tread gingerly and slowly when using the project panel.

Mac Pro 8 core, 10GB RAM, 10.5.2, QT 7.4.1

[Brian Charles]

I did manage to quit. Not by force quitting which invoked the error message — rather I right clicked on the AFX icon in the Dock and selected Quit — which brought up the Save dialog.

I saved, rebooted, opened the file and thankfully had lost nothing.

File this under weird.

[Brian Charles]

In one render session yes, its possible. Just duplicate the item in the Render Queue and change the render settings to match the output you want.

You’ll produce 2 separate files.

[Brian Charles]

Hi Peter;

I’ve haven’t a clue. I’ve never experienced this problem. You may be right, Adobe needs to update their 3D engine.

[Brian Charles]

I agree with Dave. Changes in camera technology mean you may replace a camera every three years. No so tripods, mics etc.

That said, I’ve seen and love the new Sony EX1.

Put your money into mics and tripods, rent the camera you need for now.