Apple Shake 4 - Manual (Page 344)

344 Chapter 13 Image Caching
You can set the cacheMode to one of four states:
• none: Cache data is neither read nor written.
• read-only: Preexisting cache data is read, but no new cache data is generated.
• regular: The cache is both read from and written to, but normal caching does not
occur when the global time is changed (as when moving the playhead).
• aggressive: The cache is both read from and written to, and normal caching occurs
whenever the global time is changed (as when moving the playhead).
When setting the cacheMode, consider the following guidelines:
• In most circumstances, the regular cacheMode setting should be used.
• Consider setting the cacheMode to aggressive when you are constantly scrubbing
back and forth between two or three frames (for example, when tweaking tracking
or shape control points).
• You should only set cacheMode to none if you are using Shake on a system with
extremely limited RAM and disk space. By setting the cacheMode to none, Shake is
forced to re-compute each image that you select to view, which is the least efficient
way to run.
Using the Cache Node
The Cache node lets you tell Shake to cache image data at specific points in the node
tree. This gives you explicit control over which parts of the node tree require rendering
while you work. For example, if there is a processor-intensive branch of your node tree
that you’re no longer working on, you can insert a Cache node in between the last
node of that branch and the section of the node tree in which you’re now working.
Afterwards, the currently displayed frame is immediately cached. If you want to cache a
range of frames in order to pre-render that branch of the node tree, you can use the
Render Cache Nodes command. All cached image data is stored within the same cache,
in memory or on disk.
Note: Cache nodes cache image data at the currently set proxy resolution.