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.0v2

# Release Date

31 August 2017

# Qualified Operating Systems

• Mac OS X El Capitan (10.11) 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

There are no new features in this release.

# Feature Enhancements

There are no feature enhancements in this release.

# Bug Fixes

• ID 146580 - Timeline: The RAM cache (white bar) was cleared when the Viewer gamma or gain controls were adjusted.

• ID 156851/215328/288634 - mov64Reader: Certain DNxHD and ProRes 422 clips flickered during playback.

• ID 159347 - Linux only: Scrubbing the playhead increased memory usage steadily until Hiero became unresponsive.

• ID 160266/199070 - mov64Writer: The mov64 codec failed when encoding 24-bit audio.

• ID 161450 - Read: Linux and Mac produced different pixel values to Windows when reading RAW files.

• ID 198612 - Read: The start time in a customer .mov file differed depending on whether the mov32Reader or mov64Reader was used.

• ID 216355 - mov64Reader: Reading files written with the Animation codec produced blurred images when compared to the mov32Reader.

• ID 219603 - Nuke Studio didn't load the individual default LUT settings when using the OCIO environment variable to declare a custom configuration file.

• ID 219609 - Export: Enabling a custom OCIO config using the OCIO environment variable and then disabling it did not remove the preference from the uistate.ini, resulting in invalid color transforms during export or create comp operations.

• ID 228807 - Camera: The Save button was grayed out in the Export chan file > Chan File dialog in the Camera node's Properties panel.

• ID 229571 - Read: Attempting to read large, compressed .mov files caused Hiero to crash.

• ID 231646 - Windows only: Enabling GPU processing with an NVIDIA M6000 installed caused Hiero to crash if the script contained a BlinkScript node.

• ID 248299 - OCIO: Using an OCIODisplay node as a viewerProcess did not display the alpha channel in the compositing Viewer.

• ID 266187 - Timeline: Reloading a project containing only audio tracks displayed a No Audio warning in the Viewer.

• ID 266334 - Windows only: Reading in RAW clips displayed the image upside-down.

• ID 268083 - AddTimeCode: The new timecode was added even when the node was disabled.

• ID 272142 - VFX Platform: Using the mouse scroll wheel to edit numeric controls scrolled the Properties panel.

• ID 272884 - VFX Platform: Closing the Licensing dialog printed errors in the command prompt.

• ID 275038 - Mac OS X/macOS only: The menu bar and Dock were not restored correctly when switching to the Compositing workspace.

• ID 275906 - ACES: Nuke Studio did not import the correct colorspace for .mov files.

• ID 277875 - VFX Platform: Changing a layout caused it to redraw incorrectly.

• ID 278339 - Mac OS X/macOS only: Key/value pairs could not be selected in the Read node's Metadata tab.

• ID 279047 - Documentation: Some of the links in Hiero's Help menu did not work as expected.

• ID 280788 - Mac OS X/macOS only: Opening a second scope, Histogram or Waveform, in a workspace containing no scopes by default produced artifacts in the second scope.

• ID 281244 - Metadata: Adding [metadata] to a Text soft effect or node did not display the following metadata keys:

• hiero/sequence/frame_rate

• hiero/project

• hiero/sequence

• ID 281569 - Timeline Editing: The timeline Viewer See Through Missing Media option was active for clip instances where media was not OFFLINE.

• ID 281750 - Mac OS X/macOS only: Scrubbing the playhead caused the current frame line to lag behind on the timeline.

• ID 282440 - Create Comp: Overwriting an exported .exr sequence caused Nuke Studio to crash.

• ID 282468 - Read/Write: The Media tab Colour Space control listed options for .r3d files that have been removed from the Compositing environment.

• ID 282621/305753 - Timeline Disk Caching: Changing the cache directory discarded cached frames between In and Out points.

• ID 284061 - Timeline Disk Caching: Caching long sequences occasionally stalled until the background render process was paused and then restarted.

• ID 286445 - Right-clicking on some controls in the node Properties panel occasionally displayed two menus on top of each other.

• ID 286547 - Mac OS X/macOS only: Adding a Burn-in soft effect to large shots on the timeline caused the effect's control sliders to be sluggish.

• ID 297255 - Timeline Disk Caching: Adjusting .r3d or .ari controls in the Media tab did not force the disk cache to refresh.

• ID 303733 - Documentation: The application Help > Release Notes link pointed to the wrong URL.

• ID 303931 - Preferences: Changing the Comp Disk Caching > temp directory path stopped the application loading.

• ID 304531 - HueCorrect: The hue LUT control's background in the Properties panel was gray, rather than the full color spectrum.

• ID 305082 - Preferences: Zooming in the Viewer with Panels > Viewer > use GPU for Viewer when possible enabled drew black handles in the Viewer.

• ID 305898 - Timeline Disk Caching: Changing the Timeline Disk Caching > directory path in the Preferences and then switching back to the default directory discarded changes to edits on the timeline.

# 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

There are no new features in this release.

## Feature Enhancements

There are no feature enhancements in this release.

## Bug Fixes

• ID 286759 - Mac OS X/macOS only: The mov64 example in the NDK documentation did not build using Clang.

• ID 287055 - VFX Platform: Nuke prompted customers incorrectly that Visual Studio 2010 was required for plug-ins, rather than Visual Studio 2015.

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.