Apple Shake 4 - Manual (Page 150)

150 Chapter 4 Using Proxies
Pre-Generating Your Own Proxies
Ordinarily, if you set useProxy to P1, P2, or P3, the proxies created for each frame of the
composition are written on the fly to memory. Eventually, the computer’s memory fills
up, and these temporary proxy images are written to disk—into the cache.
The cache is a closed set of files that are viewable only by Shake. Additionally, remote
renders do not recognize the cache directory if not explicitly specified to do so. Finally,
you may have so many files that the cache mechanism becomes overworked. In these
cases, it makes sense to pre-generate your proxies when you start the project with an
initial rendering process. The proxy files are then pulled from these precalculated
images rather than generated on the fly.
Important: If you decide to pre-render proxy files for your script within the Shake
interface, make sure that you set the proxySet parameter in the useProxy subtree of the
Globals tab before you generate your proxies.
You can either pre-generate the files inside the interface, or you can load them after
they are created by an external process.
To quickly pre-generate files using Shake’s default settings:
1 Open the Globals tab and open the useProxy subtree.
2 Choose the type of proxies you want to generate from the proxySet pop-up menu.
There are six options in this menu:
• Custom: This option is automatically selected whenever you choose your own
resolutions, names, and format.
• No_Precomputed_Proxies: No proxies are generated.
• Relative: Three sets of proxies are generated, with defaultScale values that are
calculated relative to the original size of the image files:
• 1/2
• 1/4
• 1/10