Apple Shake 4 - Manual (Page 343)

13
343
13
Image Caching
Shake has a powerful image caching system that keeps
track of previously rendered frames in order to speed
your workflow as you work within the interface. This
system can be customized to optimize how you work.
About Caching in Shake
Shake’s cache is a directory of pre-rendered images, with script information about each
frame. When Shake displays the image data for a node tree at a given frame, it first
checks the cache to see if that frame has been rendered before. If it has, the cached
image is recalled to save time, as opposed to reprocessing the entire tree. Shake keeps
track of how many times each cached frame has been viewed, eliminating the least
viewed frames first when the cache runs out of room.
There are two ways you can control Shake’s image caching—using the cacheMode
parameter in the renderControls subtree of the Globals tab, or explicitly within the
node tree using the Cache node.
Important: If you run two instances of Shake, only one instance is capable of reading
from or writing to the cache. When you launch the second instance of Shake, you are
given the option to either move the current cache to a temporary location, or disable
caching.
Cache Parameters in the Globals Tab
The following parameters are found in the renderControls subtree of the Globals tab of
the interface.
cacheMode
This parameter controls the caching behavior of all of the nodes in your script. Every
node in your script is capable of being cached, in one way or another.