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

# Release Date

24 July 2017

# Qualified Operating Systems

• Mac OS X 10.11 (El Capitan) or macOS Sierra (10.12)

• Windows 7 or Windows 10 (64-bit)

• CentOS 6 or CentOS 7 (64-bit)

Note: If you intend to use floating licenses with Hiero 11, you'll need to upgrade the version of RLM used in the Foundry Licensing Tools (FLT) on your server. See Foundry Knowledge Base article Q100320 for information.

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 2.0 (Fermi) or above. A list of the compute capabilities of NVIDIA GPUs is available at www.nvidia.co.uk/object/cuda_gpus_uk.html.

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 8.0 & 6.5 or above.

• On Windows and Linux, CUDA graphics drivers are bundled with the regular drivers for your NVIDIA GPU. Driver version r361 or above is required.

Go to http://www.nvidia.com/Download/Find.aspx?lang=en-us for more information.

• On Mac, the CUDA driver is separate from the NVIDIA graphics driver and must be installed, if you don't have it already. The minimum requirement is driver version r361 which can be downloaded from www.nvidia.com/drivers.

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

#### AMD

• On Windows and Linux, an AMD GPU and driver from the following list:

Windows GPU | Driver | Linux GPU | Driver
--- | --- | --- | ---
AMD FirePro W8100 | 17.Q2.1 | AMD FirePro W8100 | 17.Q2.1
AMD FirePro W9100 | 17.Q2.1 | AMD FirePro W9100 | 17.Q2.1
AMD Radeon R9 Fury X | 17.4.3 - 17.6.2 | AMD Radeon R9 Fury X | 17.10
AMD Radeon RX 480 | 17.Q2.1 | AMD Radeon RX 480 | 17.Q2.1
AMD Radeon Pro WX 7100 | 17.4.3 - 17.6.2 | AMD Radeon Pro WX 7100 | 17.10

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

• On Mac an AMD FirePro GPU on late 2013 Mac Pro 6,1, mid 2015 MacBook Pro 11,5, and late 2016 MacBook Pro 13,3, running OS X 10.9.3 'Mavericks', or later.

#### 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 FirePro W9100s.

# New Features

#### VFX Platform 2017 Compliance

This is a significant update to Nuke's core libraries and numerous third party libraries, with the aim to provide a common target platform for building software for the VFX industry. For more information on the library versions shipped with Nuke 11, see Appendix D in the Online Help.

#### AAF Import

Nuke Studio and Hiero now support non-linear retimes imported from Avid Media Composer in the .aaf format. Retimes exported from Avid are converted to Timewarp soft effects in the timeline so that you can adjust them in the Curve Editor if necessary.

#### Expanded AMD GPU Support

Nuke’s OpenCL support has been expanded on Windows and Linux operating systems. As a result, certain AMD GPUs are now compatible with Nuke, giving you more choice in the hardware you use. See Requirements for Nuke's GPU Acceleration for more information.

#### ARRIRAW and R3D SDK

The ARRIRAW and R3D SDKs have been updated as part of the VFX Platform 2017 work. The new library versions are ARRIRAW 5.3 and R3D 6.2.2.

Note: Nuke does not currently support ARRIRAW files in the .mxf format, such as those from the ARRI ALEXA Mini. Support for .mxf files is scheduled for a future release.

#### Denoise

Denoise now includes a temporal processing option, which can help to improve results by averaging the noise reduction over several frames, instead of just a single frame.

#### Frame Server in Nuke

Nuke Studio's Frame Server is now available in Nuke and NukeX, allowing you to reduce render times by sharing work over the number of render processes specified in the Preferences. You can also use external machines as render workers. The Frame Server logs renders in the Background Renders panel, including information such as script name, Write node, frame range, progress, and whether or not the render produced errors.

The Frame Server is disabled by default, but you can enable it in the Preferences > Threads/Processes or on a per render basis in the Write node's Render dialog.

#### Latest Operating System Support

Hiero 11 is qualified on the following operating systems:

• Mac OS X 10.11 (El Capitan) or macOS Sierra (10.12)

• Windows 7 and 10 (64-bit)

• CentOS 6 and 7 (64-bit)

Other operating systems may work, but have not been fully tested.

#### LensDistortion

NukeX and Nuke Studio's LensDistortion node has been improved and streamlined for ease of use. It includes support for spherical and anamorphic lenses and a number of presets and distortion models, and displays the Distortion Equations for the selected lens type. You can estimate the distortion in an image using automatic Grid Detection or draw curves in the Viewer manually to solve the lens. The node also allows you to output STMaps in the motion channel for use elsewhere in the script.

#### LiveGroups

LiveGroups are a type of container node that can be used in conjunction with LiveInput nodes so that multiple artists can work on different parts of the same shot as separate scripts, without the need for rendering. LiveGroups also offer all the functionality of Precomps, Groups, and Gizmos combining all the functionality that they lack individually.

Just like Precomps, LiveGroups can store independent, open source .nk files, allowing you to save a subset of the node tree as a separate .nk script, render the output of this saved script, and read the rendered output back into the master comp as a single image input.

You can also use LiveGroups like Group nodes to nest multiple nodes inside a single node. The original nodes are replaced with the LiveGroup node. When you create a LiveGroup node, its internal structure is shown in a separate Node Graph tab.

#### Smart Vector Toolset Improvements in NukeX

The SmartVector toolset's SmartVector node can now export a Write node to calculate vectors in the background while you're working.

Additionally, the VectorDistort node now includes a new blur size control, which can help remove micro distortions. This is particularly useful when propagating thin or fine structures over time.

#### Timeline Disk Caching

Timeline Disk Caching provides reliable playback for more complex timelines by rendering frames to disk using the GPU. The cache provides persistent frames per edit in the timeline that only needs updating for full changes on the edit, such as adding a soft effect. For editorial changes, only the new frames need to be cached.

#### New Toolsets

The ready-made example scripts in the Toolsets menu have been updated and split into two broad categories: 2D and 3D. The ToolSets give you access to several examples of common compositing tasks, such as multipass rendering from common third-party renderers, keying, particle systems, and rig removal. See ToolSets Nodes for more information on the examples that ship with Nuke.

The scripts also contain a link to footage you can download to use with the examples:

http://thefoundry.s3.amazonaws.com/products/nuke/toolsets/toolset_examples.zip

#### Truelight

FilmLight and Foundry have elected to no longer bundle Truelight as of Nuke 11. The Truelight node has been superseded by the free version of Baselight for Nuke which itself can import a BLG (Baselight Linked Grade) that can contain a Truelight strip, plus optionally a lot more in terms of creative grading intent. Together with OpenColorIO and the native Nuke Vectorfield node we feel all the Nuke color management issues for which the Truelight node was originally intended are now addressed.
For further information on Baselight for Nuke, please contact plugin-support@filmlight.ltd.uk

# Feature Enhancements

• ID 138125 - Precomp: Scripts containing Group nodes with a Write node inside now automatically connect the Write to the Output of the Precomp node.

• ID 278084 - The Mailing Lists option under Hiero's Help menu has been replaced by a link to the Foundry Forums, allowing you to keep in touch with the Hiero community more easily.

# Bug Fixes

• ID 151676 - Linux only: Running NVIDIA GPUs in high bit-depth (30-bit) mode made the UI visually unstable.

• ID 161942 - DeepExpression: The < and > comparators were both evaluated as < (less than).

• ID 218316 - ARRIRAW: The arriReader did not support the full range of integers (-12 to +12) for the tint control.

• ID 242501 - ARRIRAW: Reading certain .ari files displayed resolution not supported in current ArriSDK version in the Viewer.

• ID 250117 - Export: Certain sequences could not be exported using the Frame Server.

• ID 252438 - Windows only: Resizing panels during playback created multiple instances of the panel and lowered the framerate.

• ID 263006 - AAF: Executing Match Media on certain imported .aaf sequences did not conform some clips.

• ID 264028 - Mac OS X El Capitan only: Dragging handles in the 3D Viewer was slower to update than in previous versions of Hiero.

• ID 266672 - AAF: Negative retimes imported from .aff files were displayed incorrectly in the timeline Viewer.

• ID 266911 - AAF: Freeze frames were displayed as missing data.

• ID 267674 - BlinkScript: Default values could not be changed for float4x4 matrix and float3x3 matrix in BlinkScript kernels.

• ID 269346 - AAF: Percentage values on certain imported linear retimes were incorrect.

• ID 269873 - Particles: Rendering multiple views from the P_RainBox toolset did not work as expected.

• ID 272604 - Documentation: The Frame Server worker command, --nukeworkerthreads, was listed incorrectly as --numworkerthread.

• ID 272637 - AAF: Retimed clips with embedded, pre-rendered media imported from Avid Media Composer were the wrong length.

• ID 272639 - AAF: Timewarp soft effects imported from .aaf files displayed an error when not at the beginning of the sequence.

• ID 273865 - AAF: Timewarp effects on shots after the first shot in the sequence displayed an error.

• ID 274615 - Unknown nodes in scripts, such as custom OFX plug-ins, were not replaced by NoOp nodes on script load if they didn't specify xpos and ypos values.

• ID 274679 - BlinkScript: The Rolling Kernel example in the Blink Reference guide contained an error.

• ID 274964 - AAF: Importing multiple clips with linear retimes did not mirror the order exported from Avid Media Composer.

• ID 275195 - The text on the Crash Reporter dialog referred to the old Foundry Support address.

• ID 275271 - AAF: Cropped clips contained missing frames when imported into Nuke Studio.

• ID 275630 - AAF: Negative retimes included a frame offset when the source clips had no handles.

• ID 275720 - Linux CentOS 7 only: The Export Queue magnifying glass button did not work as expected.

• ID 275854 - AAF: Imported retimes ignored anchor keyframes.

• ID 277333 - AAF: Imported shots were truncated when compared to the source.

• ID 278078 - The --remap command line argument's error messages contained typographic inaccuracies.

• ID 278106 - Audio: Retiming and then slipping audio shots past the start of the shot caused Nuke Studio to crash or rendered the waveform incorrectly.

• ID 282239 - Read/Write: The tooltip for .r3d files color space control was out of date.

# Developer Notes

Here are the changes relevant to developers. See Help > Documentation from the Hiero menu bar or www.thefoundry.co.uk/products/nuke/developers/110/ndkdevguide/appendixc/index.html for more information.

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 plugins and/or make changes to the source code.

Release Type | Example | Compatibility | Recompile | Rewrite
--- | --- | --- | --- | ---
Version | 10.0v1 to 10.0v2 | API and ABI |  |
Point | 10.0v1 to 10.5v1 | API |  |
Major | 10.0v1 to 11.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")

## New Features

#### VFX Platform 2017 Compliance

This is a significant update to Nuke's core libraries and numerous third party libraries, with the aim to provide a common target platform for building software for the VFX industry. For more information on the library versions shipped with Nuke 11, see Appendix D in the Online Help.

## Feature Enhancements

There are no feature enhancements in this release.

## Bug Fixes

There are no bug fixes in this release.

Did you find this helpful?

Yes No

## Sorry you didn't find this helpful

Why wasn't this helpful? (check all that apply)

Couldn't find what I was looking for
Instructions are confusing
Instructions didn't work
Title is misleading
Content is out-of-date
The translation is poor

Thanks for your feedback.

If you can't find what you're looking for or you have a workflow question, please try Foundry Support.

If you have any thoughts on how we can improve our learning content, please email the Documentation team using the button below.

That's great!

Thanks for taking time to give us feedback.