NukeX Changelog

What's new in NukeX 15.0v1

Oct 12, 2023
  • The new version of Nuke includes native Apple silicon support, faster CopyCat training, continued evolution of the new 3D system, and more improvements designed to make your workday more efficient.
  • Extended High-Resolution Support:
  • For users working at very high resolutions, on installations such as large events, theme park rides, and in virtual production, Nuke now supports a number of planar operations on images up to 64K, with sufficient hardware. This means that for Nuke 14.1, all CaraVR nodes, Spherical Transforms and Lens Distortions can now be used on even larger resolutions, giving you greater scalability in your projects.
  • Faster CopyCat Training:
  • With Nuke 14.1’s new distributed training, you can share the load across multiple machines using standard render farm applications. This makes training faster and means you can carry on using Nuke with CopyCat running in the background. And with multi-resolution training, CopyCat will now automatically lower image resolutions to reduce file size during the early stages. This can reduce training times by up to 50%.
  • New GeoMerge Workflows (Beta):
  • The updated GeoMerge node gives you greater control when merging your geometry and USD layers. The GeoMerge node includes four new modes: Merge Layers, Duplicate Prims, Flatten Layers, and Flatten to Single Layer. So whether you just want to merge branching pipes quickly, recreate classic duplication workflows, or have greater control over how your layers are managed, the new mode and UI will provide a more intuitive experience.
  • 3D Viewer Selection (Beta):
  • Improved viewer selection tools offer greater control when working with much larger stages within the 3D system, with a dedicated 3D toolbar and new two-tier selections. With the new toolbar, you can quickly switch between object, face or vertex mode, while new controls enable you to specify your selection based on the type or kind of the prims in the scene. This brings greater control over which level on a piece of geometry you make your selection. And with two-tier selection you can contain it within your geometry, making it easier to focus on one item in a stage – giving you greater control when creating selections in complex scenes.
  • Scene Graph Popup In The Mask Knob (Beta):
  • The USD-based 3D system introduced in Nuke 14.0 means you can work with larger, more complex scenes. However, larger scenes means more data and assets. The new Scene Graph Popup makes it easy to filter through the 3D scene data, using the Mask knob to inspect, filter, and select cameras and prims in the context of the scene’s hierarchy. This means you can spend less time searching for the assets you need and more time focusing on the final picture. There’s also a search and filter feature on the main 3D scene graph, for easier navigation.
  • ScanlineRender2 Updates (Beta):
  • Building on what we introduced in Nuke 14.0, we’ve further developed ScanlineRender2. It now provides a familiar utility render experience for the new 3D system, while bringing additional benefits and crucially, laying the groundwork for the future of 3D rendering in Nuke. Among various improvements designed to support the rendering of all the utility passes you’re used to, the UI has been made more intuitive, while a new raytracing subsystem allows for improved shadows with raytrace occlusion.
  • Saturation Slider For Nuke’s Viewer:
  • For Nuke 14.1, a saturation slider has been added to Nuke’s Viewer. This is a small but much-requested feature, and is designed to help check your work, much like the Gamma and Gain controls already in the Viewer.
  • Timeline Review Improvements:
  • Nuke 14.1 is designed to make Nuke Studio review sessions faster and more reactive. Auto-selection of shots under the playhead means you can quickly apply multiple actions, without the need to select individual shots. What’s more, Nuke Studio’s new multi-playhead enables you to compare different frames on the timeline quickly and easily. These and other timeline improvements mean you can compare shots and add effects on the timeline much faster than before, boosting efficiency.
  • Multi-Pixel Blink Effects In The Timeline:
  • With Nuke Studio and Hiero you can now apply Blink effects, such as LensDistortion and Denoise at the timeline level, so you don’t have to go back and forth between the timeline and comp environments. The improved BlinkScript enables computation of more than one pixel at a time, so you can write your own effects to perform powerful and complex operations on the timeline.
  • Machine Learning Inference In The Timeline:
  • Whether it’s beauty-fix work, matte generation, or something completely different, creative uses for CopyCat are growing as compositors continue to unlock its full potential. With machine learning inference in the timeline, you can ‘audition’ and apply these effects across multiple shots at once during conform and review. You can apply pre-trained .cat files to shots or sequences directly using the Inference soft effect, meaning you can stay focused on the edit and quickly review the results across multiple shots in context, without alternating between the timeline and comp environments.
  • Automatic Timeline Disk Cache:
  • Previously, manually re-creating the disk cache every time a change was made to your edit or soft effects on the timeline was a barrier to fast and efficient reviews. With the improved timeline tools, Nuke Studio and Hiero can automatically re-cache any frames that require updates. So no matter how complex your timeline effects or how many you’ve applied, you can continue reviewing while Nuke automatically refreshes the disk cache in the background.
  • File Format SDK Updates:
  • Stay up-to-date with industry standards with support for the latest SDKs and cameras. Nuke 14.1 brings improved support for the new ARRI Alexa 35 camera with the ability to read files in HDE format, and we’ve also updated the HDE SDK to version 4.0.3. Whatever the show, we’ve got you covered with a wide range of updates to supported cameras, monitor out cards, and file formats.
  • OpenColorIO Updates:
  • Maintain color consistency across your pipeline with OpenColorIO (OCIO) updates in Nuke 14.1. To align with OCIO version 2, we’ve updated the “Write” node and Export dialog for Nuke Studio with a clearly labeled Output Transform subsection, for a simplified, easy-to-understand way of baking in display transforms. The new OCIO Aliases attribute allows configs to define a set of alternate names for a color space.
  • OpenAssetIO (Tech Preview):
  • In Nuke 14.1 we’re introducing a tech preview of OpenAssetIO, an open-source interoperability standard for tools and content management systems. Implementing OpenAssetIO across your software stack can help simplify pipeline integration and streamline workflows. This new standard will also make it easier for artists to find and identify the assets they need with more sophisticated asset and version management workflows.
  • ​​OpenAssetIO connects Nuke to an Asset Management System via a “Manager Plugin” for more information on this see the OpenAssetIO Integration Guide. For details on this mechanism and how to get started writing a plugin for your pipeline, please see the project documentation here.

New in NukeX 14.0v1 (Dec 6, 2022)

  • New USD-Based 3D Architecture (Beta):
  • We’re completely revamping Nuke’s 3D system introducing a new beta USD-based system to allow artists to efficiently work with modern 3D scenes at scale.
  • The new USD architecture brings Nuke’s 3D in line with modern standards and introduces a dedicated scene graph, new path and masking workflows, over 40 nodes, and new USD-based workflows. We’ll be continuing to develop the new 3D system across the Nuke 14 series and, to ensure artists don't lose access to any workflows they are used to, the new system will work in parallel with the classic 3D system.
  • New 3D System: Scene Graph:
  • With the new 3D system comes the introduction of a dedicated scene graph that allows users to easily view, navigate and manage large, complex 3D scenes. Artists will get a clear, visual overview of a scene and experience the intuitive drag-and-drop functionality to new path masks in nodes. This advanced scene graph is consistent with modern 3D workflows and ensures every primitive inside the new system will have a unique ID path that will exist in a scene graph hierarchy.
  • New 3D System: Paths and Masking:
  • We’re giving artists greater control with new path and masking workflows. All nodes that create geometry will have a new path knob that enables users to determine where the geometry they’re creating lives in the scene hierarchy and how it's named. Similarly, any nodes that modify geometry will have a new mask knob that allows artists to specify which part of the 3D scene that node should affect. These knobs are based on a simplified CEL expression language that allows the use of tokens and expressions. For artists, this means that the knobs can default to intuitive workflows with minimal input, but also allow for complex selections if you want to go deeper.
  • New 3D System: Lights and Materials:
  • Introducing new material and light nodes in Nuke 14.0. With support for USD material networks, a new PreviewSurface material node allows for USD-based specular or metallic workflows and materials can display immediately in the viewer when working with USD files with their own looks. This gives artists a way to quickly see their assets in a more accurate representation inside Nuke’s 3D viewer. New USD lights mean that when importing lights from other USD-based applications, you will have the exact same lights inside Nuke and when combined with Hydra and potential future support of additional renderers in Nuke’s viewport, this means artists could see a more consistent image across applications going forward.
  • New 3D System: Feedback Forum:
  • So that you can help continue to shape the new 3D system across the 14 series, we are introducing a dedicated community forum to enable discussions and feedback with the 3D team. We’re interested in hearing from you in regards to all areas, from existing nodes and workflow improvements, new node or workflow suggestions, feedback on performance, the API, or new features such as the scene graph or path and masking workflows.
  • UnrealReader:
  • In Nuke 14.0, UnrealReader features support for Unreal Custom Render Passes allowing for effects like non-photorealistic rendering, OpenColorIO to allow matching of color spaces between Nuke and Unreal, easier picking of Sequences, and access to Unreal Sequence metadata to retrieve info on objects like lights.
  • CopyCat Performance Improvements:
  • Nuke 14.0 ships with UI and performance improvements to Nuke’s AIR tools. These updates include a new checkpoint targeting human matting that has been added to CopyCat, speeding up training by up to ten times. We’ve also upgraded to PyTorch 1.12.1 which widens the range of support for models converted to .cat via the CatFileCreator node and sped up CopyCat training by 20% on NVIDIA Ampere GPUs.
  • Introducing the Cattery:
  • The Cattery is a library of free third-party, open source machine learning models converted to .cat files to run natively in Nuke. Cattery aims to bridge the gap between academia and production, giving everyone access to a range of open-source ML models that all run in Nuke. We’ll be giving you access to state-of-the-art models addressing segmentation, depth estimation, optical flow, upscaling, denoising, and style transfer, with plans to expand the models hosted in the future and open the site up to user submissions.
  • Timeline Updates:
  • You now have access to full OCIO soft effect support in HieroPlayer. This means projects imported from Studio or Hiero can be opened and all the OCIO soft effects can be accessed and adjusted. New instances of OCIO soft effects can be added on new tracks or clips, giving you even greater control over how you work in HieroPlayer and allowing you to review in the context of a sequence. We’ve also updated OTIO to the latest 0.15 version so that pipelines can continue to explore this new format for moving editorial data throughout your pipeline.
  • Colorimetry Metadata in Monitor Out:
  • For artists working with HDR data, we are including colorimetry metadata support to allow for users to have an easier and quicker setup for their monitoring devices. You can now enable and control metadata passed over HDMI or SDI, so that their video content is automatically displayed in HDR on their appropriate monitor, helping to reduce setup time and providing greater workflow efficiencies.
  • OCIOv2.1 and ACES 1.3
  • We’ve updated Nuke to support OCIO 2.1.2 and, as part of that, users will also be able to use the latest ACES version 1.3. This includes new color space conversion transforms for supporting ARRI, Sony, Red and BMD cameras as well as the ACES Reference Gamut Compression algorithm for fixing highly saturated images lit with LED light sources.
  • We are also pleased to announce that we have also added two new configs:
  • Studio-config-v0.1.0_aces-v1.3_ocio-v2.1.2 - The ACES Studio config is geared toward studios that require a config that includes a wide variety of camera colorspaces, displays and looks. In spirit it is close to the ACES 1.2 config whilst leveraging the new OCIO 2 features and being smaller. As of this release, it does not contain any external dependencies such as LUT files.
  • Cg-v0.2.0_aces-v1.3_ocio-v2.1.2 - The ACES CG config is intended for use in
  • Login-Based Team Licensing:
  • We have extended support for login based licensing to the entire Nuke Family (including render licenses and plug-ins) and expanded it to include new features and functionality for teams and organizations.
  • Login-based team licensing allows you to manage your pool of licenses, with a number of new tools and features for administrators to control who has access to them, giving you more control and greater flexibility over how you administer and use your software and licenses.CG lookdev, lighting, and rendering applications. It implements a fully-featured ACES color pipeline without the many camera input transforms that make up the bulk of the OCIO v1 ACES configs. The CG config is completely self-contained (no external LUT files), providing a single file color pipeline with minimal clutter. It has robust support for the most common texture and working color spaces, and SDR and HDR output transforms used in high-end CG production environments.
  • Bug Fixes:
  • ID 439456 - Read/Write: Reading DNxHD files that did not contain certain metadata displayed a Mov64 Reader: Failed to create DNx decoder error message.
  • ID 511559 - BlinkScript: Fetching a sample value using [#] (square brackets) caused compilation to fail on the GPU.
  • ID 516263 - Metadata: Resizing the Metadata column and then scrubbing on the timeline or switching to a different item reset the size of the Keys column.
  • ID 518594 - Navigating to Help > Nuke Plug-ins did not redirect to the plug-ins page as expected.
  • ID 520255 - Soft Effects: The Burn-In effect did not work as expected.
  • ID 521294 - Sync Review: Enabling or disabling track blending or masking during a sync session affected other sessions' Viewer unexpectedly.

New in NukeX 13.0v5 (Nov 23, 2021)

  • NewFeatures:
  • BUG ID 244774 - Timeline Editing: You can now copy and paste shots and soft effects between different
  • Projects in the same Nuke Studio or Hiero session and between Nuke Studio and Hiero sessions.
  • Bug Fixes:
  • BUG ID 351910 - Timeline Editing: Copying a sequence into a new project did not work as expected.
  • BUG ID 352502 - Localization: Clearing a comp or closing and reopening a script discarded the green
  • Localization progress bar on Read nodes.
  • BUG ID 380723 - Read/Write: Clicking Load Settings from RMD in .r3d files written using IPP2
  • Incorrectly enabled the Colorspace and Gamma Curve controls.
  • BUG ID 391032 - DeepRead: Using Tcl and Python expressions in the file control displayed a Plugin
  • Error message.
  • BUG ID 405652 - Node liftimeStart knob values were not saved in the Nuke script if the start or end
  • Values were 0.
  • BUG ID 413707 - EdgeExtend: The Matte has no fully white pixels to sample from error message was
  • Not ignored correctly in some cases, causing renders to fail unnecessarily.
  • BUG ID 426901 - File Formats Update: In IPP2 Custom mode, enabling the Use GPU checkbox displayed
  • Grading controls from the IPP2 Pipeline incorrectly.
  • BUG ID 435284 - Python: Calling nuke.message() or nuke.alert() did not pause processing on the main
  • Thread as expected.
  • BUG ID 440798 - Timeline Editing: Using the Ripple Delete (Shift+Backspace) shortcut in the timeline
  • Occasionally offset frames incorrectly.
  • BUG ID 461944 - Python: Changing a Read node from an image sequence to a container file format
  • Pythonically caused Nuke to crash if the Read node had postage stamp set to a static frame.
  • BUG ID 462986 - Read/Write: Importing .mov files with custom resolutions occasionally caused the
  • Application to crash.
  • BUG ID 468630 - Monitor Out: Certain controls in the Monitor Out strip did not work as expected.
  • BUG ID 475029 - Cryptomatte: The cryptoLayerChoice knob value was not retained when opening
  • Certain scripts containing a gizmo.
  • BUG ID 483089 - Python: Calling import nuke failed to load modules using Nuke's Python interpreter.
  • BUG ID 483350 - Read/Write: Loading unknown file types after loading a .mov file caused Nuke to crash.
  • BUG ID 483554 - Developer Info: numCPUs was used where numThreads should be used.
  • BUG ID 483961 - Python: Nuke renders did not set the thread count reliably using -m or nuke.env
  • ['threads'] = n.
  • BUG ID 484526 - Python: Dragging and dropping a custom PySide2 widget on a panel in Nuke caused
  • The application to crash.
  • BUG ID 484726 - Soft Effects: Undoing cut or delete operations on cloned effects occasionally
  • Decoupled the clone state, reverting it to a standard effect
  • BUG ID 484879 - Soft Effects: Cutting and pasting a clone occasionally created a standard effect, rather
  • Than a clone.
  • BUG ID 485146 - Developer Info: Nuke's arg parser used a too-small, signed int for memory limits.
  • BUG ID 485619 - Cryptomatte: Mattes with floating point IDs containing hyphens could not be selected
  • In the Viewer.
  • BUG ID 487403 - Cryptomatte: Clicking Picker Add did not allow you to pick mattes with names
  • Containing - (dash) characters.
  • BUG ID 488584 - Cryptomatte: Clicking Picker Remove didn't work for mattes with floating point ID
  • Values

New in NukeX 12.0v3 (Nov 15, 2019)

  • Bug Fixes:
  • BUG ID161075 - Monitor Output: Play back of stereo RGB footage using YUV conversion did not work as expected on Blackmagic 4K Extreme 12g cards
  • BUG ID388835 - Timeline Playback: Enabling Monitor Output occasionally caused the Viewer to drop frames during playback with Blackmagic Decklink 4K Extremecards.
  • BUG ID393610 - Cara VR:Standard Nuke Write nodes included a new Cara VR tab
  • BUG ID399741 - Monito rOutput: Opening a projectset to 4K output and immediately enabling monitor output through an AJAK on a 4 card displayed garbage on the monitor.
  • BUG ID399908 - Deep: Using Deep Recolor with
  • target in put alpha enabled on a single channel created artifacts in the other channels
  • BUG ID400497 - High DPI:
  • The Crop node bounding box outline was thinner and smaller than in legacy versions of Nuke.
  • BUG ID400505 - High DPI: The Corner Pin node bounding boxo utline was thinner and smaller than in legacy versions of Nuke.
  • BUG ID402331 - Camera Shake:The Viewer controls remained after deleting the node

New in NukeX 12.0v2 (Oct 21, 2019)

  • Soft Selection:
  • The Soft Selection feature extends how you can interact with geometry and cards in the 3D viewer. Soft Selection gives you a customizable falloff to your geometry vertex, face, or edge selection. Combined with Nuke 11.3’s lasso selection mode, this feature makes modifying geometry for projection setups, last minute adjustments, or any number of 3D workflows more streamlined.
  • Edge Extend Node:
  • Discover Edge Extend, the second of our new GPU accelerated nodes. Edge Extend speeds up artist’s everyday workflows, allowing you to erode or dilate your sample region to pull pixels from deeper inside your alpha. As well as giving you the ability to recover the original detail and noise with no introduction of artifacts.
  • Inpaint Node:
  • Introducing Inpaint, one of our new GPU accelerated nodes for common compositing tasks. Our Inpaint node gives you the ability to create contextual paint strokes similar to Photoshop’s Healing Brush, whilst controlling the level of detail, or pulling this detail from another part of the source image, or a second image entirely.
  • Grid Warp Tracker:
  • The Grid Warp Tracker helps create match moves, track warps and morphs, as well as allowing you to warp across custom defined grid shapes and use Smart Vectors to drive the grids. The 'To and From' grid workflow enables you to add and copy tracking data between grids, allowing you to retest or make amendments without losing your original data, or having to create a backup version. Exclusively in NukeX, you can use Smart Vectors to drive the grids or set multiple grids for finer adjustments.
  • Cara VR Node Integration in NukeX:
  • The majority of Cara VR’s nodes are now integrated into NukeX. This includes a suite of GPU enabled tools for VR and stereo workflows, as well as enhancing traditional camera solving and clean up workflows. Multiple camera setups become easier to manage with Cara VR’s Camera Solver, allowing artists to easily toggle between custom camera setups and solve, to generate a single image. The CameraIngest nodes allows you to easily import cameras from CG or other packages, to use with the Camera Solver. As part of this merge, VR Headset support will be available across the Nuke family, including in Nuke, Nuke Studio, and Hiero.
  • Nuke Studio, Hiero & HieroPlayer Playback Performance:
  • This release includes much more stable playback across the timeline-based tools in the Nuke family. The update comes as a result of new timing and control logic in the playback engine, optimized for the heavy I/O demands of color managed workflows with multichannel EXRs, especially at higher resolutions and frame rates.
  • Interactive Performance:
  • Nuke 12.0 ships with a variety of optimizations, throughout the software, to improve performance, especially when working at scale. One key improvement offers a much smoother experience when working on large projects and noticeably maintains UI interactivity when working in scripts with over 1,000 nodes. This benefit extends to scripts with many nodes encapsulated in Groups and Live Groups and also results in faster loading of large scripts.
  • EXR Read and Write Performance:
  • We’ve optimized performance of both reading and writing of EXRs. Some of the biggest improvements are seen when using planar-based compression types, such as PIZ, Zip16, DWAA and DWAB, allowing for faster reading of files, whether locally from disk or off a network. Reading in data can be a major performance bottleneck, improving read speeds adds to interactive performance and reduces processing time when rendering scripts.
  • OCIO Role Support:
  • The Nuke family now supports OCIO roles, which allows you to set custom role names as an alias for a specific colorspace, making it easier for artists to know which LUT to use and to share scripts between projects or facilities. You still get access to all the colorspace options you always have, but now the roles can act as a quick way to understand the color workflow of a given show. We’ve also improved error handling, so when artists are switching between shows, there isn’t any mishandling of which roles or LUTs are available or should be used.
  • Industry Standards and File Format Updates:
  • Nuke 12.0 supports VFX Reference Platform 2019, which sees Nuke using the latest versions of Qt and OpenEXR. The RED SDK has been upgraded to version 7.1, including support for CUDA-based GPU decoding of RED files in Nuke and NukeX. Sony SDK version 3.3 adds support for v4 of the VENICE camera and X-OCN XT files. SDKs for BlackMagic and AJA monitor out cards have also been upgraded to the latest major versions. Additionally, the Nuke family now supports reading of DNxHR encoded .mxf files. See the Tech specs and release notes for full details of updated format, GPU and operating system support.

New in NukeX 11.3v4 (May 3, 2019)

  • Feature Enhancement:
  • Deep:
  • The DeepHoldout nodes now include a compute occluded samples control. When enabled, the values of samples from main are affected by the occlusion values of the holdout samples in front of them. When disabled, holdout occlusion is ignored.
  • Additionally, the DeepMerge drop zero threshold control is now included in DeepHoldout, allowing you to filter out samples whose alpha value falls below this threshold, such as those caused by floating point inaccuracy.
  • Bug Fixes:
  • Deep:DeepMerge nodes set to holdout produced a less accurate result when compared to DeepHoldout nodes.
  • DeepHoldout: Alpha occlusions did not hold out correctly
  • Deep: The Deep Holdout and DeepMerge in holdout mode produced different results
  • DeepMerge: Setting operation to holdout combined alpha values if the B input was semi-transparent and behind the Ainput.
  • LensDistortion: Adding a LensDistortion2 node to the NodeGraph displayed a Warning:enumeration index value cannot be converted to int for item Lanczos4 message on the command line
  • Deep: The knob names and tooltips for the DeepHoldout and DeepMerge nodes were misleading

New in NukeX 11.3v1 (Dec 14, 2018)

  • Feature Enhancements:
  • BUG ID 343648 - Documentation: The Nuke help now includes a supported camera formats page.
  • Bug Fixes:
  • BUG ID 154598 - MXF: Setting debayer quality to High Quality on some Sony RAW files displayed
  • An error decoding frame message in the Comp Viewer.
  • BUG ID 176742 - SmartDistort: Error messages during input connection were misleading.
  • BUG ID 235679 - NDK Documentation: The documentation stated incorrectly that the GeoInfo::copy
  • () function copies primitive data.
  • BUG ID 272897 - Timeline Disk Caching: Caching continued after closing the project associated with
  • The frames being cached.
  • BUG ID 277342 - LiveGroups: Undoing a change to a node knob inside a LiveGroup didn't work as
  • Expected.
  • BUG ID 304664 - Timeline Disk Caching: The sequence Properties > Clip Reformat options did not
  • Work as expected when Timeline Disk Caching was enabled.
  • BUG ID 308870 - Licensing: Nuke 11.0v2 created client floating license files with incorrect names.
  • BUG ID 324685 - Denoise: Various controls in the Properties panel did not work as expected.
  • BUG ID 328102 - Write: Reloading a script incorrectly enabled the check file matches input option
  • In .exr Write node Properties.
  • BUG ID 329048 - ARRIRAW: Undoing changes to Read Properties settings displayed an error in the
  • Viewer.
  • BUG ID 329252 - ARRIRAW: Setting an incorrect Debayer Mode in Nuke Studio did not display an
  • Error.
  • BUG ID 350887 - VectorDistort: Error reporting was unclear when attempting to calculate vectors for
  • A single frame.
  • BUG ID 353546 - Denoise: Setting Source to Digital did not work as expected for all input
  • Resolutions.
  • BUG ID 354345 - Monitor Output: Realtime playback on the timeline was not possible when the
  • Output resolution was set to 2160p30.
  • BUG ID 358699 - R3D: In legacy mode, the default colorspace was not read from the .rmd metadata.
  • BUG ID 358988 - DnD: Drag-and-drop functionality did not work as expected on the Project
  • Settings panel.
  • BUG ID 359553 - Stereo: Changing the order of views in the Project Settings changed the hero view
  • In the Compositing environment.
  • Release Notes for Nuke and Hiero 11.3v1 | Feature Enhancements
  • RELEASE NOTES 8
  • BUG ID 359747 - Soft Effects: Certain BlinkScript kernels caused Nuke Studio to become
  • Unresponsive.
  • BUG ID 361673 - LiveGroups: Python exceptions were displayed incorrectly for some functions.
  • BUG ID 361843 - Localization: Undoing actions during localization did not work as expected.
  • BUG ID 362147 - Bounding Box Warning: Setting the threshold to 0% caused the warning to behave
  • Erratically.
  • BUG ID 362683 - LiveGroups: Expression links within LiveGroups occasionally produced corrupt files
  • When the script was saved.
  • BUG ID 362885 - LensDistortion: Certain scripts exhibited slow render times and lag.
  • BUG ID 362908 - Write: Enabling read file in the Properties occasionally reset the file type control.
  • BUG ID 363903 - LiveGroups: Overrides on exposed knobs did not work as expected inside nested
  • LiveGroups.
  • BUG ID 363967 - Denoise: Setting the Output control to Noise produced unexpected results.
  • BUG ID 329061/364388 - ARRIRAW/MXF: Undoing or re-doing changes to a shot did not update the
  • Properties panel.
  • BUG ID 365089 - LiveGroups: Copying and pasting an editable, but unmodified LiveGroup created
  • An edited LiveGroup.
  • BUG ID 365096 - LiveGroups: Publishing an editable, but unmodified LiveGroup created an edited
  • LiveGroup on reload.
  • BUG ID 365102 - Windows only: Reading files with spaces in the file path did not work as expected.
  • BUG ID 365190 - MXF: Changing controls in the Properties panel did not always update the Viewer
  • Correctly.
  • BUG ID 365567 - MXF: Exporting .mxf sequences as .mov files using Process as Sequence
  • Produced frame offsets.
  • BUG ID 365712 - Export: Spurious knob value warnings were displayed on certain export tasks.
  • BUG ID 365863 - MXF: Reading or importing Venice Raw SQ files did not work as expected.
  • BUG ID 366072 - LiveGroups: Invisible knobs were not ignored by the override functionality.
  • BUG ID 366263 - LensDistortion: Loading a script created a larger bounding box than expected.
  • BUG ID 366574 - Denoise: Nuke script precision was changed incorrectly to use Scientific Notation
  • Downstream of Denoise nodes.
  • BUG ID 366697 - LiveGroups: Reloading a LiveGroup and then enabling an output node in the
  • Advanced controls published the LiveGroup incorrectly.
  • BUG ID 366872/369082 - ARRIRAW: Clicking load settings from metadata in the Properties panel
  • Destroyed the undo stack.
  • BUG ID 367591 - Particles: Output from a certain Particles system appeared to bounce incorrectly.
  • BUG ID 359974/359983/368716 - Timeline Multiview: Stereo output set to display both eyes or side
  • By side did not display correctly on SDI monitors.
  • Release Notes for Nuke and Hiero 11.3v1 | Bug Fixes
  • RELEASE NOTES 9
  • BUG ID 368743 - Channel Management: Reading clips that broke the channel limit followed by clips
  • That didn't break the limit occasionally caused Nuke to crash.
  • BUG ID 368883 - MXF: Copy and pasting Read nodes did not copy the knob values correctly.
  • BUG ID 368915 - LiveGroup: Entering an invalid file path and then undoing the action placed the
  • LiveGroup into the editable state, but the padlock icon was still displayed on the LiveGroup tab.
  • BUG ID 369083 - Sony SDK: Selecting the unsupported SGamut in the Read properties did not
  • Display an error.
  • BUG ID 369425 - MXF: Metadata for some key pairs did not display the correct values.
  • BUG ID 369510 - Sony SDK: Editing comps containing certain .mxf files caused Nuke Studio to crash.
  • BUG ID 369749 - Mac OS X/macOS only: Exporting multi-view timelines to the .exr format displayed
  • An error unnecessarily.
  • BUG ID 369787 - R3D: Clicking Load Settings from RMD in the Properties panel destroyed the
  • Undo stack.
  • BUG ID 369899 - LiveGroups: Knobs that can add/remove other knobs, such as the Read node's File
  • Knob, could still modify the Properties panel in locked scripts.
  • BUG ID 370124 - Mac OS X/macOS only: The monitor output Side by Side mode did not play back as
  • Expected.
  • BUG ID 370360 - LiveGroups: Right-clicking a published LiveGroup's Properties panel and selecting
  • Set knobs to default set the LiveGroup's state to editable.
  • BUG ID 370392 - ARRIRAW: Tooltips did not include information on other file types, such as the .mxf
  • Extension.
  • BUG ID 370395 - Viewer Selection Modes: making selections using different modes did not update in
  • The Viewer in real time.
  • BUG ID 370415 - ARRIRAW: Selecting the Debayer Mode incorrectly did not display a clear error
  • Message.
  • BUG ID 370501 - ARRIRAW: Setting the Colorspace incorrectly to any of the available Monochrome
  • Settings did not display a clear error message.
  • BUG ID 370506 - LiveGroups: The padlock icon on the LiveGroup's sub-graph was not clearly visible.
  • BUG ID 370509 - Multi-View Timelines: The Reconnect Media function did not include the detect
  • Views option and couldn't reconnect multi-view clips.
  • BUG ID 370512 - LiveGroups: Knobs added to published LiveGroups were not saved with the script.
  • BUG ID 370519 - LiveGroups: Making a parent LiveGroup editable enabled the Undo and Redo
  • Buttons on child LiveGroup Properties panel.
  • BUG ID 370536 - Channel Management: Existing Read nodes in the script displayed an error
  • Incorrectly when the Channel Warning Threshold was reached.
  • BUG ID 370626 - ARRIRAW: Setting Proxy Playback to Half Size Proxy did not work as expected.
  • Release Notes for Nuke and Hiero 11.3v1 | Bug Fixes
  • RELEASE NOTES 10
  • BUG ID 370645 - ARRIRAW: Enabling the lens squeeze options in legacy scripts caused them to
  • Disappear.
  • BUG ID 370750 - Multi-View Timelines: Single view tracks below multi-view tracks were not visible
  • When Obey Alpha and See Through Missing Media were enabled.
  • BUG ID 370846 - Sony SDK: The SLog2 colorspace in Nuke Studio did not match Sony Raw Viewer.
  • BUG ID 371220 - ARRIRRAW: The Noise Reduction control was not supported and has been
  • Removed.
  • BUG ID 371327 - Multi-View Timelines: Double-clicking certain clips caused Nuke Studio to crash.
  • BUG ID 371377 - Multi-View Timelines: Localizing stereo clips did not work as expected.
  • BUG ID 371428 - Particles: Multiple particle inputs did not render correctly.
  • BUG ID 371435 - Multi-View Timelines: Certain multi-view .exr files did not show the hero view on
  • Extra tracks.
  • BUG ID 371437 - Multi-View Timelines: Clips with invalid views imported with partially filled
  • Localization bars in the Project panel.
  • BUG ID 371463 - Linux only: The R3D Use CUDA option in the Read Properties panel was disabled.
  • BUG ID 371466/371476 - Particles: The P_Fogbox toolset occasionally didn't emit particles correctly.
  • BUG ID 371529 - ParticleBounce: The Properties panel included three ParticleBounce tabs.
  • BUG ID 371596 - Viewer Selection Modes: Sampling a pixel in the Viewer using Ctrl/Cmd-click
  • Disabled Viewer selections in the Gridwarp node.
  • BUG ID 371598 - Multi-View Timelines: Exporting certain files attempted to access the Preferences
  • In command line mode and displayed an error.
  • BUG ID 371685 - Multi-View Timelines: Switching between mono and stereo setups occasionally
  • Caused the Viewer to render black.
  • BUG ID 371747 - ARRIRAW: Nuke Studio could not create comps from certain .mxf files.
  • BUG ID 371903/371987 - ARRIRAW: Certain combinations of Aspect Ratio, Resolution, and Lens
  • Squeeze displayed an error in the Viewer.
  • BUG ID 371926 - LiveGroups: Pressing 1, 2, 3, and so on to add a Viewer to the Node Graph does not
  • Work as expected when a Viewer exists in a locked LiveGroup.
  • BUG ID 371931 - LiveGroups: Undoing Publish or Make Editable did not return the LiveGroup to its
  • Previous state.
  • BUG ID 371973 - ARRIRAW: The Aspect Ratio control has been moved above the Resolution control
  • To reflect precedence.
  • BUG ID 372286 - LiveGroups: Deleting a custom rgba knob on a LiveGroup created gaps in the
  • Properties panel layout.
  • BUG ID 372290 - LiveGroups: Deleting an override knob did not revert the source knob to its original
  • Value.
  • Release Notes for Nuke and Hiero 11.3v1 | Bug Fixes
  • RELEASE NOTES 11
  • BUG ID 372422 - LiveGroups: Certain override values were not completely deleted when the
  • Associated knob was deleted.
  • BUG ID 372466 - LiveGroups: Publishing a deleted LiveGroup Pythonically returned True.
  • BUG ID 372496 - Channel Management: Reading certain files that broke the Channel Warning
  • Threshold from the command line displayed Warning: Read1: Cannot assign channel number to
  • Channel995 multiple times.
  • BUG ID 372620 - Channel Management: The channel threshold warning did not display after
  • Executing File > Close Comp or Clear.
  • BUG ID 372639 - Channel Management: Reading clips containing more than 1024 channels caused
  • Nuke to crash.
  • BUG ID 372672 - Sony SDK: Setting different resolutions for the same file in multiple Read nodes
  • Caused Nuke to crash during playback.
  • BUG ID 372740 - ARRIRAW: The thumbnails for .ari and .mxf files were not set to their native
  • Resolutions.
  • BUG ID 372749 - LiveGroups: Deleting overrides on exposed knobs and re-publishing did not lock
  • The LiveGroup.
  • BUG ID 372772 - LiveGroups: Nesting a Published LiveGroup inside another LiveGroup and then
  • Undoing the action locked the overrides on the published LiveGroup.
  • BUG ID 372777 - Sony SDK: Invalid relative resolutions were available when using High Quality
  • Debayering.
  • BUG ID 372934 - ARRIRAW: The error message displayed for unsupported resolutions in legacy
  • Scripts was misleading.
  • BUG ID 373011 - ARRIRAW: Certain .ari and .mxf files displayed an error message when read into
  • Nuke.
  • BUG ID 373069 - Sony SDK: Scrubbing the playhead while a Read node was updating caused Nuke to
  • Crash.
  • BUG ID 373242 - ARRIRAW: Legacy controls were not correctly mapped to the new knob name
  • Changes.
  • BUG ID 373296 - ARRIRAW: Loading legacy scripts unexpectedly changed knob values.
  • BUG ID 373375 - Sony SDK: Multiple Read nodes referencing the same file with different control
  • Values was not supported.
  • BUG ID 373386 - DeepRecolor: Soft edges for different objects in auxiliary channels were not
  • Combined correctly when target input alpha was enabled.
  • BUG ID 373581/373708 - Multi-View Timelines: Comps were not created correctly when views were in
  • Separate clips, rather than from multi-view files such as .exr clips.
  • BUG ID 373676 - ARRIRAW: Certain legacy scripts could not be loaded.
  • BUG ID 373682 - Channel Management: The Channel Count text in Nuke's interface was the wrong
  • Color.
  • Release Notes for Nuke and Hiero 11.3v1 | Bug Fixes
  • RELEASE NOTES 12
  • BUG ID 373684 - Channel Management: The Channel Count in Nuke's interface was clamped to
  • 1024.
  • BUG ID 373701 - Multi-View Timelines: Comps were not named correctly when created from
  • Separate clips, rather than from multi-view files such as .exr clips.
  • BUG ID 373720 - LiveGroups: Modifying a LiveGroup and then undoing the action did not revert the
  • LiveGroup to the editable state.
  • BUG ID 373860 - Windows only: The Proxy Playback control was not set correctly with legacy .ari
  • And .mxf files.
  • BUG ID 373868 - ARRIRAW: Loading certain scripts displayed a warning.
  • BUG ID 373897 - ARRIRAW: Right-clicking on a sequence with the Properties panel open for .ari and
  • .mxf shots caused Nuke Studio to crash.
  • BUG ID 373992 - LiveGroup: Applying overrides to exposed knobs did not update the LiveGroup
  • State icon in the Node Graph correctly.
  • BUG ID 374109 - LiveGroups: Undoing a Make Editable action was not registering as an individual
  • Undo in the stack.
  • BUG ID 374259 - Channel Management: The info bar at the bottom-right of the Hiero interface was
  • Not displayed correctly and errors were printed on the command line.
  • BUG ID 374628 - ParticleWind: The steps per frame control in the ParticleSettings node was not
  • Taken into account when applying wind.
  • BUG ID 375178 - R3D: Switching the Image Pipeline from legacy to IPP2 mode did not display all
  • The available options.
  • BUG ID 375204 - Soft Effects: Hidden knobs were exposed incorrectly on certain effects' Properties
  • Panels.
  • BUG ID 375909 - Windows only: Reloading a LiveGroup displayed a LiveGroupInfo: Unknown
  • Command message.
  • BUG ID 375928 - Export: Transcoding audio shots from multi-view sequences did not work as
  • Expected.

New in NukeX 11.2v3 (Aug 17, 2018)

  • Feature Enhancements:
  • BUG ID 352907 - Write: You can now specify which channel is written first in multi- channel .exr files using the first part dropdown in the Write node's Properties panel. All subsequent channels are written in alphanumeric order.
  • Bug Fixes:
  • BUG ID 133297 - Project Settings: The right- click Edit > Edit Expression option on the Color tab was not grayed- out when no LUT curve was selected
  • BUG ID 156605 - Write: Codec options were not consistent between interactive and command- line renders.
  • BUG ID 281553 - Linux only: The Project Settings > Color Management > Default Color Transforms were not populated with LUTs if an OCIO config was specified using and environment variable.
  • BUG ID 331524 - ARRIRAW: Changing the color space control and then clicking the Revert all changes option in the Properties panel displayed an Invalid LUT error in the Viewer.
  • BUG ID 337765 - R3D: Clicking Load Settings from RMD did not populate the Color Space and Gamma Curve controls correctly.
  • BUG ID 351195 - R3D: Loading certain CDL files displayed unhandled exception errors.
  • BUG ID 351446 - OCIO: Default values were saved incorrectly to the preferences.nk file.
  • BUG ID 353294 - OCIO: Nuke Studio and Hiero used the uistate.ini for colorspace defaults even when the OCIO environment variable was set.
  • BUG ID 355262 - ARRIRAW: The thumbnails for Read nodes referencing .mxf files displayed incorrectly.
  • BUG ID 357315 - The right- click context menu in the Nuke 11.2 Properties panel was inconsistent with legacy versions of Nuke.
  • BUG ID 357725/359571 - OCIO: Changing the OpenColorIO settings in the Preferences caused errors in the Project Settings after saving and reloading the project.
  • BUG ID 357825 - OCIO: Setting the OCIO environment variable did not affect the Project Settings .
  • BUG ID 358470 - Timeline: Setting a color for a shot disabled the timeline keyboard shortcuts
  • BUG ID 360365 - The Project Settings panel was resized incorrectly.

New in NukeX 11.2v1 (Jul 18, 2018)

  • New Features:
  • Improved Tab Menu:
  • The Node Graph's tab menu has been improved, including a new search algorithm, allowing you to search for
  • And add nodes more easily using partial names. Commonly used nodes are weighted so that they appear higher
  • Up the list of choices and you can also favorite nodes, pinning them to the top of the list with the star icon.
  • Weights and favorites can be enabled, disabled and cleared in Preferences > Behaviors > Nodes. The J
  • Bookmarked nodes menu also supports the updated search functionality.
  • New Interface for User Knob Creation:
  • Also known as Drag-and-drop knobs (DnD), this update significantly reduces the time spent exposing user
  • Knobs and adding custom knobs to node properties panels within Nuke. As a result, you can create and modify
  • Gizmos and Live Groups more easily, stream-lining collaborative workflows.
  • Instead of right-clicking and selecting Manage User Knobs, simply click the edit button at the top of the
  • Properties panel to get started. You can drag-and-drop knobs between open node panels or add your own
  • Using the knob icons listed at the top of the panel. You can also order, hide, customize and delete knobs within
  • The Properties panel. If you work with floating panels, you can float the User Knob Editor too. Click the edit
  • Button again to finish customization.
  • Nuke Studio Project Panel Improvements:
  • These are a collection of enhancements to the way you can organize, manage and navigate through your
  • Projects in Nuke Studio. This new functionality also applies to the spreadsheet and the timeline.
  • New Sorting - we have introduced a new way to arrange your project bin alphabetical or by custom order. This
  • Is accessible through the new buttons at the top of the Project panel and it has controls for the hierarchy view
  • And on the bin view independently.
  • Improved Searching - we have also improved the search functionality on the Project panel and on the
  • Spreadsheet with new options to search all metadata or not, and to use all or any of the input string.
  • Poster Frame - a new poster frame functionality allows you to set the poster frame for your source clips and
  • Shots. You can set it for single or multiple source clips using absolute or relative frames, which is useful when
  • You have shots with slates or black handles.
  • Color Assignments - you can now assign colors to your source clips, shots, and spreadsheet events. You can
  • Also set colors based on file types.
  • Smart Vector Toolset Improvements:
  • The Smart Vector Toolset in NukeX has several improvements that speed up the generation of the Smart
  • Vectors and extend the use cases where the toolset can be used.
  • GPU Acceleration - the SmartVector and VectorDistort nodes have been rewritten to make the best use of
  • The GPU, dramatically reducing the time it takes to both create the smart motion vectors and use them to warp
  • Images.
  • Mask Input to SmartVector - to help with handling occlusions and image boundaries, you can now supply a
  • Mask to the SmartVector node to specify regions containing unwanted objects or motion.
  • Background Vector Rendering - you can now render SmartVectors in the background using the Export Write
  • Button.
  • File Localization API Extension:
  • Building on the updates to the localization system in Nuke 11.1, the system has been further extended to provide
  • Greater control over customization through new callbacks. We have also added a new environment variable,
  • NUKE_LOCALIZATION_NUMWATCHERS, to improve performance when checking the validity of localized
  • Files, especially when working with scripts with a high number of Read nodes or a high number of frames.
  • Additional python callbacks:
  • The following python callbacks have been added, giving further control over files and Read nodes as they are
  • Added to the queue to be localized and transition between being out of date and localized.
  • Callback functions executed on each file’s localization event:
  • Localization.FileEvent.ADDED
  • Localization.FileEvent.REMOVED
  • Localization.FileEvent.OUT_OF_DATE
  • Localization.FileEvent.CACHE_FULL
  • Localization.FileEvent.DISK_FULL
  • Callback functions executed on each Read nodes localization event:
  • Localization.ReadStatus.NOT_LOCALIZED
  • Localization.ReadStatus.LOCALIZING
  • Localization.ReadStatus.PARTIALLY_LOCALIZED
  • Localization.ReadStatus.LOCALIZED
  • Localization.ReadStatus.OUT_OF_DATE
  • Localization.ReadStatus.LOCALIZATION_DISABLED
  • Auto switch to from localized to network files:
  • A new preference, read source files when localized files are out of date, has been added. When enabled,
  • Nuke checks the localized files against the source files and switches to their source files if the local files become
  • Out of date.
  • Control over the number of simultaneous file checks:
  • A new environment variable NUKE_LOCALIZATION_NUMWATCHERS controls the number of simultaneous
  • File checks, improving performance when working with large scripts over a high capacity network. We have
  • Found that checking the status or force updating a large number of reads or large sequences could create a
  • Bottleneck as Nuke evaluated the files. To improve this we have added an option to increase the number of file
  • Checks that can occur at once to expedite this process with an appropriate network configuration.
  • ARRI SDK Update:
  • ARRIRAW has been updated to version 5.4.3.5, adding the following features:
  • Alexa LF formats and color tables
  • Rec2100/PQ and Rec2100/HLG HDR colorspaces
  • Extended white balance CC values from -16 to +16
  • The full ARRI SDK release notes are publicly available from:
  • Http://www.arri.com/support/downloads/searchable_downloads/
  • R3D SDK Update:
  • R3D SDK has been updated to version 7.0.6, adding the following features:
  • R3D Weapon Monstro 8K VV and Helium 8K S35 Sensors
  • ImageColorDCIP3, ImageColorProPhotoRGB, ImageColorDCIP3D65 colorspaces
  • ImageGammaHybridLogGamma, ImageGamma2_2, ImageGamma2_6 Gamma Curves
  • New Deep Compositing API:
  • Nuke has a new API for Deep Compositing which manages memory more efficiently, resulting in improved
  • performance for some Nodes. Nuke’s native deep compositing nodes have been converted to this new API and
  • in our tests, scripts are processed up to 1.6x faster compared to Nuke 11.1. Performance improvements vary by
  • node and set up; for example, DeepRecolor and DeepTransform show the best gains, while DeepColorCorrect
  • has little improvement.
  • To take advantage of these performance improvements, custom deep nodes need to be converted to the new
  • API. Existing custom nodes will still work in Nuke 11.2, defaulting to the pre-existing API, but will not have any
  • gains in performance.
  • Deep Compositing Improvements:
  • In addition to the new API, Nuke 11.2v1 includes a number bug fixes and improvements to the deep compositing
  • tools including the DeepExpression node having functional parity with Nuke’s standard Expression node.
  • Workflows using metadata have also been added to Nuke’s Deep nodes. Metadata nodes (ModifyMetadata,
  • ViewMetadata, CopyMetadata, and so on) can now be used in a tree with Deep nodes.
  • The DeepMerge node has been updated to allow you to use metadata from either the A input, the B input, or
  • both.

New in NukeX 11.1v3 (Apr 17, 2018)

  • Feature Enhancement:
  • The Nuke online help has been updated to a more responsive top navigation style
  • BUG ID151366-Deep:Deep Write nodes are now auto-labeled in the same way as regular Write nodes.

New in NukeX 10.5v1 (Feb 22, 2017)

  • New Features:
  • Blend Tracks:
  • Nuke Studio's track blending feature now allows you to apply several new blend modes, as well as the existing over
  • blend. Additionally, a new masking feature has been implemented to limit the selected blend function to only those
  • areas covered by the image's alpha channel.
  • You can still designate blend tracks using the right-click Editorial menu, but track headers now feature buttons to
  • turn blending on and off without using the menu.
  • Click the Blend icon to toggle blending on and off.
  • Click and hold the Blend icon to select the blend mode.
  • Click the Mask icon to toggle alpha masking on and off. The Mask feature limits the effect of the blend to just
  • those areas covered by the alpha channel in the blend image.
  • Create Comp:
  • Nuke scripts created from the timeline now maintain concatenation, and are laid out more neatly. The total number
  • of nodes is also reduced as we have removed Constant and Copy nodes, and swapped the FrameRange and
  • AppendClip nodes for TimeClip and Merge nodes.
  • Export:
  • Nuke Studio's Export dialog has been re-arranged for clarity and ease of use. The core functionality is unchanged,
  • but the new layout improves visibility and uses the available space more efficiently.
  • BUG ID 234898 - Export: Loading a project from an earlier version of Nuke Studio displays a warning, suggesting
  • you save a new version of the project before continuing.
  • 153233 - Versioning: Writing a new version of a clip instance now creates a corresponding new folder in the export
  • path, if the folder doesn't already exist.
  • Format and Resolution Improvements:
  • Working with multiple formats and resolutions is now much easier. Now you can easily change the resolution format
  • of your timeline and maintain any transforms or crop soft effects to match the new timeline resolution.
  • We have also changed the options for the interpretation of clip instances on the timeline to be more intuitive, using
  • the timeline Properties panel, which defaults to None, maintaining the timeline resolution. These options also carry
  • over to the Export dialog where you can decide at what resolution you want to render your comps.
  • RayRender:
  • BUG ID 233034 - A new Transmission shader has been added, found under 3D > Shader, which adds support for
  • transparent shadows.
  • Feature Enhancements:
  • BUG ID 152134 - Write: Rendering now creates the necessary directories as specified in the Write node's file
  • control, if they don't exist.
  • BUG ID 153528 - Nuke, Nuke Studio, and Hiero now support Apple ProRes 4444 XQ encoding.
  • BUG ID 177736 - Export: The Export dialog now includes the do not attach prefix option for .exr files.
  • BUG ID 177737 - Export: The Export dialog now includes the interleave option for .exr files.
  • BUG ID 198597 - Timeline: Nuke Studio now includes reformatting controls for clip instances on the timeline in the
  • Properties tab. You can also set the behavior for new clip instances at Project Settings level and Preferences
  • level. The Project Settings determine how clips are formatted in new sequences, and the Preferences determine
  • how clips are formatted in new projects.
  • BUG ID 215257 - Channels: Nuke now sorts the RGBA layer first by default. To process channels using the legacy
  • method, set the NUKE_LEGACY_CHANNEL_SORTING environment variable.
  • BUG ID 239202 - Export: You can now define which Write node in your export structure you want to use as your
  • main output for the timeline using the Content menu > Timeline Write Node dropdown. The Write node
  • selected is connected to the Viewer in the resulting script and is also used to render any comp containers in the
  • sequence.
  • Bug Fixes:
  • BUG ID 140401 - Roto: Enabling downrez caused B-spline points to jump to the lower-left corner of the Viewer
  • when the Roto node was disconnected.
  • BUG ID 144541 - Roto: Drawing/editing a spline in downrez mode, with the Roto node disconnected from the
  • Viewer, produced unexpected results.
  • BUG ID 150101 - Gizmos/Groups: Enabling downrez caused handles to jump to the lower-left corner of the
  • Viewer.
  • BUG ID 150935 - Export: Shot exports did not apply clip instance reformat size changes by default.
  • BUG ID 151049 - Versioning: Selecting Version > Version Up/Down on an empty sequence caused Nuke Studio
  • to crash.
  • BUG ID 151907 - RotoPaint: Drawing or editing a spline in downrez mode when the RotoPaint node was not
  • connected directly to a Viewer, produced unexpected results.
  • BUG ID 152695 - Monitor Output: 8-bit and 10-bit color conversion was sometimes inaccurate, causing a slight
  • color shift.
  • BUG ID 154342 - ModifyMetaData: Adding a ModifyMetaData node to the node tree broke concatenation.
  • BUG ID 155479 - Export: The {projectroot} token added // (forward slashes) to the path when chosen from the
  • file browser.
  • BUG ID 161910 - Windows only: Rendering .mov files from the timeline was very slow in projects with multiple
  • cuts.
  • BUG ID 162519 - mov64: The first frame of files containing the moov atom were not read correctly.
  • BUG ID 162892 - QuickTime: Certain files written with both the mov32 and mov64 writers appeared offset by 20
  • frames when compared.
  • BUG ID 162950 - Playback speed occasionally dropped significantly, jumping to an un-cached region of the
  • timeline.
  • BUG ID 163120 - Export: Tags were added to exported clips when they were added to the render queue, rather
  • than when the export was completed successfully.
  • BUG ID 172943 - Deep: Changing a DeepExpression while the node was attached to a Viewer caused Nuke to
  • crash.
  • BUG ID 176330 - Blend Tracks: Tracks in Viewer buffer B were not blended as expected.
  • BUG ID 185405 - OCIO: Closing a comp using File > Close Comp discarded any OCIO config settings that were
  • applied in the Project Settings.
  • BUG ID 194899 - Export: The DWAA/DWAB compression controls were not displayed correctly.
  • BUG ID 196651 - QuickTime: Reading .mov files containing annotation (not those created by Nuke Studio exports)
  • caused Nuke to crash.
  • BUG ID 201436 - Export: Nuke Studio added an extra / (forward slash) in export paths specified using the Choose
  • button.
  • BUG ID 202140 - Adding a ModifyMetadata node occasionally caused unexpected cropping in the compositing
  • Viewer.
  • BUG ID 207336 - Python: Opening a sequence created through Python in the Script Editor caused Nuke Studio to
  • crash.
  • BUG ID 215394 - Export: Using the {ext} token to create or save an export structure for two exports of different
  • formats in the same folder with same name did not work as expected
  • BUG ID 216023 - Windows only: Using the root of a drive for the {projectroot} variable was ignored for Create
  • Comp operations.
  • BUG ID 217362 - Write: Setting the file type control to mov did not enable the Advanced controls for the default
  • Apple ProRes 4444 codec.
  • BUG ID 228379 - Monitor Output: Video mode limited colors in RGB space, rather than in the expected colorspace.
  • BUG ID 229556 - RayRender: Rebuilding AOVs from beauty passes did not match the rgba output of RayRender.
  • BUG ID 229597 - RayRender: Color information was missing from the direct diffuse AOV.
  • BUG ID 229734 - Monitor Output: 12-bit output was incorrect with some cards.
  • BUG ID 230994 - Text: Adjusting a transform Pythonically caused Nuke to crash.
  • BUG ID 231019 - Timeline: Playback was muted incorrectly if mute was active when playback stopped previously.
  • BUG ID 231443 - ModifyMetaData: Groups containing ModifyMetaData nodes caused Nuke to crash on exit.
  • BUG ID 232553 - Timeline Viewer: Certain rows of pixels were not decoded correctly for some .tiff files.
  • BUG ID 233744 - Monitor Output: The selected output resolution changed when playback started.
  • BUG ID 233797 - Create Comp: Non-blended track items with a Fade In transition applied, faded from the track
  • below, rather than from black.
  • BUG ID 234744 - Blend Tracks: The default track header size was too small to contain the new blend buttons and
  • the track name.
  • BUG ID 235451 - Linux only: The mov32 encoding not available on Linux warning appeared too often when
  • creating .mov export presets.
  • BUG ID 235545 - Create Comp: Track-level soft effects did not include Backdrop nodes in the comp.
  • BUG ID 235583 - Create Comp: Not all nodes associated with a disabled track item were disabled in the resulting
  • comp.
  • BUG ID 235693 - TimeClip: Values of 1 for the frame rangelast or original rangelast controls were reset to 100
  • when a script was reloaded.
  • BUG ID 239079 - Create Comp: Scrubbing the playhead on comps containing retimed blend tracks caused Nuke
  • Studio to crash.
  • BUG ID 239212 - Export: Some Process as Clips export presets were merged together in the Export dialog.
  • BUG ID 239291 - Soft Effects: Loading a legacy project that employed the deprecated Flip, Flop, or Turn options
  • added multiple copies of soft effects, when the project was saved and then loaded in Nuke Studio 10.5.
  • BUG ID 239295 - RayRender: Adding motion blur when using the AmbientOcclusion shader produced wireframe
  • artifacts on the geometry.
  • BUG ID 239341 - Create Comp: Disabled clip instances or tracks occasionally caused Create Comp to fail.
  • BUG ID 239383 - QuickTime: The mov32 encoder did not present the correct timestamp for repeated frames when
  • compared to mov64.
  • BUG ID 239493 - Create Comp Special: Using the Motion retime method in the Export dialog produced incorrect
  • results when compared to earlier versions of Nuke Studio.
  • BUG ID 239964 - Export: The Preview file path under the shot template did not resolve folder paths, only file
  • paths.
  • BUG ID 241290 - Create Comp: Creating a comp with no Write node selected in the Export dialog failed, displaying
  • an unclear error message.
  • BUG ID 241297 - HieroPlayer: Left- or right-clicking on a track header caused HieroPlayer to crash.
  • BUG ID 241492 - Create Comp: Metadata nodes in disconnected soft effect track layouts were connected to nodes
  • in the previous track.
  • BUG ID 241525 - Export: Enabling Collate Shot Name duplicated soft effects on the collated clip instance.
  • BUG ID 241829 - Create Comp: Comps containing retimes were offset by one frame.
  • BUG ID 241932 - Timeline: Attempting to delete empty spaces on the timeline caused Nuke Studio to crash.
  • BUG ID 242111 - Mac OS X only: Adding dissolves to blended tracks occasionally dropped frames during the
  • transition.
  • BUG ID 242281 - Create Comp: Projects containing duplicated tracks or tracks with the same name displayed
  • errors when creating comps.
  • BUG ID 242521 - Create Comp: Adding multiple Transform effects to tracks in a comp did not fill the format
  • correctly, resulting in lower tracks being visible in the comp.
  • BUG ID 242895 - Localization did not work for clips with multiple versions.
  • BUG ID 243335 - Export: Footage was rendered black when rendering with Apple ProRes (HQ, LT, PROXY) and
  • several other codecs.
  • BUG ID 243442 - Create Comp: The Burn-in effect occasionally displayed incorrect values for hiero/clip and
  • input/frame.
  • BUG ID 245022 - Mac OS X only: When building a track, all exported clips were separated rather than being
  • compiled together, and only one track was created.

New in NukeX 10.0v6 (Feb 22, 2017)

  • Released on 31 January 2017
  • Feature Enhancements:
  • BUG ID 233227 - Monitor Output: The AJA driver version has been updated to 12.x on all platforms.
  • Bug Fixes:
  • BUG ID 159942 - Monitor Output: Switching between 8-bit and 10-bit output produced precision and scaling
  • inconsistencies.
  • BUG ID 224244 - Write: The mov64 writer encoded DNxHD metadata incorrectly.
  • BUG ID 224645 - Linux only: Disabling a Monitor Output audio device in the Preferences caused Nuke to crash on
  • playback.
  • BUG ID 228369 - Monitor Output: The color range was incorrect for some inputs with video mode enabled in Nuke
  • Studio's Monitor Output controls.
  • BUG ID 228388 - Monitor Output: The color range in 10-bit output was incorrect.
  • BUG ID 232230 - Linux only: Monitor Output from AJA Kona 3G and Kona 4 cards produced clicking sounds during
  • playback.
  • BUG ID 232743 - Monitor Output: 10-bit output from Blackmagic 4K Extreme cards was incorrect.
  • BUG ID 233213 - Mac OS X only: Kona 3G cards were not recognized under Yosemite (10.10.5) with the latest AJA
  • driver installed.
  • BUG ID 235438 - Track Blending: Slipping a clip instance below a blended track displayed an input color space
  • index out of range warning in the Viewer.
  • BUG ID 240120 - Write: The mov64 writer encoded DNxHD files as Video Range when Full Range was specified
  • in the Write Properties.
  • BUG ID 241833 - Monitor Out: 8-bit and 10-bit output was inconsistent between the compositing and timeline
  • Viewers for non-grayscale images.
  • BUG ID 242147 - Monitor Out: Blackmagic cards produced inconsistent results for 8-bit output.
  • BUG ID 243096 - Licensing: Hiero did not launch with a Nuke Studio license.
  • BUG ID 248113/248294 - Monitor Output: Blackmagic DeckLink Mini cards produced flickering or striped output
  • on playback.
  • BUG ID 248443 - Monitor Output: Blackmagic DeckLink Mini and 4K Extreme cards produced incorrect color
  • output.
  • BUG ID 248497 - Monitor Output: 10-Bit output from Blackmagic 4K Extreme and AJA Kona 3G cards did not
  • appear as expected in the Compositing environment.
  • BUG ID 248755 - Monitor Output: 10-bit output from Blackmagic DeckLink 4K Extreme cards produced gray spots
  • in the Compositing environment.
  • BUG ID 250041 - Monitor Output: Output was incorrect on the monitor for images containing color outside the 0-
  • 1 range in the Timeline environment.

New in NukeX 10.0v5 (Feb 22, 2017)

  • Released on 17 November 2016
  • Windows 7 or Windows 8 (64-bit only) - Other operating systems may work, but have not been fully tested
  • Feature Enhancements:
  • BUG ID 132922 - DeepRead: A new check box, black outside, has been added to prevent streaking in the Viewer
  • where the bounding box touches non-black pixels at edges.
  • Bug Fixes:
  • BUG ID 159600 - OCIO: Colorspace preferences were not saved correctly.
  • BUG ID 176557 - Read: Drop Frame timecode metadata was incorrect for .dpx files, when compared to other
  • applications.
  • BUG ID 195992 - Write: The mov64 Photo - JPEG codec did not match the source file color output.
  • BUG ID 227287 - OCIO: Loading a customer script containing Python callbacks displayed ValueError: A
  • PythonObject is not attached to a node on Read nodes.
  • BUG ID 229438 - RayRender: The near clip value for the AmbientOcclusion shader node was not zero by default.
  • BUG ID 233363 - OCIO: Updating the default LUT settings with Project Settings > Color > color
  • management set to Nuke, only affected Read nodes once. Subsequent changes were ignored.
  • BUG ID 240116 - Timeline: New tracks were occasionally assigned duplicate or inconsistent names

New in NukeX 10.0v4 (Aug 25, 2016)

  • NEW FEATURES:
  • Analytics: In an effort to further improve quality and reliability, from this release onward we'll ask you to allow us to collect usage statistics from the machines on which you license Nuke, NukeX, Nuke Studio, Hiero, and HieroPlayer. This usage information also assists our Support team to resolve issues more quickly.
  • The first time you start an application, and on every major release, a dialog displays asking for permission for us to collect this information. You can enable or disable collection at any time in the Preferences under Behaviors > Startup.
  • BUG FIXES:
  • Preferences: The Panels > Script Editor > clear input window on successful script execution option was missing.
  • Timeline: Exporting offline track items did not create an .nk script.
  • Windows only: Exporting with non-ASCII characters in file paths created incorrectly named
  • BlinkScript: Kernels that don't write to every pixel in the output filled the space with random - Timeline: Exporting audio with handles did not include the requested frames.
  • MatchGrade: Using Match Graded Source with different source and target resolutions caused - ReadGeo: UV projection on to .abc geometry did not match projections on to Nuke primitives or
  • Disconnecting a Constant node in a customer script caused Nuke to crash.
  • OFlow: Adding animated transforms downstream of OFlow nodes caused Nuke to crash.
  • Tracker: Setting pre-track filter to median caused Nuke to crash during tracking.
  • RayRender: Textures connected to the src input of ModelBuilder were not rendered correctly.
  • BlinkScript: A customer kernel that ran correctly on Windows did not run on Mac OS X.
  • Mac OS X only: The Copy Exporter displayed an error when exporting to server locations.
  • OFX: Undoing the deletion of an OFX plug-in, such as F_RigRemoval, caused Nuke to crash.
  • ReadGeo: Entering a file path in the node properties and then undoing the action caused Nuke to
  • Soft Effects: Adding effects to blend track items that overlapped other track items caused Nuke
  • Timeline: The Frame Rate setting on an existing sequence was cleared after opening a new sequence.
  • RayRender: Applying high skew values to geometry occasionally produced artifacts or grainy output.
  • Running a customer script on dual-CPU machines with many cores caused Nuke to crash.
  • Localization: Updates to source files were not rendered in the Viewer.
  • Export: Sequence exports did not use the latest Nuke script for comp containers if the updated script had not been rendered to the timeline.
  • Using all available threads on certain machines caused Nuke to become unresponsive or crash.
  • Linux only: Nuke Studio and Hiero could not read a QuickTime ProRes 4444 (XQ) .mov file that loaded into Nuke correctly.
  • RayRender: Certain scripts rendered pixels incorrectly, when compared to ScanlineRender output.
  • Exporting a sequence containing offline clips and selecting Export Offline did not render black for missing frames.
  • Create Comp: Importing a customer project caused Nuke Studio to crash.
  • RayRender: The camera near and far clipping planes caused scaling issues in a customer scene. - RayRender: Rendering beauty passes for geometry without UVs produced incorrect output.
  • RayRender: The FillMat node did not produce the same results, when compared to
  • RayRender: Adding a TimeOffset node to a scene rendered motion vectors incorrectly for static
  • Export: Certain .nk scripts created by Process as Sequence did not render correctly in terminal
  • Including a Normals node in the node tree produced inconsistent output, when Output didn't match ScanlineRender motion blur with high shutter values.
  • The shutter offset modes did not work as expected when samples was set to 0 or
  • Setting projection mode to orthographic did not render as expected.
  • Scaling geometry with spherical projection produced artifacts or black pixels. Camera scale z controls did not work as expected.
  • Using Nuke's default camera with Project3D rendered geometry pink.
  • Rendering certain scripts containing overlapping geometry caused Nuke to become
  • Cameras set to spherical projection into Project3D nodes differed from
  • RayRender: Motion blur rendered as if one fewer sample was used, when compared to ScanlineRender.
  • Compositing environment: Nuke could not read file names that included hashes (#) when they were unrelated to frame padding.
  • RayRender: Motion vectors generated from RayRender appeared inverted when the moving object was not clamped against the near plane.
  • RayRender: The depth channel was calculated incorrectly.
  • RayRender: Rendering motion vectors that depend on camera motion produced noise in the output.
  • RayRender: Disabling interpolate animation, with motion blur shutter set to 3 and samples set to 5, removed motion vector information from the output.
  • RayRender: Disabling a FillMat node with a light in the scene caused Nuke to crash.
  • RayRender: Using a FillMat node in combination with a Phong node produced inconsistent output, when compared to ScanlineRender

New in NukeX 10.0v2 (Jun 10, 2016)

  • New Features:
  • Windows only: Nuke no longer requires a local installation of QuickTime to work correctly.
  • Bug Fixes :
  • BUG ID 146791 - Windows only: Nuke would not start without QuickTime installed.

New in NukeX 9.0v8 (Feb 18, 2016)

  • New Features:
  • AAF Import and Conform
  • Imported AAFs now support transform, crop, and retime edit decisions implemented in third- party applications, such as Avid Media Composer or Apple Final Cut Pro. The information in the .aaf is interpreted using soft effects, such as Transform and Crop. Non- linear retimes are not currently supported, but constant linear retimes are handled in the same way as in previous versions of Nuke Studio and Hiero.
  • Multi-View QuickTime
  • Nuke, Nuke Studio, and Hiero can now read multi- view .mov files, in a similar way to .exr files, except that they are set to only show the first view by default. To enable all views in a multi- view .mov file: 1. Import the .mov file as normal, File > Import File , or Read it in using the Node Graph. 2. Navigate to Project > Edit Settings > Views , or Edit > Project Settings > Views , and click Set up views for stereo . You'll notice that the .mov in the bin or Node Graph is now marked with to denote multiple views. 3. Navigate to Window > Media or open the Read node's properties and disable First track only. 4. You can now switch between views using the buttons above the timeline or compositing Viewers.
  • Feature Enhancements:
  • Nuke, Nuke Studio, and Hiero's stereo scopes have been improved for usability. Stereo clips now only show a scope for the active view, left and right by default. If there are two stereo clips in the A/B input buffer, two scopes are displayed - one for each clip's active view.
  • NOTE: If a stereo display mode is active in the Timeline Viewer, this behavior can change. For example, activating Side by Side displays four scopes if there are two stereo clips in the A/B input buffer
  • BUG ID 44403/47711 - OCIO: The Use OCIO nodes when exporting in Nuke preference is now enabled by default when an OCIO config file is specified using the Preferences dialog or OCIO environment variable.
  • BUG ID 45155 - Tags added to frames in the Viewer are now displayed above the timeline on the frame slider.
  • BUG ID 48964 - BurnIn: The metadata dropdowns in the BurnIn node's properties now accept custom metadata key pairs added to track items as tags. Adding a tag, with a note, to a track item allows you to access the tag from the BurnIn controls, as follows: hiero/tags/*tagname*/note
  • BUG ID 49496 - Create Comp: The warning dialog displayed when creating comps from multi- view track items now includes a Do not warn again checkbox, allowing you to hide the warning for the rest of the current session.
  • BUG ID 50116 - Roto/RotoPaint: The keyboard shortcut to cycle through a selected tool's modes has been moved to S , providing that the Viewer has mouse- over focus and the Roto or RotoPaint properties are open.
  • BUG ID 50296 - Frame Server: Error handling and reporting when worker processes don't start has been improved.
  • BUG ID 50384 - Timeline: Nuke Studio's timeline error reporting has been improved, including error messages in the timeline Viewer, similar to the Comp Viewer, and soft effects in an error state highlighted in red
  • Bug Fixes:
  • Annotations
  • BUG ID 50479 - Adding annotations to clips retimed at clip- level did not work as expected. Conform
  • BUG ID 50385 - Dissolves in .aaf and .edl sequences did not match the corresponding dissolves in Adobe Premiere and DaVinci Resolve.
  • BUG ID 50568 - Importing Avid .aaf files into Nuke Studio displayed incorrect Src In times.
  • BUG ID 50866 - Importing .xml to a sequence with a different frame rate, when Keep timecodes was enabled, did not resize soft effects correctly.
  • BUG ID 50974 - Importing .aaf files containing dropframe frame rates rounded up incorrectly.
  • BUG ID 51015 - Imported .aaf sequences used the name of the .aaf file, rather than the sequence name from the third- party application. Exporting
  • BUG ID 49411 - Specifying Clip Length in the Handles export controls ignored any Additional Nodes from tags in the resulting Nuke script.
  • BUG ID 50228 - Hiero: Exports did not work as expected if the Default Color Transforms controls in the Project Settings were unset, such as when the OCIO environment variable was disabled.
  • BUG ID 50600 - Exporting still frame track items with a dissolve produced incorrect .nk scripts.
  • BUG ID 51109 - Transcoding with Reformat set to scale in the Export dialog caused the export to fail with a TranscodeExport.startTask error
  • Frame Server
  • BUG ID 42082 - The Frame Server process occasionally interfered with Nuke Studio's responsiveness. Keyboard Shortcuts
  • BUG ID 49995 - In the Properties panel of nodes containing curve selection controls, such as ColorLookup, the Ctrl / Cmd + A keyboard shortcut did not select all entries
  • OCIO
  • BUG ID 47591 - Changing the OCIO config specified did not update the colorspace of existing clips and caused Create Comp to fail.
  • BUG ID 48225 - Display transforms in config files containing a single non- default display did not work as expected.
  • BUG ID 48948 - OCIO config files containing differing view lists per display did not work as expected.
  • BUG ID 49366 - The OCIOLookTransform node's in and out controls were reset when the Viewer was connected.
  • BUG ID 50345 - The OCIO environment variable was incorrectly written into scripts, when set.
  • Performance
  • BUG ID 42660 - Nuke's caching was much faster when running on a few threads (4) compared to many (24) in certain scripts containing Transform nodes.
  • BUG ID 49329 - A customer script ran faster when limited to a single CPU on a dual CPU machine.
  • Preferences
  • BUG ID 49064 - Hiero: The Panels > Node Colors section, for assigning colors to soft effect properties panels, was missing from the Preferences.
  • BUG ID 49458 - It was possible to open the Preferences dialog multiple times
  • Read and Write
  • BUG ID 45966 - Deep: Editing Deep .exr channel names in a Shuffle node caused Nuke to crash.
  • BUG ID 48992 - The Media tab Color Space dropdown was unavailable for .r3d footage.
  • BUG ID 49056 - Rendering certain .exr files from ScanlineRender was faster when using fewer threads compared to many.
  • BUG ID 50714 - Reading incomplete .exr sequences (sequences that contain qube placeholder files) caused Nuke to crash.
  • BUG ID 50969 - Reading certain .exr files took longer than in previous releases.
  • BUG ID 51072 - Exporting a sequence containing comp containers to a .mov file produced path remapping errors.
  • BUG ID 51258 - Nuke behavior when reading files without file extensions had changed since the 9.0v1 release
  • Roto/RotoPaint
  • BUG ID 48808 - Open spline width and feather handles were drawn in screen space and were not affected by the zoom level. Scopes
  • BUG ID 47875 - Disabling the Preferences > Panels > Scopes > Include viewer color transforms control stopped the Viewer B input buffer scope updating as expected.
  • BUG ID 51159 - The mouse- over vertical line marker was offset on stereo scopes.
  • Soft Effects
  • BUG ID 48764 - Soft effects were not transcoded during export when HANDLES was set to Clip Length.
  • BUG ID 49296 - Burn- in: Opening a Nuke Studio comp containing Burn- in effects from the command line printed attribute errors in the Terminal or command prompt.
  • BUG ID 49324 - Burn- in: Modifying the Burn- in effect's properties, when the effect was added using Python, didn't update the Viewer.
  • BUG ID 49669 - Enabling the Preferences dialog Panels > Control Panels > expand/collapse panels checkbox did not work as expected for soft effect properties.
  • BUG ID 50327 - Transform effects were not applied to the track item's handles in Nuke comps.
  • BUG ID 50352 - Burn- in: Timelines containing Burn- in effects caused Nuke Studio to auto- save even when no changes were made to the project.
  • BUG ID 50590 - Burn- in: Expressions were not evaluated when viewing an annotation precomp.
  • BUG ID 50737 - Executing New Track from EDL/XML/EDL on the timeline added soft effects in an invalid state.
  • Spreadsheet
  • BUG ID 50061 - Selecting numerous clips in the spreadsheet view caused the application to become unresponsive for a few seconds
  • Stereo
  • BUG ID 49942 - Dragging a multi- view clip from a bin to the Node Graph added the clip as a single view Read node and did not display the add/replace views dialog.
  • BUG ID 50060 - The auto- creation of views from multi- view clips was inconsistent between the Timeline environment and Compositing environment.
  • BUG ID 50603 - Reading in certain stereo shots, deleting them, and then closing the application without saving caused Nuke to crash on exit.
  • BUG ID 51151 - Saving a script with Project Settings > Views > View selection uses buttons? deselected caused Nuke to crash when the script was re- opened.
  • Text
  • BUG ID 47097 - Picking the font knob in a Group's user knobs caused Nuke to crash on exit.
  • Timeline
  • BUG ID 49213 - Nudging did not work as expected on Fade and Dissolve track items.
  • BUG ID 50044 HieroPlayer: The track item right- click menu Clip > Set Soft Trims option was not available on editable tracks.
  • BUG ID 50053 - Scrubbing in a timeline containing Alexa ProRess 4444XQ track items caused Nuke Studio to crash.
  • BUG ID 50422 - HieroPlayer: The right- click Clip > Replace Clip function did not work as expected.
  • BUG ID 50533 - Executing Build Track > From Export Structure for Audio Export presets caused Nuke Studio to crash.
  • Viewers
  • BUG ID 49217 - Timeline Viewer: Activating the A/B Viewer input buffers with QuickTime track items including audio caused Nuke Studio to crash.
  • BUG ID 50580 - Comp Viewer: Maximizing the Viewer caused the info bar's clip information to stop updating.
  • Windows Only
  • BUG ID 49930 - Importing a file or folder into the Project tab caused the folder tree to collapse.
  • BUG ID 50309 - Forcing Nuke to write .mov files using the mov32 prefix resulted in a temp file with no file extension
  • Miscellaneous
  • BUG ID 5177 - Memory allocation errors occasionally occurred when using an expression to sample images in the Viewer, causing Nuke to crash.
  • BUG ID 24550 - Documentation: Viewer Stereo Modes were missing from the Previewing Stereoscopic Images section in the Nuke documentation.
  • BUG ID 46311 - Loading Nuke Root LUTs using an index didn't work as expected when a custom curve was added to the script.
  • BUG ID 47958 - Path substitutions between Mac OS X and Windows contained an extra / (forward slash), breaking cross- platform file paths.
  • BUG ID 48656 - Versioning up a track item with offset frames did not update to the correct frame range
  • BUG ID 49172 - Flipbook: Creating views in a script with long names (~300 characters) omitted the view name in the Flipbook.
  • BUG ID 49529 - Documentation: The Blink Reference Guide contained some typographic inaccuracies.
  • BUG ID 49753 - Running certain scripts with the - - tg flag on the command line caused Nuke to crash. RELEASE NOTES FOR NUKE AND HIERO 9.0V8 | BUG FIXES RELEASE NOTES 10
  • BUG ID 49804 - Adding expressions to Project Settings > LUT curves occasionally caused Nuke to crash.
  • BUG ID 49994 - Documentation: The Nuke Developers Guide - 2D Architecture section contained some typographic inaccuracies.
  • BUG ID 50165 - HieroPlayer: Bin items in an .hrox project from Nuke Studio or Hiero were unlocked after executing Save as Player Project .
  • BUG ID 50524 - File browser: The file browser took a long time to populate when navigating to directories containing long frame sequences of heavy files.
  • BUG ID 50691 - Documentation: The Blink Reference Guide contained incorrect bilinear syntax.
  • BUG ID 50713 - OFX: Buttons on OFX plug- ins did not work unless the plug- in's Properties panel was open.
  • BUG ID 50808 - Deleting a Group node containing clones, undoing the delete action, and then copy/pasting the Group displayed a blank error message and corrupted the script.
  • BUG ID 51035 - STMap: The Properties panel tooltip for the STMap node was ba

New in NukeX 9.0v6 (May 29, 2015)

  • Feature Enhancements:
  • BUG ID 47761 - The EDL Exporter now allows the {filehead} keyword in the From Clip Name field.
  • BUG ID 47898 - Views: Tooltips now display for view names in split knobs.
  • Bug Fixes:
  • Deep:
  • BUG ID 47616 - DeepExpression was not working with layer names beginning with a capital A or B.
  • Exporting:
  • BUG ID 46841 - When the worker process crashed, Nuke Studio reported the export as finished, with no error.
  • Kronos:
  • BUG ID 47292 - There were black frames when animating Output speed over time.
  • BUG ID 47296 - Corrupt frames were occasionally found in the rendered output.
  • BUG ID 48551 - Kronos resulted in error on specific frames, under certain conditions, when the properties were open.
  • Monitor Output:
  • BUG ID 44900 - AJA MonitorOut: The HDMI was not attaching when NUKE_AJA_CHANNEL was not set to 1.
  • OCIO:
  • BUG ID 48474 - The OCIO Project Settings were reset when running a script from the command line or Terminal.
  • Read and Write:
  • BUG ID 47741 - Selecting File > Save Comp As ignored any characters after the last . (period) in a filename if the .nk extension was not specified.
  • BUG ID 47781 - Non-integer frame rates in .nk clips were read incorrectly by nkReader.
  • BUG ID 48714 - Alembic: Load times were longer than expected for .abc files containing facesets.
  • BUG ID 48890 - Mac OS X only: It was not possible to specify a particular flavor of Nuke (Nuke, NukeX, and so on) in the right-click Open With menu.
  • ScanlineRender:
  • BUG ID 27045 - Overscanning stretched pixels on the left and right side.
  • Soft Effects:
  • BUG ID 47287 - Text: It was impossible to draw a box before typing in the timeline.
  • Timeline:
  • BUG ID 48238 - Timeline View: Scrubbing out of range caused scrolling issues.
  • BUG ID 48541 - Timeline Editing: The Slip Clip overlay images were displayed incorrectly.
  • BUG ID 48542 - Dropping a video clip onto the timeline and then pressing Ctrl+Z to undo caused Nuke Studio to crash in certain projects.
  • Transform:
  • BUG ID 47021 - There were clipping issues with the Reformat node when using the maintain bounding box on 10k or greater source elements.
  • Viewer:
  • BUG ID 47777 - Closing the Comp Viewer tab and referencing it through Python were causing Nuke to crash.
  • BUG ID 48255 - Comp Viewer: The input selectionusing the up and down arrows failed when the current input was NULL and the number of inputs was 1.
  • Miscellaneous:
  • BUG ID 47697 - Unnecessary project files were written to .nuke when quitting Nuke Studio.
  • BUG ID 47788 - Closing a non-modal python panel caused Nuke to crash.
  • BUG ID 48320 - Open Project: The message displayed when opening a project already open mentioned Hiero, rather than the application's name.
  • BUG ID 48444 - Using VectorGenerator and IDistort nodes in combination caused Nuke to crash under some circumstances.
  • BUG ID 48545 - OFX: Changing bounding box downstream from an OFX node, for instance Keylight, caused Nuke to crash in certain circumstances.
  • BUG ID 48689 - Snapshots: Restoring a snapshot caused Nuke Studio to crash.
  • BUG ID 48717 - OFX: Nuke crashed when adding a large number of OFX nodes in some circumstances.

New in NukeX 9.0v5 (Apr 15, 2015)

  • New Features:
  • Nuke Non-commercial:
  • This release includes a new non-commercial version of Nuke that runs outside the regular licensing model. Nuke Non-commercial is free and designed for personal, educational, and other non-commercial use. It is aimed at students, industry professionals, and others interested in Nuke. It includes most of the features of the commercial version of Nuke, offering you a chance to explore and learn the application fully, while using it from the comfort of your own home.
  • You can run Nuke, NukeX, and Nuke Studio in non-commercial mode by clicking the appropriate application icon or by using the --nc command-line argument. For example, to launch Nuke Studio in non-commercial mode on Mac OS X, either:
  • Open Finder, navigate to /Applications/Nuke9.0v5, and then double-click the NukeStudio9.0v5 Noncommercial icon, or
  • Open Terminal and enter: /Applications/Nuke9.0v5/Nuke9.0v5.app/Contents/MacOS/Nuke9.0v5 --nc --studio
  • Nuke Non-commercial is a fully functional version of Nuke, but as it's designed for non-commercial use only, it does differ from the commercial version in some aspects. Here are the main differences:
  • Certain nodes are disabled in Nuke Non-commercial, including BlinkScript, GenerateLUT, Primatte, Ultimatte, and WriteGeo.
  • Rendered output is restricted to 1920x1080 HD and the MPEG4 and H.264 formats are disabled.
  • Command-line renders are restricted to encrypted .nknc scripts.
  • Frame Server slave rendering is disabled.
  • Exporting EDL/XML sequences is disabled.
  • Exporting LUTs from MatchGrade is disabled.
  • Gizmos, clipboard contents, .hrox project files, and .nk scripts are all encrypted.
  • Monitor Output is disabled.
  • Feature Enhancements:
  • BUG ID 27501 - Support for Blackmagic RAW 2.5K CinemaDNG has been added.
  • BUG ID 30272 - Transcode Exporter: A new to scale option has been added to the Reformat dropdown.
  • BUG ID 44508 - Timeline: Undo, Redo, Clone, Copy as Clones, and Declone have been added to the timeline right-click Edit menu.
  • BUG ID 45848 - Viewer/Timeline: Zooming functionality in the Viewer frame slider and timeline has been improved.
  • BUG ID 46605 - Export: Build Track from Export Structure or Tag can now use an existing track if the same name is used and warns if a track item is about to be overwritten.
  • BUG ID 47074 - Soft Effects: Node presets, chosen using the wrench icon in node properties, have been enabled for Soft Effects.
  • BUG ID 47351 - Support has been added for drop frame timecodes in .mov files.
  • BUG ID 47560 - Nuke Assist: The Grade node has been added to Nuke Assist.
  • BUG ID 47598 - Nuke Studio now uses libpng 1.4.8 and plug-ins should be built against this version.
  • BUG ID 47676/47677 - Export: The Compositing environment Write node mov32/mov64 QuickTime controls have been added to the export dialog's Nuke Write Node content processor.
  • BUG ID 47736 - Preferences: Nuke now includes the Performance > Caching > Memory Caching > playback cache size preference, in line with Nuke Studio and NukeX.
  • Bug Fixes:
  • AppendClip:
  • BUG ID 47674 - The tooltips were missing for all controls in the Properties panel.
  • BlinkScript:
  • BUG ID 46944 - Documentation: The cross() function was described incorrectly in the BlinkScript documentation.
  • Create Comp:
  • BUG ID 46869 - Comping files containing unsupported characters in their file names caused Nuke to become unresponsive or crash.
  • BUG ID 47441 - Selecting Effects > Create Comp with Preferences > General > force project autosave after set to 1-3 seconds, caused Nuke Studio to become unresponsive.
  • Curve Editor/Dope Sheet:
  • BUG ID 44765 - Curve Editor: Changing curve interpolation was not always registered as a separate undo action.
  • BUG ID 47415 - Dope Sheet: Interaction with the Dope Sheet became slow when a large number of keyframes were displayed.
  • Exporting:
  • BUG ID 47283 - Selecting Build Track > From Export Tag with the Media tab open caused Nuke Studio to crash.
  • BUG ID 47305 - Selecting Build Track > From Export Tag in a certain project, with Apply Retimes enabled in the Basic Nuke Shot preset, caused Nuke Studio to crash.
  • BUG ID 47354 - Build Track > From Export Tag did not work as expected with multiple transcodes in the same export.
  • BUG ID 47551 - Using the whole Clip Length in an export and then selecting Build Track > From Export Tag added handles to the clip in the wrong place.
  • BUG ID 47814 - OFlow nodes were occasionally added to the script for non-retimed clips.
  • OCIO:
  • BUG ID 40033 - Adding an OCIO CDLTransform that referenced certain .ccc files and clicking select occid caused Nuke to crash.
  • BUG ID 45992 - Setting the Viewer process to the default OCIO LUTs did not display some channels correctly.
  • BUG ID 47082 - Certain OCIO config files caused Nuke to crash.
  • BUG ID 48120 - Documentation: Several OCIO FileTransform and OCIO CDLTransform node controls were omitted from the Reference Guide.
  • Preferences:
  • BUG ID 47474 - Setting Preferences > General > force project autosave after to a low value caused the Viewer to re-cache after the specified interval when a TimeWarp soft effect was used.
  • BUG ID 47477 - Setting Preferences > General > force project autosave after to a low value caused the Viewer info bar to shift the image up or down after the specified interval.
  • BUG ID 47514 - Setting Preferences > Project Defaults > General > time display to frames didn't work as expected.
  • Read and Write:
  • BUG ID 38192/46282 - Alembic: Loading Cameras and Axis nodes from .abc files always loaded animation at 24 fps, regardless of the frame rate set in the file.
  • BUG ID 45739 - Nuke did not render drop frame timecodes to .mov files correctly.
  • BUG ID 47003 - Playback for ProRes files was not as consistent as previous releases.
  • BUG ID 47045 - mov64Reader: Trimming or cutting an .mp4 track item occasionally displayed only black frames and a requested layer not found error.
  • BUG ID 47306 - Transcoding with Apply Retimes enabled in a certain script did not work as expected.
  • BUG ID 47361 - Connecting an un-cached Write node set to render multi-channel .exr output caused Nuke to crash.
  • BUG ID 47568 - Importing a certain Flix-generated .aaf file caused Nuke Studio to crash.
  • BUG ID 47574 - movWriter: Rendering two .mov files concurrently produced an unsupported codec error and occasionally caused Nuke to crash.
  • BUG ID 47594 - Nuke Studio incorrectly treated certain .mov files as having drop frame timecodes.
  • BUG ID 47621/47622 - mov64Writer: Writing additional channels along with RGBA to a QuickTime caused Nuke to crash.
  • BUG ID 47704 - mov64: Attempting to view the Metadata tab while reading certain mov32 exclusive codecs (such as DVCPRO) with the mov64Reader occasionally caused Nuke to crash.
  • Roto/RotoPaint:
  • BUG ID 47145 - RotoPaint: The active RotoPaint node lost focus if another RotoPaint node had ripple edit enabled.
  • BUG ID 47439 - Roto: Undo didn't work when the Compositing Viewer was in fullscreen mode on a second monitor.
  • ScanlineRender:
  • BUG ID 46534 - ScanlineRender: Concatenation between nodes was causing abnormally bright pixels outside textured areas in a customer script.
  • Soft Effects:
  • BUG ID 44471 - The Mirror effect could not be cloned.
  • BUG ID 46402 - Creating a comp containing a CDL effect did not set the working space control correctly if a custom OCIO config was used.
  • BUG ID 46875 - Creating a soft effect with a transition selected created an invalid effect.
  • BUG ID 47004 - Exports containing Text effects displayed Setting knob values from validate is not supported and may cause unexpected behavior errors on completion.
  • Text:
  • BUG ID 47006 - Entering text containing expressions caused Nuke Studio to crash on playback.
  • BUG ID 47422 - Marquee selecting characters with tails, such as j and g, was awkward.
  • BUG ID 47532 - The Text node's initial bounding box wasn't drawn until pen up.
  • BUG ID 47681 - Multiple instances of the Text node in a customer script caused performance issues.
  • Timeline:
  • BUG ID 46533 - At extreme zoom levels, track items occasionally looked like gaps in the timeline.
  • BUG ID 46919 - Viewing or dragging large 5K .psd files to the timeline occasionally caused Nuke Studio to crash.
  • BUG ID 46934 - Selecting Open In > Timeline View on a comp container always opened the first version of the comp, regardless of which version was active.
  • BUG ID 47542 - Navigating around the timeline was sluggish in large projects.
  • BUG ID 47793 - Track items with missing frames were colored inconsistently in the timeline.
  • BUG ID 47810 - Scrubbing past the ends of the timeline caused the frame range to slip in Global mode.
  • Tracking:
  • BUG ID 46945 - CameraTracker: Undoing and then redoing clicking User Tracks > Export Tracker caused Nuke to crash.
  • BUG ID 47726 - Documentation: The CameraTracker update solve and update tracking data processes were not explained correctly.
  • Viewers:
  • BUG ID 46783 - Compositing Viewer: Enabling Stereo Mode > Interlaced stopped the Viewer updating correctly when switching between A/B modes, such as wipe and over.
  • BUG ID 46905 - Compositing Viewer: Modifying shapes or transform handles from different nodes in the Viewer caused the undo history to become unreliable.
  • BUG ID 47446 - Compositing Viewer: The A/B input buffer dropdown menus could become out of sync when Viewers with multiple inputs in the Node Graph were disconnected.
  • BUG ID 47462 - Zooming in and out of the frame slider using the mouse wheel did not work as expected when the clip's frame range was less than 5 frames.
  • BUG ID 47510 - The selected playback rate was not always displayed correctly after being saved in a script.
  • BUG ID 48103 - Tags: Adding a preset tag to clips and track items by drag-and-dropping in the Viewer hotspots did not work as expected.
  • Windows Only
  • BUG ID 47024 - Viewing the output of a cloned ReadGeo node that referenced an Alembic file caused Nuke to crash.
  • BUG ID 47025 - Scrubbing in the frame slider when viewing a script with Dilate in the Node Graph caused Nuke to crash.
  • BUG ID 47456 - Dragging single frame clips from the Timeline environment to the Node Graph set the Read node frame range control before and after dropdowns to black, rather than hold.
  • BUG ID 47485 - Using multiple samples in Kronos or MotionBlur nodes caused Nuke to crash.
  • WriteGeo:
  • BUG ID 35067 - WriteGeo: A certain customer script containing a WriteGeo node caused Nuke to crash.
  • Miscellaneous:
  • BUG ID 14375 - Connecting arrows in the Node Graph disappeared when zoomed out.
  • BUG ID 46495 - File Browser: Pasting certain text into the file path field caused Nuke to crash.
  • BUG ID 46557 - Reconnecting multiple clips or comps from the Versions Bin caused Nuke to crash.
  • BUG ID 47123 - Selecting File > Insert Comp Nodes populated the Edit menu with entries for all nodes inserted in the Node Graph.
  • BUG ID 47447 - Nuke Studio projects were auto-saved when no changes were made.
  • BUG ID 47460 - Discarding changes to a project when closing it, and then saving changes to a comp within the project, caused Nuke Studio to crash.
  • BUG ID 47500 - Stereo: The Compositing Viewer flickered on mouse move when No incomplete stereo and A/B wipe mode were enabled.
  • BUG ID 47671 - Documentation: The Merge node minus function description was incorrect in the Nuke Reference Guide.
  • BUG ID 47672 - Documentation: The Merge node algorithm and merge order were documented incorrectly.
  • BUG ID 47771 - Scopes: Enabling A/B wipe didn't immediately update the B input buffer of the scope.
  • BUG ID 47779 - Navigating to File > Clear or Quit caused Nuke to crash in a customer script.
  • BUG ID 47891 - Documentation: The knob names for the Write node's mov32 and mov64 controls were out of date.
  • BUG ID 48462 - Documentation: The Keyer node's Input and Controls descriptions were missing from the Nuke Online Help and Reference Guide.

New in NukeX 9.0v4 (Feb 3, 2015)

  • New Features:
  • Support for reading the Sony RAW .mxf file format has been added.
  • Feature Enhancements:
  • PlanarTracker: You can now set a reference frame for relative CornerPin2D nodes exported from PlanarTracker on the CornerPin2D Tracking tab. The reference frame populates the from1-4 xy controls on the From tab in the properties.
  • The Appearance controls have been re-instated under Preferences > Panels, allowing you to customize the look of Nuke's interface.
  • Nuke Studio's Compositing and Timeline undo histories are now more robust, with improved segregation.
  • A new Timeline environment preference has been added under Preferences > Panels > Timeline > show frame end marker, which draws an extra line on the timeline to the right of the playhead, indicating the end of the current frame.
  • You can now set Preferences > Performance > Threads/Processes > Frame server processes to run to 0 (zero) so that Nuke only uses workers on external machines.
  • Alembic: A new preference, always load abc files as all-in-one, has been added under Behaviors > File Handling. When enabled, all nodes in an .abc file are automatically imported, with all alembic geometry nodes imported into a single ReadGeo node.
  • Issue Reporter: You can now specify where reports are written to by default using the FN_CRASH_DUMP_PATH environment variable.
  • Alembic: Importing cameras now runs a post-processing Euler filter to look for alternate sets of Euler angles that result in the same orientation, and chooses the set which most closely matches the angles from previous frames.
  • Bug Fixes:
  • Annotations:
  • The full range of tools in the toolbar were not displayed until you clicked on the Selection tool.
  • The paint color wheel disappeared when the cursor was not over it.
  • Changes in opacity were not showing in exports to the Compositing environment.
  • BlinkScript:
  • The kernel source did not accept a space between Image calls and parameters.
  • Loading the Swirlomatic example kernel displayed an error.
  • Scripts containing both STMap and BlinkScript nodes used an excessive amount of memory.
  • Create Comp:
  • Clip-level soft effects set a redundant lifetime range when applied to comps.
  • Rendering Nuke Studio comps on the timeline in projects that had remapping, resulted in the comp container failing to show renders.
  • Curve Editor/Dope Sheet:
  • The time required for frame mapping increased dramatically with branching node trees.
  • Frame Server:
  • Comps could not locate their renders when the --remap cross-platform path substitution argument was used.
  • Comps created with custom OCIO configs and remapping between Windows and slaved Mac OS X or Linux machines did not render correctly.
  • The error message displayed when no workers are connected contained a typographical error.
  • Keyboard Shortcuts:
  • Custom workspaces did not load using the Ctrl/Cmd+N keyboard shortcut.
  • The Node Graph keyboard shortcut to paste into a branch (Ctrl/Cmd+Shift+V) did not work as expected in Nuke Studio.
  • LensDistortion:
  • LensDistortion: Adjusting Radial Distortion 1 with Output
  • Using the fit keyboard shortcuts (F and H) in the Compositing Viewer did not deselect the previously chosen zoom level.
  • Opening a script with a blank file path caused Nuke to become unresponsive.
  • Dragging in and out points or tag indicators in the frame slider displayed an empty tab on the taskbar until the action was completed.
  • A customer script containing an uncached STMap node caused Nuke to crash.
  • Adding expressions in Text node controls caused Nuke to become unresponsive.
  • Adding GPU accelerated nodes to a script in Nuke PLE mode printed Failed to get a license for RIP library on the command line.
  • Previewing files in the file browser caused Nuke to crash.
  • Transcoding audio track items did not work as expected.
  • Compositing Environment: The left-hand node Toolbar panel size was affected by resizing other panels.
  • Enabling the use lifetime control in the Node tab properties with an expression-linked Switch node didn't enable the lifetime range controls.
  • The File menu was not reset to default after closing a project.
  • Closing a scope docked in a floating Timeline Viewer closed the Viewer and timeline as well.
  • Tags: Pressing Return in the tag dialog Name field deleted the tag.
  • Switching between linked panels, such as the Timeline Viewer/timeline and Compositing Viewer/Node Graph, did not work as expected.
  • EditGeo: Moving to a frame outside the rendered frame range caused Nuke to crash.
  • Defocus: Viewing .exr files with PIZ or ZIP (16) compression was extremely slow with a Defocus node in the node tree.
  • MTTF log files were written to .nuke, rather than the location specified by the NUKE_TEMP_DIR environment variable.
  • Documentation: The soft-light Merge math was missing from the Nuke documentation.

New in NukeX 9.0v2 (Dec 12, 2014)

  • Feature Enhancements
  • Create Comp:
  • BUG ID 46677 - Ctrl/Cmd+double-clicking a Nuke comp (in the bin or timeline view) now opens up the comp in a new instance of NukeX.
  • You can also do this by right-clicking the Nuke comp and choosing Open In > New Nuke Session.
  • PlanarTracker:
  • BUG ID 46696 - The warp matrix in PlanarTracker has been improved to be more accurate.
  • BUG ID 46697 - The PlanarTracker search along the lesser (horizontal) dimension has been improved for tracking footage with extreme aspect ratios.
  • Read and Write:
  • BUG ID 44999 - Build Track: A new checkbox, Create Comp Clips, has been added to the Build Track From Export Tag dialog so that you can choose whether you want to import the .nk script or the renders from the .nk script.
  • BUG ID 45366 - Added read support DNxHD QuickTime movies with the 64-bit Mov Reader.
  • BUG ID 46481 - Added support for encoding DNxHD QuickTime movies with the 64-bit Mov Writer.
  • BUG ID 46650 - The Read node now includes the name of the compression type in the .exr metadata.
  • BUG ID 46651 - Added support for encoding .exr files using b44a compression.
  • BUG ID 46764 - 64-bit Mov Writer: Added support for encoding the alpha channel with the Apple ProRes 4444 codec
  • Bug Fixes:
  • Annotations:
  • BUG ID 43904 - Nuke Studio incorrectly allowed you to add annotations to a locked track.
  • Blink Script
  • BUG ID 41421 - Scrolling in the Kernel Source script editor did not work.
  • BUG ID 44621 - The error message, displayed when loading a plug-in that was built for an incompatible Blink version, was not clear.
  • Create Comp:
  • BUG ID 42873 - The Project Root dialog for Create Comp was not using the Nuke default file browser
  • BUG ID 46397 - Switching between two up-to-date, rendered versions of a Nuke comp incorrectly changed the Nuke comp color to yellow.
  • Frame Server:
  • BUG ID 45420 - The path remap argument (--remap) did not work when mapping between Windows and Mac OS X or Linux file systems.
  • BUG ID 46576 - The Frame Server was very slow and dropped frames when rendering multiple Nuke comps.
  • BUG ID 46790 - Using the Frame Server across platforms did not work as expected.
  • Keyboard Shortcuts:
  • BUG ID 44498 - The 'close all properties keyboard' shortcut (Ctrl/Cmd+Shift+A) did not close all panels in the Properties pane.
  • BUG ID 45460 - Changing the channel or layer using the Page Up and Page Down keyboard shortcuts did not reflect the changes in the channel/layer dropdowns.
  • BUG ID 46565 - Pressing Enter on the keyboard numeric keypad, when the Viewer had focus, did not switch focus to the current frame control.
  • Monitor Out:
  • BUG ID 46515 - Changing the Monitor Output to a 4K UHD mode occasionally caused Nuke Studio to crash.
  • BUG ID 46541 - Playing-back using Monitor Output and then setting an out point caused audio to be out of sync.
  • OCIO:
  • BUG ID 44921 - After setting an OCIO config file and restarting Nuke Studio, the ColorTransform menu did not display or apply the default value.
  • BUG ID 46716 - A role was added to OCIO to determine the default LUT, but it was not necessary as there were existing tools in place for that purpose.
  • PlanarTracker:
  • BUG ID 46218 - With several PlanarTracker layers created, selecting one of the tracked shapes in the Viewer did not select the PlanarTracker layer.
  • BUG ID 46532 - With a lifetime set on a PlanarTracker shape, tracking outside of the range caused Nuke Studio to crash.
  • Preferences:
  • BUG ID 40672 - The last viewed sub-menu was not restored when the Preferences were re-opened.
  • BUG ID 44503 - The Panels > Viewer (Sequence) > guides control did not display overlays as expected.
  • BUG ID 44544 - The preference Automatically rescan versions when moving off end of the version list was missing from Nuke Studio's Preferences.
  • BUG ID 46645 - Nuke 9.0 was not loading preferences that were stored in Nuke 8.0.
  • BUG ID 46769 - The Viewer tab in the Preferences dialog was missing the texture size and texture mode labels for the associated dropdown menus.
  • BUG ID 46817 - The default number of threads per reader control was set to 2, which was insufficient for 4K .dpx playback. This default has been increased to 4 for machines that have more than four physical cores.
  • NOTE: If required, this setting can be adjusted for different formats, such as .jpeg and .tiff files.
  • BUG ID 46681 - The background renders preference was set to start background renders on Comp save by default instead of don't auto-start background renders.
  • Read and Write:
  • BUG ID 44617 - The column dividers in the Export Queue dialog were not visible for resizing the columns.
  • BUG ID 44780 - If you moved the Write node into a new folder in the Export dialog, it was not automatically included in the exported Nuke script.
  • BUG ID 46540 - The mov64Reader only read in the first frame timecode.
  • BUG ID 46543 - EDL Import: Importing clips with negative retimes resulted in them having the incorrect source timecodes.
  • BUG ID 46598 - Match Media: Matching media from the a certain project caused Nuke to become unresponsive.
  • BUG ID 46626 - Exporting a preset without a file extension did not produce an error and did not render.
  • BUG ID 46630 - Changing the export preset Render with control from Frame Server to Single RenderProcess and back again, produced errors in the terminal output.
  • BUG ID 46775 - ARRIRAW: Nuke Studio was unable to read certain .ari files at a specific resolution.
  • BUG ID 46715 - The mov64Reader was not reading in metadata correctly in all instances.
  • Script Editor:
  • BUG ID 40940 - The echo commands to output window preference was not working as expected.
  • BUG ID 46121 - The Python commands for adding favorite directories in the file browser did not work.
  • Soft Effects:
  • BUG ID 44965 - Text: In a Text soft effect's properties, the group context menu – accessed by right-clicking on a group in the Groups tab – was missing several options.
  • BUG ID 46408 - Text: After adding a Text soft effect, clicking in the Viewer, and then changing frames, the cursor was placed in the incorrect position.
  • BUG ID 46416 - Timewarp: The result of Timewarp was sometimes incorrect when applied to a clip that had been retimed and then trimmed.
  • BUG ID 46435 - Grade: If the gamma value of the Grade soft effect was set to zero, the timeline Viewer showed incorrect results.
  • BUG ID 46719 - Text: Copying and pasting a Text soft effect occasionally caused incorrect formatting of the characters.
  • BUG ID 46749 - Timewarp: Deleting a track item and a TimeWarp soft effect simultaneously, occasionally caused Nuke Studio to crash.
  • BUG ID 46865 - Pasting a soft effect onto two track items with a dissolve between them incorrectly treated them as one track item, which caused an error in the soft effect.
  • Spreadsheet:
  • BUG ID 44223 - Opening a project in the Spreadsheet using the right-click menu did not automatically link it to the timeline.
  • Timeline:
  • BUG ID 44140 - Dragging a clip onto the timeline to create a sequence, and then undoing it, incorrectly cleared the associated linked panels.
  • BUG ID 45672 - Scopes: The Include viewer color transforms preference was not working as expected.
  • BUG ID 45695 - Sequences: The timeline playhead remained in its previous position when you created a new sequence.
  • BUG ID 46445 - Trimming a 4GB animation clip (mov64) caused Nuke Studio to crash.
  • BUG ID 46475 - Time Display: Opening a clip in Timeline View, changing the Time Display to Frames, and setting a new current frame did not work as expected.
  • BUG ID 46524 - Retiming: After retiming and then trimming, the timeline Viewer occasionally showed an incorrect first frame.
  • Undo:
  • BUG ID 46233 - PlanarTracker: Completing a track removed any previous actions from the undo stack.
  • BUG ID 46551 - Roto: Undoing numerous actions including creating a shape using a Roto node, connecting the Roto node to a Viewer, and moving the Roto node around in the Node Graph, caused Nuke to crash.
  • BUG ID 46632 - Pressing Return on the keyboard to perform an action was not recorded in the undo stack.
  • BUG ID 46640 - RotoPaint: Removing a paint stroke created in RotoPaint, using the Delete or Backspace keys, was not recorded in the undo stack.
  • Viewer:
  • BUG ID 46037 - Viewer Tools: Setting the Viewer playback mode to Bounce did not toggle both play buttons to stop buttons.
  • BUG ID 46317 - Compositing Viewer: It was difficult to exit the color-picking mode when using the 'display color information' tool above the Viewer.
  • ZDefocus
  • BUG ID 46324 - With the math control in the ZDefocus properties set to depth, objects that were infinitely far away were incorrectly treated as infinitely close.
  • BUG ID 46555 - When animating the focal plane value, there was noticeable aliasing/jumping between the output images of a ZDefocus node set to use its internal disc filter pattern, and a ZDefocus node set to use an external disc image.
  • Miscellaneous:
  • BUG ID 6734 - Panel Text Fields: You could not use the middle-mouse button to scroll in panel text fields.
  • BUG ID 38880 - Colorspace Node: The Colorspace node now supports Rec.2020 primaries.
  • BUG ID 42641 - Shuffle Node: Inserting a Shuffle node after a Denoise node caused rendering to be slow.
  • BUG ID 43839 - Nuke Studio UI: With the menu bar in timeline mode, clicking in the compositing toolbar did not
  • switch the menu bar to compositing mode.
  • BUG ID 46455 - Launching: Launching Nuke from the command line using a subset of a flag caused it to crash.
  • BUG ID 46656 - Performance: The Copy node was slowing down performance considerably.
  • BUG ID 46765 - Nuke 9.0 only: Custom panels were not restored correctly.
  • BUG ID 46867 - Dissolve: Inserting a dissolve

New in NukeX 9.0v1 (Nov 19, 2014)

  • Performance Updates:
  • "Just make it go faster". The most common request since we took over Nuke's development.
  • A lot of engineering has been dedicated to making performance boosts across the board. We have significantly increased overall performance in Nuke 9 compared to Nuke 8. For example, improved exrReader and Deep EXR, scene building and sampling in ScanlineRender, and mip-map filters have been added to ScanlineRender.
  • Nuke now includes R3D GPU debayering if you have CUDA 6.0, or higher, which can significantly reduce decode times for R3D clips read into the Node Graph. You can enable GPU debayering in the Read node's properties, under r3d options, by selecting use cuda if available.
  • BUG ID 45116 - Mac OS X only: A new global preference (Preferences > Hardware > enable Multi-GPU support) has been added for multi-GPU processing on Late-2013 Mac Pros running 10.9.3 'Mavericks', or later.
  • Kronos, VectorGenerator, and MotionBlur:
  • The Foundry's motion estimation algorithm has been improved, based on Ocula technology, resulting in improvements in vector generation, retiming, and motion blur:
  • Improved retime quality - less artefacts and smoother warp.
  • Improved image reconstruction, giving sharper images and less "pulsing" between sharp and blurry results as you move between the original frames.
  • A new Method dropdown allowing you to choose the interpolation method from Frame, Blend, and Motion.
  • Additional work includes:
  • New Resampling methods, including Lanczos4 and Lanczos6 for scaling.
  • New control over retime curves in the input time range, as well as improved range integration, combining to give you concise, intuitive control of your speed ramps.
  • Considerable effort has gone into making sure that renders processed on the GPU and CPU are 'same-same', meaning the output appears identical, and wherever possible, is identical bit-wise.
  • A new Channels dropdown has been added to the node properties, allowing you to retime on a sub-set of channels.
  • OFlow:
  • Nuke's OFlow node has benefitted from some of the improvement work done on Kronos and VectorGenerator:
  • New Resampling methods, including Lanczos4 and 6 for scaling.
  • New control over retime curves in the input time range, as well as improved range integration, combining to give you concise, intuitive control of your speed ramps.
  • Considerable effort has gone into making sure that renders processed on the GPU and CPU are 'same-same', meaning the output appears identical, and wherever possible, is identical bit-wise.
  • A new Channels dropdown has been added to the node properties, allowing you to retime on a sub-set of channels
  • Denoise:
  • The Denoise node is now available to use in Nuke, rather than NukeX only.
  • PlanarTracker:
  • PlanarTracker has been integrated into the Roto and RotoPaint nodes on a new Tracking tab, incorporating all the features of Roto and PlanarTracker. Additional work includes:
  • A pattern-matching algorithm.
  • A region tracking algorithm which works with featureless areas of footage.
  • A new luminance shift option for shots where luminance alters within the tracking region.
  • A CornerPin creation dropdown has been added to the Roto/RotoPaint Tracking tab in the properties panel.
  • New Image Format Support and QuickTime Improvements:
  • Nuke now includes a new mov64 reader and writer, in addition to the mov32 reader and writer from previous releases. You can choose which decoder/encoder to use in Nuke's Read and Write nodes properties:
  • mov32 - uses the full range of QuickTime codecs using the official QuickTime 32-bit SDK, but can be slow to process due to extra complexity during decode/encode.
  • mov64 - uses its own packing and unpacking and streams decode/encode for extra processing speed, but only supports a sub-set of offical QuickTime codecs.
  • Nuke is now an Apple Authorized ProRes third-party product and can read and write Apple ProRes 4444 and Apple ProRes 422 on Mac OS X, Linux, and Windows using the mov64 reader at SD, HD, 2K, and UHD resolutions. Apple
  • ProRes 422 includes the HQ, LT, and Proxy formats.
  • An mxfReader has been added for the following codecs:
  • Avid DNxHD (all 1080p and 720p formats, 4:4:4:4 and 4:2:2 )
  • Uncompressed (4:2:2 YCbCr and RGB).
  • AVCI and DV (AVCI 'unconstrained' variety are not currently supported).
  • ARRIRAW:
  • The ARRI SDK has been updated to version 4.5, which adds several .ari specific controls including lens squeeze and aspect ratio.
  • OCIO:
  • The OpenColorIO library version has been updated to 1.0.9.
  • Native Flipbook Tool:
  • Nuke now features a native Flipbook panel. Clicking the Flipbook this viewer button under the Compositing
  • Viewer now uses an internal real time flipbook Viewer by default.
  • ScanlineRender Mip-map Texture Filters:
  • ScanlineRender now includes several new mip-map filter options providing performance improvement when sampling from large textures. The new filters are listed below from fastest to most accurate:
  • Nearest
  • Bilinear
  • Trilinear
  • Anisotropic
  • Performance Timers:
  • Nuke's performance timers have been updated to give more accurate and detailed timing information on all platforms. When performance timing is enabled, timing information is displayed in the Node Graph, and the nodes
  • themselves are colored according to the proportion of the total processing time that was spent in each one, from green (fast nodes) through to red (slow nodes).
  • In addition, new python calls have been added to provide python access to timing information for individual nodes.
  • Alternatively, Nuke can now be run from the command line with the -Pf argument to obtain the full performance profile for a render in XML format. Performance profiling can help you to debug slow scripts and find out where the bottlenecks lie; this new feature was also used internally during the development of Nuke to help us target our performance work most effectively.
  • Node Improvements:
  • Backdrop nodes now have a Z Order control, allowing you to set the layering of Backdrops within other Backdrops. The Backdrop with the highest Z Order is placed at the front.
  • All Nuke nodes with a Node tab in their properties now include lifetime controls allowing you selectively enable and disable nodes according to frame range when use lifetime is enabled.
  • Miscellaneous:
  • The Text node now includes a Shadows tab, allowing you to add drop shadow to text in the Viewer, either as a soft effect or regular node in the Node Graph. Drop shadows incude color, softness (blur), and shrink/expand (dilate) controls.
  • The Text node's general performance has been improved, including enhanced caching.
  • The Merge node now allows you to merge metadata as well as image data from selected or all inputs using the metadata from dropdown.
  • Nuke's Read node now includes a Metadata tab showing all metadata associated with the file(s) read in.
  • BUG ID 43858 - Preferences: The Preferences dialog has been edited for clarity and accuracy.

New in NukeX 8.0v6 (Sep 16, 2014)

  • Feature Enhancements:
  • BUG ID 42803 - The R3D SDK has been updated to version 5.0. This update adds RedDragon support and various .r3d specific controls, including the DRAGONcolor colorspace and RedGamma4 gamma space.
  • Bug Fixes:
  • BUG ID 35627 - Rendering long sequences displayed a Too many open files error.
  • BUG ID 41104 - Text: It was not possible to input additional text or highlight text when TCL expressions were included in the message field.
  • BUG ID 41471 - Windows only: Viewing an .exr through a LensDistortion node was slow to render in the Viewer.
  • BUG ID 41966 - PlanarTracker: Layers in the shapes list were deselected when changing Roto tool.
  • BUG ID 42769 - BlinkScript: Some kernels that ran correctly on the CPU did not compile on the GPU.
  • BUG ID 43088 - Licensing: Nuke did not release floating licenses unless the server was stopped and re-started.
  • BUG ID 43535 - Mac OS X only: A customer script caused Nuke to crash when viewing an IDistort node downstream of a BlinkScript node.
  • BUG ID 43536 - BlinkScript: It was possible to output images with fewer than the full four channels required for some kernels.
  • BUG ID 43577 - Larger scripts caused slow-down in the Node Graph.
  • BUG ID 43595 - Mac OS X only: When crash reporting was enabled, running multiple different versions of Nuke reported all crashes against the first build opened.
  • BUG ID 43759 - Opening .psd files containing an alpha channel swapped parts of the image around in the Viewer.
  • BUG ID 43859 - R3D: The Read node's standard colorspace control was set incorrectly to linear when the gamma space control was set to REDgamma4.
  • BUG ID 43881 - Opening a certain customer script caused Nuke to crash.
  • BUG ID 44137 - RotoPaint: Painting strokes with a large Node Graph downstream of the RotoPaint node caused Nuke to become unresponsive.
  • BUG ID 44453 - Text: Using [timecode] in the message string for a sequence with no timecode caused Nuke to become unresponsive.

New in NukeX 8.0v5 (Sep 16, 2014)

  • New Features:
  • Roto Open Splines:
  • Roto and RotoPaint now have a new Open Spline tool in the shape toolset. The Open Spline tool lets you draw curves in a similar way to other shapes, except that they don't need to form a closed shape. Press Return or select a different tool to complete the spline without closing it, or close the spline by clicking on the first point created.
  • After creation, you can edit points on the splines using the standard smooth and transform handles, but they also have individual thickness and feather handles
  • Feature Enhancements:
  • BUG ID 20692 - Nuke's Read nodes now includes an edge pixels dropdown to determine how to handle the edges of .exr files. The default, plate detect, mimics Nuke's old behavior for backward compatibility.
  • BUG ID 41460 - The Camera node tooltip has been improved to include information on the various controls and their units of measure.
  • Bug Fixes:
  • BUG ID 29548 - CameraTracker: On the Properties User Tracks tab, clicking Import Tracker caused Nuke to crash.
  • BUG ID 39693 - Roto/RotoPaint: Floating the Properties panel and then pressing Cancel to close the panel, and revert any changes since opening, caused unpredictable results and was not undo-able.
  • BUG ID 41710 - Tracker/CameraTracker: The animation menu button, to the right of the tracks table in the Properties panel, was always disabled when a track was selected.
  • BUG ID 41833 - Licensing: Selecting Install License > Use Server forced you to specify a port number.
  • BUG ID 41956 - CameraTracker: The Viewer toolbar Add User Track button did not remain enabled when clicked.
  • BUG ID 41980 - MatchGrade: Closing and re-opening the Properties panel disabled the Create OCIOFile Transform button.
  • BUG ID 42013 - Documentation: Appendix A in the Nuke User Guide did not include hotkeys for adding nodes to the Node Graph (R, W, C, and so on).
  • BUG ID 42118 - CameraTracker: Tracking clips containing no detectable features caused Nuke to crash.
  • BUG ID 42119 - CameraTracker: Tracking in Nuke's terminal mode always defaulted to Sequence tracking.
  • BUG ID 42165 - Furnace Plug-ins: Using certain Furnace nodes in conjunction with Time nodes, such as AppendClip,
  • FrameHold, Retime and so on, caused Nuke to crash.
  • BUG ID 42327 - Python: Running two Python scripts in quick succession caused Nuke to crash.
  • BUG ID 42566 - Alembic: Vertical film offset in cameras imported from Maya was not read/written correctly.
  • BUG ID 42608 - CornerPin: Setting animation on to controls and then clicking Copy 'from' caused Nuke to crash.
  • BUG ID 42634 - Deep: Reading in .exr files cropped the data window to the image format.
  • BUG ID 42650 - Certain scripts containing disabled Mirror nodes caused Nuke to crash when Primatte or Roto node's Properties panels were opened in the same script.
  • BUG ID 42652 - Certain scripts containing Reformat and ScanlineRender

New in NukeX 8.0v4 (Sep 16, 2014)

  • New Features:
  • BUG ID 39305 - Color Picker: A new preference has been added to the Preferences > Control Panel tab to determine the behavior of the color picker.
  • BUG ID 40522 - CameraTracker: A new Reset Scene Transform button has been added to the properties Scene tab. Additionally, a scale control is displayed, along with the translate and rotate controls, when scale is adjusted along a single axis.
  • BUG ID 40917 - Roto/RotoPaint: A new Motion Blur tab has been added to the properties panel of the Roto and RotoPaint nodes. You can now apply motion blur to individual shapes in the shape list or to the all shapes in the current node using the global controls:
  • Shape Blur - shape motion blur determines the exposure for each moving shape and blends the resulting blurred shapes. This may be more efficient than the global motion blur since each shape will only be blended once.
  • Feature Enhancements:
  • BUG ID 38456 - MatchGrade: Two new controls have been added to the MatchGrade properties to assist you when the Source and Target clips are different formats:
  • Align Target to Source - click to add a Reformat node and a Transform node upstream of the MatchGrade node to align the clips.
  • Crop Target - enable this control if the Target contains a region that isn't present in the Source, such as a black border.
  • BUG ID 39605 - CameraTracker: You can now nudge User Tracks using the standard Nuke nudge keys (numeric pad arrow keys).
  • BUG ID 40335 - The online help for nodes in Nuke has been extended to include Ocula nodes.
  • BUG ID 40520 - CameraTracker: The solve failure error message has been improved and now includes troubleshooting tips.
  • BUG ID 41130 - Licensing: A new environment
  • BUG ID 41524 - MatchGrade: The Target input name is now suffixed with Graded Source when the matching Task is set to Match Graded Source.
  • BUG ID 41525 - MatchGrade: A new control, Apply Grade to Masked Region, has been added to select whether to apply the computed grade to the whole source image or just the masked region when a mask is used to generate
  • the grade.
  • Bug Fixes:
  • BUG ID 13093 - CameraTracker: Pressing Delete did not delete tracks in the Viewer.
  • BUG ID 24345 - Mac OS X only: Reading a sequence into Nuke when sequences was disabled in the Read File(s) browser, displayed a too many open files warning.
  • BUG ID 31030 - Alembic: Frame ranges were not recalculated when the frame rate was changed.
  • BUG ID 32827 - Tracker: Clicking the Stop button during tracking occasionally created a duplicate keyframe.
  • BUG ID 34244 - RotoPaint: Using the Eraser tool on alpha-only output offset the Viewer output compared to actual frame number.
  • BUG ID 36447 - Deep EXR: The Viewer proxy and downrez modes don't work on .exrs containing Deep data.
  • BUG ID 37062 - Certain scripts caused Nuke to crash when opening the Roto properties panel.
  • BUG ID 38738 - CameraTracker: The Viewer right-click menu did not show options if they were not applicable to the current selection.
  • BUG ID 38770 - Roto/RotoPaint: Animating shapes using the extra matrix control in the properties panel occasionally produced incorrect motion blur.
  • BUG ID 39190 - CameraTracker: The thumbnail of a keyframe currently in the Viewer was not highlighted in the thumbnail gallery.
  • BUG ID 39331 - CameraTracker: UserTrack keyframes only appeared on the Viewer timeline if there was a keyframe in the x column of the track table..
  • BUG ID 39432 - CameraTracker: Holding Ctrl/Cmd+Alt to add a new userTrack did not deactivate when released after modifying a toolbar item.
  • BUG ID 39479 - Pixel Analyzer: Switching mode to full frame disabled color picking for all color controls in Nuke.
  • BUG ID 39494 - CameraTracker: When running a standard Nuke license, clicking Track on a solved scene displayed the license prompt twice.
  • BUG ID 39495 - CameraTracker: When running a standard Nuke license, clicking Update Track or Update Solve displayed the Frame range dialog before the license prompt.
  • BUG ID 39498 - CameraTracker: When running a standard Nuke license, clicking Clear Solve displayed a license prompt.
  • BUG ID 39501 - CameraTracker: Increasing the AutoTrack threshold controls did not allow rejected tracks to be included.
  • BUG ID 39503 - CameraTracker: Selecting red tracks in the Viewer resulted in an orange highlight color.
  • BUG ID 39507 - CameraTracker: The enabled/disabled state of tracks in the UserTracks table was inconsistent.
  • BUG ID 39509 - CameraTracker: On the AutoTracks tab, clicking Delete Rejected did not remove all rejected tracks.
  • BUG ID 39511 - CameraTracker: It was not possible to solve lens distortion on single frame.
  • BUG ID 39604 - CameraTracker: The zoom window didn't always update correctly when moving between frames.
  • BUG ID 39606 - CameraTracker: After placing User Tracks, clicking Autotrack did not track on the first frame of stereo footage.
  • BUG ID 39663 - CameraTracker: Solving certain scenes including survey points generated an upside down, 180-degree rotated camera.
  • BUG ID 39677 - CameraTracker: User Tracks still appear when their thumbnails are hidden during tracking.
  • BUG ID 39700 - CameraTracker: Copying and pasting a CameraTracker node with solved survey points produces errors in the reprojected points.
  • BUG ID 39705 - CameraTracker: User Track zoom windows didn't work as expected when using a maximized floating Viewer on a second monitor.
  • BUG ID 39720 - CameraTracker: Clicking Update Track deleted existing tracking data in stills sequences.
  • BUG ID 39770 - Adding a FrameRange node to the Node Graph with no input changed the format when it was connected to a Viewer.
  • BUG ID 39810 - Certain controls did not round correctly to 8 decimal places when casting from a float value.
  • BUG ID 39824 - CameraTracker: Scrubbing or clicking on the timeline to go to another frame occasionally caused unexpected keyframe preview and panel behavior.
  • BUG ID 39913 - CameraTracker: Setting a Film Back Preset and then saving and reopening the script occasionally produced Bad value for filmBackSizePresets errors.
  • BUG ID 40144 - CameraTracker: Solving the cameras for a stereo sequence with Camera Motion set to Rotation Only caused Nuke to crash.
  • BUG ID 40147 - CameraTracker: Unconnected sets of still frame thumbnails were not highlighted in the Viewer.
  • BUG ID 40164 - GPU Acceleration: In the Nuke personal learning edition (PLE), attaching a GPU accelerated node, such as Kronos or Denoise, to the Viewer caused Nuke to crash.BUG ID 40203 - Nuke 8.0 was taking longer to run Python commands than Nuke 7.0.
  • BUG ID 40228 - Viewer/Pixel Analyzer: Ctrl/Cmd+clicking to sample a single pixel only worked if you dragged the mouse slightly.
  • BUG ID 40230 - Licensing dialog: Dragging and dropping a .lic file to the Copy/Paste license file here field occasionally didn't install the license.
  • BUG ID 40340 - Allocated memory was not released back into the OS memory pool after clearing the buffers.
  • BUG ID 40356 - DeepRead could not view deep data channels for some .exr files.
  • BUG ID 40510 - CameraTracker: It was not possible to solve single frames from survey points with rotation only.
  • BUG ID 40512 - CameraTracker: Placing User Tracks before setting reference frames in stills sequences ignored the frames containing the User Tracks during tracking.
  • BUG ID 40514 - CameraTracker: Solving known survey points using rotation only failed to match any points.
  • BUG ID 40516 - CameraTracker: Clicking Solve added keyframes to all frames, even when the solve failed.
  • BUG ID 40521 - CameraTracker: Clicking Update Track failed to solve new tracks in certain stills sequences.
  • BUG ID 40523 - CameraTracker: Solving a single frame with Camera Motion set to Rotation Only failed and displayed a Failed to calculate all frames for the shot warning.
  • BUG ID 40592 - CameraTracker: User Tracks did not update when Undistort Input was enabled.
  • BUG ID 40624 - Reading in multi-part .exr files with different bounding boxes per part and connecting the Read node to the Viewer caused Nuke to crash.
  • BUG ID 40630 - Mac OS X only: Copying and pasting valid license text into the Licensing dialog Copy/Paste license file here field did not work as expected.
  • BUG ID 40648 - Licensing: Clicking View Your Account did not link to the correct page on The Foundry website.
  • BUG ID 40665 - CameraTracker: The Film Back Preset values for Sony EX1 were incorrect.
  • BUG ID 40686 - Licensing: The trial license dialog prompted for a username rather than email address.
  • BUG ID 40696 - GridWarp: Nudging points using the numeric pad arrow keys caused Nuke to crash.
  • BUG ID 40778 - Executing a render from a floating Write node properties panel caused Nuke to crash after rendering, if the panel was closed during rendering.
  • BUG ID 40817 - Licensing: The Use Server field did not behave consistently with other fields in the Licensing dialog.
  • BUG ID 40893 - Roto: Nuke 6.3 legacy Roto shapes wrote attributes multiple times.
  • BUG ID 40990 - Executing a customer script containing AColor_Knob caused Nuke to crash.
  • BUG ID 41012 - The Help > Release Notes link pointed to the wrong page on The Foundry website.
  • BUG ID 41021 - Loading .exr files from Houdini with numeric channel names caused Nuke to crash.
  • BUG ID 41053 - VectorGenerator: Requesting output for a single channel, other than forward.u, produced incorrect results.
  • BUG ID 41202 - BlinkScript: The Swirlomatic example in the documentation caused Nuke to crash.
  • BUG ID 41467 - Windows only: SSL was not working in QT webview.
  • BUG ID 41471 - Windows only: Viewing an .exr through a LensDistortion node was slow to render in the Viewer.

New in NukeX 8.0v3 (Mar 17, 2014)

  • New Features:
  • A new licensing dialog is being rolled out across The Foundry products. The new dialog only applies to installing new licenses - if you already have a permanent license, there is no noticeable change.
  • The new license installation process is dependent on what type of license you requested. Launching Nuke without a license displays the Licensing dialog. Click Install License to display the installation options:
  • License file - if you requested a license file, typically foundry.lic, this option allows you to browse to the file location and install it automatically.
  • Activation Key or license text - if you requested an Activation Key or license by email, this option allows you to paste the key or license text into the Licensing dialog, which then installs the license in the correct directory.
  • A floating license - if you requested a floating license to supply licenses to multiple client machines, this option allows you enter the server address that supplies the client licenses.
  • Feature Enhancements:
  • There are no feature enhancements in this release.
  • Bug Fixes:
  • Windows only: Nuke 8.0v2 broke NDK compatibility with 8.0 by changing the access specifier of getPlaneFromChannel(Channel chan) from public to protected.
  • This change has been reverted to restore compatibility with Nuke 8.0v1.
  • Alembic: The ReadGeo use geometry color control did not default to disabled.
  • NDK Documentation: There were two pages missing from the bundled documentation regarding Sample Source Code.
  • Online Help: The Preferences > Control Panels > documentation source dropdown defaulted to local, rather than foundry.

New in NukeX 8.0v2 (Feb 5, 2014)

  • Feature Enhancements
  • Read: The reset control in the ARRIRAW reader has been re-labelled load settings from metadata.
  • EXR 2.0: Nuke's Write node now includes a Truncate channel names control for .exr files.
  • When enabled, layer names are truncated to 32 characters for backward compatibility with EXR 1.0 readers.
  • CameraTracker: The warning message regarding non-connected frames in Stills tracking mode has been improved.
  • ModelBuilder now supports the standard nudge keys (the arrow keys on the numeric keypad) in the UV preview window.
  • CameraTracker: A new export option, Camera set, has been added to the Create dropdown.
  • This option creates a camera for each tracked frame, but without the associated card created when using the Card option.
  • BlinkScript: You can now change how text in the Kernel Source appears using the controls in the Preferences > Script Editor tab.
  • After saving your preferences, close and then re-open the BlinkScript properties panel to apply the changes.
  • CameraTracker: The Principal View control now appears on the properties panel cameraTracker tab as well as the Settings tab in stereo scripts.
  • Additionally, Interaxial Distance has moved to the properties panel Settings tab.
  • Alembic: ReadGeo now has a use geometry colors control. When enabled, geometry color attributes are read from .abc files and applied to the Nuke geometry.
  • Bug Fixes
  • QuickTime: Alpha was automatically added on Mac and Windows when it shouldn't be.
  • Extended metadata from ARRIRAW files was not shown in the ViewMetaData node.
  • ModelBuilder: Using the Face Selection tool in the 3D Viewer disabled the Scale handles (Ctrl/Cmd+Shift).
  • ARRIRAW default color space should be set to Log C - Wide Gamut, rather than ACES.
  • Tracker: Painting in the Tracker window caused Nuke to crash.
  • Text: Typing text in the properties panel message field always used the default font settings.
  • QuickTime: When the pixel format control was set to default (for the Animation codec), the ycbcr matrix control was not disabled.
  • Text: Selecting an animation group did not highlight characters in the Viewer or message field.
  • CameraTracker: In Source > Stills mode, tracking ignored the Global frame range specified.
  • CameraTracker: Drag selecting and moving multiple User Tracks was not possible.
  • stretched the features overlay abnormally.
  • QuickTime: The Write node ycbcr matrix control was not grayed out when the default pixel format was RGB(A).
  • QuickTime: The b64a pixel format did not behave as expected.
  • Virtual sliders were too sensitive on some integer fields.
  • QuickTime: Using the ProRes4444 codec with a pixel format of either YCbCrA 8-bit 444 Biased (r408) or YCbCrA 32-bit 444 Float (r4fl) did not produce the alpha channel correctly.
  • CameraTracker: Exporting certain data to a Tracker node was unreliable.
  • CameraTracker: Holding Shift and clicking User Tracks in the Viewer didn't add to the current selection.
  • CameraTracker: It was not possible to copy XYZ position values from the User Tracks table unless the track was marked as a survey point.
  • QuickTime: Limiting the number of helper processes, using the Preferences > QuickTime > reader subprocess limit dropdown, occasionally caused read errors.
  • CameraTracker: User Track paths did not update in the Viewer when deleting keyframes.
  • Mavericks only: Imported CameraTracker User Tracks were not added to the Viewer correctly.
  • Windows only: Importing a CameraTracker User Track created on another operating system caused Nuke to become unresponsive.
  • ModelBuilder: Creating a ModelBuilder node without a NukeX license displayed warnings about missing knobs.
  • BlinkScript: The Kernel Source field lost focus when the cursor moved to another panel.
  • CameraTracker: When a track was selected in the Viewer, no hover-over track info was available.
  • CameraTracker: After solving the camera, the Alt+ previous/next keyframe hotkeys do not work for User Tracks.
  • QuickTime: The Blackmagic RGB 10 bit (r210) codec did not default to the b64a pixel format.
  • QuickTime: DirectDraw Transfer codecs were not blacklisted for 2vuy codecs.
  • QuickTime: Transform handles required multiple undos in scripts containing QuickTime Read nodes.
  • BlinkScript: Kernel parameters with spaces in their names did not work when the kernel was reloaded.
  • Adding a Transform node downstream of certain .exr Read nodes and enabling auto alpha or raw data in the Read properties caused Nuke to crash, if the Transform was scaled on both the x and y axis.
  • ModelBuilder: Changing the separation value using the virtual slider caused Nuke to crash.
  • Adding MotionBlur after a Convolve with no filter caused Nuke to crash.
  • CameraTracker: Survey solves on single frame reported 'insufficient frames' if the survey points were keyed on a different frame.
  • Text/Dope Sheet: Adding a Transform and reversed Retime after a Text node containing an expression caused Nuke to become unresponsive.
  • Text: Character transformation information was not saved properly when an expression was present in an animation group.
  • Moving the color picker sample region did not update the picked control's color swatch.
  • Opening scripts containing certain stereo .exr files and viewing the image caused Nuke to crash.
  • - BlinkScript: Adding a BlinkScript node to the Node Graph in PLE mode caused Nuke to crash.
  • Color Picker: Color values were reported incorrectly when the order of the channels analyzed by the Viewer sampler or the Pixel Analyzer was not the same as the order in which they appeared within a ChannelsSet.
  • Dope Sheet: Keyframe selections were occasionally lost when scaling keys in the Dope Sheet.
  • Alembic: Navigating to a frame outside the rendered frame range caused Nuke to crash.
  • Read: Clicking Breakout Layers for a .psd file caused Nuke to become unresponsive.
  • Linux and Windows only: Clicking Capture this viewer did not work as expected.
  • DeepRead: Viewing .exr files containing deep data displayed blank frames.
  • • BUG ID 39848 - A customer script containing a vectorExtendEdge gizmo was causing Nuke to become unresponsive when a Roto node's properties panel was opened.
  • Alembic: Geometry imported from Maya did not carry over the correct vertex colors.
  • Rendering .exr files containing disparity layers produced glitches in the rgba layer.
  • Tracker/Roto: Moving data between Tracker and Roto occasionally produced odd glitches and random values in certain controls.
  • - Bezier: Marquee selecting multiple points on an animated curve caused the points to revert to their original positions.
  • There was an error in the SimpleBlur.cpp file in the Nuke bundle.
  • Documentation: The Reference Guide documentation referred to Ramp, rather than Radial Ramp.
  • Text: Changing the cursor position in the Viewer didn't update the cursor position in the message field.
  • ScanlineRender: Certain Alembic geometry rendered black.
  • Text: Characters selected using the Select All hotkey (Ctrl/Cmd+A ) were not affected by changes to properties panel controls, such as font size and tracking.
  • QuickTime: Using the Avid DNxHD codec with certain pixel formats caused darkening or frame locking when the timeline was scrubbed.
  • Linux only: Nuke displayed the old icons for the Applications menu and desktop shortcut icons

New in NukeX 7.0v9 (Sep 20, 2013)

  • New Features:
  • BUG ID 36378 - MergeMat: A new also mergedropdown has been added to the properties panel allowing you to merge additional channel sets.
  • NOTE: The compute capability is a property of the GPU hardware and can't be altered by a software update.
  • Feature Enhancements:
  • BUG ID 34656 - DeepRead: You can now use custom file extensions for Deep .exrfiles in the same way as standard files. For example, adding an odzReader.tclfile to your .nukedirectory containing the lines
  • load "exrReader.so"
  • add_file_extension_alias "odz" "exr"
  • Allows Nuke to read .odzfiles using the .exrreader.
  • Bug Fixes BUG ID 14637 - Setting the Reformat node typeto scalecaused proxy to behave incorrectly.
  • BUG ID 21327 - Mac OS X and Windows only: Dragging R3D files from the OS file browser set the wrong gamma spacecurve.
  • BUG ID 21760 - RotoPaint: It was not possible to expression link the Transform tab center xand yvalues.
  • BUG ID 26224 - The Ramp node’s Viewer handles did not update as expected.
  • BUG ID 30535 - The right-click Edit> Generatefunction could not create more than 4002 keyframes for animated controls.
  • BUG ID 33016 - Dope Sheet: Changing the Interpolationtype for Roto spline keys had no effect.
  • BUG ID 33916 - Reading a different Alembic file into a Camera already reading an Alembic file caused Nuke to crash.
  • BUG ID 34543 - Tracker: Copying and pasting nodes containing expression links did not update the links to point to the new nodes.
  • BUG ID 35201 - Nuke Assist: Pasting in a tree of nodes failed when the first unsupported node was reached.
  • BUG ID 35203 - Nuke could not read a particular customer .hdrfile.
  • BUG ID 35244 - Lens Distortion: Adjusting Radial Distortiondid not update the Card Parameters.
  • BUG ID 35329 - RotoPaint: Certain properties panel controls returned to their default values when switching between paint tools.
  • BUG ID 35461 - Nuke Assist: Buttons inside gizmos were disabled.
  • BUG ID 35500 - It was not possible to enable interactivemode for lights if the Camera connected to the ScanlineRender node was reading from a file.
  • NOTE: This issue is still occuring on Linux builds. See Other Known Issues for more information.
  • Bug fixes:
  • BUG ID 35989 - The output of a Merge node from inputs with identical bounding boxes increased the bounding box's size to 0 on the Yaxis.
  • BUG ID 36011 - RotoPaint: Merging empty RotoPaint nodes with other images, when the Merge node’s set bbox tocontrol was set to union, extended the bounding box to the format’s origin (0,0).
  • BUG ID 36039 - Particles: Changing the particle input from sprite to geometry, or vice versa, occasionally caused Nuke to crash.
  • BUG ID 36209 - OCIO: The Viewer gainand gammacontrols ignored the alpha channel when OCIO Viewer LUTs were used.
  • BUG ID 36269 - Particles: Using emit from> in orderwith a high emission ratecaused Nuke to crash.
  • BUG ID 36278 - Project3D: Projecting onto the same geometry with PrmanRender and ScanlineRender did not produce similar results.
  • BUG ID 36306 - Particles: ParticleEmitters with geometry connected to the particle input caused Nuke tocrash if the orientation settings produced NaN (not a number) results.
  • BUG ID 36337 - OCIO: Enabling Preferences> Viewer> use GPU for Viewer when possibleand using OCIO Viewer LUTs caused the alpha channel to disappear.
  • BUG ID 36461 - Attaching a HueCorrect node down-stream of an .exe containing NaN (not a number) pixels to a Viewercaused Nuke to crash.
  • BUG ID 36810 - Linux and Windows only: The Viewer zoom shortcut Windows Key+ middle mouse button did not work.
  • BUG ID 37488 - Write: It was possible to select file type> abcin the standard Write node’s properties panel, even though Nuke cannot write Alembic files without using a WriteGeo node.

New in NukeX 7.0v8 (Sep 10, 2013)

  • Bug Fixes:
  • BUG ID 36190 - Tracker: Expanding tracking anchor search areas caused Nuke to crash.

New in NukeX 7.0v7 (Sep 10, 2013)

  • Feature Enhancements:
  • BUG ID 35259 - A Modo equivalent 3D control typehas been added to
  • Preferences> Viewers> Interaction.
  • BUG ID 35548 - The examples in the documentation for the command line
  • rendering -F frame range argument have been improved.
  • BUG ID 35658 - Alembic: Load times and playback speeds have been
  • improved for .abcfiles, particularly where the geometry is transform
  • animated.
  • Bug Fixes:
  • BUG ID 16894 - Windows only: Enabling PrmanRender> RIB> filterdid
  • not work as expected.
  • BUG ID 17104 - Particles: Attaching a Constant to the ParticleEmitter
  • particleinput did not display color in the 3D Viewer.
  • BUG ID 21535 - Windows only: Playback did not reach 24 fps when
  • downrezwas set to 32.
  • BUG ID 23236 - The Ramp node's Viewer handles did not pivot until
  • mouse up.
  • BUG ID 25365 - Playback speed did not reach the full framerate when
  • ViewerStereo Modeswas set to anything other than Single.
  • BUG ID 31965 - Windows XP only: Rendering ZDefocus or Convolve
  • nodes on the CPU caused Nuke to crash.
  • BUG ID 32791/32794 - ParticleEmitter: Disconnecting a particleinput
  • when an emitter was connected to a Viewer caused Nuke to crash.
  • BUG ID 33018 - ReConverge: The use Ocula if availablecheck box has
  • been removed. ReConverge no longer uses Ocula, even when available.
  • BUG ID 33340 - ModelBuilder: Pressing Enterwhile adding geometry
  • caused Nuke to crash.
  • BUG ID 34357 - Adjusting translateor rotatevalues in Transform nodes
  • upstream of Tracker nodes causedNuke to become unresponsive.
  • BUG ID 35024 - HieroNuke: Transcode scripts created in Hiero
  • displayed the message Reader did not set bounding boxwhen imported
  • into Nuke.
  • BUG ID 35197 - Windows only: Using Ctrl+Cin Nuke when Hiero was
  • open caused Nuke to become unresponsive.
  • BUG ID 35297 - When the FN_NUKE_DISABLE_TMPLIC_NOTIFY_DIALOG
  • environment variable was set, Nuke7.0v6 launched straight into PLE
  • mode if no license was available.
  • BUG ID 35388 - OCIO Colorspace and OCIO Display used the knob index
  • rather than the names of knob values, causing the wrong LUT to be used
  • if the OCIO config file was changed manually.
  • BUG ID 35496 - A Viewer was removed from a customer script due to an
  • invalid viewerProcess.
  • BUG ID 35552 - Some cross-referenced pages in the Getting Started
  • Guidewere incorrect.
  • BUG ID 35554 - Copying .movRead nodes using Ctrl+Cduring thumbnail
  • rendering caused Nuke to crash.
  • BUG ID 35581 - Disabling Preferences> Viewers> use GPU for Viewer
  • when possibleslowed the playback rate of Stereo Interlaced footage in
  • the Viewer.

New in NukeX 7.0v6 (Sep 10, 2013)

  • Feature Enhancements:
  • Nuke now reads R3D file metadata and converts the gamma spacesetting
  • to Linearautomatically.
  • Click Load Settingsin the properties panel to apply the gamma space
  • specified in the file.
  • Nuke’s performance when handling Alembic (.abc) files has been improved.
  • BUG ID 8253 - Nuke now supports ARRIRAW files, which use the .arifile
  • extension. Nuke uses the same ARRIRAW SDK version as Hiero to
  • maintain consistency.
  • BUG ID 34828 - CameraTracker: The Create Pointsbutton has been
  • reverted to the Nuke 6.3 name, Create Scene, and now creates a Camera,
  • PointCloud, and Scene with a single click.
  • BUG ID 32554 - R3D file reader: Re-ordered the gamma and colorspace
  • menu options to make them easier to find.
  • Bug Fixes:
  • Bug Fixes BUG ID 10028 - Deleting and undoing cloned nodes caused corruption in
  • saved scripts.
  • BUG ID 19788 - Windows only: Writing frames occasionally displayed a
  • Can't rename .tmp to final, Permission deniederror.
  • BUG ID 24413 - Nuke crashed when opening a script that had an
  • undefined knob in a Write node.
  • BUG ID 24785 - OCIOLookTransform was missing from the Other> All
  • pluginsmenu.
  • You can also access OCIOLookTransform by pressing Xon the Node
  • Graph, making sure TCLis selected in the dialog that opens, typing OCIOLookTransform, and clicking OK.
  • BUG ID 29966 - RotoPaint: There was no visual representation at the
  • playhead of keyframes set on the stereo offsetcontrol.
  • BUG ID 30008 - Alembic: Particle lifetime settings were not respected
  • when a particle system was written to the .abcformat.
  • BUG ID 30791 - Light nodes did not display an error when an Alembic file
  • was specified in the Filecontrol.
  • BUG ID 32891 - SplineWarp: The second correspondence point added
  • between curves was always placed incorrectly.
  • BUG ID 33922 - Linux only: Manually unzipping the installer file created a
  • Documentation/Pythondirectory with restrictive permissions.
  • This directory now has drwxr-xr-x permissions.
  • BUG ID 34363 - DeepToPoints didn’t handle bounding boxes correctly.
  • BUG ID 34385 - When rendering particles to Alembic (.abc) files, particle
  • colors were only written on the first frame because Alembic doesn’t
  • support time-sampled colors. This sometimes gave particles the wrong
  • color.
  • Nuke now finds the frame with the most particles and writes the colors
  • from that frame instead.
  • BUG ID 34436 - Nuke’s exit codes have now been documented in the end
  • of the Previews and Renderingchapter of the Nuke User Guide. You can
  • also find them here:
  • 0 = success
  • 1 = render error
  • 100 = license failure
  • BUG ID 34734 - The Precomp node’s label was missing, causing the node
  • to be called 1instead of Precomp1.
  • BUG ID 34878 - CameraTracker: No warning was displayed when
  • attempting to track and solve from a single frame.
  • BUG ID 35009 - Nuke crashed when opening the Roto properties panel in
  • a customer script that included a disabled SplineWarp node.

New in NukeX 7.0v5 (Sep 10, 2013)

  • Feature Enhancements:
  • The DPX reader now supports infra red (IR) passes produced using FilmLight’s Northlight film scanner.
  • Bug Fixes:
  • BUG ID 21971 - Processing a Convolve node took longer when channels was set to allrather than rgba, even if there were no other channels in the input.
  • BUG ID 23025 - Certain customer scripts that included RotoPaint were slower in Nuke 6.3 than 6.2.
  • BUG ID 25066 - Using a Switch node with F_Kronos while scrubbing the
  • timeline caused a segmentation fault.
  • BUG ID 25446 - Roto: When motionblurwas enabled, setting opacityto 1
  • didn’t always produce a fully opaque shape.
  • BUG ID 25907 - The outputcontrol on Roto nodes did not default to
  • alpha. RotoPaint nodes remain unchanged, defaulting to rgba.
  • BUG ID 26508 - PointCloudGenerator: Right-clicking in the groups list on
  • the Groupstab produced unnecessary animation menu items.
  • BUG ID 31205 - LensDistortion: The results produced by Analyze
  • Sequencediffered slightly between Nuke 6.3v8 and Nuke 7, due to
  • LensDistortion being updated to use the same tracking as CameraTracker
  • and PlanarTracker.
  • BUG ID 31965 - Windows XP only: Attempting to process ZDefocus and
  • Convolve nodes on the CPU caused Nuke to crash.
  • BUG ID 32791/32794 - ParticleEmitter: Disconnecting a particleinput
  • when the emitter is connected to a Viewer causes Nuke to crash.
  • BUG ID 33710 - ZDefocus didn’t always work if use input channelswas
  • checked.
  • BUG ID 33820 - When using a customer Python script, Nuke 7.0 returned
  • an additional error in the error console, causing issues with command line
  • renders when error trapping.
  • BUG ID 33968 - Using several Kronos and Denoise nodes caused Nuke to
  • spawn a large very number of threads, which sometimes resulted in a
  • crash.
  • BUG ID 34027 - Roto shapes imported into Nuke 7.0 from other
  • applications were offset after the Nuke script was saved and reopened.
  • BUG ID 34176 - LensDistortion: When drawing a line with Drawing Mode
  • Onenabled, points were offset from the cursor.
  • NOTE: Bugs 23025, 25066, 25446, and 25907 above were incorrectly
  • omitted from the 7.0v1 Release Notes.

New in NukeX 7.0v4 (Sep 10, 2013)

  • Feature Enhancements
  • New icons have been added to the documentation for points of interest in
  • the text, such as notes and tips.
  • BUG ID 30602 - The Preferences> Suppress bad channelscheckbox has been removed from the Preferencesdialog. Nuke now automatically discards any channels that are not referenced in the script when it is saved.
  • Bug Fixes:
  • BUG ID 33586 - Particles: ParticleEmitters with 2D sprites connected to the particleinput did not render in the 2D Viewer.
  • BUG ID 33615 - Linux only: On some systems, disabling use GPU if availablein the ZDefocus and Convolve Properties panel caused Nuke to crash when a Viewer node was connected.

New in NukeX 7.0v3 (Sep 10, 2013)

  • New Features:
  • BUG ID 32355 - Nuke has been updated to use OCIO version 1.0.7.
  • Feature Enhancements:
  • BUG ID 33101 - A new environment variable has been added to disable the license expiration dialog. To enable the new variable set FN_NUKE_DISABLE_TMPLIC_NOTIFY_DIALOG to 1.
  • However, you still get a warning if nolicense is found, for example if you
  • only have a Nuke license but you try to run NukeX.
  • Feature Enhancements:
  • BUG ID 30576 - A new dropdown has been added to the Licensing dialog allowing you to use either FLEXlm or RLM license servers.
  • BUG ID 32240 - ModelBuilder: The Bake scene selectionbutton has been
  • split into a Selected geometrydropdown and Bakebutton.
  • Bug Fixes:
  • BUG ID 11951 - It was not clear in the documentation that the $NUKE_PATH environment variable is processed in reverse order when loading Python scripts.
  • BUG ID 21068 - RotoPaint: Creatinga RotoPaint node after loading a customer plug-in at startup then saving the layout and restarting, caused Nuke to crash.
  • BUG ID 21212/23709 - Windows only: QuickTime filepaths containing expressions or relative paths (such as ../myClip.mov) caused Nuke to become unresponsive.
  • BUG ID 28094 - Alembic: The PointCloudGenerator> Point Sizecontrol
  • was not written to .abcfiles correctly.
  • BUG ID 29341 - ModelBuilder: Pressing Enterwhen adding a shape canceled the action.
  • BUG ID 29997 - The tooltips on someof the Light node’s controls were incorrect.
  • BUG ID 30334 - When exporting some QuickTime files, a frame from the
  • sequence was occasionally held for two frames.
  • BUG ID 31455 - Updating to RenderMan 17 and connecting a PrmanRender node to the Viewer caused Nuke to crash.
  • BUG ID 31511 - Tracker: Holding Shiftto create new tracking anchors did
  • not display the +cursor correctly.
  • BUG ID 31817 - ModelBuilder: It was not possible to change the opacity
  • of the highlight when in Face selectionmode.
  • BUG ID 31965 - Windows XP only: Attempting to process ZDefocus and
  • Convolve nodes on the CPU caused Nuke to crash.
  • BUG ID 32118 - Card3D: FrameHold and TimeOffset were ignored when motionblurwas enabled.