User manual APPLE SHAKE LATE-BREAKING NEWS

[. . . ] 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 (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. [. . . ] Note: Moving the pointer over the Viewer will force a refresh. 8  Images output from a MultiPlane node operation may produce NAN values if the input image is 32 bits and the background is black. Workaround: Insert a SetBGColor node before the input node and the MultiPlane node.  Screen refresh issues may appear when editing upstream nodes while the MultiPlane node is open in the Viewer.  Roll may be introduced when moving the camera's position.  When switching between differently viewed nodes, the framing may become offset.  Editing the parameters of a MultiPlane node always forces the quad view to be displayed in the Viewer, even if the MultiPlane node itself is not being viewed.  When the MultiPlane node's onscreen controls are deactivated, pressing the Space bar to switch to full-screen mode causes a refresh issue.  MultiPlane parameter names may appear clipped in the Curve Editor. LensWarp Node  Using large values in any of the parameters of the Lenswarp node to create distorting effects may require an enormous amount of memory to process. If the resulting memory requirements exceed the amount of available RAM, swap disk space will be required. In some instances, the amount of memory needed may exceed even the available swap disk space, which may cause Shake to become unresponsive.  Undesirable image artifacts may be created when using LensWarp to create extreme warps.  LensWarp nodes that are copied and pasted in the Node View may not correctly duplicate all shapes and parameter settings.  Applying a Distort followed by an inversely proportional Undistort may not restore an image to its original shape and size. AutoAlign Node  The Viewer may not update correctly while the AutoAlign node is analyzing the inputs. Note: The Viewer will update correctly once the analysis is completed. SmoothCam Node  In some instances, a SmoothCam analysis may yield unacceptable results even on a seemingly simple clip. The SmoothCam node has trouble evaluating some images that have a significant lack of contrast, or are too dark.  Cases where using a mask fails to improve the resulting SmoothCam analysis may also be caused by lack of contrast or brightness in the image.  Unusual values may briefly appear in the ProcessedRange parameter when the Analyze button is clicked. 9 Truelight Node  OneDlut does not seem to work with a Kodak2302 film profile. Reason: Truelight's RGB 1D calibrations are made using values along a neutral axis-- in effect assuming when building the 1D LUTs that a red value of x is accompanied by green and blue values that are also of x. As a result, three 1D tone curves are produced, similarly to ordinary color film. [. . . ] When you eventually output the sequence to video, or render it as a QuickTime movie, the gamma of the output is identical to that of the original, unless you've added color correction filters of your own. However, during playback on your computer's monitor, Final Cut Pro automatically lowers the gamma of a sequence playing in the Canvas to 1. 8 for display purposes. This is to approximate the way it will look when displayed on a broadcast monitor. This onscreen compensation does not change the actual gamma of the clips in your sequence. [. . . ]