Apple Shake 4 User Manual

Page 348

Advertising
background image

348

Chapter 13

Image Caching

cacheStatus
This is a display-only parameter that shows whether the input image has been cached
or not.

not cached: Nothing has been written to the cache.

in disk cache: Input image data has been moved to the disk cache. This is a result of
the memory cache becoming full, or cache images having been saved after exiting a
previous Shake session.

in memory cache: The input image data has been written to the memory cache.

in transient memory cache: The input image data has been written to the transient
memory cache.

forceCache
This parameter lets you set how cached image data is stored when you update the
cache with the Render Cache Node command. The selected forceCache behavior
bypasses the Global cacheMode caching behavior. There are two options:

disk+memory: The input image is written to the memory cache whenever the cache
node is updated, and then transferred to the disk cache when the memory cache is
full. All frames in the memory cache are moved to disk when Shake quits. In most
cases this is the preferred behavior.

memory only: Moves the input image into the memory cache every time the Cache
node is updated, but never writes cache data to disk.

Internal Cache Parameter Display

The Cache node also displays the following parameters:

imageSize
The size (in megabytes) of the input image. The imageSize is determined by the
following formula:

Bit-depth * Image Width * Image Height

imageSizeLimit
The maximum allowable size of the input image, in megabytes. This is set with the
diskCache.cacheMaxFileSize global plug. The default value is 32 MB.

Note: The imageSizeLimit display lets you easily spot situations where a Cache node is
not rendering because the imageSize is greater than the imageSizeLimit.

totalCacheMemory
The total RAM (in megabytes) available for caching to memory. This is set with the
diskCache.cacheMemory global plug. The default value is 128 MB.

For more information on the global plugs referenced above, see “

Customizing Image

Caching Behavior

” on page 352.

Advertising