Broadcast Monitor

• The Broadcast Monitor button remains green (appears enabled) all the time.
• When additional Viewers are spawned for the broadcast monitor output, their Viewer “number” is incorrectly displayed.
• When the broadcast monitor displays a proxy, the same proxy calculation is improperly applied to the displayed image.
• A render hit may occur with broadcast monitor turned on.

Crashing Issues

• A crash may occur when switching buffers with the on-screen controls visible.
• Copying a layer node and pasting it as a link crashes Shake.
• Shake may crash when applying consecutive “apply filter” nodes.

• When you cut and paste keyframes in the Curve Editor they insert just a fraction off of full frame.
  
  Workaround — Make sure Time Snap is enabled in the Curve Editor (in the Curve Editor right-click menu). Consequently, if the insertion point was the current time indicator, the points insert at an integer. Also, if the newly-pasted points become the current selection, you can drag the points to the correct integer with Time Snap. Time Snap is your friend.
  
  
• If you split the Curve Editor, you cannot apply curve functions (smooth, jitter, etc.) to curves only visible in the top editor.
  

• The Viewer progress bar state disappears when the focus is changed to another application.
  
• Killing the Viewer progress bar does not stop an active render.

• Recover: If relative paths are used in a script, using File > Recover / File > Add Script, or clicking the “undo” button can make the FileIn nodes invalid in some cases. This is the expected behavior, since the script is loaded from a different directory that no longer matches the relative paths.

• Text: Some True Type fonts (.ttf) do not function in Shake (but work correctly in other applications).
• Wacom: In some cases, the Wacom stylus may “stick” to the parameter that was just changed (does not release control) when Shake is processing the new parameter settings.
  

  Workaround — Download the most current Wacom drivers.
  

• When a node parameter refers to a non-existent variable (for example, local variable), it is flagged as invalid (red in the Node View). If this variable is created later, the node still displays an error.
• Undo can be unpredictable.
• When creating a script from the command line using the -savescript argument, the specfied timeRange is not saved. The resulting timeRange is always set to 1.
• Setting the Compare mode of the Viewer to Fade when using the AB buffers results in image corruption in the Viewer.
• Copy and Paste as link does not work with all nodes.
  
  Note: This problem affects all nodes using the "x" expression including:
  
  Lookup, ColorCorrect,ColorX, WarpX, etc. This problem occurs because these nodes declare additional variables that
  their input parameters use. There is currently no workaround.
• When holding down the “M” key over a color swatch, only the green channel is affected.
• “Save as...” does not prompt you to overwrite an existing script if environment variables are used.
• If the timeRange starts at a negative value, the Home command incorrectly resets the visible timeline area to begin at 0.
• The Parameters Curve Editor (IPCE) has resizing problems.
• A loss of interactivity can occur under some instances.
  

• Selecting upstream or downstream nodes does not properly work in a node group.
• Node groups do not recognize selection hot keys such as Shift+U.
• In the Node View, the pointer may not align with the node being edited.
  

MultiLayer and Photoshop File Support

• The MultiLayer node is slower than using the node equivalent.
• The background layer is always visible in the MultiLayer node.
• "LayerX" is listed in the compositing mode list and generates an invalid MultiLayer node.
  

Note: We have received some reports from customers complaining about the rendering time of Shake scripts when QuickPaint nodes are used. This may be related to the numbers of QuickPaint nodes contained in a script. With each added paint node, Shake creates at least one full size image buffer equal to the resolution of your image; two are created if reveal is used. This memory comes from the processing cache. When shake hits the upper limit of the processing cache, it begins to swap used memory blocks to disk, starting with the oldest ones. If the shake processing cache parameter is too low for a particular computer's RAM configuration, and the script requires a lot of processing cache, shake may start swapping memory. On the other hand, if shake's processing cache is too high, you may also encounter memory swapping. For these reasons, it is highly recommended to tweak the cache parameters to have more processing cache. For more information, see the Caching chapter of the “New Features Guide” in the on-screen help menu.

A rough estimation of the processing cache that a paint node uses can be calculated with the following formula:

${width} * ${height} * 4 channels/pixel * ${byte_depth} * 2 (if reveal is used).

For a 2k 10-bit image using reveal, a paint node will require the following ram:

2048 * 2048 * 4 channels/pixel * 2 bytes/channel * 2= 64 MB

The above is only for one QuickPaint node. Warping nodes also use more memory for the processing cache. Additional RAM is necessary for the image cache.

If you find one script takes too much RAM, the workaround if to break it down into smaller scripts with smaller memory requirements.

• Saving a sequence as Quicktime with mixed resolution images will result in dropped frames and bad sequencing.

Workaround: If your sequence has mixed resolutions at the FileOut level, use a crop node prior to the FileOut to ensure that the same resolution is used for all frames.

• The Shake viewer may indicate 16-bits per channel when reading an 8-bit codec Quicktime file.

Note: If the codec used to create the file supports 16-bit ARGB rendering, Shake displays the file using 16-bits to ensure it maintains the highest quality available. You can use the “force 8-bit” switch on the FileIn in Shake to force Shake to read the file as 8 bits and potentially avoid a performance slowdown. It is not unlikely that you'll encounter this situation since most 8-bit codecs do not support 16-bit rendering.


• A gamma shift or compression artifacts may result in images rendered as 10-bit QuickTime files.
  
  Note: Some codecs may introduce artifacts when converting from YUV to RGB.

• Some third-party 10-bit codecs installed on your computer can cause image degradation, even when other codecs are used.
  
  Workaround — We recommend that you use the Apple Uncompressed 10-bit 4:2:2 codec. If you see artifacts in the resulting image, deinstall all third-party 10-bit codecs and rerender the image.

• File names are not preserved when loading a Final Cut Pro movie into Shake.
  
  Note: You can adjust the node name using copy and paste from the File Path.
  

RotoShape Node

• Baked Tracker to shape link data is not viewable or editable.
• Adjusting a soft rotoshape edge may result in unwanted artifacts in the resulting gradient.
• Changing a rotoshape Edge control point from Linear to Smooth also changes the Main shape control point.
• When you have many shapes in a RotoShape node, the Tool Tabs, Parameters, and onscreen controls may flicker when adjusting the shapes.
• Child shapes do not keyframe properly.
• In some cases, the parameters for a node created following a RotoShape node are not loaded.
• Shapes may display artifacts after using add child/remove parent several times.
• If you attempt to modify a RotoShape node at the top of a node tree while viewing the final image, all instances of the Rotoshape node in the tree may appear on top of each other, making it very difficult to adjust.
• User can't select edge nodes from a boundary box.
• Results may be unpredictable when using soft edge and motion blur.
• Adding more than 41 shapes to a RotoShape node may cause a crash when clicking the right mouse button.
  

SFileIn/SfileOut/Proxy/Thumbnails

• Proxy Globals are changed by a proxy set in file browser.
• You cannot render proxies if the proxy configuration has not been set.
  
  Note: You must select the proxy configuration before creating the SfileIns. Otherwise, the “render proxies” function creates invalid proxies since Shake defaults to “No_Precomputed_Proxies” in the Globals Parameters. For more information, see “About Proxies” on page 103 of the printed Shake Reference Manual, or page 105 of the Shake Reference Guide on-screen help PDF.
  

• If an SFileOut node is named "audio", the node will not render.
• A node that appears red (missing) remains red after the missing source has been replaced.
  

  Workaround — Save and reload the script.
  

• Considerable slowdown may occur in scripts that contain numerous retimed SFileIn nodes. The retimed SFileIns are rebuilt internally when their cache IDs are reevaluated (when the time changes).
  

  Workaround — There is no current workaround other than to use the manual update mode.
  

  Considerable speed improvements have been made but the problem may still occur with scripts that contain multiple retimed SfileIn nodes.
  

• There is a problem with retiming a clip that is not positioned to start at time 1 (using the “retime” function under the Timing tab in the new SFileIn). This problem occurs with clips brought in with the Placement (File Browser radio button selection) set to “seq start” or “current frame,” but also to any clip that has been slipped in time.
  
• The default retime expression does not take the time shift into account properly. To correct this, bring the clip in at time 1, retime the clip, and then slide the clip in the Time View. Alternatively, you can bring the clip in with a start frame of 1 (though no frame 1 exists) to keep it aligned in time but starting at 1. The frames prior to the first existing frames are black, and error messages about missing input frames appear in the shell.
  
• An SFileOut does not recognize its own local variables.
  
• There is a thumbnail permission problem when you log in as User after using root.
  
  Note: By default, the cache does not have “write” privileges when you log in as a different user. If you launch Shake when logged in as a different user (for example, root), the cache permission does not have “write” privileges, and causes problems with the thumbnails and caching mechanism. To change the cache privileges (to writable), do the following:
  
  
  1. Launch Terminal.
  2. Type the command: su
  3. When prompted, enter the root password.
  4. Type the command: cd /var
  5. Type the command: chmod 777 tmp/ (to change the permissions to the cache directory)
  6. To discontinue root user access, either quit the Terminal or type the command: exit
  7. Relaunch Shake.
     
     

Tracker/Stabilize/Matchmove

• Stabilize does not correctly update the CornerPin node.
• Stabilize: Changing the “auto” time range may reset itself when reloading a script.
• The Tracker onscreen control does not update when no input is connected.
• There is a loss of motion blur with the Stabilize node under some circumstances.
  

Viewer

• The Viewer LUT turns off after clicking the “undo” button (at the top right of the interface).
• The Timecode Viewer Script fails to update with RotoShape and QuickPaint.