Apple Shake 4 - Manual (Page 163)

Chapter 4 Using Proxies 163
Note: When you toggle the useProxy parameter from Base to P1, P2, or P3, you do not
necessarily load a FileIn node’s corresponding proxy1File, proxy2File, or proxy3File
media. The proxy mechanism loads the set that is closest to the global settings, and
does a further scale based on that set. For example, if you haven’t loaded a 10-percent
pre-generated proxy and you set useProxy to P3, a 10-percent file is generated on the
fly from the generated P2 proxy.
When Not to Use Proxies
Proxies are fine for gauging color and relative position. However, proxies do not work
well for pixel-sensitive operations such as DilateErode (where you may chew just one
pixel in or out), or for tracking nodes, due to round-off errors. This is not true for all
filters. Blur, for example, works fine at a proxy resolution.
If you’re performing an operation where it’s not advisable to use proxies, an easy way
to increase Shake’s refresh speed while working on high-resolution images is to
activate the Viewer DOD button.
For more information, see “ The Domain of Definition (DOD) ” on page 82.
Do Not Use Proxies for Tracking
This is worth repeating. Because proxies eliminate detail by lowering an image’s
resolution, proxies will introduce rounding errors with Shake’s motion tracking nodes—
including the MatchMove, Stabilize, and Tracker nodes.
Proxies and Z-Depth
Proxies also interfere with Z-depth compositing, as there is no anti-aliasing with the Z
channel. The left image is a full-resolution Z composite. The right image is the same
composite at a proxy resolution. The anti-aliasing of the depth channel significantly
alters the image quality.
This quality loss can be somewhat minimized by using a Box filter for your proxies, but
then the rest of your image quality suffers as well.
Full resolution Proxy image