Release Notes for Nuke and Hiero 12.0v6

Release Date

26 March 2020

Warning:  As a result of the current COVID-19 lockdown here in the UK, Foundry cannot guarantee that our usual high standards of QA have been applied to Nuke's monitor output functionality, including VR headset support, in this release.

Qualified Operating Systems

• macOS High Sierra (10.13) or macOS Mojave (10.14)

• Windows 7 or Windows 10 (64-bit)

• CentOS 7.4 (64-bit), or later

Note:  The VFX Platform 2019 upgrade includes library versions that are only compatible with CentOS 7.4, or later. Nuke 12 is qualified on the Centos 7.4, 7.5, and 7.6 distributions.

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.

NVIDIA

An NVIDIA GPU with compute capability 3.0 (Kepler) or above. A list of the compute capabilities of NVIDIA GPUs is available at https://developer.nvidia.com/cuda-gpus

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 10.1 or above. On Windows and Linux, CUDA graphics drivers are bundled with the regular drivers for your NVIDIA GPU. Driver versions 418.96 (Windows) and 418.39 (Linux), or above are required. See https://www.nvidia.com/Download/Find.aspx for more information.

Note:  We recommend using the latest graphics drivers, where possible, regardless of operating system.

AMD

Note:  Bit-wise equality between GPU and CPU holds in most cases, but for some operations there are limitations to the accuracy possible with this configuration.

• On Windows and Linux, an AMD GPU from the following list:

Note:  Other AMD GPUs may work, but have not been fully tested.

• Radeon™ RX 480

• Radeon™ Pro WX 7100

• Radeon™ Pro WX 9100

• Radeon™ Pro SSG

• Radeon™ Pro WX 8200

Note:  For information on the recommended driver for each GPU, see https://www.amd.com/en/support

• On Mac, AMD GPUs are supported on any late 2013 Mac Pro, mid 2015 MacBook Pros onward, and late 2017 iMac Pros.

Warning:  Although AMD GPUs are enabled on other Mac models, they are not officially supported and used at your own risk.

Multi-GPU Processing

Nuke's GPU support includes an Enable multi-GPU support option. When enabled in the preferences, GPU processing is shared between the available GPUs for extra processing speed.

Note:  Multi-GPU processing is only available for identical GPUs in the same machine. For example, two NVIDIA GeForce GTX 1080s or two AMD Radeon™ Pro WX 9100s.

New Features

There are no new features in this release.

Feature Enhancements

There are no feature enhancements in this release.

Bug Fixes

• ID 410531 - macOS only: Changing knob values on a cloned soft effect caused the Viewer to behave erratically.

• ID 411328 - Timeline Editing: Switching between sequences occasionally caused Nuke Studio to crash.

• ID 414089 - DeepMerge: Deep samples that intersect and have an alpha equal to 1 produced artifacts in the Viewer.

• ID 416381 - macOS only: Selecting file type > mov and a mov32 codec and then clicking Advanced > codec options caused Hiero to become unresponsive.

• ID 417109 - Monitor Output: Enabling Stereo Mode > Flicker caused the monitor to flicker in blue.

• ID 417111 - Linux only: Floating Window monitor output resized the image instead of alternating between the left and right views in stereo Flicker mode.

• ID 420459 - DeepExpression: Changing channel set to rgb caused Hiero to crash in certain scripts.

• ID 422298 - High DPI: The icons in the first sub-menu of Hiero's node toolbar were too small.

• ID 422421 - Viewer: Holding Alt and right-clicking and dragging in the Viewer rotated the camera, rather than panning, when the camera was locked.

• ID 422729 - Monitor Output: Stereo monitor output A/B mode did not work as expected.

• ID 422874 - Create Comp: Changing the file type to mov in the Node Graph occasionally caused Nuke Studio to crash.

• ID 423288 - Flipbook: Specifying a custom OCIO config with defined roles that match the default LUT settings inside Hiero and then launching a flipbook reverted all the default LUT settings back to the nuke-default values.

• ID 425362 - DeepMerge rendered artifacts or crashed in a customer script.

• ID 425378 - DeepToImage produced incorrect results in a customer script.

• ID 425665 - Monitor Output: The safe zone guides did not work as expected when Blackmagic 8-bit video mode levels was set to off.

• ID 426284 - DeepMerge: Referencing a custom channel in a Read node caused Nuke to crash.

• ID 426501 - DeepMerge2 and DeepToImage2 were slower to render than legacy versions of the nodes.

• ID 426583 - LensDistortion: Disabling use GPU if available in the node Properties panel did not calculate distortion on the CPU as expected.

• ID 427468 - LensDistortion: Results from the CPU and GPU where not identical.

New Known Issues Specific to Nuke 12.0

This section covers new known issues and gives workarounds for them, where appropriate.

Note:  NVIDIA GPUs with compute capability of 3.0 (Kepler) cannot process .r3d files due to a known issue in the R3D SDK preventing decoding and debayering. Nuke defaults to CPU processing when reading .r3d files with these cards installed. A list of the compute capabilities of NVIDIA GPUs is available at: www.nvidia.co.uk/object/cuda_gpus_uk.html

• ID 429293 - Launching HieroPlayer with only Hiero, NukeX, and Nuke Studio local licenses displays the Licensing dialog and causes HieroPlayer to crash on exit.

• ID 429245 - UI: Using / (slashes) or spaces in path substitutions in the Preferences pads table rows incorrectly, making the UI unusable.

• ID 427913 - Monitor Output: Looping a sequence on a monitor out device causes playback to skip frames.

• ID 427420 - Windows only: libeay32.dll and ssleay32.dll are currently missing from the Nuke bundle, which can cause PySide2 networking errors.
As a workaround, add a location to your PATH environment variable that contains libeay32.dll and ssleay32.dll files.

• ID 425201 - Python: Using lambda functions inside a PySide2/Qt Signal currently returns a boolean rather than the argument passed.

• ID 423515 - Windows only: Launching Hiero in --safe mode causes the application to become inaccessible, even though it is running.

• ID 422181 - macOS only: Moving the Curve Editor panel to second monitor displays a blank image.

• ID 420676 - Python: The KnobChanged callback does not update Colorspace knobs correctly.

• ID 420675 - Linux only: The RotoPaint ripple edit outline in the Viewer does not draw correctly.

• ID 420671 - macOS only: Monitor output from AJA cards at 4K / 10-bit causes the playhead to redraw incorrectly and lag behind playback.

• ID 420354 - Workspaces: Node panels do not update correctly if the Properties panel is open on a second monitor.

• ID 420326 - Viewers: Using an OCIO config other than nuke-default with use GPU for Viewer enabled stops the Viewer clip_warning working as expected.

• ID 419010 - Timeline Editing: Enabling and disabling track visibility is slow compared to legacy versions of Nuke Studio.

• ID 418369 - C_Blur: The transition between values using Bilinear filtering is not smooth.

• ID 418303 - macOS only: Colorspace controls in the node Properties panel are sized incorrectly.

• ID 417443 - macOS only: HieroPlayer UI scaling does not work as expected.

• ID 414939 - macOS only: The dock does not always display the correct icon for the Nuke product launched.

• ID 414482 - macOS only: The Nuke Studio and NukeX launch shortcuts do not work as expected.
As a workaround, launch the required application from the command line. See the Nuke Online Help for more details.

• ID 410829 - Linux only: Creating nodes Pythonically from the OS command line causes the Python interpreter to crash.

• ID 410015 - Windows only: Monitor output from AJA Kona 4 cards using HDMI is split incorrectly in to four images on the monitor.

• ID 409910 - macOS only: Monitor output playback is not smooth towards the end of certain clips using AJA cards.

• ID 409909 - macOS only: Switching between monitor output devices in Nuke Studio occasionally causes the device selection dropdown to disappear.

• ID 404189 - Bin View: Disparity channels are not displayed consistently in clip thumbnails.

• ID 403804 - Linux only: Switching resolution on the HTC Vive HMD occasionally displays black output in the headset. As a workaround, update the Viewer by changing frame or press F5 to refresh the headset output.

• ID 403337 - High DPI: Changing the primary monitor causes the UI to update incorrectly.

• ID 403210 - High DPI: Swapping between fullscreen and regular workspaces does not retain the UI scale.

• ID 402564 - Windows only: The installer currently overwrites the default install directory without warning.

• ID 401946 - High DPI: F_WireRemoval on-screen controls are draw incorrectly.

• ID 400506 - High DPI: F_Align's bounding box outline is thinner and smaller than in older versions of Nuke.

• ID 400445 - High DPI: F_WireRemoval's controls are smaller and the icon is different to older versions of Nuke.

• ID 400389 - High DPI: The F_Steadiness node controls are thinner than in older versions of Nuke.

• ID 400268 - High DPI: F_Align's controls and outlines are smaller and thinner than in older versions of Nuke.

• ID 399232 - Python: Declaring TimeBase(None) causes Nuke to crash.

• ID 399228 - High DPI: Moving Nuke between monitors with different scaling ratios causes GLWidgets to draw incorrectly.

• ID 398978 - GridWarpTracker: Selecting grids Pythonically does not update the node Properties correctly.

• ID 398213 - macOS only: Switching to a Retina display and then drag-selecting nodes in the Node Graph causes the interface to flicker.

• ID 397516 - DNxHR: Certain .mov file transfer_function metadata in Nuke does not match when compared to nclc atom.

• ID 394789 - macOS only: Scrolling in properties panels that contain a curve widget, such as ColorCorrect, occasionally causes the interface to flicker.

• ID 393373 - GridWarpTracker: Dragging multiple grid vertices and holding Shift does not snap points to the grid.

• ID 393052 - macOS only: Tooltips occasionally don't display correctly.

• ID 392223 - macOS only: The installer window is slightly blurred.
As a workaround, resize the window to improve the resolution.

• ID 392143 - GridWarpTracker: Moving keyframes created by autokey in the Curve Editor or Dope Sheet adds another keyframe at the current frame.

• ID 392127 - GridWarpTracker: The magnifying window displayed over grid vertices during mouse-over changes position if you press Ctrl/Cmd.

• ID 390551 - GridWarpTracker: Enabling Invert stops the preview working as expected.

• ID 389356 - GridWarpTracker: Attempting to use GridWarpTracker in vanilla Nuke only displays a license error once.

• ID 388836 - GridWarpTracker: Toggling grid visibility does not affect the transform widget.

• ID 386719 - Windows only: AJA Kona 4 12-bit dual link 1080p50a, 1080p59.94a, and 1080p60a output is incorrect.

• ID 386517 - Timeline Playback: Clicking the skip to start button and clearing the playback cache simultaneously causes Nuke Studio to crash.

• ID 383542 - GridWarpTracker: Adding a NoOp downstream of a GridWarpTracker with linked knobs occasionally causes Nuke to crash.

Developer Notes

Here are the changes relevant to developers. See Help > Documentation from the Nuke menu bar or https://learn.foundry.com/nuke/developers/120/ndkdevguide/appendixc/index.html for more information.

As Nuke develops, we sometimes have to make changes to the application programming interface (API) and application binary interface (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 plug-ins and/or make changes to the source code.

Release Type

Example

Compatibility

Recompile

Rewrite

Version

11.2v1 to 11.2v2

API and ABI

 

 

Point

11.1v1 to 11.2v1

API

 

Major

11.0v1 to 12.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 422568 - PySide2: Adding QApplication.instance() or QCoreApplication.instance() to init.py or menu.py returned the wrong type.

• ID 423136- Python: Calling nuke.scriptSave() twice in the same session caused Nuke's Python interpreter to crash.

• ID 423935 - Python: Calling nukescripts.create_read() produced incorrect ordering of multiple Read node outputs.

• ID 424326 - RIPFramework.lib was missing from Nuke 12.0 builds.