Re: RENDER problems - Nucleo?

At the point where the render fails (the start of a new layer) I suspect one of the Nucleo render processes fails to render a frame. After Effects itself will display an error message but all Nucleo knows about the render processes under it's control is that they fail and crash.

The resolution you are rendering to is approx. 2.5x larger than a 1080p frame. We recommend at least 2 GB per core for HD resolutions so it probably is a memory limitation.

When Nucleo's render fails it passes the render duties back to After Effects. Although the QuickTime file is there, since it failed to finish the render queue item isn't marked as done and now After Effects wants to start from the beginning to redo the render (and overwrite the incomplete QT).

If you look at the Resource Settings window (in the Nucleo status icon menu in the menu bar) you will see the setting the Nucleo render processes are using as RAM Cache values. The render processes are faceless After Effects processes and the total memory they can use is about double the RAM Cache number. So if you are seeing 30% listed then each one has a RAM Cache of 30% and total memory of 60%. The percentages are of the total any one After Effects process can access - about 3 GB on Mac OS X, 2 GB on 32-bit Windows and 4 GB on 64-bit Windows.

To increase the amount you need to:
- quit other memory hungry apps before starting AE
- lower AE's RAM Cache (and restart AE) so that there is more to go to Nucleo
- lower the number of Nucleo processes (it defaults to one render process per core)
- add more RAM

The work around in this case may be to render with Nucleo the portion of the comp that works to an image sequence and then use just After Effects to render the chunk that needs as much RAM as it can get.



Chris
GridIron Software - Verification and Customer Support
Check our Frequently Asked Questions (http://www.gridironsoftware.com/pg/Nucleo_FAQ)