Release Notes for Nuke and Hiero 10.5v6
Release Date
21 September 2017
Qualified Operating Systems
• Mac OS X Mavericks (10.9) or Yosemite (10.10)
• 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 MacBook 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 MacBook 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.
Note: To ensure you get the best performance from OpenCL GPUs on late 2013 Mac Pro 6,1 and mid 2015 MacBook Pro 11,5, we recommend updating Mavericks to 10.9.5, or above for full functionality. However:
If you're running an earlier version of Mac OS X than 10.9.5 and processing images greater than 4 mega pixels resolution, VectorGenerator, Kronos, and MotionBlur do not support GPU acceleration.
If you're running an earlier version of Mac OS X than 10.9.4, Kronos and MotionBlur do not support GPU acceleration.
New Features
There are no new features in this release.
Feature Enhancements
There are no feature enhancements in this release.
Bug Fixes
• ID 137014 - DeepRead: Setting the missing frames control to black did not render any missing frames black.
• ID 158689 - EXR: Setting the last frame after dropdown to black was ignored for certain .exr files.
• ID 182509 - Expressions: Linking two ColorLookup master curves caused images containing negative values to display as nan (not a number) in the linked curve.
• ID 218316 - ARRIRAW: The arriReader did not support the full range of integers (-12 to +12) for the tint control.
• ID 225493 - Windows only: Installing QuickTime 7.7.6, or earlier, removed certain .mov codecs from the Write node's Properties panel.
• ID 239752/270592 - ZDefocus: Rendering a script containing two or more ZDefocus nodes from the command line caused Nuke to crash.
• ID 246403 - Monitor Output: The Blackmagic Desktop Video Utility and Nuke Studio Monitor Output panel did not always display the same data rate output.
• ID 248914 - Composting Viewer: The Properties panel mask mode dropdown had no effect on the Viewer.
• ID 250718 - WriteGeo: The window scale uv values were ignored during export of .abc and .fbx cameras.
• ID 252765 - Export: Exporting an updated shot (light green) incorrectly displayed a dialog asking you to re-render the shot.
• ID 253647 - Monitor Output: 12-bit 4:4:4 output was incorrect for AJA Kona 3G cards.
• ID 266338 - Audio: Playing audio backwards in a source Viewer caused the application to become unresponsive and the audio to play forwards as normal.
• ID 267027 - Monitor Output: Working in the linear colorspace caused the monitor to display colors incorrectly until the colorspace was changed.
• ID 267674 - BlinkScript: Default values could not be changed for float4x4 matrix and float3x3 matrix in BlinkScript kernels.
• ID 269361 - Monitor Output: 12-bit 4:4:4 output did not work as expected with a single BNC cable for AJA Kona 3G cards.
• ID 275703 - Monitor Output: Selecting the video legal range option did not limit output in 10-bit mode for Blackmagic 4K Extreme 12G cards.
• ID 278106 - Audio: Retiming and then slipping audio shots past the start of the shot caused Nuke Studio to crash or rendered the waveform incorrectly.
• ID 281177 - Monitor Output: Setting the LUT to none or custom in the Monitor Output panel displayed artifacts in the monitor.
• ID 281179 - Monitor Output: Switching to Full Resolution Stereo output during playback with Blackmagic cards caused Nuke Studio to crash.
• ID 283921 - Export: Transcoding Sony F5 - 5500K .mxf files to Apple ProRes 4444 .mov displayed an error decoding frame error.
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
• ID 270405 - Python: Setting the MAGNITUDE flag using setFlag(0x00000001) on compatible nodes, such as Constant, caused Nuke to crash.