Release Notes for Nuke and Hiero 12.1v2

Release Date

08 April 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 Mojave (10.14) or macOS Catalina (10.15)

• 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.1 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 284030 - Rending a node tree containing a Blinkscript node randomly generated the node_hash metadata value.

• ID 377967 - SmartVectors: Adding SmartVector toolset nodes to the Node Graph displayed errors.

• ID 402330 - High DPI: Denoise noise analysis messages were cut off in the Viewer.

• ID 409454 - High DPI: The UI for the GridWarpTracker's grid lines was rendering at the wrong scale on high DPI enabled monitors.

• ID 409507 - High-DPI: The Viewer overlays for GridWarpTracker displayed incorrectly on 4K displays.

• ID 410493 - High DPI: The current frame indicator was misaligned in the timeline.

• ID 412053 - High DPI: The label field had no border when using the application in high DPI mode on a 4K monitor, and keeping the monitor scale percentage at 100%.

• ID 414631 - LensDistortion: Rendering images using the frame server or command line did not work as expected.

• ID 414828 - ProRes QuickTimes included incorrect color metadata, identifying the color primaries as Rec.601 rather than Rec.709.

• ID 415797 - High DPI: Node name text was not vertically centered.

• ID 418251 - High DPI: Column headers had changed to light gray.

• ID 418261 - High DPI: The pulldown knob spacing had changed.

• ID 419156 - Windows only: Column header text was not centered correctly in tables.

• ID 419489 - Kronos/OFlow: Attaching a Viewer to a Kronos or OFlow node with a negative bounding box caused Nuke to crash.

• ID 419842 - PlanarTracker: Clicking the track range Viewer buttons didn't work as expected and displayed an ExecuteDialog error.

• ID 420296 - GPU Caching: Opening a script containing a C_STMap node with a Bilinear filter enabled displayed an error.

• ID 420472 - High DPI: Text in the Script Editor did not appear as expected.

• ID 421268 - GridWarpTracker: Undoing keyframe creation removed the grid from the Dope Sheet.

• ID 421269 - GridWarpTracker: Undoing keyframe creation removed all keyframes from adjustment grids.

• ID 421648 - Reading certain H.264 encoded .mp4 or .mov files failed to decode the first few frames and displayed an error.

• ID 422162 - High DPI: Enabling the Lock in the Dope Sheet did not highlight the button correctly.

• ID 422201 - C_STMap and Nuke's STMap node did not always produce exactly the same result.

• ID 422379 - GridWrapTracker: The track_name label did not scale correctly and could not be renamed in exports to Tracker.

• ID 422385 - Version Linking: Clips added to the timeline by clicking Set Reference Media were always unlinked.

• ID 422572 - C_STMap: The Radius control was missing for the Lanczos filters.

• ID 423235 - macOS Catalina only: The Project export presets were not updated to reflect the deprecation of mov32 support.

• ID 423239 - macOS only: Icons in Nuke's file browser did not deselect correctly.

• ID 424826 - Shuffle2: Changing the In dropdown and then undoing the action did not work as expected.

• ID 426069 - Audio: Exporting .mov shots produced audio tracks that were a few milliseconds shorter that the associated video tracks.

• ID 426223 - High DPI: The view repositioning arrows were missing from the Project Settings > Views tab.

• ID 426894 - MOV: Exporting .mov formats using mov64 codecs did not include timecode metadata.

• ID 426988 - MOV: ProRes 422HQ files were rendered incorrectly, resulting in color distortion.

• ID 427077 - Shuffle2: Copying and pasting Shuffle2 nodes containing invalid channels did not work as expected.

• ID 427420 - Windows only: libeay32.dll and ssleay32.dll were missing from the Nuke bundle, which occasionally caused PySide2 networking errors.

• ID 427430 - MXF: Rendering DNxHR .mxf files produced incorrect ranges from both the Full Range and Video Range options.

• ID 427475 - ZDefocus: Setting filter type to image and enabling use input channels displayed a Kernel not found in cache and source is missing error.

• ID 427502 - VectorBlur displayed an Input is missing N.x, N.X, N.Y, N.Z error in a customer script.

• ID 427600 - Monitor Output: Zooming in one view and then swapping to a second view caused flickering on the monitor.

• ID 428784 - macOS Catalina only: Dragging clips from the Project bin to the Set Reference Media button did not work as expected.

• ID 428948 - mov64Writer: 16-bit RGB .png render quality was equivalent to 8-bit RGB renders.

• ID 429603 - LensDistortion: Enabling Viewer proxy or downrez modes cropped the bounding box incorrectly.

• ID 430021 - LensDistortion: Enabling Viewer proxy or downrez modes rendered output incorrectly.

New Known Issues Specific to Nuke 12.1

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 430184 - LensDistortion: Attempting to calculate distortion on clips with anamorphic (non-square) pixel ratios constrains feature and line detection to within the square pixel ratio area of the Viewer.

• ID 430081 - BlinkScript: Using the normalize() function in a Blinkscript kernel displays an Error compiling kernel: Error compiling kernel for GPU error.

• ID 429749 - Reading in QuickTime reference files causes Nuke to crash.

• ID 427642 - MOV: Writing .mov files using the Uncompressed codec occasionally displays an Unable to open video codec error.

• ID 427037 - UI: Adjusting the size of the node Properties > Node tab causes the font controls to resize incorrectly.

• ID 425049 - Audio: Deleting an audio clip during timeline playback causes unexpected behavior.

• ID 424122 - Windows only: Adjacent menu options have no break between their highlights on high DPI screens.

• ID 423133 - Read: Reverting a change to the Clip Settings > Colorspace or Look > Colorspace dropdowns for certain .ari and .r3d files displays an Invalid LUT error in the Viewer.

• ID 420685 - Linux only: Qt does not always follow local monitor scaling correctly.

• ID 420608 - High DPI: Flipbooking to HieroPlayer on a 4K Monitor occasionally doesn't work as expected.

• ID 420589 - C_CameraSolver: Running out of memory produces different results when matching and solving rigs.

• ID 419808 - BlinkScript: The normalize function doesn't work as expected.

• ID 419186 - High DPI: Dragging windows between screens with different resolutions occasionally scales the size of the window content, but not the window itself.

• ID 419183 - High DPI: Panel extend icons are not drawn correctly.

• ID 418778 - Read/Write: MJPEG A and B are currently written with incorrect Matrix settings.

• ID 418433 - High DPI: Some panel borders exhibit artifacts or discoloration.

• ID 418315 - High DPI: The UI is rendered incorrectly when waking the computer from sleep.
As a workaround, click anywhere in the UI to redraw the interface.

• ID 418027 - Windows only: The right-click menu in the Curve Editor sometimes scales to the wrong size.

• ID 417583 - C_DisparityGenerator: Processing is slower in CUDA than in OpenCL.

• ID 417418 - MXF DNxHR: Exporting files with the OP Atom and reading the files back into Nuke does not display the Tape ID metadata. In Avid, the Tape ID metadata is read correctly.

• ID 417408 - High DPI: The Preferences window doesn't scale correctly on non-4K monitors when they are set as the primary.

• ID 417100 - Windows only: Using the ! operator on an integer image in Blink causes Nuke to crash due to a call to an unimplemented virtual function.
As a workaround, add .x on the end of !p_conditions(). This avoids ! being unimplemented for int<1> on Windows.

• ID 416659 - Windows only: Disconnecting a Shuffle input and then swapping the Input Layers occasionally causes Nuke to crash.

• ID 416571 - High DPI: Pane edges are displayed with pixel artifacts in larger tabs.

• ID 416388 - High DPI: An extra line is displayed at the end of the progress bar on the Tracker node.

• ID 416134 - High DPI: The contents of a floating window don't fit properly when moved from a non-4K monitor to a 4K monitor.
As a workaround, re-scale the floating window to pop the view back into the right place.

• ID 415836 - High DPI: Properties containing a graph widget are not displaying correctly when moved to a non-4K screen.

• ID 415673 - High DPI: When the file browser is dragged to a non-4K monitor, multiple versions of the icons appear.

• ID 412221 - Backdrop: The border on Backdrop nodes in the Node Graph does not scale at different zoom levels.

• ID 412218 - Backdrop: The border on Backdrop nodes in the Node Graph appears uneven at certain zoom levels.

• ID 412116 - Windows only: The audio build of Nuke plays multi-channel audio at lower audible levels on Windows 10 when using SoundBlaster PCI card or a generic USB interface.

• ID 411468 - macOS only: Exporting Apple ProRes 444 .mov files displays irrelevant errors on completion.

• ID 410556 - High DPI: The Multiple Views (V) icon on track items is no longer transparent.

• ID 406686 - Linux only: Switching from 4K to a non-4K screen can cause the UI to display incorrectly.

• ID 404708 - High DPI: Moving floating panels between monitors does not work as expected if scaling is not set to 100%.

• ID 399226 - High DPI: The color swatches in the Preferences are not aligned with the text.

• ID 388445 - Linux only: Resetting the Workspace on a 4K monitor sends the workspace to the main monitor. If it's not a 4K monitor, the scale doesn't reset and context menus are not in the correct place.
As a workaround, right-click anywhere in the UI to correct the scaling.

• ID 388422 - High DPI: Bin items keep their orange highlighting after being deselected.

• ID 384455 - Windows only: Resetting a workspace and then moving it to 4K monitor causes some panels to overlap.

• ID 384433 - High DPI: After resizing the Viewer, artifacts appear above and below the Viewer controls.

Developer Notes

Here are the changes relevant to developers. See Help > Documentation from the Nuke menu bar or https://learn.foundry.com/nuke/developers/121/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 427650 - Python: Icons created Pythonically were not visible in the top menu bar in the Timeline environment.