Release Notes for Nuke and Hiero 12.2v6

Release Date

25 March 2021

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)

Note:  We recommend macOS Mojave customers update to 10.14.6 to take advantage of performance enhancements.

• Windows 10 (64-bit)

• CentOS 7.4, 7.5, and 7.6 (64-bit)

Note:  The VFX Platform 2019 upgrade includes library versions that are only compatible with CentOS 7.4, or later.

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 WX 8200

• Radeon™ Pro W5700

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

Sync Review Improvements

Sync Review is no longer a beta feature and now includes all the actions needed on a Review Session, such as changes in the timeline, importing new footage, or creating new soft effects. Sync Review for NukeStudio, Hiero, and HieroPlayer enable teams to collaborate and continue working together towards a shared vision of the final image.

HieroPlayer now includes the same annotations capabilities as Nuke Studio and Hiero, providing greater creative control during review sessions.

Previously, only the playback controls, versioning system and annotations were updated during the session, and editorial changes required a manual push to update other participants' sessions. In this release, most actions available in the timeline, Viewer, and Project bin are synced automatically during the session including:

• Changes in the Viewer: Layer and channel selection, the TC/TF frame slider option, Viewer guides, and zoom in and out.

• Changes in the Timeline: Creating new tracks, renaming shots, adding or deleting soft effects, retimes and transitions, changes to soft effects parameters, lock status of tracks, trimming, and moving shots on the timeline.

• Changes in the Project bin: Creating, renaming, moving or deleting project items, importing files, creating new sequences, tags, and bins.

Feature Enhancements

• ID 360412 - Annotations: Sequences exported from Nuke Studio and Hiero now have the option to include burnt-in annotations. The export option is in the Transcode Image exporter under Effects and Annotations > Include Annotations.

Bug Fixes

• ID 137121 - Nuke crashed on start up if the disk cache location set in the Preferences was no longer available.

• ID 379806 - Python: The Hiero example file spreadsheet_csv_export.py did not work as expected.

• ID 385696 - MergeMat: Copy/pasting a disabled MergeMat node to combine two Project3D nodes caused Nuke to crash.

• ID 401016 - Python: Calling Gizmo.filename() returned the value of a gizmo's file knob, rather than the gizmo's location on disk.

• ID 401881 - Windows only: Custom shortcuts using Shift and keypad numbers could not be initialized.

• ID 431846 - Shuffle2: Expression linking Input or Output Layer controls to a channel control in another node caused Nuke to crash.

• ID 431886 - Dragging files into the Project bin occasionally caused Nuke Studio and Hiero to become unresponsive.

• ID 433153 - UI: The overlay and guides menu was occasionally disabled if it included custom guides.

• ID 434560 - Python: PySide2 version 5.12.x did not support mocking in Nuke.

• ID 437042 - Windows only: Nuke did not register Nuke scripts with an associated program when installed.

• ID 438360 - Documentation: The NDK documentation for Setting up Projects and Compilers was out of date.

• ID 447820 - Deep: Viewing a DeepMerge node with deep.front and deep.back set to inf values caused Nuke to crash.

• ID 448363 - BlinkScript: Creating unsigned variables using uint displayed an error when GPU acceleration was enabled.

• ID 453738 - Sync Review: Deleting a clip from the Host Project panel did not update Client sessions as expected.

• ID 462887 - OCIO: Loading custom OCIO configs using the OCIO environment variable did not work as expected.

• ID 463633 - Colorspace: Exporting a script with various output colorspaces displayed an Invalid LUT selected error.

• ID 463791 - Soft Effects: Exporting a sequence containing Text effects on a separate video track set clip to > bbox, rather than format.

• ID 464372 - Python: Nuke could not load movWriter from an external version of Python.

• ID 464455 - Python: The foundrySG_Example.py example and documentation did not work as expected.

• ID 464508 - Transform: Adjusting the scale control in a Transform node's Properties panel with show overscan active in the Viewer settings caused Nuke to crash.

• ID 464891 - Sync Review: Soft effect version names and numbers occasionally got out of sync between sessions.

• ID 465012 - Python: FnFilenameField.py was missing an import of QtCore.QEvent and displayed errors in the console.

• ID 465045 - Read/Write: The info bar overlay in Nuke Studio's Viewer displayed a one frame offset for .mov and .mxf files compared to the source timecode.

• ID 465375 - Tags: Selecting shots with tags on the timeline was slow compared to shots without tags.

• ID 466597 - Documentation: The Sample Scripts page was missing from the Nuke Python Developer's Guide.

• ID 467078 - Python: Renaming tags using the setName() function did not work as expected.

• ID 468211 - UI: Dragging widgets between panes occasionally named tabs incorrectly.

• ID 468608 - User Knobs: User knobs created in the Project Settings were duplicated when a script was closed and re-opened.

New Known Issues Specific to Nuke 12.2

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

Note:  Changes to the way motion vectors are calculated in Nuke 12.2 cause any node using the Local option for motion estimation, such as Kronos and VectorGenerator, to render slightly different vectors when compared to legacy versions of Nuke. The default Regularized motion estimation method is unaffected.

• ID 471373 - macOS Nuke Indie only: C_STMap is incorrectly recognized as a custom plug-in and cannot be loaded.

• ID 470465 - Preferences: The Performance > Hardware > disable blink cache control has a misleading label and tooltip.

• ID 470388 - ABC: Deselecting locator items in an Alembic ReadGeo import and then clicking Create all-in-one node causes the import of all objects to fail.
As a workaround, enable the view entire scenegraph control and then click the Load column for the required objects.

• ID 470096 - Python: Clicking the Load column for items in a custom sceneView_Knob clears the object name in the Scenegraph.

• ID 468956 - Read/Write: Importing .aaf files with the file browser Preview panel open causes Nuke Studio to crash.

• ID 466754 - USD: Enabling read from file in a Camera or Axis node's Properties and then clicking No in the popup does not disable read from file as expected.

• ID 466720 - USD: Copy/pasting a .usd file from a browser into the Node Graph adds a / (forward slash) to the file path and displays a No such file or directory error.
As a workaround, delete the / and press enter to display the import dialog as normal.

• ID 466485 - Linux only: Nuke can not read .r3d files without CUDA libraries available on the machine.
As a workaround, you can manually install the CUDA libraries from NVIDIA, even if you don't have an NVIDIA GPU installed.

• ID 465300 - Read/Write: Certain Photo - JPEG encoded .mov files with non-standard format sizes cause Nuke Studio to crash.

• ID 461944 - Python: Changing a Read node from an image sequence to a container file format Pythonically causes Nuke to crash if the Read node has postage stamp set to a static frame.

• ID 460411 - Read/Write: Rereading a .mov encoded with mov32 settings using the file control in legacy scripts causes Nuke to crash.

• ID 460240 - masOS only: Existing export presets using the deprecated mov32 codecs cause Hiero to crash on export.
As a workaround, recreate the preset in a Hiero 12.2 release

• ID 460038 - Particles: Secondary particles emitted from other particles do not render as expected.

• ID 459859 - ACES: Nuke Studio incorrectly allows artists to alter the R3D IPP2 colorspaces in Read nodes using IPP2 Custom selection, which results in Half Float ACES Linear colorspace mismatches between Nuke Studio and Nuke.

• ID 459609 - USD: The Scenegraph does not automatically expand the first layer of items when loaded for the first time.

• ID 448524 - macOS only: The resolution restriction informational message for Nuke Indie contains incorrect text.

• ID 444347 - Export: Presets that rely on mov32 do not populate the Content field in the Export dialog.

• ID 443296 - Windows only: The Nuke Indie icon is incorrect.

• ID 442165 - MOV: Writing out .mov files using the H.264 codec at resolutions above the 4K limit imposed by the codec causes Nuke to crash.

• ID 441979 - USD: Deselecting a group in the USD importer and then enabling view entire scenegraph does not load the group.

• ID 441555 - USD: Clicking Cancel in the USD import dialog and then enabling view entire scenegraph does not load the .usd file as expected.

• ID 441439 - R3D: Red decode CPU performance is slower in Nuke 12.2 compared to 12.1 builds.

• ID 440943 - USD: Expanding parent and children groups in the scenegraph manually does not create the horizontal scroll bar correctly.
As a workaround, right-click and select expand all to display the scroll bar.

• ID 440884 - Sync Review: Clicking the update button in a Client session with Viewer A/B mode active disconnects the Client.

• ID 440057 - Roaming: Hiero license roaming with a Nuke Studio license stack is not working as expected.
As a workaround, launch Nuke Studio and select License > Roaming and then set the Workspace to Conforming.

• ID 439856 - Sync Review: Client sessions do not cache sequences as expected when the Viewer A/B mode is active on the Host before the Client connects.

• ID 439011 - ApplyMaterial: Selecting filter > name and then clicking choose incorrectly displays Load state icons.

• ID 439002 - ApplyMaterial: Selecting filter > name and then clicking choose allows editing of the read-only names in the scenegraph.

• ID 436560/436551 - Sync Review: The formatting in the Sync Session panel and Host and Connect dialogs is inconsistent.

• ID 434956 - USD: Columns in the Scenegraph tab can only be rearranged once.

• ID 434574 - File Formats Update: Reading .mxf files in the HybridLogGamma colorspace defaults to linear incorrectly.

• ID 432438 - Vertex UV values are occasionally displayed incorrectly for .abc and .usd files.

• ID 430779 - File Formats Update: All deprecated IPP2 .r3d colorspaces appear the same as current colorspaces.

• ID 430760 - File Formats Update: DRAGONcolor2 and REDcolor4 use the same IPP2 .r3d colorspace.

• ID 429788 - macOS only: Legacy mov32 presets are no longer retained, choosing a preset always displays the Don't show this message dialog.

• ID 426901 - File Formats Update: In IPP2 Custom mode, enabling the Use GPU checkbox displays grading controls from the IPP2 Pipeline incorrectly.

• ID 425200 - Read/Write: Legacy Write node Motion JPEG A/B files do not display the Quality control with mov64 selected as the encoder.

• ID 424070 - RIP: Ops requesting unused inputs occasionally prevent images being released from the device cache.

Developer Notes

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.

Release Type	Example	Compatibility	Recompile	Rewrite
Version	12.0v1 to 12.0v2	API and ABI
Point	12.0v1 to 12.1v1	API
Major	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")