Apple Shake 4 User Manual

Page 338

Advertising
background image

338

Chapter 12

Rendering With the FileOut Node

updateFromGlobals
Indicates if your settings match the Globals tab settings (updated), or if you have
modified the settings (update now), in which case the button allows you to update the
settings from the Globals tab.

timeRange
Set a new time range using Shake’s standard frame syntax; for example, 1-100 renders 1
to 100, 10-20x2 renders frames 10, 12, 14, up to 20, and so on.

useProxy
Sets your proxy settings.

quality
When this is set to lo (0), anti-aliasing is disabled. This results in poorer image quality,
but improved render speed.

motionBlur
Motion Blur quality level. 0 is no blur, whereas 1 represents standard filtering. For more
speed, use less than 1. This value multiplies the motionBlur parameter of every node
that uses motion blur in your script.

shutterTiming
A subparameter of motionBlur. Shutter length 0 is no blur, whereas 1 represents a
whole frame of blur. Note that standard camera blur is 180 degrees, or a value of .5. This
value multiplies the shutterTiming parameter of every node that uses motion blur in
your script.

shutterOffset
A subparameter of motionBlur. This is the offset from the current frame at which the
blur is calculated. Default is 0; previous frames are less than 0. This value multiplies the
shutterOffset parameter of every node that uses motion blur in your script.

maxThreads
Specifies how many processors are devoted to the render on a multiprocessor machine.

sequential
If you have multiple FileOut noded in your script, it may be more efficient to render the
nodes sequentially. Turning sequential on causes each FileOut node to process every
frame in the tree above it before allowing the next FileOut node to be rendered. When
sequential is turned off, all FileOut nodes are rendered simultaneously. Sequential
rendering is more efficient in cases where FileOut nodes share upstream nodes and
trees. However, if there are too many processes running at the same time they will
compete for CPU and memory resources, which may cause the overall processing time
to increase, in which case turning sequential off may be more efficient.

Advertising