This is a good point. The way I used to do it was to queue one or two
machines generating mi files and have them submit each frame to the rest of
the farm as it was built. If the generator machines are also in the farm
they can pick up more frames when they've done.
> -----Original Message-----
> From: owner-xsi(at)Softimage.COM [mailto:owner-xsi(at)Softimage.COM] On
> Behalf Of Raffaele Scaduto-Medola
> Sent: 01 October 2007 17:44
> To: XSI(at)Softimage.COM
> Subject: Re: MI Generation of files
>
> Hi Stefan, and all.
>
> I used to do a lot of MI generation using SoftImage3D, and I've been
> meaning to set it up in XSI.
> The one thing I would suggest though is to do all you MI generation on
> one
> fast (large memory) system, instead of having every system generate on
> mi
> frame.
> The main reason, from what I experienced with Soft3D, is
> opening/reading
> in a scene takes a while (especially larger scenes).
> So my workflow process was to have the fastest box (with enough memory
> to
> handle big scenes), open a scene and generate the MI files sequence,
> and
> have the renderers offset by a couple frames.
> If it was a really big sequence, (because I would see a memory increase
> over time), I would break up the MI generation over two or three
> systems.
>
>
>
> RSM.
>
> _____________________________________________________
> Raffaele Scaduto-Mendola - www.turbolinea.com
> raffaele(at)turbolinea.com
> ---
> Unsubscribe? Mail Majordomo(at)Softimage.COM with the following text in
> body:
> unsubscribe xsi
---
Unsubscribe? Mail Majordomo(at)Softimage.COM with the following text in body:
unsubscribe xsi
