Release Notes for Nuke and Hiero 10.5v4

Release Date

4 May 2017

Qualified Operating Systems

• Mac OS X 10.9 (Mavericks) or 10.10 (Yosemite)

• Windows 7 or Windows 8 (64-bit only)

• CentOS/RHEL 5 or CentOS/RHEL 6 (64-bit only)

Other operating systems may work, but have not been fully tested.

Requirements for Nuke's GPU Acceleration

If you want to enable Nuke to calculate certain nodes using the GPU, there are some additional requirements. You need to 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.

With graphics drivers capable of running CUDA 4.2 or above.

Note:  In order to use R3D GPU debayering in the Compositing environment, CUDA 6.0 (or higher) is required.

• 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.

• 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 and mid 2015 Mac Pro 11,5, running OS X 10.9.3 'Mavericks', or later.

Late 2013 and Mid 2015 Mac Pros Only

Nuke supports GPU-enabled nodes on the late 2013 Mac Pro 6,1 and mid 2015 Mac Pro 11,5 (running OS X 10.9.3 'Mavericks', or later), including a new Enable multi-GPU support option. When enabled in the preferences, GPU processing is shared between the available GPUs for extra processing speed.

New Features

There are no new features in this release.

Feature Enhancements

There are no feature enhancements in this release.

Bug Fixes

• ID 132856 - OCIO CDLTransform: The read from file and cccid controls did not work as expected.

• ID 148383 - Expressions: Holding Shift and then dragging the animation icon in a node's Properties panel did not copy expressions correctly.

• ID 154814 - Timeline: Importing multiple EDL tracks using New Track > New Track(s) from EDL created the tracks in reverse order.

• ID 164572 - DeepWrite: Leaving the file type control blank caused Nuke to crash.

• ID 208545 - OCIO CDLTransform: CDLs with no ColorCorrection id value set caused Nuke to become unresponsive.

• ID 253481 - Export: Adding additional nodes to an export track did not work as expected.

• ID 270344 - Switch: Disabling a Switch node did not pass the default input down the node tree.

• ID 271332 - Monitor Output: Blackmagic Decklink Studio 2 cards distributed colors slightly differently between the 8-bit and 10-bit modes.

Developer Notes

Here are the changes relevant to developers. See Help > Documentation from the Nuke menu bar or www.thefoundry.co.uk/products/nuke/developers/100/ndkdevguide/appendixc/index.html for more information.

As Nuke develops, we sometimes have to make changes to the API and ABI under the hood. We try to keep these changes to a minimum and only for certain releases, but from time to time API and ABI compatibility is not guaranteed. See the following table for the situations when you may have to recompile your plugins and/or make changes to the source code.

Release Type	Example	Compatibility	Recompile	Rewrite
Version	10.0v1 to 10.0v2	API and ABI
Point	10.0v1 to 10.5v1	API
Major	10.0v1 to 11.0v1	-

Additionally, node Class() names occasionally change between major releases. 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 9 and Nuke 10, the CameraShake node Class() changed from CameraShake2 to CameraShake3. In the toolbars.py file for the two releases, the entries for the CameraShake node appear as follows:

m.addCommand("CameraShake", "nuke.createNode(\"CameraShake2\")", icon="CameraShake.png")
m.addCommand("CameraShake", "nuke.createNode(\"CameraShake3\")", icon="CameraShake.png")

New Features

There are no new features in this release.

Feature Enhancements

There are no feature enhancements in this release.

Bug Fixes

There are no bug fixes in this release.