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.2v6

# Release Date

07 February 2023

# Qualified Operating Systems

• macOS Big Sur (11.x) or macOS 12.x (Monterey). Nuke is currently supported under Rosetta emulation on Apple's new Apple Silicon hardware and M1 chips. Native support is not currently available and Foundry is planning to support the Nuke family natively on Apple's M1 and M2 hardware at a later date.

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

## Simulate Physical Lens Behavior with Bokeh

Nuke now includes Bokeh, which is a native version of a plug-in originally developed by Peregrine Labs and acquired by Foundry in 2022. The native version of Bokeh in Nuke is backwards compatible with version 1.4.8 of the pgBokeh plug-in. Bokeh defocuses an image according to a Z depth map, Deep data, or Camera information and allows you to control where the focal plane lies so you can focus on specific elements in an image, and simulate real-world lenses. You can also control the shape of the defocus kernel using the Kernel input.

See the Bokeh reference documentation for more information.

# Feature Enhancements

• ID 505463 - Non-Commercial: BlinkScript is now supported in Nuke Non-Commercial.

• ID 523882 - Read/Write: Support for the ALEXA Mini LF .mxf ProRes codec has been improved.

# Bug Fixes

• ID 439456 - Read/Write: Reading DNxHD files that did not contain certain metadata displayed a Mov64 Reader: Failed to create DNx decoder error message.

• ID 475398 - Monitor Out: Blackmagic Design cards output incorrect 10-bit values.

• ID 486552 - Read/Write: Importing certain stereoscopic footage and then replacing views caused Nuke to crash.

• ID 503821 - UI: The icon size preference had no effect on handles in the timeline Viewer.

• ID 505439/516346/516353 - Disabling track items, versioning clips, or switching between tracks in the A/B input buffers caused the Viewer to temporarily turn black.

• ID 510025 - Python: Calling nuke.layers() returned the layers incorrectly.

• ID 518041 - Timeline Editing: Making edits to a track caused the Viewer to render black outside the in and out points.

• ID 518878 - Timeline Editing: Sequences with multiple tags and Burn-In effects decreased playback performance.

• ID 520255 - Soft Effects: The Burn-In effect did not work as expected.

• ID 520308 - Read/Write: Reading Sony Venice and Venice 2 files incorrectly loaded the Rec.709 gamut.

• ID 520364 - Monitor Out: The bottom few code values (<5/1023) were not accessible in Nuke from Blackmagic Design cards outputting 10-bit values.

• ID 521294 - Sync Review: Enabling or disabling track blending or masking during a sync session affected other sessions' Viewer unexpectedly.

• ID 521310 - Soft Effects: Adjusting the controls in a Grade effect did not always update the Viewer as expected.

• ID 521593 - macOS only: Applying a soft effect to a shot upstream of in and out points applied the effect to the whole track.

• ID 521750 - Soft Effects: Adding certain effects caused the timeline Viewer to render black.

• ID 523609 - Read/Write: Certain .mxf files created using FFmpeg displayed at the wrong resolution.

• ID 524237 - CaraVR: C_Stitcher did not produce consistent results on the CPU and GPU.

• ID 528596 - Python: Calling nuke.clone() in terminal mode caused Nuke to crash.

# New Known Issues Specific to Nuke 13.2

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

• ID 524273 - CopyCat: Restarting training after encountering an error causes the contact sheet output to render black.

• ID 524096 - Monitor Out: Blackmagic Design cards do not output 1.5G signals to Phabrix test tools as expected.

• ID 520410 - Inference: The kernel compilation progress bar does not display on machines with Ampere GPUs when Inference is the first node used.

• ID 519874 - 3D Transform Handles: Rotating the camera around a Card with different XYZ scale values causes the handles to distort.

• ID 519224 - NDI: The stream name is not always displayed when a project is opened.
As a workaround, disable and re-enable Monitor Out.

• ID 519126 - CopyCat: The contact sheet created in the checkpoint directory is rgba and the .png files are premultiplied. Depending on the software used to view the images, they could appear blank.

• ID 518254 - CopyCat: Training with the Preview input connected to an image with shuffled A and B layers does not work as expected.
As a workaround, leave the Preview disconnected and use the contact sheet to monitor training.

• ID 510063 - 3D Pivot Point: Snapping doesn't work as expected on very small or very large scale geometry.

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

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

• ID 508116 - 3D Pivot Point: Drag-rotate on geometry with a large scale value doesn't work as expected.

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

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

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

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

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

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

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

• ID 505687 - 3D Pivot Point: Match Geo to selection ignores and overrides pivot point transformations.

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

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

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

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

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

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

• ID 503829 - 3D Transform Handles: Rotating the camera on the Z-axis causes the Card3D node's screen space handles to change alignment in the 2D Viewer.

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

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

• ID 503617 - UI: Moving the Nuke interface to a second monitor resets the color picker window size to the default dimensions.

• ID 503338 - 3D Pivot Point: Geometry position and orientation occasionally behave inconsistently.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

• ID 499383 - 3D Transform Handles: Rotate doesn't work as expected on small scale geometry.

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

• ID 498140 - 3D Pivot Point: The snap menu options in the EditGeo nodes don't work as expected.

• ID 498139 - 3D Pivot Point: Match selection doesn't work as expected when pivot control are not at their default values.

• ID 497459 - 3D Transform Handles: Changing values directly inside knobs does not respect pivot compensation.

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

• ID 496332 - Linux only: Changing toolbar/handles mode Pythonically doesn't update 3D handles in the Viewer as expected.

• ID 495515 - 3D Transform Handles: Scaling parent transforms negatively causes the orientation of handles to behave unexpectedly.

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

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

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

Can't find what you're looking for? Use our feedback widget on the right to request more information.
You must accept cookies from learn.foundry.com and disable any ad-blockers to provide feedback.