[CodyKallas]

I am trying to find any way to make my renders faster and really dialing my options in on what I can use in this certain amount a time and what I can't.

And I did a test with MXI DISABLED, and correct me if I am mixing things up, but I can preview the render (rendering over network) then open it in MXI viewer. But when the render is completely finished, I can't open it in MXI viewer anymore and it is just the way I set it up, a tiff.

So my concern is, if I am rendering over the network, am I not saving time of MXI being disabled? And is disabling an MXI even an option to save time? (I think someone mentioned it in my rendering animation thread I created earlier)

Thoughts always appreciated.

Thanks

Cody

[hatts]

For cooperative renders, MXIs are being written regardless. MX Network has to write temp MXIs while it combines the renders from cooperative nodes.

The time you save when disabling MXI output is just the time it would've taken to save an MXI.
E.g., if you're rendering a single 800x600 frame to a local location, there's very little point to disabling MXI output, as writing the MXI wasn't going to take long anyway. If, however, you're rendering 1000 large frames to a network location, each MXI write is gonna take up some time, and added together that might be significant.

When you hit "preview" on a network render you're instructing the network to grab all the data it has so far and make an MXI out of it. It's gotta put that somewhere, so it stores it in a temp directory.

So yes there is a purpose to disabling MXI output. It is mostly helpful if you have limited storage space and/or tons of frames and/or large file sizes.

[JDHill]

It's also worth mentioning that rendering with no MXI means that you have no MXI from which to resume, should a crash or other catastrophic failure occur.

[polynurb]

http://support.nextlimit.com/display/mx ... Parameters

-mintime

could be helpful too

[CodyKallas]

That is mostly what I figured. But thanks for the insight.