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 14.1v5

# Release Date

11 July 2024

# New Features

There are no new features in this release.

# Feature Enhancements

## Monitor Out

- “Show Panel” option for Output Transform

  For users who register their own viewer processes directly in Nuke the “show panel” option in the View Transform menu has always been extremely useful. This functionality has now also been added to the Monitor Out Output Transform.
  This allows users to easily access the node properties for the custom viewer process being applied to the monitor out device.

## Performance

- Nuke requires significantly less resources for GUI path processing so that calling nuke.suspendPathProcessing() is unnecessary for large scripts.

# Bug Fixes

## Rotopaint

- ID 407519 - Nuke was crashing when cloning in a Rotopaint node with multiple Views in use and multiple Viewers open, on Windows.

- ID 565898 - Paint strokes were painted in the wrong View, when multiple Views were in use and with two Viewers

## Viewer Saturation Control

- ID 567482 - Hovering over the saturation slider 's' provides incorrect description in the tooltip.

## 3D

- ID 498140 - Snap_menu options functionality works as expected in EditGeo node

- ID 502363 - Match geo and Match pivot point now orient correctly

- ID 505168 - Match selected position and orientation now snaps the correct geometry to a selection when multiple geo nodes are selected at once and their snap properties used

- ID 510063 - Pivot point snapping works as expected if the user is snapping geometry at a very small or very large scale

- ID 525897 - AppendClip as texture input for new geometry does not animate

- ID 533979 - Adding a keyframe to the Lens-in Focal value in a GeoCard node no longer causes the card to enlarge

- ID 537386 - A 'NoneType object is not subscriptable error' no longer erroneously occurs when using the Snap Menu on points in a Point Cloud

- ID 539702 - GeoPointsToMesh node now re-topologising a mesh from Point clouds

- ID 539853 - Vertex selection now highlighting in blue as 'selected' on new 3D points

- ID 543519 - Viewing GeoPointsToMesh and PoissonMesh nodes no longer cause Nuke to crash

- ID 554540 - Querying a pivot knob on Camera/Axis/Light nodes now returns the correct information

- ID 559616 - Transformed image textures now display correctly in the 3D View compared to the 2D View

- ID 561510 - Light handles in the 3D Viewer now update to match the light's location when using a GeoTransform node

- ID 562004 - Nuke no longer crashes when viewing a GeoDuplicate node with an invalid prim path

- ID 562005 - Setting GeoDisplace nodes Source knob to "alpha" no longer crashes Nuke

- ID 564690 - The snap_menu no longer produces an incorrect "local variable 'normal' referenced before assignment" error when used on certain Alembic geometry subsets

- ID 567863 - Axis handle when using snap menu for objects with transforms snaps to the correct location in the new 3D system

- ID 568259 - The z-axis of Axis node snapped to GeoImported .abc no longer points in opposite direction of expected

- ID 568825 - Nuke no longer crashes when deleting a ReadGeo node

- ID 569309 - Camera locator correctly populates the local parent xform values

- ID 572296 - GeoCard/GeoCube/GeoRevole: Specify Matrix functionality restored

- ID 573622 - Camera now correctly rotates around parent axis op

- ID 574524 - Classic geometry does not display hidden vertices when in vertex selection mode.

- ID 577351 - Nuke does not crash when selecting vertices or faces in classic 3D system geometry imported from USD files containing empty meshes or point clouds.

- ID 578999 - FrameHold, FrameRange, or TimeOffset node downstream of a 3D no longer makes geometry disappear and stop rendering

## Color

- ID 560178 - Updated the OCIO link in context tab's tooltip for all relevant OCIO nodes.

## Compare

- ID 557623 - Filtering by tags in the Viewer buffer does not work if there are track items above the tagged track

## Disk Cache

- ID 552644 - Disabling a track item during auto timeline disk caching invalidates the existing cached frames in the track item's range

- ID 554595 - Cache properly invalidated when retiming a track item with a dissolve

## Example Plug-ins

- ID 564067 - Nuke NDK Example Plugins README.md now lists the correct compilers

## Exporting

- ID 573008 - "Setting knob values from validate is not supported" error occurs when Exporting MOV files using an ACES OCIO config in Nuke Studio/Hiero with colorspace set to default

- ID 573012 - "Invalid LUT selected" errors occur when Exporting DNxHD/DNxHR files using an ACES OCIO config in Nuke Studio/Hiero with transform type set to "Display"

## File Export

- ID 569723 - Nuke renders 30 FPS MXF files at 29.97 FPS

## File Import

- ID 563148 - Nuke crashes when Reading compressed TIFF/TIF images

- ID 569851 - arri_colorspace/arri_colorpsace knob is incorrectly spelled for ARRI read nodes

- ID 572759 - ARRI raw read nodes loose knobs if the media is unavailable, resulting in data loss if you save the Nuke script

- ID 575341 - Nuke crashes when reading MXF files from the ARRI Alexa 35 with custom metadata

## Machine Learning

- ID 488896 - CatFIleCreator: Node doesn't execute in terminal mode
- ID 554864 - CopyCat: Distributed training timeout error isn't clear

## Miscellaneous

- ID 567047 - Sentry crash reporting now works in terminal mode if enabled with a terminal argument or the environment variable.

## Node

- ID 162897 - The PostageStamp node previously broke transform concatenation. Now, transforms properly concatenate through the PostageStamp node.

## Performance

- ID 539682 - GUI path processing is not performed when in terminal mode, decreasing RAM usage.

- ID 554606 - Nuke does not freeze intermittently when using scripts with a very large number of nodes.

## Python

- ID 560504 - Setting a Write node's OCIO key knobs via onCreate callback or knobDefault does not set the key_Display knob

- ID 561182 - Soft effects/SubtrackItems don't always update their color on the timeline until the timeline is active or given focus

- ID 565537 - A TypeError occurs when using the spreadsheet_csv_export Python example for Nuke Studio/Hiero

- ID 567213 - A playback error that was caused when reconnecting the media of an invalid clip added via Python has been fixed

- ID 572096 - Running nuke.math with Vector2, Vector3(), or Vector4() no longer produces a TypeError and now the math vector output displays correctly

## Shortcuts

- ID 431980 - [macOS] The Script Editor does not receive focus when a clip is selected on the Timeline and using the CMD+Enter hotkey in Studio/Hiero

- ID 574863 - Some panels in Hiero/Nuke Studio cannot be expanded/collapsed after the panel receives focus, or if the user interacts with it

## Soft Effects/Transitions

- ID 560042 - The Burn-In soft effect evaluates before a Crop soft effect when above it in the stack.

- ID 564098 - Soft Effects can separate from their TrackItem when using Nudge Up/Down, if there is more than one SubTrack

- ID 565495 - Burn-Ins outside of the image area are cropped

## Sync Review

- ID 457706 - Cursors are now cleared from the viewer when a user leaves a session

- ID 517713 - Clip knob changes not synced when using Sync Review

- ID 541659 - Client Sync Review sessions crash when importing many clips quickly

- ID 542767 - Copy and pasting or duplicating bin items doesn't get synced between Sync Review sessions

## Timeline

- ID 330729 - Video tracks in studio overlap when resized

- ID 555265 - Inactive Dissolve now show the original frame (instead of black).

- ID 560675 - In and out points were being added to the undo stack multiple times, breaking the undo stack. These commands have been modified to create new edits that are only added to the undo stack once, resulting in normal undo behavior.

- ID 565036 - Playhead auto-selection prevents hiero.ui.TimelineEditor functions like setSelection() from working

- ID 568750 - Fixed Nuke Studio / Hiero crash on exit if the Timeline/Sequence panel is floating with more than one pane in the floating panel

- ID 572619 -
  Playhead auto-selection causes the 'kSelectionChanged' event to trigger without the Timeline selection changing

- ID 575935 - Auto-select from Hard-select does not trigger kSelectionChanged event

- ID 576178 - Auto-Select: Box select causes the 'kSelectionChanged' event to trigger without the Timeline selection changing

- ID 576595 - Fixed crash when adjusting the auto selected tracks volume using the track properties box as the first step after the loading or creating of the tracks in the sequence.

- ID 576670 - Clearing the out point clears the in point and vice versa.

- ID 577463 - In and Out points cannot be placed on the same frame.

- ID 579499 - In and Out points cannot be toggled using the I or O hotkeys.

## UI

- ID 541692 - Dope Sheet keyframes update correctly when creating time nodes that connect automatically to the viewer.

- ID 550373 - Removed CameraTracker and DepthGenerator from side toolbar menu of NukeAssist

- ID 567027 - Add a comment to the Audio Device preference to make it clear that it doesn't work with Monitor Out

- ID 574167 - Dope Sheet updates correctly when adding a time node after an animated node.

- ID 575351 - Script report 'Total nodes' count fixed to include nodes inside sub Groups, properly representing the actual node total.

## USD

- ID 541124 - Correct values are now imported in the Camera3 node when using a USD file with a Y axis value of 90 or -90

## Vector Generator

- ID 546685 - Nuke no longer crashes when attaching the deprecated F_VectorGenerator to a LayerContactSheet node

## Viewer

- ID 533412 - Texture scaling no longer influenced by toggling between 2D and 3D view

## ZDefocus

- ID 564419 - Nuke crashes when viewing a ZDefocus node set to output filter shape setup

# Known Issues

- ID 563857 - Adding a clip below a track with effects removes the effects

- ID 581508 - During looped playback, switching between playheads, with disk-cache enabled and in/out points set, causes a long pause before playback resumes.

## Machine Learning

- ID 574745 - CopyCat: If CopyCat hits error when training, it will pause the viewer

- ID 579210 - CopyCat: When training with multiple views all knobs except "Resume Training" and "Create Inference" are disabled

- ID 579465 - Inference: When hitting out of memory error, Inference won't let go of the vram

# Qualified Operating Systems

- macOS Monterey (12.x), or macOS Ventura (13.x). Nuke 14.1 is supported under Rosetta emulation on Apple's silicon hardware and M1 and M2 chips. Native support is available in Nuke 15.0 on Apple's M1 and M2 hardware.

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

- Windows 10 (64-bit) or Windows 11 (64-bit)

- Linux 7.6 to 7.9 (64-bit)

  Nuke requires libnuma to run under Linux distributions, the library is required by the Nablet h164 Codec SDK.

  The currently supported version of VFX Reference Platform includes library versions that are only compatible with CentOS/RHEL 7.6 to 7.9.

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 graphics drivers capable of running CUDA 11.8, or above. A list of the compute capabilities of NVIDIA GPUs is available at https://developer.nvidia.com/cuda-gpus

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 11.8, or above. On Windows and Linux, CUDA graphics drivers are bundled with the regular drivers for your NVIDIA GPU. Driver versions 522.06 (Windows) and 520.61.05 (Linux), or above are required. See https://www.nvidia.com/Download/Find.aspx for more information on compatible drivers.

We recommend using the latest graphics drivers, where possible, regardless of operating system.

### AMD

Bitwise 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:

  Other AMD GPUs may work, but have not been fully tested.

  - AMD Radeon PRO W7900

  - AMD Radeon PRO W6600

  - AMD Radeon PRO W6800

  - AMD Radeon Pro W5700

  - AMD Radeon RX 6800 XT

  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.

  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.

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.

## GPU Requirements for the Machine Learning Toolset

Training using the CopyCat node requires an NVIDIA GPU, with compute capability 3.5 or above; or MacOS Apple silicon integrated GPUs.

If an appropriate GPU is not available, Inference and other machine learning plug-ins can run on the CPU with significantly degraded performance.

# 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 | 14.0v1 to 14.0v2 | API and ABI |  |
Point | 14.0v1 to 14.1v1 | API | ⬤ |
Major | 14.0v1 to 15.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 13 and Nuke 14, the Axis node Class() changed from Axis3 to Axis4. In the toolbars.py file for the two releases, the entries for the Axis node appear as follows:

    			m3Dclassic.addCommand(
    				"Axis",
    				"nuke.createNode(\"Axis3\")",
    				icon="Axis.png",
    				tag=MenuItemTag.Classic,
    				node="Axis3",
    				tagTarget=MenuItemTagTargetFlag.TabMenu)

    				m3D.addCommand(
    				"Axis",
    				"nuke.createNode(\"Axis4\")",
    				icon="Axis_3D.png",
    				tag=MenuItemTag.Beta, node="Axis4")