1. No category

Release Notes for Nuke Studio
Public Beta 06
Release Date
07 November 2014
Qualified Operating Systems
• Mac OS X 10.7 (Lion), 10.8 (Mountain Lion), 10.9 (Mavericks)
NOTE: Nuke is expected to function correctly under Mac OS X 10.9 (Mavericks), but we are seeing UI
performance degradation compared to previous OS X versions. We are working on resolving these issues.
• Windows 7 64-bit and Windows 8 64-bit
• CentOS/RHEL 5 and CentOS/RHEL 6
Other operating systems may work with Nuke, but have not been fully tested. If you have any problems with a
particular operating system, please contact [email protected].
Requirements for GPU Acceleration
If you want to enable Nuke to calculate certain nodes using the GPU, there are some additional requirements. You
need to have, either:
• an NVIDIA GPU with compute capability 2.0 (Fermi) or above. A list of the compute capabilities of NVIDIA GPUs is
available at www.nvidia.co.uk/object/cuda_gpus_uk.html
NOTE: The compute capability is a property of the GPU hardware and can't be altered by a software
update.
With graphics drivers capable of running CUDA 4.2 or above.
• On Windows and Linux, CUDA graphics drivers are bundled with the regular drivers for your NVIDIA GPU.
Drivers from April 2012 onward support CUDA 4.2.
RELEASE NOTES FOR NUKE STUDIO PUBLIC BETA 06 | LAUNCHING AND LICENSING INFORMATION
Go to http://www.nvidia.com/Download/Find.aspx?lang=en-us for more information.
• On Mac, the CUDA driver is separate from the NVIDIA graphics driver and must be installed, if you don't have it
already. The minimum requirement for CUDA 4.2 is driver version 4.2.5, which can be downloaded from
www.nvidia.com/drivers.
NOTE: We recommend using the latest graphics drivers, where possible, regardless of operating system.
• an AMD FirePro GPU on late 2013 Mac Pro 6.1, running OS X 10.9.3 'Mavericks', or later (see below and the Blink
API documentation for caveats on CPU/GPU result consistency on Mac Pros).
Late 2013 Mac Pro Only
Nuke Studio supports GPU-enabled nodes on the late 2013 Mac Pro 6.1 (running OS X 10.9.3 'Mavericks', or later),
including a new Enable multi-GPU support option. When enabled in the properties of supported nodes, GPU
processing is shared between the available GPUs for extra processing speed.
NOTE: Due to outstanding Mac OS X issues with OpenCL, GPU processing is not currently available on late
2013 Mac Pro 6.1, in the following circumstances:
• If you're running an earlier version of Mac OS X than 10.9.4 'Mavericks', Kronos and MotionBlur do not
support GPU acceleration.
• If you're running an earlier version of Mac OS X than 10.9.5 'Mavericks' and processing images greater
than 4 mega pixels resolution, VectorGenerator, Kronos, and MotionBlur do not support GPU
acceleration.
Launching and Licensing Information
• Nuke can be run on the command line from the installation directory without any arguments. For example, on
Windows:
C:\Program Files\Nuke9.0v1\Nuke9.0.exe
NukeX and Nuke Studio can be run on the command line from the installation directory using the --nukex and --studio arguments. For example, on Windows:
C:\Program Files\Nuke9.0v1\Nuke9.0.exe --studio
• NukeX requires nukex_i and nuke_i licenses with valid maintenance.
• Nuke Studio requires nukestudio_i, nukex_i, and nuke_i licenses with valid maintenance.
New Features
Nuke is now an Apple Authorized ProRes third-party product and can read and write Apple ProRes 4444 and Apple
ProRes 422 on Mac OS X, Linux, and Windows using the mov64 reader at SD, HD, 2K, and UHD resolutions. Apple
2
RELEASE NOTES FOR NUKE STUDIO PUBLIC BETA 06 | FEATURE ENHANCEMENTS
ProRes 422 includes the HQ, LT, and Proxy formats.
NOTE: Apple ProRes 4444 XQ support is scheduled for a future release of Nuke.
Feature Enhancements
• BUG ID 46018 - QuickTime: The .mov codecs present in the Timeline and Compositing environments have been
unified for clarity.
• BUG ID 46203 - Frame Server: The reporting for Python processes that fail during Frame Server rendering has been
improved.
• BUG ID 46244 - Export: Nuke Studio's exporters have been updated to use the new OFlow node.
• BUG ID 46250 - The Properties panel Node tab has been re-arranged for clarity.
• BUG ID 46331 - Keyboard Shortcuts: Several timeline keyboard shortcuts have been re-allocated to avoid clashes
on multiple platforms:
• The up and down arrow keys now skip to the previous and next edit.
• The numeric pad arrow keys now switch selection between track items of a similar type.
• , (comma) and . (period) or Ctrl/Cmd+numeric pad 4 and 6 nudges track items left and right, where space
permits.
• Alt+, (comma) and . (period) or Ctrl/Cmd+numeric pad 2 and 8 nudges items between tracks.
• Ctrl/Cmd+Shift+numeric pad 4 and 6 skip backwards and forwards incrementally (except on Windows,
currently).
• Alt+, (comma) or . (period) move track items between tracks, overwriting existing track items.
• Alt+Shift has replaced Ctrl/Cmd+Shift for Min/Max Version.
Bug Fixes
• BUG ID 16622 - PlanarTracker: Repositioning a planar surface was slower than expected.
• BUG ID 43142 - CameraTracker: Tracking low contrast source images occasionally caused Nuke to crash.
• BUG ID 43408 - Comp Viewer: The fps dropdown was not updated by the Nuke Project Settings > fps dropdown
for existing Viewers.
• BUG ID 43962 - Export: Closing the Export dialog always displayed a save changes warning, even when no changes
were made.
• BUG ID 44253 - Viewers: The A input buffer dropdown was initially disabled when a comp was opened.
• BUG ID 44315 - Timeline Viewer: The blue keyframe indicators in the frame slider disappeared during playback.
• BUG ID 44651 - Having more than one Sequence or Spreadsheet panel open at once caused synchronization issues
between panels.
• BUG ID 44695 - DopeSheet: Moving soft effect keyframes did not update the Dope Sheet.
3
RELEASE NOTES FOR NUKE STUDIO PUBLIC BETA 06 | BUG FIXES
• BUG ID 44823 - Saving and restoring a workspace did not retain monitor specific settings
• BUG ID 45109 - Comp Viewer: Updating the Project Settings > fps did not immediately update a shot's timecode
in the Viewer.
• BUG ID 45382 - mxfReader: Importing the same .mxf file into the Timeline and Compositing environments applied
different LUTs.
• BUG ID 45463 - Timeline Viewer: Enabling See Through Missing Media in the Viewer settings showed frames
with the wrong resolution or LUT.
• BUG ID 45753 - Python: Rendering mov32 and mov64 Write nodes using Python caused Nuke to crash.
• BUG ID 45814 - Opening scripts from a file browser, with Nuke already open, did not load the script.
• BUG ID 45842 - Avid DNxHD: Exporting Avid DNxHD sequences caused Nuke Studio to crash.
• BUG ID 45915 - Linux only: Launching Nuke Studio from the terminal with the -V argument and then creating a
comp caused Nuke Studio to crash on exit.
• BUG ID 45924 - QuickTime: The write controls in the Export dialog did not match those found in the Write node
properties.
• BUG ID 45933 - PlanarTracker: Correcting the planar surface in a certain script offset the tracked points to negative
positions.
• BUG ID 45950 - Timeline environment: The playhead was positioned to the right in a new project on launch.
• BUG ID 45957 - Create Comp: Rendered frames were not showing in the Viewer when rendering long comps.
• BUG ID 46039 - Viewer: Setting In and Out points automatically added the same points to new Viewers.
• BUG ID 46146 - PlanarTracker: Undoing a planar surface corner point adjustment offset the tracked roto shape.
• BUG ID 46182 - Frame Server: Using external machines as Frame Server render slaves didn't work when the write
permissions were incorrect for the slave machine.
• BUG ID 46222 - The Nuke splash screen displayed during startup was gray while loading OFX plug-ins.
• BUG ID 46224 - Kronos/MotionBlur: Computation was significantly slower in Nuke 9, using the old Motion > Local
algorithm, than in Nuke 8, using certain settings.
• BUG ID 46232 - Monitor Output: Using Blackmagic cards in the Compositing environment with a half-float GL
buffer size and 8-bit pixel format caused corrupted output.
• BUG ID 46252 - Launching Nuke from the command-line or Terminal using the --tg argument caused a crash.
• BUG ID 46253 - Create Comp: Comps created with downrez enabled didn't display correctly in the Viewer.
• BUG ID 46257 - PlanarTracker: The add offset key button didn't work unless a key had already been set on
another frame.
• BUG ID 46260 - PlanarTracker: Tracking open roto shapes caused Nuke to crash.
• BUG ID 46273 - VectorGenerator: Connecting a Viewer to a node tree containing a VectorGenerator, where the
image moved out of the bounding box or changed resolution, caused Nuke to crash.
• BUG ID 46286 - Rendering imported .nk scripts from the timeline using the right-click Render Comp option did
not work as expected.
• BUG ID 46296 - Frame Server: External slave machines always checked out interactive licenses (nuke_i), rather than
render licenses (nuke_r).
4
RELEASE NOTES FOR NUKE STUDIO PUBLIC BETA 06 | KNOWN ISSUES AND WORKAROUNDS
• BUG ID 46297 - QuickTime: Setting mov32 as the encoder was not honored in exports from the Timeline
environment or when copy/pasting a Write node in the Node Graph.
• BUG ID 46301 - Launching Nuke from the command line or Terminal did not print version and build information.
• BUG ID 46305 - Kronos: Retimes were always applied to rgba, even when rgb or alpha was selected.
• BUG ID 46319 - Flipbook: Setting a Read node frame control to start at a float value displayed a blank flipbook.
• BUG ID 46320 - Flipbook: Attempting to flipbook a Read node that was not connected to a Viewer caused Nuke to
crash.
Known Issues and Workarounds
This section covers known issues and gives workarounds for them, where appropriate.
• Mac OS X only: If you're running Mac OS X 10.10 "Yosemite", you may need to install alternative NVIDIA CUDA
drivers so that Nuke can detect your GPU correctly. You can obtain the required drivers directly from NVIDIA here:
http://www.nvidia.com/object/macosx-cuda-6.5.18-driver.html
• Multi-view, such as stereoscopic, is not supported for track items created using right-click Effects > Create Comp.
• Nuke Studio .hrox projects are not backward compatible with Hiero 1.8 or 1.9.
• BUG ID 46380 - QuickTime: Certain QuickTimes with linear retimes applied will not decode correctly.
• BUG ID 46302 - QuickTime: Some codecs saved in Nuke 8 scripts are not restored with the correct codec when read
into Nuke 9.
• BUG ID 46235 - Comps with relative paths are not currently working when imported into the Project bin.
• BUG ID 45433 - AAF: Track names are not imported correctly from AAF sequences.
• BUG ID 44895 - Exporting file types using mov64 using the {ext} token in the shot template always resolves to
.mov, regardless of the format chosen.
As a workaround, ensure that you set the File Type of the movie file explicitly in the path, rather than using the
{ext} keyword.
• BUG ID 43913 - Locking a track currently prevents adding track items from the locked track to the Viewer input
buffers. You can still open track items in the various right-click Open In options and access track item metadata.
• BUG ID 43747 - The Export dialog token {nameindex} has been replaced by {_nameindex} to avoid clashes with
non-unique shot names. The new token accomplishes this by appending _01, _02, and so on, to the shot names.
If you saved an export preset in a previous release containing the old form, Create Comp cannot find the preset
and fails. There are several solutions to this issue:
• Delete your custom export presets referencing {nameindex}.
• Replace all instances of {nameindex} with {_nameindex} in your export .xml files.
• Click Restore Preset Defaults in the Export dialog to return all presets to their default values, automatically
replacing the token with the updated form.
• BUG ID 43319 - GPU Accleration: If your computer enters sleep mode, the CUDA drivers cannot recover and you
must restart Nuke to use GPU acceleration.
Click on the Node Graph to un-pause and update the Viewer.
5
RELEASE NOTES FOR NUKE STUDIO PUBLIC BETA 06 | KNOWN ISSUES AND WORKAROUNDS
• BUG ID 42717 - Certain .exr files rendered from Modo display the alpha channel rather than the rgba channels by
default.
• BUG ID 42581 - Linux only: Using Ctrl+C to quit Nuke from the command line when a dialog box is open displays
an error.
• BUG ID 42557 - The Conforming Viewer doesn't display the same keyboard shortcuts for zoom and fit options as
the Compositing Viewer.
• BUG ID 42486 - The Viewer gain slider currently changes the alpha channel of clips, affecting the alpha's
transparency.
• BUG ID 42462 - Editing the timeline disables the Viewer pause caching button, causing caching to resume.
• BUG ID 42438 - Soft Effects: Effects are only visible in the Viewer if there is a track item below them in the timeline.
• BUG ID 42428 - Pressing D to enable or disable track items and soft effects occasionally causes the current time
indicator to jump back to the start of the sequence.
• BUG ID 42401 - Soft Effects: Renaming a soft effect does not update the track item until you click in the timeline.
As a workaround, you can edit or rename your ~/Nuke9.0v1/plugins/menu.py file.
• BUG ID 42307 - Soft Effects: Adding soft effects at clip level, using Open In > Timeline View, is only available
using the add effect button on the timeline panel. The right-click Effects menu is currently disabled.
• BUG ID 42271 - The Nuke Studio interface still references Hiero in some instances.
• BUG ID 42261 - Viewer A/B blending modes aren't working correctly with multiple tracks and Obey Alpha enabled.
• BUG ID 42236 - Editing: The Razor tool cursor doesn't always update to display the full razor icon on the timeline
making accurate edits difficult.
As a workaround, click away from the target track item and then mouse back over the point you want to edit to
force a refresh.
• BUG ID 42159 - Nodes that use the Iop::sample() call to get input pixels, such as LensDistortion, perform poorly
when they are downstream of nodes using PlanarIop, such as Denoise.
• BUG ID 42152 - Soft Effects: Timeline or clip in and out points currently restrict where soft effects are permissible.
Areas outside the in/out range cannot hold new soft effects.
• BUG ID 42053 - It is currently possible to change the displayed frame range in the Compositing Viewer by
dragging the playhead past the current frame range in Input and Global modes.
• BUG ID 42010 - Soft Effects: Certain Transform soft effect controls do not work as expected.
• BUG ID 41981 - Licensing: Launching Nuke on new MacPros with multiple Thunderbolt devices may display a
licensing dialog explaining that FLEXlm licensing has been disabled, probably due to having too many ethernet
addresses active on the machine.
Please contact [email protected] to work around this issue.
• BUG ID 41745 - It is not currently possible to drag-and-drop a clip to a new track between or below existing tracks.
As a workaround, drag the clip to a new top-level track and then manually move the track to the required position.
• BUG ID 41665 - Create Comp: There are currently no options to load or overwrite an existing script when you select
Create Comp.
6
RELEASE NOTES FOR NUKE STUDIO PUBLIC BETA 06 | DEVELOPER NOTES
Developer Notes
Here are the changes relevant to developers. See Help > Documentation from the Nuke menu bar for more
information.
NOTE: Node Class() names occasionally change between major releases, such as Nuke 7 to Nuke 8. While
these changes do not affect legacy scripts, you may not get the results you were expecting if a node class
has been modified. The toolbars.py file, used to create Nuke's node toolbar, contains all the current node
class names and is located in <install_directory>/plugins/nukescripts/ for reference.
As an example, between Nuke 7 and Nuke 8, the Text node Class() changed from Text to Text2. In the
toolbars.py file for the two releases, the entries for the Text node appear as follows:
m.addCommand("Text", "nuke.createNode(\"Text\")", icon="Text.png")
m.addCommand("Text", "nuke.createNode(\"Text2\")", icon="Text.png")
New Features
There are no new features in this release.
Feature Enhancements
There are no feature enhancements in this release.
Bug Fixes
• BUG ID 46188 - Registering a PySide widget as a panel caused Nuke to crash on exit.
• BUG ID 46231 - Calling reconnectMedia() displayed a dialog, causing the function to stall.
• BUG ID 46262 - NDK: The optional arguments for file_types() were not actually optional.
7
Release Notes for Nuke Studio
Public Beta 05
Release Date
31 October 2014
Qualified Operating Systems
• Mac OS X 10.7 (Lion), 10.8 (Mountain Lion), 10.9 (Mavericks)
NOTE: Nuke is expected to function correctly under Mac OS X 10.9 (Mavericks), but we are seeing UI
performance degradation compared to previous OS X versions. We are working on resolving these issues.
• Windows 7 64-bit and Windows 8 64-bit
• CentOS/RHEL 5 and CentOS/RHEL 6
Other operating systems may work with Nuke, but have not been fully tested. If you have any problems with a
particular operating system, please contact [email protected].
Requirements for GPU Acceleration
If you want to enable Nuke to calculate certain nodes using the GPU, there are some additional requirements. You
need to have, either:
• an NVIDIA GPU with compute capability 2.0 (Fermi) or above. A list of the compute capabilities of NVIDIA GPUs is
available at www.nvidia.co.uk/object/cuda_gpus_uk.html
NOTE: The compute capability is a property of the GPU hardware and can't be altered by a software
update.
With graphics drivers capable of running CUDA 4.2 or above.
• On Windows and Linux, CUDA graphics drivers are bundled with the regular drivers for your NVIDIA GPU.
Drivers from April 2012 onward support CUDA 4.2.
RELEASE NOTES FOR NUKE STUDIO PUBLIC BETA 05 | LAUNCHING AND LICENSING INFORMATION
Go to http://www.nvidia.com/Download/Find.aspx?lang=en-us for more information.
• On Mac, the CUDA driver is separate from the NVIDIA graphics driver and must be installed, if you don't have it
already. The minimum requirement for CUDA 4.2 is driver version 4.2.5, which can be downloaded from
www.nvidia.com/drivers.
NOTE: We recommend using the latest graphics drivers, where possible, regardless of operating system.
• an AMD FirePro XXXX running on Mavericks 10.9.5 (see below and Nuke's Help > Documentation > Guide to
Writing Blink Kernels menu for caveats on CPU/GPU result consistency on Mac Pros).
Late 2013 Mac Pro Only
Nuke Studio supports GPU-enabled nodes on the late 2013 Mac Pro 6.1 (running OS X 10.9.3 'Mavericks', or later),
including a new Enable multi-GPU support option. When enabled in the properties of supported nodes, GPU
processing is shared between the available GPUs for extra processing speed.
NOTE: Due to outstanding Mac OS X issues with OpenCL, GPU processing is not currently available on late
2013 Mac Pro 6.1, in the following circumstances:
• If you're running an earlier version of Mac OS X than 10.9.4 'Mavericks', Kronos and MotionBlur do not
support GPU acceleration.
• If you're running an earlier version of Mac OS X than 10.9.5 'Mavericks' and processing images greater
than 4 mega pixels resolution, VectorGenerator, Kronos, and MotionBlur do not support GPU
acceleration.
Launching and Licensing Information
• Nuke can be run on the command line from the installation directory without any arguments. For example, on
Windows:
C:/Program Files/Nuke9.0v1/Nuke9.0.exe
NukeX and Nuke Studio can be run on the command line from the installation directory using the --nukex and --studio arguments. For example, on Windows:
C:/Program Files/Nuke9.0v1/Nuke9.0.exe --studio
• Nuke Studio requires nukex_i and nuke_i licenses with valid maintenance.
New Features
• BUG ID 45116 - Mac OS X only: A new global preference (Preferences > Hardware > enable Multi-GPU
support) has been added for multi-GPU processing on Late-2013 Mac Pros running 10.9.3 'Mavericks', or later.
9
RELEASE NOTES FOR NUKE STUDIO PUBLIC BETA 05 | FEATURE ENHANCEMENTS
• BUG ID 45327 - Soft Effects: Sequence-level effects added to populated tracks are now limited and linked to the
range of the track item to which they are applied. Linked soft effects are moved and edited along with their parent
track item.
If you add a soft effect to an empty track, this new behavior doesn't apply.
Feature Enhancements
• BUG ID 36201/45883 - Documentation: There is now a link to the Hiero Python Dev Guide for Nuke Studio's
timeline operations on the Help > Documentation landing page.
• BUG ID 39148 - Linux only: mov64Reader now reads alpha channels correctly.
• BUG ID 43835 - QuickTime: Nuke can now read nclc and general meta atom metadata using mov64Reader.
Optionally read in metadata can be parsed to more closely match standard Nuke metadata, including stripping
reverse DNS notation.
• BUG ID 44841 - Soft Effects: Character caching has been overhauled in the Text effect to improve performance.
• BUG ID 45207 - PlanarTracker: The TSR dropdown has been replaced by individual buttons, including sheer and
perspective.
• BUG ID 45313 - mxfReader: Nuke can now read JPEG2000 files.
• BUG ID 45320 - Export: Soft effects are now applied to a clip's full length, incuding handles, where available.
• BUG ID 45410 - Metadata: Passing metadata key pairs between the Comp and Timeline environments has been
unified.
• BUG ID 45411 - Create Comp: The node tree output from comp track items has been rearranged so that the soft
effects can get metadata from the timeline.
• BUG ID 45414 - OCIO: Nuke now sets sensible default color transforms automatically when you specify a custom
OCIO config file.
• BUG ID 45505 - UHD_4K has been added to the root formats in the timeline and compositing environments. In
addition, the Comp and Timeline root formats have been made more consistent.
• BUG ID 45529 - Python: Custom toolbars are now added to the content menu Windows > Custom menu, rather
than the Pane menu.
• BUG ID 45650 - PlanarTracker: A CornerPin creation dropdown has been added to the PlanarTracker properties.
• BUG ID 45818 - Viewer: The proxy resolution dropdown now displays an asterisk next to the ratio, such as 1:1*,
when the resolution was set automatically.
• BUG ID 45829 GPU Acceleration: The FN_NUKE_DISABLE_CUDA environment variable has been renamed FN_
NUKE_DISABLE_GPU_ACCELERATION to reflect the fact that it also affects OpenCL (including Mac Pro AMD cards).
Bug Fixes
• BUG ID 16226 - mov64Reader: Reading h.264 files did not always show the correct frame.
10
RELEASE NOTES FOR NUKE STUDIO PUBLIC BETA 05 | BUG FIXES
• BUG ID 24059 - ScanlineRender: The playback cache bar did not always work as expected when the bg input was
not connected.
• BUG ID 41102 - Monitor Out: Enabling Monitor Out from the Conforming layout when it was already enabled in
the Compositing layout did not display a warning that the SDI was already in use.
• BUG ID 41408 - Windows only: Reading .avi files in the Compositing layout displayed a Read error: no plugin
named "aviReader" found error.
• BUG ID 41630 - Nuke Studio would not play back clips when no audio device was selected.
• BUG ID 41878 - Zooming in A/B horizontal or vertical mode occasionally caused the A or B buffer input to be
partially covered by the other buffer.
• BUG ID 42126 - Soft Effects: Adding multiple soft effects concurrently was slow and printed mulitple
QNetworkReplyImplPrivate::error messages in the command line or Terminal.
• BUG ID 42435 - Soft Effects: The TimeWarp effect Viewer rendering and exported output were inconsistent.
• BUG ID 42479 - Documentation: There was no information on applying soft effects using the Python API in the
Developer documentation.
• BUG ID 42560 - The Compositing and Conforming Viewers did not have a keyboard shortcut for Fit Width
assigned.
• BUG ID 42669 - TImeline: Track items on the timeline temporarily disappeared after adding annotations or when
soft effects were rendering.
• BUG ID 42770 - Closing Nuke by clicking the x button in between the splash screen and project dialog appearing
caused Nuke to crash.
• BUG ID 44434 - PlanarTracker: Tracking a plane using the Python API caused Nuke to crash.
• BUG ID 44609 - Frame Server: Using multiple external Frame Server slaves could cause rendering corruption.
• BUG ID 44614 - Monitor Output: The bit-depth combo box was causing Blackmagic output issues.
• BUG ID 44683 - Using the shortcut Ctrl+I in the Project bin had no effect and an error was displayed in the
command prompt.
• BUG ID 44672 - Monitor Output: After monitor output was enabled, it could not be disabled – the output image
was retained on the monitor, even after closing application.
• BUG ID 44858 - Export: Part of the exported image was rendered black, due to Reformat node settings in Nuke
scripts.
• BUG ID 44919 - Viewers: Opening a certain script in the Conforming workspace opened two Viewers and caused
Nuke to crash on exit.
• BUG ID 44967 - Dope Sheet: Move actions were not registered in the undo stack.
• BUG ID 44971 - Roto/RotoPaint: Selecting and removing a shape from the curves list, by pressing Delete,
occasionally removed multiple unselected shapes.
• BUG ID 45060 - Script Editor: Text in the Output panel was echoed by the command line or Terminal.
• BUG ID 45069 - Flipbook: Flipbooking the B input buffer and then the A input buffer affected clip timecodes and
playback.
• BUG ID 45083 - Flipbook: New Flipbooks always defaulted to Timecode, rather than inheriting the Viewer setting.
• BUG ID 45087 - Flipbook: Setting Frame range to Viewer# did not use the correct frame range.
11
RELEASE NOTES FOR NUKE STUDIO PUBLIC BETA 05 | BUG FIXES
• BUG ID 45112 - Soft Effects were ignored or caused playback to freeze when they were placed above a transition.
• BUG ID 45185 - Soft Effects: Timewarp keyframes on clip-level soft effect were not translated properly when
added to the timeline.
• BUG ID 45199 - Scopes were not split into two when both the A and B input buffers were active.
• BUG ID 45259 - Flipbook: Having hiero_tools code inside your .nuke > init.py file caused a flipbbok nodeName
error.
• BUG ID 45280 - Monitor Out: Changing workspace to or from Finishing occasionally caused Nuke to crash when
monitor output was active.
• BUG ID 45389 - Export: Transitions in exports did not match the output in the Timeline Viewer.
• BUG ID 45494 - Compositing Viewer: The Next/Previous keyframe buttons did not use the correct icons and
tooltips.
• BUG ID 45504 - QuickTime: The mov32 and mov64 readers loaded different metadata.
• BUG ID 45508 - PlanarTracker: Expressions links in the CornerPin node did not specify the PlanarTrackLayer.
• BUG ID 45593 - Resizing or zooming in a Viewer in A/B mode caused displacement of the buffers across the
available space.
• BUG ID 45692 - QuickTime: Audio did not play back from certain QuickTimes with non-integer framerates.
• BUG ID 45711 - Annotations did not respect clip reformat settings and were displayed in the wrong place.
• BUG ID 45720 - GridWarp: Actions within GridWarp were not registered in the Undo tree.
• BUG ID 45722 - GridWarp: Removing and re-adding GridWarp nodes using the Undo system caused Nuke to crash.
• BUG ID 45737 - OCIO: Flipbooks were empty when flipbooking the Write node from a comp created with a project
specific OCIO config file.
• BUG ID 45745 - Create Comp: Specifying a project level custom OCIO config file caused Create Comp to fail silently.
• BUG ID 45755 - OCIO/QuickTime: Playback of .movs never reached 60 fps when an OCIO config file was specified.
• BUG ID 45759 - Reading files before the Viewer was loaded in the Node Graph caused Nuke to crash.
• BUG ID 45772 - PlanarTracker: The Properties panel did not have the controls required to handle corrections.
• BUG ID 45776 - Timeline: Scrubbing over a dissolve transition between a razored track item caused one track item
to display black in the Viewer.
• BUG ID 45822 - Create Comp: Frame server rendering was slower than expected when Preferences >
Performance > Threads/Processes > no renderer limits was enabled.
• BUG ID 45834 - OCIO: Specifying an OCIO config file added Undo change root.OCIO_config into the Edit menu.
• BUG ID 45843 - OCIO: Create Comp did not include an OCIOColorspace node when a custom OCIO config was
specified for the project.
• BUG ID 45846 - Soft Effects: Keyframes in clip-level soft effects were incorrect when viewed at sequence level.
• BUG ID 45853 - OCIO: Specifying an OCIO config file that did not exist caused Nuke to crash.
• BUG ID 45863 - OCIO: The default OCIO config file preference was not exposed in the Nuke Preferences.
• BUG ID 45870 - Write: The Properties panel Views control displayed incorrectly.
• BUG ID 45873 - OCIO: The default color transforms for new projects were incorrect after specifying a project OCIO
config file.
12
RELEASE NOTES FOR NUKE STUDIO PUBLIC BETA 05 | BUG FIXES
• BUG ID 45875 - Creating a bin clip a second time and assigning it to the same variable name caused Nuke to crash.
• BUG ID 45888 - OCIO: Setting a Viewer LUT from a custom OCIO config in the Timeline Viewer displayed an
OpenColorEffectManager error in the Terminal.
• BUG ID 45896 - OCIO: Reloading an OCIO .ccc file caused problems with OCIOColorTransform.
• BUG ID 45899 - Opening a certain sequence in the timeline View caused a crash on exit.
• BUG ID 45900 - Text: Deleting the second of any two of the same character next to each other, changed the size of
the first character.
• BUG ID 45904 - Text: Frame expressions on character transforms confused which character to transform.
• BUG ID 45909 - Text: Playing through a clip with Text in the Viewer and changing font, caused character corruption.
• BUG ID 45914 - OCIO: Exports did not start if an OCIO config file was specified and use ocio nodes when export
was disabled.
• BUG ID 45917 - Importing a module that didn't exist on launch caused Nuke to dispaly a runtime error and crash.
• BUG ID 45922 - Flipbook/Capture: Rendered frames were always stored in NUKE_TEMP_DIR, regardless of the
Preferences settings.
• BUG ID 45932 - Nuke was exhibiting memory leaks during sequence playback.
• BUG ID 45941 - OFX: Adding an OFX plug-in to the Node Graph caused Nuke to crash on exit.
• BUG ID 45955 - Export: Executing Build Track from Export Structure, undoing, and then rebuilding it again read
track items incorrectly.
• BUG ID 45959 - Exporting sequences containing .nk comp track items to EDL/XML referenced the .nk files, rather
than the rendered files.
• BUG ID 45964 - OCIO: Setting OCIO config to nuke-default and enabling use OCIO nodes when exporting set
the colorspace to linear for Create Comp scripts.
• BUG ID 45970 - PlanarTracker: Tracks jumped to the end of the frame range when tracking was canceled or
stopped.
• BUG ID 45971 - PlanarTracker: Multiple track layers were not handle correctly.
• BUG ID 45976 - Flipbook: Playing a flipbook with a flipbook al2ready open doubled the playback speed.
• BUG ID 45980 - Soft Effects: Playing back effects on top of .nk track items occasional caused Viewer corruption.
• BUG ID 45984 - Flipbook: It was not posible to flipbook a Viewer after capturing it.
• BUG ID 45995 - Flipbook: It was not possible to flipbook .mxf files.
• BUG ID 45999 - 3D: Switching from a custom camera (positioned in interactive mode) to the default camera
occasionally caused Nuke to crash.
• BUG ID 46001 - Flipbook: All new flipbooks defaulted to Global rather than the frame slider range.
• BUG ID 46003 - Transitions: Sending a transition to the A/B input buffers caused Nuke to crash.
• BUG ID 46008 - OCIO: Project level OCIO config files did not support path remapping.
• BUG ID 46013 - Create Comp: Canceling a render canceled all frames, including those already rendered.
• BUG ID 46014 - Versioning: Versioning up a Nuke script versioned all Write nodes, not just the timeline Write node.
• BUG ID 46015 - Write: The Render to timeline option didn't work as expected.
• BUG ID 46026 - OCIO: The Nuke default OCIO config file was written into the project and Preferences.
13
RELEASE NOTES FOR NUKE STUDIO PUBLIC BETA 05 |
• BUG ID 46029 - Create Comp: The .nk reader did not report the actual timecode from renders.
• BUG ID 46031 - Viewers: Typing 1 or 2 in the Viewer fps control sent the current selections to the A/B input
buffers.
• BUG ID 46032 - Export: Sequence exports did not support project OCIO config settings.
• BUG ID 46035 - Export: Using custom Read nodes reported Python errors in the NukeShotExporter.
• BUG ID 46038 - Soft Effects: Text effects containing Python referencing the currentViewer caused Nuke to crash
on exit.
• BUG ID 46050 - Flipbook: Colorspace setting were not applied correctly when flipbooking directly from a Read
node.
• BUG ID 46056 - RotoPaint: Switching to 3D and then opening RotoPaint properties in a certain script caused Nuke
to crash.
• BUG ID 46061 - Gizmos: Loading a gizmo using File > Insert Comp Nodes caused Nuke to crash.
• BUG ID 46062 - OCIO: The built-in Nuke OCIO config file contained an additional entry labeled ".."
• BUG ID 46065 - File Browser: Default directory favorites were missing from the favorites panel.
• BUG ID 46066 - mov64: Reading single channel Photo - JPEG QuickTimes caused Nuke to crash.
• BUG ID 46072 - Export: During an export, if you pressed Pause, Stop All, or Clear Complete and then pressed
Continue, the export remained at 0%. This sometimes caused a crash.
• BUG ID 46079 - Create Comp: Viewing disabled comps during rendering displayed washed out frames.
• BUG ID 46088 – Export: The Export Queue panel had a Stop All button instead of a Cancel All button, which was
not consistent with the Background Renders panel.
• BUG ID 46103 - Soft Effects: Clip level Text effects did not update the frame count when the effect was is edited
until the shot was moved.
• BUG ID 46105 - Viewer: Expression driven nodes did not fill the cache bar correctly at certain zoom levels.
• BUG ID 46120 - File Browser: Favorites with expressions in their file paths did not work as expected.
• BUG ID 46127 - Localization: Decreasing the size of a localised file reported that the cache had run out of space.
• BUG ID 46132 - Timeline Viewer: Clicking in either the In or Out field with Viewer display set to TC (Timecode)
caused Nuke to become unresponsive.
• BUG ID 46157 - Timeline / Editing: The sequence Properties tab Flip, Flop, and Turn controls did not work as
expected when Resize Type was set to Scale.
• BUG ID 46171 - Reconnecting Media: Nuke script containers were not re-linked during batch folder relinking.
• BUG ID 46186 - Comp Viewer: Opening a comp containing a valid frame range did not set the In and Out points
correctly.
• BUG ID 46190 - Viewers: Splitting a Viewer vertically forced the playback buttons into the overflow menu.
14
RELEASE NOTES FOR NUKE STUDIO PUBLIC BETA 05 | DEVELOPER NOTES
Developer Notes
Here are the changes relevant to developers. See Help > Documentation from the Nuke menu bar for more
information.
NOTE: Node Class() names occasionally change between major releases, such as Nuke 7 to Nuke 8. While
these changes do not affect legacy scripts, you may not get the results you were expecting if a node class
has been modified. The toolbars.py file, used to create Nuke's node toolbar, contains all the current node
class names and is located in <install_directory>/plugins/nukescripts/ for reference.
As an example, between Nuke 7 and Nuke 8, the Text node Class() changed from Text to Text2. In the
toolbars.py file for the two releases, the entries for the Text node appear as follows:
m.addCommand("Text", "nuke.createNode(\"Text\")", icon="Text.png")
m.addCommand("Text", "nuke.createNode(\"Text2\")", icon="Text.png")
New Features
There are no new features in this release.
Feature Enhancements
There are no feature enhancements in this release.
Bug Fixes
• BUG ID 43857 - Custom panels were not registered correctly.
• BUG ID 45985 - Calling Clear() with a Group node open in the Node Graph and then loading a .nk script caused
Nuke to crash.
• BUG ID 46006 - Calling Viewer.cachedFrames() returned an empty set if the playhead was not at the first frame.
15
Release Notes for Nuke Studio
Public Beta 04
Release Date
16 October 2014
Qualified Operating Systems
• Mac OS X 10.7 (Lion), 10.8 (Mountain Lion), 10.9 (Mavericks)
NOTE: Nuke is expected to function correctly under Mac OS X 10.9 (Mavericks), but we are seeing UI
performance degradation compared to previous OS X versions. We are working on resolving these issues.
• Windows 7 64-bit and Windows 8 64-bit
• CentOS/RHEL 5 and CentOS/RHEL 6
Other operating systems may work with Nuke, but have not been fully tested. If you have any problems with a
particular operating system, please contact [email protected].
Requirements for GPU Acceleration
To take advantage of GPU acceleration, you must have:
• an NVIDIA GPU with compute capability 2.0 (Fermi) or above. A list of the compute capabilities of NVIDIA GPUs is
available at www.nvidia.co.uk/object/cuda_gpus_uk.html
NOTE: The compute capability is a property of the GPU hardware and can't be altered by a software
update.
• graphics drivers capable of running CUDA 4.2 or above.
• On Windows and Linux, CUDA graphics drivers are bundled with the regular drivers for your NVIDIA GPU.
Drivers from April 2012 onward support CUDA 4.2.
Go to http://www.nvidia.com/Download/Find.aspx?lang=en-us for more information.
RELEASE NOTES FOR NUKE STUDIO PUBLIC BETA 04 | LAUNCHING AND LICENSING INFORMATION
• On Mac, the CUDA driver is separate from the NVIDIA graphics driver and must be installed, if you don't have it
already. The minimum requirement for CUDA 4.2 is driver version 4.2.5, which can be downloaded from
www.nvidia.com/drivers.
NOTE: We recommend using the latest graphics drivers, where possible, regardless of operating system.
Late 2013 Mac Pro Only
Nuke Studio supports GPU-enabled nodes on the late 2013 Mac Pro 6.1 (running OS X 10.9.3 'Mavericks', or later),
including a new Enable multi-GPU support option. When enabled in the properties of supported nodes, GPU
processing is shared between the available GPUs for extra processing speed.
NOTE: Due to outstanding Mac OS X issues with OpenCL, GPU processing is not currently available on late
2013 Mac Pro 6.1, in the following circumstances:
• If you're running an earlier version of Mac OS X than 10.9.4 'Mavericks', Kronos and MotionBlur do not
support GPU acceleration.
• If you're running an earlier version of Mac OS X than 10.9.5 'Mavericks' and processing images greater
than 4 mega pixels resolution, VectorGenerator, Kronos, and MotionBlur do not support GPU
acceleration.
Launching and Licensing Information
• Nuke can be run on the command line from the installation directory without any arguments. For example, on
Windows:
C:/Program Files/Nuke9.0v1/Nuke9.0.exe
NukeX and Nuke Studio can be run on the command line from the installation directory using the --nukex and --studio arguments. For example, on Windows:
C:/Program Files/Nuke9.0v1/Nuke9.0.exe --studio
• Nuke Studio requires nukex_i and nuke_i licenses with valid maintenance.
New Features
• BUG ID 38019/43995/44008/44484 - OCIO: You can now set a project specific OCIO config file in the Timeline
environment, independent of the Preferences, by navigating to Project > Edit Settings > Color Management
tab. Any actions from the Timeline environment that use OCIO settings, such as Create Comp, use this setting.
New projects and Nuke scripts always pick up their OCIO settings from the Preferences > Project Defaults
> Color Management settings.
• BUG ID 40576 - OCIO: The OpenColorIO library has been updated to 1.0.9.
17
RELEASE NOTES FOR NUKE STUDIO PUBLIC BETA 04 | FEATURE ENHANCEMENTS
Feature Enhancements
• BUG ID 33304 - R3D: Nuke Studio now ignores either the X or A frame of HDRx files, so that the timecode is
correct.
• BUG ID 42914 - Read: Nuke Studio's Read node now includes a Metadata tab, allowing you quick access to clip
metadata without adding a ViewMetadata node to the script.
• BUG ID 43679 - R3D: GPU debayering has been added to the r3dReader, allowing for fast decodes without a Red
Rocket card.
• BUG ID 44166 - Timeline Viewer: Nuke Studio's Timeline Viewer now includes a timeline range lock identical to the
Compositing Viewer control.
• BUG ID 44479 - Viewers: The keyboard shortcut to enable overscan (Alt+O) has been re-purposed to remove out
points.
• BUG ID 44783 - Documentation: Appendix A: Hotkeys has been moved to Appendix B and updated to include
Timeline and revised Compositing environment keyboard shortcuts.
• BUG ID 44840 - Viewers: The frame range lock
now appears on both Timeline and Compositing Viewers and
works as expected, when compared to Nuke 8.
• BUG ID 44894 - Playback Cache: Viewer playback cache bars now show the intersection of the A and B input
buffers' cached frames. A frame is only highlighted in green if it's cached in both buffers.
• BUG ID 44904/44906 - FrameServer: Broker and worker logging has been improved to help diagnose FrameServer
issues. The logs are written to NUKE_TEMP_DIR/logs by default, and take the form:
broker.log
worker-0001f2cf-d771-4dfd-8c71-6ba417906abd.log
worker-0004f559-7465-43ec-91f6-446e2d300014.log
• BUG ID 44908/45422 - Frame Server: The Background Render panel now includes a Logs tab reporting status
for each render. The Export Queue also displays error logging.
• BUG ID 44910/45423 - Frame Server: New notification messages have been added when you try to execute Frame
Server related actions and no workers are available, or if Nuke Studio can't connect to the Frame Server.
• BUG ID 45268 - The RIP framework and Blink API are now versioned in the same way as DDImage.
• BUG ID 45293/45294 - General UI: Dropdown controls have been standardized so that multi-selection controls,
such as masks, don't close when a selection is made and toggle controls, such as channel, do. This behavior also
applies to controls that are pushed into, or pulled out of, the overflow menus when screen space is limited.
• BUG ID 45339 - Preferences: Caching behavior when the application goes into the background has been divided
into two sections, one for Timeline Viewers and one for Comp Viewers, allowing you to control caching behavior
more easily. Navigate to Preferences > Performance > Caching > Application in Background for more details.
• BUG ID 45359 - mov64Reader: Decode and playback speeds have been improved by implementing fast planar
path using mov64Reader.
• BUG ID 45373 - mxfReader: Decode and playback speeds have been improved by implementing fast planar path
using mxfReader.
18
RELEASE NOTES FOR NUKE STUDIO PUBLIC BETA 04 | BUG FIXES
• BUG ID 45532 - Viewers: New fields have been added to set the frame range on either side of the frame slider.
These fields work in the same way as Nuke 8's frame range control to quickly set in an out points.
• BUG ID 45589 - Comp Viewer: The Freeze UI button has been removed from the Viewer controls and is now
enabled as standard. The new behavior stops updates elsewhere on the interface during RAM cache playback,
helping to optimize the playback frame rate.
• BUG ID 45685 - Viewers: The add in and out point buttons (and associated shortcuts) now remove in and out
points if the playhead is on the frame at which the point resides.
• BUG ID 45872 - Create Comp: You can now open a comp track item or bin clip in the Node Graph by right-clicking
the track item or clip, and selecting Open In > Node Graph.
Bug Fixes
• BUG ID 35138 - R3D: The gamma space option Half Float Linear was incorrectly labeled Linear.
• BUG ID 39338 - DopeSheet: Attempting to undo a Move for a selection of keyframes did not work as expected.
• BUG ID 40095 - OCIO: Create Comp did not work as expected after specifying an OCIO config file.
• BUG ID 40203 - Python: Nuke took longer to execute Python scripts than previous versions to accommodate
changes in Dope Sheet functionality.
• BUG ID 41533/45390 - Timeline: Duplicate, copy, cut, delete, move functions were not disabled for track items
opened in the Timeline View (right-click, Open In > Timeline View), and could cause Nuke Studio to crash.
• BUG ID 41895 - Multiple QGLContext::makeCurrent() errors were printed in the command line when exiting
Nuke Studio.
• BUG ID 41973 - Zooming in and out in the timeline was too sensitive.
• BUG ID 42103 - Soft Effects: Transforming a Text soft effect box and then undoing it, repositioned the box
incorrectly.
• BUG ID 42107 - Soft Effects: Drag selecting text in the Viewer selected only one character.
• BUG ID 42327 - Python: Running two Python scripts in quick succession caused Nuke Studio to crash.
• BUG ID 42329 - ModelBuilder: Source footage occasionally looked 'blown out' when viewed through the camera.
• BUG ID 42358 - In the timeline, using the scroll bar to move along the timeline caused track item names and
thumbnails to slide along the clip until the transition between the current item and next item.
• BUG ID 42418 - The application font and stylesheet changed when the Preferences dialog was closed.
• BUG ID 42609 - CameraTracker: Clicking the Import Tracker button on the User Tracks tab caused Nuke Studio
to crash.
• BUG ID 42620 - CameraTracker: Tracking still frames occasionally failed when running Nuke Studio from the
command line.
• BUG ID 42676 - Mac OS X only: Dragging .hrox or .nk files onto the Nuke Studio dock icon did not open a project
or script.
• BUG ID 42841 - Undoing a batch move of clips between bins in the Project panel only replaced a single clip per
undo.
19
RELEASE NOTES FOR NUKE STUDIO PUBLIC BETA 04 | BUG FIXES
• BUG ID 42851 - Timeline Viewer: In A/B wipe mode, selecting invert & add displayed invert && add when
selected.
• BUG ID 42955 - Licensing: Launching Nuke Studio with a close to expiry license displayed a Licensing dialog with
two Launch buttons.
• BUG ID 42966 - Create Comp: Playing back a .dpx comp, generated from the same 4K 10-bit RGB files, did not play
back as fast as the source .dpx sequence.
• BUG ID 42984 - Monitor Output: Playback did not progress in Monitor Output A/B mode if there was no clip in the
B input buffer.
• BUG ID 43142 - CameraTracker: Tracking low contrast source images occasionally caused Nuke Studio to crash.
• BUG ID 43393 - Soft Effects: Setting node presets (the wrench icon in the Properties panel) did not work as
expected.
• BUG ID 43429 - 3D: The new look at input for Camera, Light, and Axis nodes doesn't work in certain scripts.
• BUG ID 43483 - Scopes: The out of range color value warnings did not update correctly.
• BUG ID 43518 - Documentation: The changes to the Python startup directory (~/.nuke/Python/Startup) were not
included in the documentation.
• BUG ID 43556 - Soft Effects: Dragging knob values or expression linking between controls did not work as
expected.
• BUG ID 43577 - Large scripts were affecting performance in the Node Graph.
• BUG ID 43795 - Soft Effects: Keyframes did not retain their position relative to their associated soft effect.
• BUG ID 43802 - Timeline Viewer: Pressing Return in the fps control did not set the value as expected.
• BUG ID 43878 - Disconnecting Denoise from the source clip, in a customer script, caused Nuke Studio to crash.
• BUG ID 44159 - UI General: Menu items collapsed into the bottom overflow menu in the wrong order when screen
space was limited.
• BUG ID 44188/45261 - Timeline Viewer: Playback occasionally stalled when the playback cache was full and the
Viewer proxy level was changed, particularly with timelines containing clips at 720p and 4K resolutions.
• BUG ID 44413 - R3D: Opening R3D clips in a Timeline Viewer and changing Media panel controls printed a
ScopeSourceIP error to the command line.
• BUG ID 44428 - EXR: Nuke Studio produced different results to Nuke 8 when writing certain premultiplied .exr
files.
• BUG ID 44460 - Create Comp: Nuke script track items displayed in the wrong color when opening a project with no
associated renders available.
• BUG ID 44472 - Timeline: The timeline panel did not auto-scroll to follow the playhead on zoomed in timelines.
• BUG ID 44474 - Create Comp: Comp track items' color did not update to green when relinked.
• BUG ID 44483 - New projects didn't use the Color Management settings from the Preferences until Nuke Studio
was restarted.
• BUG ID 44525 - EXR: Rendering .exr files with a high thread count was slower than expected.
• BUG ID 44578 - MatchGrade: LUTs created from MatchGrade clipped values incorrectly.
• BUG ID 44684 - nkReader: Scripts created in Nuke 8, or earlier, were colored green in the timeline even though they
were not rendered.
20
RELEASE NOTES FOR NUKE STUDIO PUBLIC BETA 04 | BUG FIXES
• BUG ID 44715 - Text: Rendering certain scripts from the command line printed multiple Setting knob values
from validate is not supported and may cause unexpected behavior messages.
• BUG ID 44751 - Linux only: Switching from the Compositing to Conforming workspace did not update the
menubar until you clicked in a panel.
• BUG ID 44779 - Documentation: The keyboard shortcut for show/hide overlay was not updated to Q.
• BUG ID 44824 - Timeline Viewer: Decoding .mxf DNxHD HD 1080p files was not fast enough to play back in realtime when frames were not cached.
• BUG ID 44835 - Linux only: Deleting Grade soft effect keyframes in the Dope Sheet caused Nuke Studio to crash.
• BUG ID 44848 - Write: Enabling Render in background in the Render dialog failed when Continue on Error was
enabled.
• BUG ID 44853 - Export: Exporting a certain sequence containing an audio track caused Nuke Studio to crash.
• BUG ID 44862 - Soft Effects: Transform keys didn't appear in the Dope Sheet until another key was moved.
• BUG ID 44875 - Loading scripts saved in earlier versions of Nuke did not load downrez settings correctly.
• BUG ID 44878 - mov64Reader: Write nodes using mov64Reader did not add audio into movie files, they exported
it as a separate .wav file instead.
• BUG ID 44885 - AJA Monitor Out: Setting the NUKE_AJA_CHANNEL=4 with NUKE_AJA_DUALOUTPUT=1
environment variables defaulted to DualLinkSDI through SDI 1+2 instead of SDI 3+4.
• BUG ID 44888 - Viewers: Double-clicking or MMB zooming in the Viewer stopped playback.
• BUG ID 44897 - Using the Ctrl/Cmd+Shift+I keyboard shortcut to import a folder after using the Ctrl/Cmd+I
keyboard shortcut to import a file, caused Nuke Studio to crash.
• BUG ID 44923 - Create Comp: Canceling a render before completion still changed the track item color to green.
• BUG ID 44935 - Windows only: Dissolving between two razored shots of the same clip produced an OCIO error for
some formats.
• BUG ID 44950 - Create Comp: Transitions (dissolve, fade in, and fade out) were ignored in Nuke scripts produced
from Create Comp.
• BUG ID 44963 - The leading control in the Text node and Text soft effect did not work as expected.
• BUG ID 44972/44987 - Opening a .nk or .hrox file from the OS browser, right-click menu, or desktop started the
application, but did not load the script.
• BUG ID 44993 - Text: In proxy mode, shadows created using a high expand value that reached the bbox extended
into infinity.
• BUG ID 44997 - Workspace names between Nuke and Nuke Studio were inconsistent.
• BUG ID 45011 - Windows only: Reading a .mov file into the Node Graph caused Nuke Studio to hang on exit.
• BUG ID 45031 - Timeline Viewer: Obey Alpha was always enabled during playback.
• BUG ID 45033 - Pixel Analyzer: RGBA values and HSVL values represented different colors.
• BUG ID 45084 - Preferences: Documentation preferences were not shown/hidden depending on the
documentation source chosen.
• BUG ID 45105 - Create Comp: The script name didn't update the application title bar when the comp was opened
in the Node Graph.
21
RELEASE NOTES FOR NUKE STUDIO PUBLIC BETA 04 | BUG FIXES
• BUG ID 45106 - Viewers: The thin gray seperator at the top edge of the color info bar was missing from the
Viewers.
• BUG ID 45108 - Preferences: NodeColour#Color preferences were not transferred from earlier Nuke versions.
• BUG ID 45121 - Flipbook: Manually dragging or Ctrl+clicking to place an in point reset the out point position and
vice versa.
• BUG ID 45127 - Text: Animating the tracking or kerning controls caused text to wobble.
• BUG ID 45136 - Compositing Viewer: The playback cache bar behaved erratically when the Viewer was maximized.
• BUG ID 45148 - Timeline: Changing settings in the Properties panel for a deleted track item caused Nuke Studio to
crash.
• BUG ID 45158 - Documentation: There was no documentation regarding registering a plug-in or gizmo as a soft
effect.
• BUG ID 45170 - The Timeline environment Project Settings > Export / Roundtrip > Project Root control
overlayed the folder icon next to the Choose button.
• BUG ID 45193 - Dragging .ari clips from the Project tab to the Node Graph printed no such knob errors on the
command line.
• BUG ID 45208 - Preferences: The Splines > line width and draw shadow controls were missing.
• BUG ID 45213 - Playing back while caching different resolution clips in a sequence caused playback to accelerate to
60 fps.
• BUG ID 45216 - Mac OS X only: Closing a project after performing certain operations caused Nuke Studio to crash.
• BUG ID 45250 - The Don't show this dialog again checkbox on the startup dialog appeared between the Open
and Close buttons.
• BUG ID 45260 DopeSheet: Undoing a Move for a selection of keyframes did not work as expected.
• BUG ID 45265 - Viewers: The out point (or end frame) in the frame slider was displayed inconsistently.
• BUG ID 45308 - EDL: Importing .edls forced the workspace to change to Conforming.
• BUG ID 45318 - Compositing Viewer: View buttons, such as main, left and right, were occasionally displayed
incorrectly when the Viewer was resized.
• BUG ID 45329 - Create Comp: Render output resolution was not set correctly.
• BUG ID 45334 - Soft Effects: Zooming in the VIewer rendered shadows differently when Monitor Out was enabled.
• BUG ID 45336 - r3dReader: Default values from clip metadata were not read correctly.
• BUG ID 45351 - Import: Importing a certain directory containing a mixture of media formats caused Nuke Studio
to crash.
• BUG ID 45355 - Pressing 1 or 2 in the timeline with no tracks selected did not set the A or B input buffers to display
all tracks.
• BUG ID 45361 - Viewers: The color sample and info bar at the bottom of the Viewers was not enabled by default.
• BUG ID 45362 - Text: Custom box sizes caused text to behave strangely when editing or formatting.
• BUG ID 45369 - Timeline: Locked tracks could be deleted using the right-click Delete menu option.
• BUG ID 45386 - Soft Effects: Managing user knobs was not disabled for soft effects.
22
RELEASE NOTES FOR NUKE STUDIO PUBLIC BETA 04 | BUG FIXES
• BUG ID 45417 - Create Comp: Versioning down a comp caused problems with track and color coding of track
items.
• BUG ID 45445 - Python: The undo system did not work through Python in the Script Editor.
• BUG ID 45459 - UI General: There were inconsistencies in positioning and sizing of certain control panel elements.
• BUG ID 45462 - MonitorOut: Activating monitor out with nothing in the Viewer caused Nuke Studio to crash.
• BUG ID 45463 - Timeline Viewer: Enabling See Through Missing Media displayed track items on lower tracks at
the wrong resolution or with an incorrect LUT.
• BUG ID 45466 - Timeline Viewer: Nuke Studio did not handle corrupt or missing frames correctly causing playback
or exports to stall.
• BUG ID 45467 - Timeline Viewer: Maximising the Timeline Viewer displaced the buffer input menus from their
correct positions.
• BUG ID 45499 - Export/Create Comp: Long sequences occasionally took a long time to start rendering from the
timeline or caused Nuke Studio to become unresponsive.
• BUG ID 45502 - Flipbook: The Flipbook did not display the same list of OCIO LUTs as the Viewer when Nuke Studio
was set to use an OCIO config file.
• BUG ID 45507 - Licensing: Navigating to Help > License... opened the plug-ins web page, rather than the
Licensing dialog.
• BUG ID 45520 - PlanarTracker: CornerPin nodes created from PlanarTracker had different corner ordering to the
default CornerPin node.
• BUG ID 45525 - PlanarTracker: Correcting planar surfaces when the PlanarTracker layer was not selected did not
work as expected.
• BUG ID 45540 - Dope Sheet: Switching between multiple Node Graph paths did not update the Dope Sheet.
• BUG ID 45549 - Project panel: The thumbnail size slider and filter bar didn't resize well in the Finishing workspace
on the minimum supported screen resolution.
• BUG ID 45558 - Importing some .mov files printed not enough frames to estimate rate on the command line.
• BUG ID 45562 - Soft Effects: Creating a comp after right-clicking a soft effect and selecting Set key on all knobs
did not work as expected.
• BUG ID 45563 - Timeline: Trimming a track item and then moving it to a different track caused Nuke Studio to
crash.
• BUG ID 45569 - PlanarTracker: The Viewer toolbar was hidden when no PlanarTracker layers existed.
• BUG ID 45570 - Viewers: The frame slider range dropdown Visible option did not respect the visible bounds of the
frame slider.
• BUG ID 45571 - Viewers: Some playback tools at the bottom of the Viewers did no t have tooltips.
• BUG ID 45576 - Soft Effect: Resizing the font in a Text effect and then typing text into the message field including a
[timecode] expression, caused Nuke Studio to crash.
• BUG ID 45581 - Windows only: Nuke worker instances occasionally crashed on startup.
• BUG ID 45587 - Annotations: Executing Create Comp Special for multiple track items, with Collate Shot Name
enabled in the Preset, placed annotation keyframes in the wrong place.
23
RELEASE NOTES FOR NUKE STUDIO PUBLIC BETA 04 | BUG FIXES
• BUG ID 45590 - Soft Effects: Zooming in and out in the Viewer made the Text effect shadow distance appear to
jump around.
• BUG ID 45591 - Create Comp: Track item colors were incorrect when switching between versions during rendering.
• BUG ID 45595 - Monitor Out: The Monitor out toggle in the Comp Viewer overflow menu did not work as
expected.
• BUG ID 45598 - Soft Effects: Moving a Mirror effect, or any registered custom effect, caused Nuke Studio to
become unresponsive.
• BUG ID 45606 - r3dReader: Running versions of CUDA earlier than version 6 printed multiple Failed to set cuda
device 35 messages to the command line.
• BUG ID 45623 - OCIO: Specifying an OCIO config file displayed incorrect channels in the Comp Viewer.
• BUG ID 45627 - Annotations: The sequence level annotations track was not locked as the top track when a new
track was added.
• BUG ID 45633 - Annotations: Sequence level annotations were not displayed in the A or B input buffer, dependent
on focus.
• BUG ID 45638 - Soft Effects: Drag selection in transform mode was applied to all open Text soft effects.
• BUG ID 45641 - Annotations: Re-exporting comp annotations exported all annotations, rather than just those
affecting the comp.
• BUG ID 45649 - mov64Reader: Nuke Studio didn't recognize colorspaces in the Read node.
• BUG ID 45652 - Soft Effects: Pasting effects into locked tracks was allowed.
• BUG ID 45655 - Progress bars were hidden when switching to another application then back to Nuke Studio.
• BUG ID 45660 - Viewers: Keyframes markers did not resize to fill the gaps between frame ticks in the frame slider.
• BUG ID 45661 - MXF: Reading in some .mxf file formats caused Nuke Studio to crash.
• BUG ID 45663 - QuickTime: Pre-Nuke 9 scripts with the audiofile knob set did not populate the audiofile knob in
Nuke 9.
• BUG ID 45665 - Soft Effects: Adding a soft effect and then undoing did not remove the effect's Properties panel.
• BUG ID 45677 - Workspaces: Loading the Editing workspace and then changing to another workspace carried the
second Viewer over to the new workspace.
• BUG ID 45697 - Create Comp: The comp track item created did not inherit the source clip's format.
• BUG ID 45704 - Export: Retiming clips resulted in transcode renders not matching the frames in the Timeline
Viewer.
• BUG ID 45707 - Create Comp: Playback performance for a rendered 4K UHD comp track item was poor.
• BUG ID 45709 - OCIO: Setting an OCIO config file using the OCIO environment variable did not work as expected.
• BUG ID 45711 - Annotations: Clip reformat settings were not respected, resulting in annotations displaying in the
wrong place.
• BUG ID 45713 - Export: Disabling track item reformatting when exporting a sequence did not work as expected.
• BUG ID 45735 - OCIO: LUTs did not fall back to nuke-default when no OCIO config file was specified in the
Project Settings.
24
RELEASE NOTES FOR NUKE STUDIO PUBLIC BETA 04 | BUG FIXES
• BUG ID 45740 - QuickTime: The mov32Writer had incorrect default parameters set, resulting in Warning: Write_
mov.codec: no such knob errors in the Export Queue.
• BUG ID 45743 - Audio: Reconnecting an audio bin clip, using the right-click Clip > Reconnect Media menu option,
caused Nuke Studio to crash.
• BUG ID 45754 - Viewers: The Gain control numeric field was cut off if more than a single digit.
• BUG ID 45760 - Timeline: Track item thumbnails and labels occasionally disappeared when zooming rapidly in the
timeline.
• BUG ID 45761 - Undo: Using undo keyboard shortcuts didn't work if the focus was on the Viewer.
• BUG ID 45781 - Preferences : The Script Editor font size control did not change the font size.
• BUG ID 45782 - OCIO: Viewer color transforms set in the Timeline environment Project > Edit Settings > Color
Management dialog were not applied correctly during playback.
• BUG ID 45792 - mov64Reader: Alpha channels were not read correctly in the Compositing Environment.
• BUG ID 45794 - Create Comp: Comps referencing .r3d source files didn't set the Sharpness control correctly.
• BUG ID 45796 - Viewers: The in and out point numeric fields did not display the start and end frames, in the
Timeline Viewer, or the global range, in the Comp VIewer, when a clip was added.
• BUG ID 45797 - Timeline: Pressing the J or L keyboard shortcuts multiple times to increase playback speed didn't
work when timeline had focus.
• BUG ID 45801 - Timeline: Disabling a clip connected to a transition caused Nuke Studio to crash.
• BUG ID 45806 - Nuke Studio always set the tilecache directory as the default NUKE_TEMP_DIR directory,
regardles of the directory set in the preferences under Performance > Caching > temp directory.
• BUG ID 45807 - Windows only: Enabling performance profiling and opening or rendering a customer script caused
Nuke Studio to crash.
• BUG ID 45823 - PlanarTracker: Tracking features and then switching to image tracking did not hide the feature
tracking data in the Viewer.
• BUG ID 45840 - Moving pt# widgets in the Viewer can cause Nuke to crash
• BUG ID 45878 - Matchgrade: The output of MatchGrade was slightly different to the output of Vectorfield with a
.csp file generated from MatchGrade.
25
RELEASE NOTES FOR NUKE STUDIO PUBLIC BETA 04 | DEVELOPER NOTES
Developer Notes
Here are the changes relevant to developers. See Help > Documentation from the Nuke menu bar for more
information.
NOTE: Node Class() names occasionally change between major releases, such as Nuke 7 to Nuke 8. While
these changes do not affect legacy scripts, you may not get the results you were expecting if a node class
has been modified. The toolbars.py file, used to create Nuke's node toolbar, contains all the current node
class names and is located in <install_directory>/plugins/nukescripts/ for reference.
As an example, between Nuke 7 and Nuke 8, the Text node Class() changed from Text to Text2. In the
toolbars.py file for the two releases, the entries for the Text node appear as follows:
m.addCommand("Text", "nuke.createNode(\"Text\")", icon="Text.png")
m.addCommand("Text", "nuke.createNode(\"Text2\")", icon="Text.png")
New Features
There are no new features in this release.
Feature Enhancements
• BUG ID 42722 - Linux only: Nuke Studio now calls XInitThreads at startup to avoid certain crashes caused by an
assert in X11.
Bug Fixes
• BUG ID 45485 - Calling ViewerProcess.register_viewers resulted in a TypeError, because the call to _register_
viewer_processes was missing an argument.
• BUG ID 45527 - r3dReader: Reading .r3d files called set_value on knob values inside validate, which is not
supported, resulting in multiple warnings on the command line.
• BUG ID 45528 - arriReader - Reading .ari files called set_value on knob values inside validate, which is not
supported, resulting in multiple warnings on the command line.
26
Release Notes for Nuke Studio
Public Beta 03
Release Date
26 September 2014
Qualified Operating Systems
• Mac OS X 10.7 (Lion), 10.8 (Mountain Lion), 10.9 (Mavericks)
NOTE: Nuke is expected to function correctly under Mac OS X 10.9 (Mavericks), but we are seeing UI
performance degradation compared to previous OS X versions. We are working on resolving these issues.
• Windows 7 64-bit and Windows 8 64-bit
• CentOS/RHEL 5 and CentOS/RHEL 6
Other operating systems may work with Nuke, but have not been fully tested. If you have any problems with a
particular operating system, please contact [email protected].
Requirements for GPU Acceleration
To take advantage of GPU acceleration, you must have:
• an NVIDIA GPU with compute capability 2.0 (Fermi) or above. A list of the compute capabilities of NVIDIA GPUs is
available at www.nvidia.co.uk/object/cuda_gpus_uk.html
NOTE: The compute capability is a property of the GPU hardware and can't be altered by a software
update.
• graphics drivers capable of running CUDA 4.2 or above.
• On Windows and Linux, CUDA graphics drivers are bundled with the regular drivers for your NVIDIA GPU.
Drivers from April 2012 onward support CUDA 4.2.
Go to http://www.nvidia.com/Download/Find.aspx?lang=en-us for more information.
RELEASE NOTES FOR NUKE STUDIO PUBLIC BETA 03 | LAUNCHING AND LICENSING INFORMATION
• On Mac, the CUDA driver is separate from the NVIDIA graphics driver and must be installed, if you don't have it
already. The minimum requirement for CUDA 4.2 is driver version 4.2.5, which can be downloaded from
www.nvidia.com/drivers.
NOTE: We recommend using the latest graphics drivers, where possible, regardless of operating system.
Late 2013 Mac Pro Only
Nuke Studio supports GPU-enabled nodes on the late 2013 Mac Pro 6.1 (running OS X 10.9.3 'Mavericks', or later),
including a new Enable multi-GPU support option. When enabled in the properties of supported nodes, GPU
processing is shared between the available GPUs for extra processing speed.
NOTE: Due to outstanding Mac OS X issues with OpenCL, GPU processing is not currently available on late
2013 Mac Pro 6.1, in the following circumstances:
• If you're running an earlier version of Mac OS X than 10.9.4 'Mavericks', Kronos and MotionBlur do not
support GPU acceleration.
• If you're processing images greater than 4 mega pixels resolution, VectorGenerator, Kronos, and
MotionBlur do not support GPU acceleration.
Launching and Licensing Information
• Nuke can be run on the command line from the installation directory without any arguments. For example, on
Windows:
C:/Program Files/Nuke9.0v1/Nuke9.0.exe
NukeX and Nuke Studio can be run on the command line from the installation directory using the --nukex and --studio arguments. For example, on Windows:
C:/Program Files/Nuke9.0v1/Nuke9.0.exe --studio
• Nuke Studio requires nukex_i and nuke_i licenses with valid maintenance.
New Features
• BUG ID 45113/45163 - Nuke Studio now supports the MXF file format DNxHD, MPEG2, and Uncompressed
readers.
Feature Enhancements
• BUG ID 44590 - The toggle Viewer overlay shortcut has changed from \ to Q, and the RotoPaint shortcut to return
to the current Select tool has changed to Esc.
28
RELEASE NOTES FOR NUKE STUDIO PUBLIC BETA 03 | BUG FIXES
• BUG ID 44691 - Compositing Viewer: The overflow menu button now has a new icon in-keeping with the general UI
changes for Nuke 9.
• BUG ID 45523 - Viewers: The layout of the toolbars in both Viewers has been overhauled for clarity and utility.
Bug Fixes
• BUG ID 38286 - Nuke Studio did not render Nuke comp containers with Write nodes set up for multiple views
(stereo).
• BUG ID 41605 - Soft Effects: Dragging an effect on the timeline closed its Properties panel.
• BUG ID 41631 - Scrubbing in the Viewer with an STMap node in a customer script caused Nuke to crash.
• BUG ID 41878 - Zooming in A/B Horizontal or Vertical mode occasionally caused the A or B buffer input to be
partially covered by the other buffer.
• BUG ID 41892 - Scan For Versions and Rescan Clip Range removed clip annotations and soft effects.
• BUG ID 42018 - Panning or zooming in the Viewer in A/B wipe mode occasionally clipped input buffer A.
• BUG ID 42333 - Licensing: Temporary licenses occasionally displayed multiple Licensing dialogs on launch.
• BUG ID 42452 - Linux only: The message libuuid.so.1: no version information available was printed to the
command line.
• BUG ID 43097 - Compositing Viewer: The Freeze GUI button (in the bottom menu overflow dropdown) and only
update Viewer during playback preference didn't work as expected.
• BUG ID 43434 - Compositing Viewer: The overflow (>>) button mouse-over highlights did not work.
• BUG ID 43590 - Color Sampler: The info bar color sample showed incorrect colors when picking in the Viewer.
• BUG ID 43795 - Soft Effects: Keyframes didn't retain their position relative to the soft effect with which they were
associated.
• BUG ID 43924 - BlinkScript: Displaying the Kernel Source printed Python errors to the command line.
• BUG ID 43936 - Viewer Mask and Guide selections did not work as expected when they were pushed into the
overflow menu.
• BUG ID 43981 - The Viewer A/B gang mode only worked from input buffer B.
• BUG ID 43991 - OCIO: Setting the config file using the OCIO environment variable did not work as expected.
• BUG ID 43998 - OCIO: The clip level Set Media Color Transform option did not apply the transform correctly.
• BUG ID 44302 - Windows only: Closing the command prompt during exit caused Nuke Studio to crash.
• BUG ID 44307 - Timeline Viewer: The clip timecode in the info bar did not update during playback.
• BUG ID 44310 - Timeline Viewer: The clip timecode in the info bar only updated for one buffer, not both.
• BUG ID 44405 - OCIO: LogC to ACES conversions did not work as expected.
• BUG ID 44486 - Annotations: Relinking an offline clip with clip level annotations removed the annotations and
stopped you adding new annotations.
• BUG ID 44535 - Disabling Preferences > Behaviors > File Handling > assume fixed width frame numbers
in files sequences and then flipbooking a sequence more than once, with padding that didn't start at zero,
caused Nuke Studio to crash.
29
RELEASE NOTES FOR NUKE STUDIO PUBLIC BETA 03 | BUG FIXES
• BUG ID 44561 - Annotations: Sequence level annotations in A/B mode did not add paint strokes on the
Annotations track correctly.
• BUG ID 44566 - Timeline: Copying and pasting a track item onto itself caused Nuke Studio to crash.
• BUG ID 44568 - Timeline: It was possible to paste track items into locked tracks.
• BUG ID 44822 - Create Comp: Comp track items appeared green on the timeline when created from an unrendered
Comp and its parent clip, or building a track from export tag.
• BUG ID 44832 - Create Comp: Opening a comp with a comp already open in the Compositing environment caused
Nuke Studio to crash on exit.
• BUG ID 44833 - Soft Effects: Adding animation to effects affected real-time playback.
• BUG ID 44843 - The Curve Editor and Dope Sheet were redrawn during playback, which affected the frame rate.
• BUG ID 44851 - Timeline: Slipping a track item that referenced an .mxf clip caused Nuke Studio to crash.
• BUG ID 44858 - Export: Part of the exported image was rendered black, due to Reformat node settings in the Nuke
script.
• BUG ID 44929 - Create Comp: Accessing a pre-existing comp in --safe mode displayed a permissions error.
• BUG ID 44930 - Licensing: The licensing dialog displayed when attempting to launch NukeX with only a nuke_i
license included a PLE button, rather than a Start standard Nuke button.
• BUG ID 44933 - Annotations: Inverting the Text tool bounding box prevented future resizing of the box.
• BUG ID 44943 - Preferences: The custom options displayed under Preferences > Performance >
Threads/Processes > Customize renderer limits were collapsed incorrectly when the preferences were
reopened.
• BUG ID 44969 - OFlow: The Input Range controls were not auto-populated with the incoming frame range when
the node was connected.
• BUG ID 44970 - OFlow: Setting the Timing control to Output Speed calculated the output frame range
incorrectly.
• BUG ID 45030/45074 - Timeline Viewer: Certain actions in the Viewer , such as setting an In or Out point, reset the
FPS dropdown to 24(auto) fps.
• BUG ID 45039 - Workspaces: Saving a workspace based on a custom workspace did not work as expected.
• BUG ID 45049 - File Browser: Opening the file browser occasionally printed FileChooser_Favorites.pref: No
such file or directory to the command line.
• BUG ID 45081 - Opening legacy scripts displayed multiple no such knob warnings.
• BUG ID 45085 - Viewers: The Freeze GUI and Lock Viewer to Range buttons were always placed in the overflow
menu, even when screen space was available.
• BUG ID 45086 - Flipbook: Flipbooking a sequence always started at 0, ignoring the Frame range control.
• BUG ID 45124 - Flipbook: Canceling a render and loading the completed range set the I/O points according to the
frame range control, but the actual frames started at 0, making playback difficult.
• BUG ID 45138 - Color Picker: Setting Preferences > Panels > Control Panels > color picker button opens to
floating color picker only displayed slider controls.
• BUG ID 45139 - Timeline Viewer/Flipbook: Color Picker sample regions were drawn solid orange when the ROI tool
was enabled.
30
RELEASE NOTES FOR NUKE STUDIO PUBLIC BETA 03 | BUG FIXES
• BUG ID 45140 - Node Toolbar: The hover and active states of icons in the toolbar did not work as expected.
• BUG ID 45172 - Soft Effects: Trimming a track item with a clip level Timewarp applied caused Nuke Studio to crash.
• BUG ID 45176 - Annotations: The Text tool font size dropdown contained checkboxes without labels.
• BUG ID 45195 - Undo: Dropping a bin clip into the Node Graph was not registered in the undo stack.
• BUG ID 45199 - Windows only: Scopes were not split when the A and B input buffers were active.
• BUG ID 45227 - OFlow/Kronos: Enabling Advanced > Overlay Vectors in the node properties caused Nuke
Studio to crash.
• BUG ID 45230 - Viewers: The Masks did not display as expected when enabled.
• BUG ID 45234 - Create Comp: The format of the master clip was used when creating a comp, rather than the
sequence format.
• BUG ID 45274 - GPU Acceleration: Launching Nuke Studio from the command line using the --gpu argument,
disabled the Local GPU control in the properties of accelerated nodes, such as Kronos.
• BUG ID 45278 - MotionBlur, Kronos, VectorGenerator: Launching standard Nuke from the command line with the -gpu argument printed This functionality is only available in NukeX when enabling Use GPU if available.
• BUG ID 45283 - Soft Effects: The Text effect rendered incorrectly when the box x control was negative.
• BUG ID 45310 - Export: Exporting track items with handles applied soft effects to the wrong frame range in the .nk
script.
• BUG ID 45322 - Annotations: Adding annotations on the A input buffer when A/B was in stack mode did not work
as expected.
• BUG ID 45328 - PlanarTracker: Adding and then undoing a CornerPin or Tracker using the Viewer toolbar caused
Nuke Studio to crash.
• BUG ID 45337 - Export: There was a significant delay after clicking Export for a single shot before the render
started.
• BUG ID 45341 - Windows only: An error message regarding dynamically linked libraries was displayed when adding
a node to the Node Graph.
• BUG ID 45342 - OFlow: The Method dropdown, used to select the type of frame interpolation, was missing.
• BUG ID 45346 - Viewers: The color channel display menu (Red, Green, Blue, Alpha, etc.) was not consistent between
the TImeline and Compositing Viewers.
• BUG ID 45388 - ParticleBounce: Disabling or deleting geometry attached to the geometry input caused Nuke
Studio to crash.
• BUG ID 45420 - Frame Server: The command line path remap argument (--remap) was not passed through to
Nuke workers.
• BUG ID 45438 - AAF: Importing .aaf files printed multiple unnecessary lines to the command line.
• BUG ID 45445 - Script Editor: Python undo commands were not registered within the undo stack.
• BUG ID 45447 - Viewers: The A input buffer was not always the Active buffer by default.
• BUG ID 45457 - Kronos: Opening a script where the Input Range was modified manually always reset the range to
the clip length.
• BUG ID 45458 - OFlow/Kronos: The new controls did not include a Channels dropdown.
• BUG ID 45547 - Viewers: In A/B stack mode, clicking in the Viewer switched the active buffer.
31
RELEASE NOTES FOR NUKE STUDIO PUBLIC BETA 03 | DEVELOPER NOTES
Developer Notes
Here are the changes relevant to developers. See Help > Documentation from the Nuke menu bar for more
information.
NOTE: Node Class() names occasionally change between major releases, such as Nuke 7 to Nuke 8. While
these changes do not affect legacy scripts, you may not get the results you were expecting if a node class
has been modified. The toolbars.py file, used to create Nuke's node toolbar, contains all the current node
class names and is located in <install_directory>/plugins/nukescripts/ for reference.
As an example, between Nuke 7 and Nuke 8, the Text node Class() changed from Text to Text2. In the
toolbars.py file for the two releases, the entries for the Text node appear as follows:
m.addCommand("Text", "nuke.createNode(\"Text\")", icon="Text.png")
m.addCommand("Text", "nuke.createNode(\"Text2\")", icon="Text.png")
New Features
There are no new features in this release.
Feature Enhancements
• BUG ID 45312 - A new method, BackdropNode::getNodes(), has been added to return a list of nodes contained
within a Backdrop node.
Bug Fixes
• BUG ID 44758 The DataCollection.keys() method did not display the correct help() information.
• BUG ID 45166 - It was not possible to create knobs on root nodes at startup using the init.py or menu.py files.
• BUG ID 45412 - nuke.pluginAppendPath calls made from init.py searched directories multiple times.
32
Release Notes for Nuke Studio
Public Beta 02
Release Date
16 September 2014
Qualified Operating Systems
• Mac OS X 10.7 (Lion), 10.8 (Mountain Lion), 10.9 (Mavericks)
NOTE: Nuke is expected to function correctly under Mac OS X 10.9 (Mavericks), but we are seeing UI
performance degradation compared to previous OS X versions. We are working on resolving these issues.
• Windows 7 64-bit and Windows 8 64-bit
• CentOS/RHEL 5 and CentOS/RHEL 6
Other operating systems may work with Nuke, but have not been fully tested. If you have any problems with a
particular operating system, please contact [email protected].
Requirements for GPU Acceleration
To take advantage of GPU acceleration, you must have:
• an NVIDIA GPU with compute capability 2.0 (Fermi) or above. A list of the compute capabilities of NVIDIA GPUs is
available at www.nvidia.co.uk/object/cuda_gpus_uk.html
NOTE: The compute capability is a property of the GPU hardware and can't be altered by a software
update.
• graphics drivers capable of running CUDA 4.2 or above.
• On Windows and Linux, CUDA graphics drivers are bundled with the regular drivers for your NVIDIA GPU.
Drivers from April 2012 onward support CUDA 4.2.
Go to http://www.nvidia.com/Download/Find.aspx?lang=en-us for more information.
RELEASE NOTES FOR NUKE STUDIO PUBLIC BETA 02 | LAUNCHING AND LICENSING INFORMATION
• On Mac, the CUDA driver is separate from the NVIDIA graphics driver and must be installed, if you don't have it
already. The minimum requirement for CUDA 4.2 is driver version 4.2.5, which can be downloaded from
www.nvidia.com/drivers.
NOTE: We recommend using the latest graphics drivers, where possible, regardless of operating system.
Late 2013 Mac Pro Only
Nuke Studio supports GPU-enabled nodes on the late 2013 Mac Pro 6.1 (running OS X 10.9.3 'Mavericks', or later),
including a new Enable multi-GPU support option. When enabled in the properties of supported nodes, GPU
processing is shared between the available GPUs for extra processing speed.
NOTE: Due to outstanding Mac OS X issues with OpenCL, GPU processing is not currently available on late
2013 Mac Pro 6.1, in the following circumstances:
• If you're running an earlier version of Mac OS X than 10.9.4 'Mavericks', Kronos and MotionBlur do not
support GPU acceleration.
• If you're processing images greater than 4 mega pixels resolution, VectorGenerator, Kronos, and
MotionBlur do not support GPU acceleration.
Launching and Licensing Information
• Nuke can be run on the command line from the installation directory without any arguments. For example, on
Windows:
C:/Program Files/Nuke9.0v1b106/Nuke9.0.exe
NukeX and Nuke Studio can be run on the command line from the installation directory using the --nukex and --studio arguments. For example, on Windows:
C:/Program Files/Nuke9.0v1b106/Nuke9.0.exe --studio
• Nuke Studio requires nukex_i and nuke_i licenses with valid maintenance.
New Features
BUG ID 44904/44906 - FrameServer: Broker and worker logging has been added to help diagnose FrameServer
issues. The logs are written to NUKE_TEMP_DIR/logs by default, and take the form:
broker.log
worker-0001f2cf-d771-4dfd-8c71-6ba417906abd.log
worker-0004f559-7465-43ec-91f6-446e2d300014.log
34
RELEASE NOTES FOR NUKE STUDIO PUBLIC BETA 02 | FEATURE ENHANCEMENTS
Feature Enhancements
• BUG ID 34333 - Tags: Two new Timeline Viewer hotspots have been added, in addition to the current sequence
and frame, allowing you to tag the current track item or the current clip.
• BUG ID 38990 - The Gopro Protune LUT has been added to Nuke's root LUTs and Colorspace node.
• BUG ID 41359 - Documentation: The in-application help from the Properties panel now works for soft effects as
well as regular Nuke nodes.
• BUG ID 44267 - Crash Reporter: The feature list has been updated to include Studio-specific features.
• BUG ID 44896 - Soft Effects: Render performance for the Text effect has been improved when the Viewer is
zoomed out and working at proxy resolution.
• BUG ID 44998 - The default application font and the style of various interface components have been changed to
match Nuke 8.
Bug Fixes
• BUG ID 39305 - The Preferences > Panels > Control Panels > color picker button opens dropdown, allowing
you to control the default color picker behavior, was missing.
• BUG ID 39941 - The Compositing Viewer's left-hand toolbar buttons didn't change state when selected.
• BUG ID 41231 - The Timeline Viewer's Wipe handles did not display translate or rotate icons when moused over.
• BUG ID 41465 - Soft Effects: The initial Text box cursor did not display in the Timeline Viewer.
• BUG ID 41607 - Setting the Project Root during comp creation opened a system file browser, rather than a Nuke
browser.
• BUG ID 41735 - Hiding the Timeline Viewer overlay did not affect masks, guides, or the Wipe handle.
• BUG ID 41981 - Licensing: Launching Nuke on new MacPros with multiple Thunderbolt devices caused FLEXlm
licensing to crash.
• BUG ID 41991 - Custom Viewer guides didn't work in the Timeline Viewer.
• BUG ID 42026 - The Viewer guides, masks, and clipping warning controls did not have tooltips.
• BUG ID 42040 - The Compositing Viewer's time slider did not display a black background outside the connected
Read node's framerange.
• BUG ID 42122 - BlinkScript: Loading a script containing a BlinkScript node that referenced a file, disabled the Load
button until you recomplied the kernel.
• BUG ID 42204 - Annotations: When the annotations menu was open in the Viewer, clicking the left and middle
mouse buttons together while dragging left or right, did not zoom in and out of the timeline Viewer.
• BUG ID 42235 - Soft Effects: Effects with channel controls applied to non- rgba layers, such as Grade, were
displayed in the Viewer for all layers rather than only those to which they were applied.
• BUG ID 42315 - The Viewer cache bar did not reset when the Viewer was zoomed to different levels.
• BUG ID 42346 - Scopes: Adding Scopes to a workspace caused them to flicker intermittently during playback.
35
RELEASE NOTES FOR NUKE STUDIO PUBLIC BETA 02 | BUG FIXES
• BUG ID 42705 - Soft Effects: Adjusting keyframes in the Curve Editor for TimeWarps did not update the VIewer
during playback.
• BUG ID 42830/43660 - Windows 8 only: Closing and then re-opening linked panels, with a Wacom tablet active,
caused Nuke Studio to crash.
• BUG ID 42832 - Windows only: The Histogram and Vectorscope did not update when scrubbing the timeline,
playing back, or adjusting controls.
• BUG ID 42899 - Denoise: Certain scripts containing Denoise and Copy nodes caused image corruption.
• BUG ID 43231 - Create Comp: Changing the format of the Write node from .dpx to .exr and re-rendering
produced corrupt output.
• BUG ID 43329 - Setting the output of the A/B Viewer buffer based on the Reference tag did not resize the format
of the clip to match that of the project.
• BUG ID 43465 - Changing the colorspace of clip on a Reference track did not update correctly in the Viewer when
the Tag filter was enabled.
• BUG ID 43681 - Monitor Out: SDI output did not switch between the Compositing and TImeline Viewer based on
focus.
• BUG ID 43713 - Dropdown menus substituted ellipses for full menu item names when the interface size was
adjusted.
• BUG ID 43724 - Soft Effects: Timewarps did not work as expected when placed underneath a soft effect longer
than itself.
• BUG ID 43745 - The Yes, No, and Cancel buttons on confirmation dialogs were reversed.
• BUG ID 43753 - When you used the ' (apostrophe) and ; (semi-colon) keyboard shortcuts to switch between the
left and right views of stereo footage, the Viewer buttons in the toolbar did not update to reflect the view change.
• BUG ID 43844 - Opening a project containing custom tags on a different machine did not import the icons for the
tags.
• BUG ID 43889 - There was a slight lag the in drawing of nodes when dragging them around the Node Graph, in
comparison to previous Nuke versions.
• BUG ID 44005 - Frame Server: Single frame that did not contain a frame number, did not load in the Compositing
environment.
• BUG ID 44023 - The Output Resolution dropdown in the Sequence tab did not show all the default formats at
once.
• BUG ID 44224 - Pressing 2 to insert a track into the B buffer always changed the A/B mode to wipe.
• BUG ID 44265 - After applying a tag to a track, if you renamed it and then opened a buffer input menu, Nuke
Studio crashed.
• BUG ID 44288 - In the timeline Viewer, when you enabled the format guides and zoomed or panned in Horizontal
or Vertical A/B mode, the format guides appeard in incorrect and inconsistent positions.
• BUG ID 44299 - Windows 8, Wacom: Adding a soft effect in the timeline workspace and then panning in the
timeline Viewer caused Nuke Studio to crash.
• BUG ID 44392 - Windows only: Executing Save Project or Save Project As caused Nuke Studio to crash with
certain projects.
36
RELEASE NOTES FOR NUKE STUDIO PUBLIC BETA 02 | BUG FIXES
• BUG ID 44431 - Setting files to Localization Policy > Always didn't work if the files already existed.
• BUG ID 44677 - With a Nuke comp selected, when you pressed the keyboard shortcut F5 to Render All Comp
Containers, it had no effect.
• BUG ID 44712 - The Output node's appearance was identical to the Input node.
• BUG ID 44775 - Displaying and dismissing dialog boxes, such as Rename Shots, occasionally caused the Viewer to
contain 'ghosted' images.
• BUG ID 44802 - When you clicked a Nuke comp from the Project bin, pressed Delete, and then pressed Cancel in
the confirmation dialog, the Nuke comp was still deleted.
• BUG ID 44814 - BlinkScript - An output image was able to have less than the full amount of channels (4) required
for pixel-wise kernels.
• BUG ID 44823/44825 - Saving and restoring a workspace did not retain maximized or monitor specific settings.
• BUG ID 44826 - Soft Effects: When soft effect handles were open in the Viewer, clicking the left and middle mouse
buttons together while dragging left or right, did not zoom in and out of the timeline Viewer.
• BUG ID 44829 - When you created multiple Nuke comps and cancelled the renders, Nuke Studio crashed on exit.
• BUG ID 44864 - Soft Effects: Scaling keyframe selections in the Dope Sheet did not work as expected.
• BUG ID 44874 - Create Comp: When you created a Nuke comp and the original project root directory had been
removed, there was no dialog warning you that the directory did not exist.
• BUG ID 44893 - Create Comp: When you created a Nuke comp of a track item, which had an animated Mirror soft
effect applied to it, Nuke Studio failed to create the Nuke comp.
• BUG ID 44898 - No error was displayed when attempting to open a Nuke Personal Learning Edition (PLE) script in
Nuke Studio.
• BUG ID 44911 - Preferences: The option start file browser from most recently used directory was missing
from the Panels – File Browser section in the Preferences dialog.
• BUG ID 44912 - Monitor Out: Dropdown controls were populated incorrectly until the panel was closed and
reopened.
• BUG ID 44914 - When you opened a saved project, the footage did not automatically display in the Viewer.
• BUG ID 44920 - Frame Server: When you chose to render a Nuke comp with a disconnected Write node, the Frame
Server processes' memory usage increased dramatically and exceeded preference limits.
• BUG ID 44936 - When you added a Text soft effect, clicked in the Viewer and started typing while the cursor is
moving – if you typed a letter that is also a Viewer shortcut, the application performed the shortcut function
instead of entering the letter into the text.
• BUG ID 44937 - FFmpeg Writer: Some codecs that were included in the FFmpeg writer did not read into QuickTime
file formats correctly.
• BUG ID 44938 - FFmpeg Reader/Writer: Roundtripping using the photo-jpeg codec, either through FFmpeg or the
official QuickTime reader, resulted in a color shift.
• BUG ID 44940 - FFmpeg Reader/Writer: Warning messages relating to jpeg and rgb48le were printed
unnecessarily to the terminal during normal operation.
• BUG ID 44942 - AAF: Intentional gaps at the beginning of tracks was ignored, forcing clips to start at the beginning
of the timeline.
37
RELEASE NOTES FOR NUKE STUDIO PUBLIC BETA 02 | BUG FIXES
• BUG ID 44977 - The Node Graph keyboard shortcut for cloning nodes (Alt + K) did not work as expected.
• BUG ID 44984 - Disconnecting a Convolve node in a customer script caused Nuke Studio to crash.
• BUG ID 45007 - 8-bit and 10-bit uncompressed .mxf clips were not recognized in Nuke Studio.
• BUG ID 45009 - FFmpeg Reader/Writer: Listed codec names did not match their QuickTime equivalents.
• BUG ID 45029 - The Help > Timeline Keyboard Shortcuts menu item did not display a list of shortcuts.
• BUG ID 45065 - Soft Effects: Double-clicking on a comp after modifying the animation on TimeWarp effect, caused
Nuke Studio to crash.
• BUG ID 45075 - Roto/RotoPaint: The icons in the toolbar appeared incorrect when compared to Nuke 8.
• BUG ID 45127 - Text: Characters occasionally wobbled when animating kerning or tracking.
• BUG ID 45131 - Soft Effects: TimeWarps that overlapped other track items affected the entire clip, rather than only
the section the TimeWarp covered.
• BUG ID 45168 - Create Comp: Keyframes were offset by -1000 when creating a comp from multiple track items.
• BUG ID 45189 - Nuke Studio allowed you to edit project settings when no project was selected in the Project tab.
• BUG ID 45201 - Flipbook: Switching between A/B buffers using the Enter keyboard shortcut caused Nuke Studio
to crash.
38
RELEASE NOTES FOR NUKE STUDIO PUBLIC BETA 02 | DEVELOPER NOTES
Developer Notes
Here are the changes relevant to developers. See Help > Documentation from the Nuke menu bar for more
information.
NOTE: Node Class() names occasionally change between major releases, such as Nuke 7 to Nuke 8. While
these changes do not affect legacy scripts, you may not get the results you were expecting if a node class
has been modified. The toolbars.py file, used to create Nuke's node toolbar, contains all the current node
class names and is located in <install_directory>/plugins/nukescripts/ for reference.
As an example, between Nuke 7 and Nuke 8, the Text node Class() changed from Text to Text2. In the
toolbars.py file for the two releases, the entries for the Text node appear as follows:
m.addCommand("Text", "nuke.createNode(\"Text\")", icon="Text.png")
m.addCommand("Text", "nuke.createNode(\"Text2\")", icon="Text.png")
New Features
BUG ID 44676 - A new foundry.ui.openFileBrowser() method has been added, allowing you to raise the Nuke file
browser to retrieve lists of files and directories. See help(foundry.ui.openFileBrowser) for usage details.
Feature Enhancements
BUG ID 44909 - Frame Server: You no longer need to specify the --noparent flag as a default option when running
runframeserver.py on external render machines with Nuke Studio.
Bug Fixes
There are no bug fixes in this release.
39
Release Notes for Nuke Studio
Public Beta 01
Release Date
02 September 2014
Qualified Operating Systems
• Mac OS X 10.7 (Lion), 10.8 (Mountain Lion), 10.9 (Mavericks)
NOTE: Nuke is expected to function correctly under Mac OS X 10.9 (Mavericks), but we are seeing UI
performance degradation compared to previous OS X versions. We are working on resolving these issues.
• Windows 7 64-bit and Windows 8 64-bit
• CentOS/RHEL 5 and CentOS/RHEL 6
Other operating systems may work with Nuke, but have not been fully tested. If you have any problems with a
particular operating system, please contact [email protected].
Requirements for GPU Acceleration
To take advantage of GPU acceleration, you must have:
• an NVIDIA GPU with compute capability 2.0 (Fermi) or above. A list of the compute capabilities of NVIDIA GPUs is
available at www.nvidia.co.uk/object/cuda_gpus_uk.html
NOTE: The compute capability is a property of the GPU hardware and can't be altered by a software
update.
• graphics drivers capable of running CUDA 4.2 or above.
• On Windows and Linux, CUDA graphics drivers are bundled with the regular drivers for your NVIDIA GPU.
Drivers from April 2012 onward support CUDA 4.2.
Go to http://www.nvidia.com/Download/Find.aspx?lang=en-us for more information.
RELEASE NOTES FOR NUKE STUDIO PUBLIC BETA 01 | LAUNCHING AND LICENSING INFORMATION
• On Mac, the CUDA driver is separate from the NVIDIA graphics driver and must be installed, if you don't have it
already. The minimum requirement for CUDA 4.2 is driver version 4.2.5, which can be downloaded from
www.nvidia.com/drivers.
NOTE: We recommend using the latest graphics drivers, where possible, regardless of operating system.
Late 2013 Mac Pro Only
Nuke Studio supports GPU-enabled nodes on the late 2013 Mac Pro 6.1 (running OS X 10.9.3 'Mavericks', or later),
including a new Enable multi-GPU support option. When enabled in the properties of supported nodes, GPU
processing is shared between the available GPUs for extra processing speed.
NOTE: Due to outstanding Mac OS X issues with OpenCL, GPU processing is not currently available on late
2013 Mac Pro 6.1, in the following circumstances:
• If you're running an earlier version of Mac OS X than 10.9.4 'Mavericks', Kronos and MotionBlur do not
support GPU acceleration.
• If you're processing images greater than 4 mega pixels resolution, VectorGenerator, Kronos, and
MotionBlur do not support GPU acceleration.
Launching and Licensing Information
• Nuke can be run on the command line from the installation directory without any arguments. For example, on
Windows:
C:/Program Files/Nuke9.0v1b106/Nuke9.0.exe
NukeX and Nuke Studio can be run on the command line from the installation directory using the --nukex and --studio arguments. For example, on Windows:
C:/Program Files/Nuke9.0v1b106/Nuke9.0.exe --studio
• Nuke Studio requires nukex_i and nuke_i licenses with valid maintenance.
New Features
Nuke, NukeX, and Nuke Studio
Nuke Studio is a new application mode, offering a timeline environment in addition to the nodal, single shot,
environment Nuke is known for. If you've used Hiero in the past, it essentially offers you Hiero's conforming, project
management, playback, and export feature set within the same application as Nuke. This allows entire sequences of
41
RELEASE NOTES FOR NUKE STUDIO PUBLIC BETA 01 | NEW FEATURES
shots to be worked on, both in terms of the timeline and the individual shot Node Graphs, and farmed out to other
Nuke artists.
Nuke Studio can be accessed from the relevant shortcut, or using the --studio flag on the command line. When run
in studio mode, the application uses a separate set of workspaces which include the relevant timeline, Viewer, project
and spreadsheet panels. Source material can be auditioned, timelines edited, Soft Effects applied, comps created,
edited, and rendered, and the final spot exported all from within the single package.
See Nuke Studio 9 Features for more information.
Nuke 9 Features
Performance Updates
"Just make it go faster". The most common request since we took over Nuke's development.
A lot of engineering has been dedicated to making performance boosts across the board. We have significantly
increased overall performance in Nuke 9 compared to Nuke 8. For example, improved exrReader and Deep EXR,
scene building and sampling in ScanlineRender, and mip-map filters have been added to ScanlineRender.
OFlow
Nuke Studio's OFlow node has benefitted from some of the improvement work done on Kronos and
VectorGenerator:
• New Resampling methods, including Lanczos4 and 6 for scaling.
• New control over retime curves in the input time range, as well as improved range integration, combining to give
you concise, intuitive control of your speed ramps.
• Same-same Blink GPU and CPU processing.
New Image Format Support
Support to read from MXF:
• DNxHD (all 1080p and 720p formats, 4:4:4:4 and 4:2:2 )
• MPEG2 (from Canon C300)
• Uncompressed (4:2:2 YCbCr and RGB).
• AVCI and DV (AVCI 'unconstrained' variety are not currently supported).
Native Flipbook Tool
Nuke Studio now features a native Flipbook panel. Clicking the Flipbook this viewer button under the
Compositing Viewer now uses an internal real time flipbook Viewer by default.
42
RELEASE NOTES FOR NUKE STUDIO PUBLIC BETA 01 | NEW FEATURES
Scanline Render Mip-map Texture Filters
ScacnlineRender now includes several new mip-map filter options providing performance improvement when
sampling from large textures. The new filters are listed below from fastest to most accurate:
• Nearest
• Bilinear
• Trilinear
• Anisotropic
Performance Timers
NUKE's performance timers have been updated to give more accurate and detailed timing information on all
platforms. When performance timing is enabled, timing information will be displayed in the node graph, and the
nodes themselves will be colored according to the proportion of the total processing time that was spent in each
one, from green (fast nodes) through to red (slow nodes).
In addition, new python calls have been added to provide python access to timing information for individual nodes.
Alternatively, NUKE can now be run from the command line with "-Pf " to obtain the full performance profile for a
render in XML format. Performance profiling can help you to debug slow scripts and find out where the bottlenecks
lie; this new feature was also used internally during the development of NUKE 9 to help us target our performance
work most effectively.
Node Improvements
• Backdrop nodes now have a Z Order control, allowing you to set the layering of Backdrops within other
Backdrops. The Backdrop with the highest Z Order is placed at the front.
• All Nuke nodes with a Node tab in their properties now include lifetime controls allowing you selectively enable
and disable nodes according to frame range when use lifetime is enabled.
Miscellaneous
• The Text node now includes a Shadows tab, allowing you to add drop shadow to text in the Viewer, either as a soft
effect or regular node in the Node Graph. Drop shadows incude color, softness (blur), and shrink/expand
(dilate) controls.
• You can now import and conform .aaf files in a similar way to .edl and .xml files. This initial implementation may
fail to conform certain file formats, but these are scheduled to be addressed in a future release.
• The Merge node now allow you to merge metadata as well as image data from selected or all inputs using the
metadata from dropdown.
• Nuke's Read node now includes a Metadata tab showing all metadata associated with the file(s) read in.
43
RELEASE NOTES FOR NUKE STUDIO PUBLIC BETA 01 | NEW FEATURES
NukeX 9 Features
PlanarTracker
PlanarTracker has been integrated into a single node, incorporating all the features of Roto and PlanarTracker.
Additional work includes:
• A pattern-matching algorithm.
• A region tracking algorithm which works with featureless areas of footage.
• A new luminance shift option for shots where luminance alters within the tracking region.
• A new Tracking tab in the Roto and RotoPaint nodes features some of PlanarTracker's features.
Kronos, VectorGenerator, and MotionBlur
The Foundry's motion estimation algorithm has been improved, based on Ocula technolgy, resulting in
improvemnets in vector generation, retiming, and motion blur:
• Improved retime quality - less artefacts and smoother warp.
• Improved image reconstruction, giving sharper images and less "pulsing" between sharp and blurry results as you
move between the original frames.
Additional work includes:
• New Resampling methods, including Lanczos4 and 6 for scaling.
• New control over retime curves in the input time range, as well as improved range integration, combining to give
you concise, intuitive control of your speed ramps.
• Same-same Blink GPU and CPU processing.
Nuke Studio 9 Features
Soft Effects
Soft Effects are GPU accelerated effects which can be added and manipulated directly in the timeline to perform
common tasks in real-time. Soft effects appear as a layer above track items on the timeline, or can be applied to their
own separate video sub-track layer. Soft effects apply their effect to whatever is beneath them in the timeline, for
the duration represented by the color bar in the timeline.
You can add Soft Effects by right-clicking track items and selecting Effects or by clicking the Effects icon in the
timeline Editing Tools and selecting the required effect. The following Soft Effects are currently available:
• Transform
• Mirror
44
RELEASE NOTES FOR NUKE STUDIO PUBLIC BETA 01 | NEW FEATURES
• Crop
• TimeWarp
• Grade
• LUT (OCIOFileTransform)
• CDL (OCIOCDLTransform)
• ColourSpace (OCIOColourSpace)
• Text
Create Comp
Create Comp adds containers to the timeline that ‘wrap up’ Nuke .nk scripts, allowing it to be played back, versioned,
and edited in the timeline as you would normally do with image clip media. A Comp container (indicated by a Nuke
icon) points to a .nk file on disk can be seen as clips in the bin or as track items in a sequence.
You can Create Comp using a predefined export preset or by using Create Comp Special, which allows you to set
the export properties on a shot-by-shot basis. Both options are available by right-clicking track items and selecting
Effects or by clicking the Effects icon in the timeline Editing Tools and selecting the required option.
Annotations
Annotations allow you to draw paint strokes and add text to your footage directly in the Timeline Viewer, enabling
you to add artistic direction or comp notes to your shots, and communicate your ideas visually to others.
You can enable annotations in the Viewer by clicking the annotations button in the Timeline Viewer toolbar (paint
brush). This button also toggles the visibility of annotations. From here you draw paint strokes or add text notes
using the left-hand toolbar. The color and stroke width of annotations can be modified, as well as the text’s font.
Annotations can be added to track items at the sequence or clip level, or on a per-frame basis, using the ‘+’ button on
the toolbar. They are saved into the project and can be exported into Nuke scripts. These can be passed on to artists
and viewed in Nuke by connecting the Annotations Precomp to the Viewer.
Viewer Re-design
Nuke Studio has two distinct Viewer types: Timeline and Compositing. The overall UI has been re-designed to make
them the same in all major aspects, with some differences specific to their purpose. For example, the Timeline Viewer
doesn't have any 3D controls or bounding box.
This is still a work in progress, we’ll let you know when every aspect of the new design has been implemented.
Background Renders Panel
A new Background Renders panel has been added, showing the progress of every Comp’s background render.
45
RELEASE NOTES FOR NUKE STUDIO PUBLIC BETA 01 | FEATURE ENHANCEMENTS
Workspace Overhaul
Nuke Studio features several new workspaces designed to help navigate around the various modes and workflows
invloved in the application. The default workspace, Finishing, contains a mix of the timeline and compositing
environment panels, letting you quickly switch between the two. Tabs in separate panels come to the fore if one of
the other tabs in their linked group are brought to the front.
Feature Enhancements
• ParticleBounce now includes a geometry input, allowing you to specify Nuke-native or imported geometry as the
bounce surface.
• BUG ID 3448/8412 - The Camera, Light, and Axis nodes now have look at and axis inputs.
• BUG ID 10128/44281 - FFmpeg: Writing QuickTimes now sets the timecode correctly.
• BUG ID 28082/36645 - Nuke Studio now includes Sony SLog2, SLog3, Canon CLog, and Gamma2.4 in the root
LUTs and nuke-default OpenColorIO config file. The Viewer LUTs have also been updated to include rec1886 and
gamma2.4.
• BUG ID 37787 - Curve Editor: You can now press Tab to switch between x and y values when manually editing
curves. Pressing Esc exits the editing dialog.
• BUG ID 41273 - Linux only: Audio tracks can now be combined with video tracks on export using ffmpegWriter.
• BUG ID 42691 - Improvements have been made to FFmpeg's color handling, which now uses 16-bit intermediate
formats to reduce banding in 10-bit codecs. Additionally, Nuke Studio now uses Rec601 and Rec709 colorspaces
correctly according to resolution.
• BUG ID 42803 - The R3D SDK has been updated to 5.0 for the CPU path only. GPU debayering is scheduled for a
later release. This update adds a new colorspace and gamma setting, DragonColor and RedGamma4, and support
for the Red Dragon camera and sensor.
• BUG ID 42914 - A new Metadata tab has been added to the Read node's Properties panel, allowing you to access
metadata from the associated files.
• BUG ID 44286 - Monitor Out: On AJA Kona 3G and above, 12-bit 4:4:4 3G SDI output is now supported in addition
to 8- and 10-bit 4:2:2.
• BUG ID 44593 - The Denoise node is now available to use in Nuke, rather than NukeX only.
Bug Fixes
• BUG ID 7420/43971 - Precomping a script containing a Precomp produced black output, but did not report any
errors.
• BUG ID 30526 - Cropped .exr files were not displayed correctly in the Viewer.
• BUG ID 35627 - Rendering long sequences displayed a Too many open files error.
• BUG ID 35975 - Files with a pixel aspect ratio of 1.0 specified in their headers, were sometimes read in incorrectly.
46
RELEASE NOTES FOR NUKE STUDIO PUBLIC BETA 01 | BUG FIXES
• BUG ID 39135 - Transcoding or exporting timelines with multiple tracks took longer than expected to render.
• BUG ID 39571 - QuickTime: Transform handles required multiple undos in scripts containing QuickTime Read
nodes.
• BUG ID 41032 - Disconnecting the image input at the top of a node tree containing a Denoise node upstream of an
OFX node caused Nuke Studio to crash.
• BUG ID 41663 - Online Help: It was not clear that the example scripts only works if you launched the online help
from Nuke Studio and have set documentation source to local in the Preferences.
• BUG ID 41915/43813 - Keylight: If a LensDistortion or Denoise node was added in a node tree containing a
Keylight node, it caused the application to crash when the Viewer was connected.
• BUG ID 42252 - BlinkScript: Kernels written inside BlinkScript could not always access the required channels.
• BUG ID 42550 - FFmpeg: Nuke Studio always used the rec601 colorspace regardless of resolution.
• BUG ID 42712 - ARRIRAW: Nuke Studio failed to read some .ari frames due to a Reader did not set bounding
box error.
• BUG ID 42769 - BlinkScript: Some kernels that ran correctly on the CPU did not compile on the GPU.
• BUG ID 43485 - Scopes: Disabling Preferences > Panels > Scopes > Include viewer colour transform with a
scope present in the layout causes Nuke to crash.
• BUG ID 43813 - Keylight: If a LensDistortion node was added downstream of a Keylight node, it caused the
application to crash.
• BUG ID 43869 - Reading QuickTimes using the mov: prefix did not work as expected.
• BUG ID 44144 - Planar Iop slowed down render performance if there were samples in ScanlineRender.
• BUG ID 44378 - The Planar Iop section of the NDK Dev Guide contained several gaps and errors.
• BUG ID 44396 - Reading in tiled .exr files was very slow, particularly with multiple threads.
47
RELEASE NOTES FOR NUKE STUDIO PUBLIC BETA 01 | DEVELOPER NOTES
Developer Notes
Here are the changes relevant to developers. See Help > Documentation from the Nuke menu bar for more
information.
NOTE: Node Class() names occasionally change between major releases, such as Nuke 7 to Nuke 8. While
these changes do not affect legacy scripts, you may not get the results you were expecting if a node class
has been modified. The toolbars.py file, used to create Nuke's node toolbar, contains all the current node
class names and is located in <install_directory>/plugins/nukescripts/ for reference.
As an example, between Nuke 7 and Nuke 8, the Text node Class() changed from Text to Text2. In the
toolbars.py file for the two releases, the entries for the Text node appear as follows:
m.addCommand("Text", "nuke.createNode(\"Text\")", icon="Text.png")
m.addCommand("Text", "nuke.createNode(\"Text2\")", icon="Text.png")
New Features
• BUG ID The Python module psutil is now included in the site-packages by default.
NukeStudio includes Hiero's existing Python modules for conforming, clip management, timeline editing,
versioning, round-tripping, export, and so on.
NOTE: Documentation for the Hiero Python API is not currently included in this beta installation but will
be included for release. In the meantime please refer to the Hiero Python API dev guide:
http://docs.thefoundry.co.uk/products/hiero/developers/1.8/hieropythondevguide/
Feature Enhancements
There are no feature enhancements in this release.
Bug Fixes
There are no bug fixes in this release.
48