Apple Shake User Manual

Late-Breaking News About Shake 4
This document provides updated information about Shake 4 and covers these topics:
Â
Late-Breaking News About Shake 4.1.1 (p. 1)
Â
Previous Release Information About Shake 4.1 (p. 1)
Â
Previous Release Information About Shake 4.0 (p. 11)
Â
Differences in Gamma Handling Between Shake and Final Cut Pro (p. 14)
This document may be updated as versions of Shake are released or new information becomes available. You can check for updated information by choosing Help > Late-Breaking News when Shake is open.
For the latest information about product updates, tips and techniques, and qualified third-party devices, visit the Shake website at http://www.apple.com/shake.
Late-Breaking News About Shake 4.1.1
This update addresses compatibility issues for QuickTime codecs greater than 8 bits.
Installing Shake 4.1.1
This version of Shake is an update to Shake 4.1 and must be installed on a computer on which Shake 4.1 has already been installed.
Previous Release Information About Shake 4.1
This version of Shake is designed to run natively on both PowerPC-based and Intel-based Macintosh computers. A Linux version is also available. The Shake 4.1 release also includes a number of performance enhancements and feature improvements.
Installing Shake 4.1
Because the Mac OS X version of Shake 4.1 uses the new Universal application format, Macintosh users must install the entire application (as opposed to updating an existing Shake 4 application). For more information, see
Installing Your Software.
1
Shake 4.1 Compatibility with Older Project Files
Scripts created in Shake 4.0 should be compatible with Shake 4.1. However, forward compatibility is not guaranteed.
What’s Fixed in Shake 4.1
The following issues have been corrected in Shake 4.1.
Enhancements
Â
All onscreen scale controls now display properly from all angles at which they can be modified.
Â
Motion blur performance has been improved.
Note:
Changes in the way motion blur is calculated in the Move3D node may result in differences between Shake 4.1 output and that of earlier versions. You can adjust the shutterTiming slider in the motionBlur subtree of the Move3D node to manually match the blur results of earlier versions of Shake.
General
Â
Pressing Shift-F in the Curve Editor now frames all selected points.
Â
Ignoring, then “un-ignoring” FileIn parameters no longer resets the parameters of the node.
Â
Motion blur is now computed and displayed properly for a translating camera.
Â
Dragging a node from the Node View in a large script no longer causes Shake to stop responding.
Â
Propagated multi-input nodes no longer display field-based artifacts on Macintosh computers.
Â
Clicking the camera in perspective view no longer inadvertently rotates the camera.
Â
When using the Send to Shake command from Final Cut Pro, the RetimeMotion node now works consistently when using either Blend or Adaptive modes.
Â
Shake performance has been improved when converting UNC paths to local paths.
Â
When changing field order, retiming using either Fast or Best modes now produces the same results.
Â
The sensitivity of zooming in the Viewer when using the + (plus) and – (minus) keys has been adjusted.
Â
Scripts containing a QuickTime FileIn with force8Bit turned on will now render properly in Qmaster.
Â
Toggling visibility of branches in MultiLayer nodes no longer hides the entire input chain of that branch.
Â
Certain instability problems that occurred when working with rotoshapes over a long period of time have been resolved.
Â
When using a Clamp node in float mode, Shake now behaves consistently on all platforms.
2
Â
The “Bake tracker into shape” function now works as described.
Â
The importer for Maya files has been updated to work properly with Maya 7.
Â
Importing .SSF files on Linux systems no longer causes Shake to stop responding.
Â
Cache node performance has been improved.
Â
Motion blur is now properly rendered when using a Move3D node.
Customization
Â
Pressing N now activates auto-insert when dragging nodes in the Node View.
OpenEXR
Â
Default values no longer cause Shake to stop responding when tracking dpx/exr frames.
Â
Reordering channels in a FileIn node using the OpenEXR file format no longer causes Shake to stop responding.
Â
Shake now properly reads and displays inverted OpenEXR files.
Keylight/Primatte Node
Â
Keylight no longer introduces black pixels in float mode.
Layers
Â
Layer keyframes are now restored when undoing Attach to Camera, or when re­clicking the Attach to Camera button.
MultiPlane Node
Â
MultiPlane nodes using blend modes other than Over now render consistently.
Â
Shake no longer stops responding when viewing or modifying some MultiPlane nodes in hardware-rendering mode.
Â
Dragging scale or rotate values no longer extracts an active MultiPlane node from its input nodes.
Â
When faceCamera is turned on in a layer, the image no longer moves when using a proxy scale.
Â
In MultiPlane nodes, transform keyframes now display in the Time Bar.
Â
Using motion blur in MultiPlane nodes no longer clips objects.
Â
Perspective camera in MultiPlane nodes has been improved.
PSD Files
Â
Rendered output now matches GUI display when applying a Move2D node to a Photoshop PSD file.
Â
Shake now properly displays Photoshop PSD files that have been exported with alpha channels.
3
QuickPaint Node
Â
Repositioning a clone area no longer leaves graphic anomalies on the screen.
Â
Animating 1-point brush strokes no longer causes Shake to stop responding.
Â
Quickpaint no longer creates field-based artifacts when painting on frame-based content.
Warper/Morpher Node
Â
Clicking the Export Spline button in the Warper or Morpher node no longer causes Shake to stop responding.
Undo
Â
Performance when using Undo has been improved.
Undocumented New Features in Shake 4.1
The following new features in Shake 4.1 are not covered in the Shake documentation.
MultiPlane Node
Layer Attached to Camera at Time
In the MultiPlane node, a new mode has been added to the Attach to Camera button. The new mode—Layer Attached to Camera at Time—makes it much easier to position layers relative to a moving camera.
The Attach to Camera button now has three toggle modes:
Button Toggle Mode Description
Layer Not Attached to Camera
Layer Attached to Camera
Layer Attached to Camera at Time
The default setting.
Attaches the layer to the “camera” in a tracked sequence that has been imported from a .ma file.
Sets a time at which the layer is attached to the “camera.”
When the Attach to Camera button is toggled to Layer Attached to Camera at Time, the cameraLockFrame parameter appears in the subtree. CameraLockFrame sets a moment in time at which the layer appears fully framed by the camera. The cameraDistance parameter (also in the layer subtree) allows you to set the distance from which the camera is viewing a layer. Using this new setting, the layer remains positioned in space, based on the time that it locked to the camera.
4
Reset Within Camera View
A new shortcut menu option has been added to the layer controls in the MultiPlane node. The new option, “Reset within camera view,” moves the camera to frame the currently selected node. To access this option, right-click the layer controls in the MultiPlane node parameters, then choose “Reset within camera view” from the shortcut menu.
Function Keys
In Shake 4.1, the F1-F4 function keys are now used for saved views. The description on page 564 of the controlling the points of a rotoshape, is no longer accurate.
Shake 4 User Manual
, which describes these keys as being used for

Corrections to Shake Documentation

The following information covers corrections and updates to the documentation included with Shake 4.1.
Â
In the FilmGrain node, the default value for filmResponse is -1, not 0 as stated on page 857 of the
Â
In the “Autosave Settings” section on page 367 of the erroneously stated that the script.autoSaveDelay declaration (used to modify the frequency of autosaves) is set in the ui directory. Rather, this declaration is set in the startup directory.
Â
On page 755 of the optional matte with which you can isolate a subject or area that you want the SmoothCam node to ignore while performing its analysis.” Rather, this should state that “The second input is for an optional matte that may be used to isolate areas you want the analysis to ignore. An example would be a matte box attached to the camera that isn’t affected by camera movement. White areas of the mask determine areas to track; black areas of the mask are those parts of the image to ignore during analysis.”
Â
When repositioning an anchor point in nodes with onscreen controls, you need to hold down the Control or Command key in order to drag the anchor point. This is not covered in the
Â
The subpixel accuracy of new trackers now defaults to “1/64” instead of “1/16.”
Â
You can scale the size of the onscreen controls in the MultiPlane node by pressing Shift-+ (plus) to increase, or Shift-– (minus) to decrease the size of the control in the Viewer. In the MultiPlane node, this affects the rotation and panning controls, as well as the camera and its associated controls. This has no effect on other nodes that use onscreen controls.
Shake 4 User Manual
Shake 4 User Manual,
Shake 4 User Manual
.
Shake 4 User Manual,
it is stated that “The second input is for an
.
it is
5
Loading...
+ 11 hidden pages