Welcome to the Nuke 11.1 Beta.

Hello, Nuke users! We're excited to share the first Beta versions of our upcoming Nuke 11.1v1 release for you to try out and provide feedback on. As these builds are Betas, we strongly recommend and advise you not to use it in a production environment.

Please be aware that all features and functionality contained within these Betas are in active development and are liable to change and are not guaranteed to be in the final released version of Nuke 11.1v1.

To access these Betas you need to own Nuke/NukeX/Studio and be on current maintenance.

Worried your maintenance might have lapsed? Request a callback from our team or contact your local reseller.

These Beta versions of Nuke, NukeX and Nuke Studio 11.1v1 will run using your existing Nuke license keys (nuke_i, nukex_i and nukestudio_i) that have current maintenance.

Tell us what you think

If you have general issues to do with licensing or legacy bugs, please raise a ticket for Foundry’s Support team via our Support Portal: http://support.foundry.com

If you have feedback on the 11.1 Beta that you'd like to share with us and discuss in the Pre-Release group please message us at : foundry-nukestudio-prerelease@googlegroups.com or  foundry-nuke-prerelease@googlegroups.com

If you have any private feedback on the 11.1 Beta that you'd like to share with us, please use our private mailbox: nuke-prerelease-private@foundry.com.

But don't tell everyone!

Please do not discuss the alpha version outside of the above private mailbox. So avoid discussing it on social media, public forums or the nuke-users@/nuke-dev@/nuke-python@ mailing lists.

Thank you for your assistance, continued support and enthusiasm for Nuke!

Features in this Beta

The following features (identifiers listed below) are what we would like you to concentrate your feedback on for this alpha (more details on these features can be found below):

New in Beta #2 (11.1v1.000056b) - LAST BETA !

  • [Bug Fixes]

New in Beta #1 (11.1v1.000027b)

  • [Property Panels]
  • [Localization]
  • [Visual Diagnostics]

Please use the above feature identifiers at the beginning of the Subject line. 
For example:

“[Property Panels] - OMG the panels have great properties!!”

Source clip property panels [Property Panels]

In Nuke Studio projects, source clip properties are now accessible through a Read node style panel displayed in the Properties tab. This consolidates existing options into a single location, providing faster access and greater control, as well as introducing a more consistent UI and workflow between Nuke and Nuke Studio.

In addition to this it is now possible to use relative paths for source clips in a Nuke Studio project. The root project directory can be set in Project > Edit Settings > General. A separate export directory can still be set in the Export section (n.b. the label still states ‘Project Root:’ but it will be changed to ‘Export Root:’ in future builds).

Existing source clip options have been improved and a number of new options have been added.

  • file - Replaces the Media File option in the Media tab and now has Expression support. This, for example, allows environment variables to be used in file paths.
  • localization policy - Easy access to the localization policy for each source clip.
  • original range - Adjust the source clip frame range. Previously only accessible through ‘Open In > Timeline Viewʼ. A rescan button has also been added for quick access to ‘Rescan Clip Range’.
  • missing frames - Set how file read errors should be handled. Error, black, checkerboard or nearest frame.
  • colorspace - Replaces the Colour Space option in the Media tab and has improved error handling for missing colour spaces.
  • OCIO - Provides OCIO context support for source clips.
  • Format specific - Easy access to format specific options. For example, QuickTime decoder, ycbcr matrix and source range (video or full).

Greater control over the source clip properties in Nuke Studio also provides greater control over generated .nk scripts when using the Create Comp workflow.

In addition to this all source clip properties will be accessible through the Python API, improving scripting capabilities and therefore the ability to integrate Nuke Studio into existing pipelines.

Localization Improvements [Localization]

Localization sees the introduction of 3 system modes, namely ‘On’, ‘Off’ and ‘Manual’, as well as a new ‘On Demand’ localization policy. These additional modes and policies provide greater control and a more intuitive localization experience.

The Python API has been extended to allow developers to set system modes and localization policies programmatically. The API also provides the ability to set localization priority, apply policies based on read node type, and remove localized file according to specific criteria.

Additional updates include:

  • Pause behaviour: when the system is paused, users have the ability to perform the “force update” options.
  • Progress bar: different colours represent ‘up to date’, ‘in progress’ and ‘out of date’ states for localized files.

Visual Diagnostics [Visual Diagnostics]

Nuke’s performance profiling system is now easily accessible through the UI. Previously it could only be activated using a command line flag (--Pf).

This system can be used to help diagnose problems in Nuke scripts, for example, a particular node may be draining system resources.

A new Profile node has been added which can be inserted at any point in a script, allowing performance data to be captured for all upstream nodes. This data includes the CPU time, wall time, number of ops and memory usage.

A new Profile panel has also been added. This allows the Profile nodes to be configured and executed. Once profiling is complete the captured data will be displayed in this panel. There are a number of options to filter this data and also the ability to import and export it.