Fast previews renders with an "X"
by Suzanne Hemphill
on
Jul 31, 2007 at 3:34:14 am
When rendering using fast preview (Nucleo Pro 2.0, MacPro, 8 core) I am getting an "X" over a few of the frames. I am not using any third party filters on those particular frames, so that is not the issue. Does anyone have any clues to this problem?
Re: Fast previews renders with an "X" by Steve Forde on Jul 31, 2007 at 2:48:02 pm
[Suzanne Hemphill]"When rendering using fast preview (Nucleo Pro 2.0, MacPro, 8 core) I am getting an "X" over a few of the frames. I am not using any third party filters on those particular frames, so that is not the issue. Does anyone have any clues to this problem?
"
Those are the frames that Nucleo rendered. Are you sure you aren't using the demo version of Nucleo Pro?
Re: Fast previews renders with an "X" by Suzanne Hemphill on Jul 31, 2007 at 4:57:41 pm
I am using a registered version, but that problem has gone away and I have a new one. I am rendering and getting no audio. I rendered without Nucleo Pro and the audio is fine. The audio is just missing when I render with Nucleo Pro. I tried rendering again, and I checked to make sure that I have checked the audio box in the output module, and it still will not render the audio.
Re: Fast previews renders with an "X" by Grantly on Aug 1, 2007 at 10:41:13 am
I've had this problem before and it is sometimes inconsistant in how it works. I've narrowed down to 3rd party plug-ins that don't seem to like the launching of multiple instances that Nucleo uses (one instance per core or processor).
The best way to find the offender is systematically check each 3rd party plug in and then report it to the developer to get fixed.
Re: Fast previews renders with an "X" by Reins on Aug 9, 2007 at 8:24:11 pm
I have had this occur when using Boris Continuum. I was thinking it was a Boris problem. Could it be because Boris has multiprocessor option, and when that is turned on it interferes with Nucleo's multiprocessor renderings? Did that just make sense?
Re: Fast previews renders with an "X" by Reins on Aug 9, 2007 at 8:50:06 pm
I did the following 3 tests
A. Nucleo Pro ON, Boris CC multiprocessing ON
Got Xs through layers with a Boris filter applied.
B. Nucleo Pro OFF, Boris CC multiprocessing ON
No Xs in final render.
C. Nucleo Pro ON, Boris CC multiprocessing OFF
No Xs in final render. (much faster option than B of course)
So this seems to follow the same rule about turning AEs Multiprocessing functions off. The way I see it, only Nucleo should be taking advantage of multiprocessing or this problem can occur.
Suzanne, what filters seem to make Nucleo make the Xs? Can others try to test this out?
