Search Tips

Search is based on keyword.

`Ex: "Procedures"`

Do not search with natural language

`Ex: "How do I write a new procedure?"`

Give Feedback Support Portal

# Release Notes for Nuke and Hiero 13.2v4

# Release Date

08 September 2022

# Qualified Operating Systems

• macOS Big Sur (11.x) or macOS 12.x (Monterey) on Intel chips only. Apple M1 is tested on Rosetta emulation to ensure new functionality runs as expected on M1 hardware. (We are working toward native Apple Silicon support in future releases.)

Article: For more information on Foundry products and supported macOS versions, see Foundry Knowledge Base article Q100592.

• Windows 10 (64-bit)

• CentOS 7.4 (64-bit), or later

Note: The currently supported version of VFX Reference Platform 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.

• AMD Radeon PRO W6600

• AMD Radeon PRO W6800

• AMD Radeon Pro W5700

• AMD Radeon Pro WX 9100

• AMD Radeon RX 6800 XT

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

• On Mac, integrated AMD GPUs are supported on the following Intel CPU Macs:

• Any late 2013 Mac Pro onward (including 2019 Mac Pro),

• Mid-2015 MacBook Pros onward, and

• Late 2017 iMac Pros onward.

All supported Mac Pros include a multi-GPU support option, where applicable. Bitwise equality between GPU and CPU holds in most cases, but for some operations, there are limitations to the accuracy possible with this configuration.

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 158897 - Python API - 'log' and 'path' modules are not documented in the Python Dev Guide.

• ID 383985 - Update Hiero Python Dev Guide Environment Setup page to explain how to add multiple paths on Windows.

• ID 474428 - [PUBLIC] Conforming MXF files in Nuke Studio is slower than in previous releases.

• ID 484321 - [PUBLIC] Conforming MXF files in Nuke Studio outputs errors to the console.

• ID 488012 - Add support for ALEXA Mini LF .mxf PRORES codec for SUP 7.0 and later.

• ID 492888 - [PUBLIC] All pages with underscores as the beginning character are missing in the Python Reference.

• ID 497944 - [PUBLIC] The hiero.core.events.postEvent() function exists in Nuke Python documentation but not the Nuke Studio/Hiero software.

• ID 502092 - [PUBLIC] Shuffle [S] is missing from the Tab menu after running Update.

• ID 502131 -[PUBLIC] ShuffleCopy is missing from the Tab menu after running Update.

• ID 504360 - [PUBLIC] An error is displayed in the Viewer, when viewing the final frames of a ProRes 422 LT file.

• ID 510617 - [PUBLIC] C_CameraSolver is worse at solving camera matches, no longer matching the first camera.

• ID 511000 - The nuke.Root page is missing.

• ID 512015 - Add Word-wrap to the Spinx Template to Eliminate Scrollbars.

• ID 512541 - [PUBLIC] An error occurs when reading ProRes MXF files from the Arri ALEXA Mini LF.

• ID 512893 - [EDL] Unable to conform due to unsupported characters.

• ID 513097 - Backslashes need escaping.

• ID 513207 - Camera3 node crashes Nuke if the file knob is set to an invalid alembic/abc/fbx path.

• ID 513852 - MOV files with empty Four CC tags can crash Studio.

• ID 514149 - [Qt 5.15] macOS Only: Nuke - Render / Execute menu dropdowns not responding on 3D arch builds.

• ID 514217 - [PUBLIC] Importing clips via Python does not work in Sync client sessions and can sometimes crash Nuke Studio/Hiero.

# New Known Issues Specific to Nuke 13.2

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

• ID 491143 - [MO NDI] - Horizontal flop in the MO Node DNW (Nuke).

• ID 492637 - [3D Transform Handles] Free rotate shrinks/grows during rotation in 2D view.

• ID 497372 - [MO NDI] Monitor Out metadata - frameIndex does not work.

• ID 498754 - [PUBLIC] Nuke will sometimes fail to launch due to installed software or external hardware connected to the Windows machine.

• ID 499442 - [3D Transform Handles] Translating rotated pivot point if the geometry was scaled or rotated doesn't work as expected.

• ID 499468 - [3D Transform Handles] Handles size is affected by scale change downstream.

• ID 500138 - [3D Transform Handles] Rotating in screen and world space after scaling in screen space doesn't work as expected.

• ID 500156 - [OTIO] Warning status appear when different frame rate clips are detected in timeline.

• ID 501261 - [macOS Monterey] Nuke Studio Qt windows slow to update upon resize.

• ID 501442 - [3D Pivot Point] Scale affects the pivot drag rotate algorithm.

• ID 501525 - [CopyCat] Error message is wrong when cancelling training.

• ID 501700 - [3D Pivot Point] Object jumps when drag rotating pivot in non-default transform order.

• ID 501785 - [BM RAW] Incorrect Color space and gamma in attached project.

• ID 502226 - [IV & MO] Floating windows open in same position and size as the most recently closed floating window

• ID 502394 - [IV & MO] Output is not sent to MO device unless the related viewer is visible.

• ID 502395 - [IV & MO] Viewer list doesn't appear to be in a logical order.

• ID 502404 - [IV & MO] MO viewer list does not update when a viewer node is copy/pasted.

• ID 502495 - [CopyCat] Slow down when caching at the start.

• ID 502793 - [IV & MO] Loading an nk file doesn't open all floating windows.

• ID 502843 - [IV & MO] Use Viewer Gamma/ Gain displays on in the MO strip when disabled in properties.

• ID 502942 - [IV & MO] User needs to expand the Viewer MO panel to reveal options.

• ID 503684 - [IV & MO] Monitor Out strip shows stereo controls on launch.

• ID 503687 - [IV & MO] Not all of the knobs on the Monitor Out strip show their knob name in the tooltip.

• ID 504013 - [3D Transform Handles] Negative Scaling on TransformGeo affecting ParticalEmmiter: intermitant incorrect scales on other axes.

• ID 504191 - [IV & MO] Crash when closing while playing back with NDI active.

• ID 504406 - [CopyCat] Error in the viewer stays on when training.

• ID 504542 - [CopyCat] Epochs set to minus value crashes.

• ID 504645 - [IV & MO] NDI signals are seen twice by the NDI receiver app.

• ID 504819 - [3D Transform Handles] The pivot point of the geometry is affected by the scale changes downstream.

• ID 506004 - [Arriraw 7] When legacy mxf file is loaded with SDK7, some knob values do not match SDK 6.2 version.

• ID 506360 - [CopyCat] Resuming with different model size throws wrong error.

• ID 506569 - [MRQ Deferred Rendering] Result of "Use 32 Bit Post Process Materials" option still rendered when disabled.

• ID 506918 - [CopyCat] Resuming after changing cropsize makes contact sheet wrong size.

• ID 506965 - [MO NDI] Long NDI sender names get truncated.

• ID 507325 - [CopyCat] Channels set to none for input causes seg fault.

• ID 507325 - [CopyCat] Channels set to none for input causes seg fault.

• ID 507327 - [CopyCat] Preview cannot be fetched if preview is connected to remove.

• ID 508661 - [CopyCat] MacOS Having reads with environment variables as inputs causes Nuke to crash.

• ID 509300 - [CopyCat] Using crops with 8+ channel training causes corrupted contactsheet.

• ID 518533 - [CopyCat] Input with 0 channels causes crash.

• ID 518843 - [Transitions] Single-Frame transitions will cause Nuke to hang if extended.

# 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 | 13.1v1 to 13.1v2 | API and ABI |  |
Point | 13.0v1 to 13.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")