Apple MA434Z/A User Manual - Page 1018

The following is a good example of a common command-line test of 3D-rendered imagery: shake truck.iff -outside sign_mask.iff -over bg.iff As long as there is no ambiguity, it is not necessary to type the entire function name. For example: shake bg.iff -bri 2 calls the Brightness function since there are no functions starting with bri. However, calling: shake bg.iff -con 2 informs you that it cannot choose between Conform, Constraint, ContrastLum, ContrastRGB, or Convolve. To solve the problem, replace your command with enough letters to end the ambiguity: shake bg.iff -contrastl 2 This calls the ContrastLum function. In regard to capitalization and function names, function names are always capitalized in the interface. In the command line, function names are always lowercase so you do not have to press the Shift key. The exception is when you call a function in quotes, such as the Linear function used to animate parameters: shake truck.iff -blur "Linear(0,0@1,20@20)" -t 1-20 Note: For more information on animation curves, see "More About Splines" on page 316. Most functions are image manipulators-they modify the image you load. Others are controls to modify how Shake executes the command. For example, -brightness 2 brightens an image, but -fps 24 loads a Flipbook preset to 24 frames per second. Although image functions always occur in a linear fashion-the order of commands matters-controls can be placed anywhere. For example, the following lines are identical: shake alien/alien.#.iff -rotate 45 -t 1-50 -cpus 2 shake -cpus 2 -t 1-50 alien/alien.#.iff -rotate 45 However, the following two lines are different: shake truck/truck.iff -pan 200 0 -rotate 135 shake truck/truck.iff -rotate 135 -pan 200 0 If you place a second control on a line, it replaces the previous setting. For example: shake alien/alien.#.iff -t 1-50 -fps 24 -bri 2 -fps 30 -t 10-20 plays at 30 frames per second and renders only frames 10-20. 1018 Appendix A The Shake Command-Line Manual