Release Notes for Nuke and Hiero 12.2v3

Release Date

24 September 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)

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

• 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 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 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

Nuke Indie

The 3rd party OFX plug-ins, H.264 read and write, and ACC audio restrictions have been removed from Nuke Indie. See Foundry Learn for more information on Nuke Indie restrictions.

Feature Enhancements

• ID 383567 - A new environment variable, NUKE_DISABLE_FRAMESERVER, has been added to enable and disable Nuke's Frame Server. Setting a value of 1, disables the Frame Server and 0 enables it.

Bug Fixes

• ID 132581/418354 - Dope Sheet: Setting a working frame range with Synchronise Frame Range enabled did not set the same range in the Curve Editor.

• ID 229671 - Linux only: Clicking Import Tracks in the CameraTracker UserTracks tab caused Nuke to become unresponsive.

• ID 233945 - HieroPlayer: Timelines in autosaved projects could not be edited in HieroPlayer.

• ID 243240 - Timeline Editing: Certain container formats, such as .mov and .mp4, added 1 frame to the start frame in the timeline when compared to the spreadsheet view.

• ID 388705 - Python: Running a customer garbage cleanup script caused Nuke to crash.

• ID 398188 - Python: Calling nuke.scriptClear() in the Script Editor multiple times caused Nuke to crash.

• ID 403643 - Linux only: Clicking File > Close Comp before saving caused Nuke to crash.

• ID 418068 - Read/Write: Files written using an Apple ProRes codec produced artifacts when read using the mov64 decoder.

• ID 428432 - USD: Loading unsupported files failed silently and did not display a warning.

• ID 429293 - HieroPlayer: Clicking Quit in the License Error dialogue caused the application to crash.

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

• ID 431921 - Python: Calling hiero.core.projects()[-1].endUndo() caused the application to crash.

• ID 438219 - Python: QComboBox() objects containing items of different lengths were not aligned correctly.

• ID 438224 - Python: Adding an item to a QComboBox() after creation cut off the text in the sub-widget.

• ID 439958 - USD: Loading .abc or .usd files occasionally caused the Transform tab controls to be disabled.

• ID 440295 - Python: Calling addItems() did not update the ReadGeo's scene graph as expected.

• ID 440566 - USD: Toggling an item's parent state off and on did not work as expected.

• ID 441429 - USD: A customer point-instanced .usda file caused Nuke to crash.

• ID 441989 - USD: Loading an unsupported file after successfully loading a .usd file caused Nuke to crash.

• ID 442045 - Nuke Indie: The application shortcut was named incorrectly.

• ID 443584 - CaraVR: Creating a ParticleEmitter node downstream of a C_GlobalWarp node caused Nuke to crash.

• ID 443868 - Monitor Output: Certain Blackmagic Design devices occasionally became unresponsive.

• ID 444806 - Sync Review: Switching between sequences with the same name did not update the timeline and Viewer for client machines.

• ID 445689 - Create Comp failed silently when the Write node was set to the .mxf file type.

• ID 446406 - Sync Review: Using keyboard shortcuts to set channels in multiple Viewers caused the channels to become out of sync if a client disconnected and reconnected.

• ID 446419 - Sync Review: Pressing a channel keyboard shortcut twice, such as R, B, or A, did not revert the channel states as expected.

• ID 446827 - Export: Switching between Hiero export presets with the transcode properties open displayed and error on the command line.

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 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 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 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 429658 - Sync Review: Dragging annotations does not update positions in sync sessions until the annotation is dropped.

• ID 429656 - Sync Review: Annotation markers in the timeline do not update automatically.
As a workaround, scrub the timeline to force the update.

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

• ID 425200 - MOV: 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.

• ID 419327 - File Formats Update: DNxHD and DNxHR .mov files do not display different codec information in the Read node's Properties panel.

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
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")