Apple Shake 4 - Manual (Page 157)

Chapter 4 Using Proxies 157
If you have many plates and a high frame count, you may want to put the images for
each proxy resolution into separate directories. For example, you can provide a file path
such as:
../<name>_p.50/<base>.<format>
This approach keeps the file count down in each directory, but increases the overall
number of directories referenced by your script. Examples of this are:
images/bluescreen1/bs1.#.cin,
images/bs1_p.50/bs1.#.cin
images/bluescreen2/bs2.#.cin,
images/bs2_p.50/bs2.#.cin
images/cg_plate/cg_plate.#.iff
images/cg_plate_p.50/cg_plate.#.iff
All of your images are in subdirectories based on resolution, for example:
images/bluescreen1/2048x1556/bs1.#.cin
images/bluescreen2/2048x1556/bs2.#.cin
images/cg_plate/2048x1556/cg_plate.#.iff
In this case, the default naming scheme works fine:
../proxy.50/<base>.<format>
This gives you:
images/bluescreen1/2048x1556/bs1.#.cin
images/bluescreen1/proxy.50/bs1.#.cin
images/bluescreen2/2048x1556/bs2.#.cin
images/bluescreen2/proxy.50/bs2.#.cin
images/cg_plate/2048x1556/cg_plate.#.iff
images/cg_plate/proxy.50/cg_plate.#.iff
You can of course use the following as your path to return numerical values for a half-
proxy:
../1024x778/<base>.<format>
You can also use the <dirN> variable to access the name of any parent directory. For
example:
<dir2>/1024x778/<dir2>.<range>.<format>
creates:
images/bluescreen1/1024x778/bluescreen1.#.cin
Full-Resolution Proxies and Network Rendering
If your script references media that resides on a remote network machine, it can
sometimes be convenient to create full-resolution duplicates of this media on your
local machine.