Release Notes for Nuke and Hiero 15.1v2

Release Date

25 July 2024

Feature Enhancements

Spreadsheet

  • ID 536137 - Add the ability to filter by Track Tags in the Spreadsheet View

Bug Fixes

Group View

  • ID 568835 - When you shift-select nodes and then shift-select additional nodes, the original selection gets deselected.

  • ID 573632 - Nodes are offset from the mouse position when copy and pasting a node between groups

  • ID 574211 - Info Viewer doesn't work for nodes inside Group View

  • ID 574254 - Branch operation not working inside groups

  • ID 574457 - Nodes are not created at last click location and/or the relative correct location as they would be in the main DAG.

  • ID 574529 - The UI icon for open/close group internals is missing on LiveGroups.

  • ID 575418 - Pressing viewer hotkeys (1, 2, 3, ...) selects the currently focused viewer node.

  • ID 576534 - Make right click selection behaviour in open group views behave the same as the main DAG.

  • ID 577672 - Gizmos crash Nuke when connected to the Viewer

  • ID 578636 - Connect viewer shortcut is giving an error when attempting to create the node

Viewer Saturation Control

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

  • ID 575261 - The tooltip for the saturation slider lists saturation as being applied after the gamma and Input process, but it should be say 'before'.

3D

  • ID 574163 - GeoBindMaterial errors when a 3D transform is applied to the object

  • ID 578704 - GeoTransform now detects an animated axis input

  • ID 580634 - Cloned TimeOffset nodes do not produce the same result as the original node

BlinkScript

  • ID 553099 - BlinkScript kernel not compiling on GPU when floor() is called on an int

  • ID 572669 - Math functions do not work on single element vectors

  • ID 573324 - Adding Blinkscript soft effects in Python doesn’t update Kernel

  • ID 579223 - Selecting 'none' in the blinkscript input layer dropdown causes nuke to crash

  • ID 580859 - "Error Running Kernel" with Pixel-Wise kernels with fewer number of channels in the viewer than BlinkScript's output

CaraVR

  • ID 484589 - C_CameraSolver can't export nodes, it errors saying "list indices must be integers or slices, not float"

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

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

Graph Scope Variables

  • ID 577890 - Fix under score causing certain strings to evaluate incorrectly

  • ID 578378 - Defining shot variables in a group causes Read node postage stamps to error

  • ID 579897 - Fix presence of GSV causing TCL to evaluate

  • ID 581277 - GSV values are not correctly evaluated on File knobs and String knobs

Lens Distortion

  • ID 578147 - Unable to undistort plate with STMap and CSTMap workflow

Machine Learning

  • ID 488896 - CatFIleCreator: Node doesn't execute in terminal mode

  • ID 554762 - The training contact sheet will sometimes appear blank when getting training updates

  • ID 554864 - CopyCat: Distributed training timeout error isn't clear

  • ID 580676 - CopyCat trains on randomly selected crops from the training dataset. This fixes the consistency with which we determine this randomness, picking the same random crops across the supported operating systems.

Multishot

  • ID 581178 - Nuke was crashing after switching and disconnecting Viewer inputs from Group nodes that had a GSV set on them. This issue happened with both Group and LiveGroup nodes.

Node

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

  • ID 548895 - The tracker node will now default to using the current frame as the reference frame when adding new tracks instead of using frame 1. This will ensure that tracking starts from the correct frame.

  • ID 576693 - Original Range knobs set correctly when creating a Read node via Python (or the File Browser)

  • ID 579082 - The tracker node will now default to using the current frame as the reference frame when adding new tracks instead of using frame 1. This will ensure that tracking starts from the correct frame.

  • ID 579124 - The Tracker can switch to its reference frame when adjusting a track anchor's pattern and search areas

Python

  • ID 556538 - Python DeprecationWarning messages occur when PYTHONDEVMODE is enabled

  • 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

Rotopaint

  • ID 580889 - Points jump when cmd + drag bbox to scale a shape

Shortcuts

  • 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 563857 - Adding a clip below a track with effects does not remove the effects

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

  • ID 578561 - Text and BurnIn Soft Effects can produce Text size exceeds maximum GPU texture size errors

  • ID 579310 - Enabled blended track shows the error state of a soft effect

Sync Review

  • ID 579815 - Versioning is slower while a Sync Session is active

  • ID 580906 - UI performance decreases when a Sync Session is active

  • ID 580907 - Playback performance can change unexpectedly when a Sync Session is active

Timeline

  • ID 330729 - Video tracks in studio overlap when resized

  • 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 573766 - Fixed error case when sending a track to the A/B buffer from the Timeline will reset the Tags filter to enable all tags.

  • ID 573879 - Fixed case when no tracks are selected in the Track Chooser, 'all tracks' is displayed. The text 'no tracks' will now be displayed instead.

  • 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 578818 - Fix case when hard selecting a soft selected clip did not update the spreadsheet view.

  • ID 578979 - Drag selecting clips will not hard select and looks messy on the spreadsheet

  • ID 579497 - Zooming in on the timeline Viewer during playback results in blurriness or flickering on the image

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

  • ID 580529 - Fixed Raw OCIO Colorspace not being honored when displaying the clip in Compare mode.

Viewer

  • ID 574862 - Changing the 'Down-res' option in the Viewer to anything different to 1:1 causes the viewer to go black or to show an incorrect resolution

  • ID 575849 - Changing the Viewer's layer while comparing now displays the correct layer.

Known Issues

Group View

  • ID 582087 - Connecting viewer using hotkeys in Group tab switches tab to main Node Graph in NukeStudio

Qualified Operating Systems

  • Nuke 15.0 and later support Apple's silicon hardware.

  • macOS Ventura (13.x), or macOS Sonoma (14.x)

    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 Rocky 9.0 (64-bit)

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

    The currently supported version of VFX Reference Platform includes library versions that are only compatible with Rocky 9.0.

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