Release Notes for Nuke and Hiero 12.0v8
22 October 2020
Warning: As a result of the current COVID-19 lockdown here in the UK, Foundry is unfortunately not able to perform all of its usual QA tests for Nuke's monitor output, including VR headset support. As such, there may be some reduction in related functionality in this release.
Qualified Operating Systems
• macOS High Sierra (10.13) or macOS Mojave (10.14)
• 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.
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.
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.
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.
There are no new features in this release.
• ID 162824 - OCIOCDLTransform: Nuke now supports ASC (American Society of Cinematographers) .cdl files.
• ID 158957 - Python: Calling undoDescribe() on multiple operations only returned the latest operation.
• ID 439450 - OCIO: Loading certain .ccc files displayed a NameError incorrectly.
• ID 439862 - Timeline Editing: Scrubbing the playhead over uncached frames caused the Viewer to jitter.
• ID 449096 - Deep: ScanlineRender did not produce the same composite results compared to earlier Nuke 12.0 builds.
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 447820 - Deep: Viewing a DeepMerge node with deep.front and deep.back set to inf values causes Nuke to crash.
• ID 444901 - Deep: Viewing a DeepMerge with DeepFromImage inputs causes Nuke to crash.
• ID 444111 - Deep: Viewing Deep nodes through ScanlineRender output displays artifacts if the scene contains semi-transparent pixels in front of overlapping samples.
• ID 443793 - Referencing sys.argv in the QApplication() function causes Nuke to crash.
• ID 437042 - Windows only: Nuke no longer registers Nuke scripts with an associated program when installed.
As a workaround, install Nuke 11.3v6 to associate scripts, then change the associated file by right-clicking the .nk script and navigating to: Open With... > More Apps > look for another app on this PC to find the required version of Nuke.
• ID 436623 - macOS only: Changing the blend mode during playback causes Nuke Studio and Hiero to crash.
• ID 435284 - Python: Calling nuke.message() or nuke.alert() doesn't wait or pause the main thread as expected.
As a workaround, use QtWidgets:
from PySide2 import QtWidgets
QtWidgets.QMessageBox(QtWidgets.QMessageBox.Information, "Nuke", "Test Message", QtWidgets.QMessageBox.Ok).exec_()
• ID 434043 - Python: The pyside2-rcc component is currently missing from the bundle.
• ID 432839 - Script Editor: Selecting text in the Script Editor output pane occasionally causes Nuke to crash.
• ID 431980 - macOS only: Selecting a shot on the timeline stops the execution of Python in the Script Editor using the Cmd+Enter keyboard shortcut.
• ID 429533 - Windows only: The goofy_title.txt file is missing from the Nuke plugins directory.
As a workaround, copy the file from a legacy version of Nuke to:
• ID 429245 - UI: Using / (slashes) or spaces in path substitutions in the Preferences pads table rows incorrectly, making the UI unusable.
• ID 428360 - DeepMerge: Holdout does not work as expected on volumetric data samples.
• ID 427913 - Monitor Output: Looping a sequence on a monitor out device causes playback to skip frames.
• 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 Nuke 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 420671 - macOS only: Monitor output from AJA cards at 4K / 10-bit causes the playhead to redraw incorrectly and lag behind playback.
• ID 420592 - C_CameraSolver: Clicking Solve occasionally produces different results before and after saving a script.
• 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 419046 - NDK Documentation: These is currently very little documentation on the functionality of the Deep Op base classes, specifically DeepOnlyOp, DeepFilterOp, and DeepPixelOp.
• ID 418385 - GridWarpTracker: Clicking through various frames on the timeline with a GridWarpTracker active in the Viewer does not update the grid correctly.
As a workaround, click play on the timeline to update the grid to the correct position.
• 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 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 409622 - Create Comp: Nuke Studio occasionally attempts to fetch an image before the frame has finished rendering and displays a Media::ReadException from fetchImage warning.
The comp renders as expected and the warnings in the console can be ignored.
• ID 407847 - Linux only: CaraVR output through an Oculus CV1 headset is unreliable when looking around the scene.
• ID 405333 - Export: Missing frame errors are occasionally displayed after the error is corrected, though the export renders correctly.
• 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 drawn 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 395100 - macOS only: Certain .exr clips containing extra metadata are read more slowly than in previous releases of Nuke.
• 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 392156 - GridWarp: Existing grid keyframes are not displayed in the Dope Sheet.
• 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 387397 - Legacy scripts containing Vectorfield or Colorspace nodes set to HDR2084 do not display complete error messages on load. The complete error message should read: Invalid LUT selected: HDR2084
• 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.
• ID 268879 - LensDistortion: The Viewer overlay doesn't match the source when redistortion is applied.
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 plug-ins and/or make changes to the source code.
12.0v1 to 12.0v2
API and ABI
12.0v1 to 12.1v1
12.0v1 to 13.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")