Nuke 8.0v1 ReleaseNotdes

5/19/2018 Nuke 8.0v1 ReleaseNotdes

1/28

Release Notes for Nuke 8.0v1

Release Date

05 December 2013

Qualified Operating Systems Mac OS X 10.7 (Lion), 10.8 (Mountain Lion), 10.9 (Mavericks)

NOTE: Nuke is expected to function correctly under Mac OS X Mavericks (10.9), but we are seeing UI

performance degradation compared to previous OS X versions. We are working on resolving these issues.

Windows 7 64-bit and Windows 8 64-bit

CentOS/RHEL 5 and CentOS/RHEL 6

Other operating systems may work with Nuke, but have not been fully tested. If you have any problems with a

particular operating system, please [email protected].

Requirements for GPU Acceleration

To take advantage of GPU acceleration, you must have:

an NVIDIA GPU with compute capability 2.0 (Fermi) or above. A list of the compute capabilities of NVIDIA GPUs is

available atwww.nvidia.co.uk/object/cuda_gpus_uk.html

NOTE: The compute capability is a property of the GPU hardware and can't be altered by a software

update.

graphics drivers capable of running CUDA 4.2 or above.

On Windows and Linux, CUDA graphics drivers are bundled with the regular drivers for your NVIDIA GPU.

Drivers from April 2012 onward support CUDA 4.2.

Goto http://www.nvidia.com/Download/Find.aspx?lang=en-us for more information.
mailto:[email protected]://www.nvidia.co.uk/object/cuda_gpus_uk.htmlhttp://www.nvidia.com/Download/Find.aspx?lang=en-ushttp://www.nvidia.co.uk/object/cuda_gpus_uk.htmlmailto:[email protected]


2/28

On Mac, the CUDA driver is separate from the NVIDIA graphics driver and must be installed, if you don't have

already. The minimum requirement for CUDA 4.2 is driver version 4.2.5 which can be downloaded from

www.nvidia.com/drivers.

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

New Features

ApplyMaterial

A new filter control has been added to the ApplyMaterial node, allowing you to use a named filter when applying a

material.

ApplyMaterial can be found in the 3D>Shader menu. Click here to launch the online help page.

BlinkScript

A new BlinkScript node has been added. This utilizes our Blink framework to compile and run C++-like image

processing kernels on the CPU (with optional SIMD acceleration) or GPU. It streamlines plug-in development

workflow significantly, as you no longer have to exit Nuke to compile your code.

The Publishbutton, on theKernel Parameterstab, can be used to share your BlinkScript tools with others,

without exposing the development environment. This button creates a group containing a copy of the current nod

which can then be saved as a gizmo if desired. Only the kernel parameters and GPU controls are exposed by default

in the published version of the node.

You can also enable Protect kernel, next to the Publishbutton, before publishing. When enabled, the kernel

source is encoded inside the published version of the node, and is not readable when the published node is saved to

a script.

Click here to launch the online help page.

Breakpad Crash Reporting

Breakpad crash reporting has been integrated into Nuke. This allows you to submit crash dumps to The Foundry in

the unlikely event of a crash.

Crash reporting is enabled in GUI mode and disabled in terminal mode by default. You can toggle reporting on and

off using the --crashhandling 1or 0option on the command line or by setting the environment variable NUKE_

CRASH_HANDLING to 1 or 0.

|RELEASE NOTES FOR NUKE 8.0
http://www.nvidia.com/drivershttp://help.thefoundry.co.uk/nuke/8.0#user_guide/blinkscript/image_processing_blink.html?TocPath=User%20Guide|NukeX|Using%20the%20BlinkScript%20Node|_____0http://help.thefoundry.co.uk/nuke/8.0#reference_guide/3d_nodes/applymaterial.html?TocPath=Reference%20Guide|3D%20Nodes|_____1http://www.nvidia.com/drivers


3/28

When crash handling is enabled in GUI mode, you can control whether reports are automatically submitted or not

using the --nocrashpromptcommand line option or by setting the environment variable NUKE_NO_CRASH_

PROMPT to 0.

Crashes in terminal mode are automatically submitted when crash handling is enabled.

CameraTracker

Nukes CameraTracker has been overhauled and now includes tracking stills to create an animated 3D camera and

adding User Tracks to augment a solve or process and entirely manual track and solve.

You can automatically track features, add User Tracks or tracks from a Tracker node, mask out moving objects using

a Bezier or B-spline shape, and edit your tracks manually. CameraTracker can solve the position of several types of

cameras as well as solve stereo sequences.

The new CameraTracker has three main workflows:

Sequence- designed to track a contiguous frame sequence with minimal intervention from you.

User Tracks- allows you to manually place tracking markers to augment, or even totally replace, sequence

tracking. You also assign User Tracks as 3D Survey Points to improve solve accuracy or link solves to the same

world coordinates.

NOTE: 3D Survey Points have replaced the ProjectionSolver workflow, but you can still add

ProjectionSolver nodes by pressing Xin the Node Graph and enteringProjectionSolver as a TCL

command.

Stills- creates a camera track from reference frame stills taken on site. These represent the minimum number of

frames required to cover your subject with sufficient overlap.


Context-Sensitive Online Help

Nuke now features an online help system linked to individual nodes. The in-context help is designed to replace the

node specific tooltips in-application.

Previously, when you clicked the ? in the properties panel in Nuke a brief tooltip displayed with a short description o

the node and, in some cases, a little bit of control usage info. The new system cuts away to the default browser and

displays the relevant content from the new online HTML help, including video tutorials and example scripts.

NOTE: You can still display the tooltip by hovering over the ? in the properties panel.

http://help.thefoundry.co.uk/nuke/8.0#user_guide/cameratracker/camera_tracking.htmlhttp://help.thefoundry.co.uk/nuke/8.0#user_guide/cameratracker/camera_tracking.html


4/28

There are also some new Preferences,onthe Control Panel tab under Documentation, which will allow you to

choose to display the local copy of the online help, The Foundry version from our website, or your own custom

URLs.

Click here to launch the online help.

Dope Sheet

The Dope Sheets functionality, layout, and visibility have been improved:

Keyframe positions can be remapped in the Dope Sheet using AppendClip, Retime, TimeClip, TimeOffset, and

TimeWarp nodes. The keyframes are displayed in context, allowing you to shift keys more easily within the Dope

Sheet from their remapped positions.

Nodes that affect frame ranges are now displayed within a layer in the Dope Sheet for easier visualization.


EditGeo

Nuke now includes an EditGeo node allowing you to select and edit geometry or point cloud vertices and faces in th

3D Viewer.

EditGeo can be found in the 3D>Modifymenu. Click here to launch the online help page.

Import Nuke

A new import nukefunction has been added to allow you to use Nuke as a module in any Python interpreter. We

recommend running the Python interpreter bundled in the Nuke install directory.

You can import Nuke as a module into a third-party Python 2.7.3 interpreter by adding the file path to Nuke's site-

packagesdirectory to the usrlocal.pth file in your Python 2.7 install.

NOTE: The Foundry cannot provide customer support for third-party Python interpreters.

Whichever interpreter you choose, use the import nukedeclaration to make Nukes Script Editor functions and

commands (such as nuke.nodes.Blur()to add a Blur node) available in the interpreter.

For more information, selectHelp >Documentationfrom Nuke's menu bar and navigate to Python Developers

Guide>Running Nuke as a Python Module.

http://help.thefoundry.co.uk/nuke/8.0/Default.htmlhttp://help.thefoundry.co.uk/nuke/8.0/Default.html#reference_guide/3d_nodes/editgeo.html?TocPath=Reference%20Guide|3D%20Nodes|_____18http://help.thefoundry.co.uk/nuke/8.0/Default.html#getting_started/using_interface/using_dope_sheet_interface.html?TocPath=Getting%20Started|Using%20the%20Interface|Animating%20Parameters|Working%20with%20Keyframes%20in%20the%20Dope%20Sheet|_____1http://help.thefoundry.co.uk/nuke/8.0/Default.html


5/28

MatchGrade

MatchGrade for NukeX allows you to match grades from unrelated frames as well as the original graded source

matching function. Additionally, you can now export LUTs from the analysis to an OCIOTransform node to use

elsewhere in the node tree:

Match Graded Source- extract a baked-in grade by matching the source footage with a graded version of the

source.

Use this to create and export the grade to use with the original source footage. The same frames are expected on

the source and target inputs.

Match Different Clip - match the grade in a different clip where the source and target frames are different.

Use this to create a grade to reproduce the look of the target in the source footage. You can, for example, create

the grade to match an element between different shots by using the mask input to match the colors on the

element only in the different clips.

Analyze Reference Frames- analyze a set of reference frames. First set the matching task then key referenceframes that pick out the characteristic colors in each sequence.

Then click Analyze Reference Framesto calculate the grade.

Auto-analyze Per Frame- calculate the best grade to use on a frame-by-frame basis when extracting a baked in

grade.

SelectAuto-analyze per framewhen the task is set toMatch Graded Sourceto enable this.

Export- export the calculated grade in .csp format for use with the OCIO FileTransform node.

A CDL transform can also be calculated and exported to OCIO CDLTransform. There is the option to manually set

CDL parameters and recalculate the best fit transform.

MatchGrade can be found in the Color menu. Click here to launch the online help page.

ModelBuilder

ModelBuilder for NukeX now supports the unpacking of geometry as UVs using seams marked by hand in the

Viewer. The seams control the unwrapping, telling ModelBuilder where it's allowed to cut the model in order to be

able to lie the model flat without any faces overlapping.

Unwrapping generates UV values for each of the vertices. You can do it as many times as you like; each iteration

replaces whatever UVs you had previously.

ModelBuilder can be found in the 3D>Geometrymenu. Click here to launch the online help page.

Multi-part EXRs

Nuke now supports multi-part EXR files using ILMs OpenEXR2.0 library. Multi-part EXRs allow you to read individua

channels, layers, and views within an EXR file without unpacking all the parts contained within it.

http://help.thefoundry.co.uk/nuke/8.0/Default.html#user_guide/matchgrade/using_matchgrade.html?TocPath=User%20Guide|NukeX|Using%20MatchGrade|_____0http://help.thefoundry.co.uk/nuke/8.0/Default.html#user_guide/modelbuilder/creating_3d_models.html?TocPath=User%20Guide|NukeX|Using%20ModelBuilder|_____0http://help.thefoundry.co.uk/nuke/8.0/Default.html#user_guide/matchgrade/using_matchgrade.html?TocPath=User%20Guide|NukeX|Using%20MatchGrade|_____0


6/28

Additionally, you can write multi-part EXRs out using the Write nodes interleavedropdown which determines the

parts that are written to file:

channels, layers, and views- creates a single part image which is compatible with earlier versions of Nuke and

other applications using an old OpenEXR library.

channels and layers- separates views into the layers and channels contained within the view.

channels- separates layers into their component channels.

ParticleCache

The ParticleCache node allows you to write particle systems to file and read them back in to alleviate the constant re

evaluation of pre-frames in the simulation.

If you have downstream nodes requesting extra frames outside the normal range, such as motion blur or

ScanlineRender shutter length, use the paddingcontrol to set the number of frames to extend the sequence by, at

both start and end.

NOTE: ParticleCache nodes must be placed at the base of a single particle system or multiple merged

particle systems, they can not be placed beneath a Scene node connected to two separate streams or in

the middle of a string of particle nodes.

ParticleCache can be found in the Particlesmenu. Click here to launch the online help page.

Pixel Analyzer and Scopes

A Pixel Analyzer panel has been added to the contents menu, allowing you to collect color information from pixels inthe Viewer. The analyzer has three modes:

Ctrl/Cmd + click - samples a single pixel wherever you click in the Viewer.

Ctrl/Cmd + click and drag - samples single pixels as you drag around the Viewer, producing current, max/min,

average, and median pixel values.

Ctrl/Cmd +Shift+ click and drag - draws a marquee around multiple pixels, producing max/min, average, and

median pixel values. You can drag the marquee around to sample different areas and adjust its size using the

handles in the Viewer.

Nuke has adopted Hieros Histogram, Waveform, and Vectorscope panels, accessed from the content menu. There

are also new scope controls in the Preferences>Scopestab.

Click here to launch the online help page for the Pixel Analyzer or here for the Scopes help.

http://help.thefoundry.co.uk/nuke/8.0/Default.html#reference_guide/particles_nodes/particlecache.html?TocPath=Reference%20Guide|Particles%20Nodes|_____2http://help.thefoundry.co.uk/nuke/8.0/Default.html#user_guide/color_correction/using_scopes.html?TocPath=User%20Guide|Nuke|Working%20with%20Color|Using%20Scopes|_____0http://help.thefoundry.co.uk/nuke/8.0/Default.html#user_guide/color_correction/using_pixelanalyzer.html?TocPath=User%20Guide|Nuke|Working%20with%20Color|Using%20the%20Pixel%20Analyzer|_____0http://help.thefoundry.co.uk/nuke/8.0/Default.html#reference_guide/particles_nodes/particlecache.html?TocPath=Reference%20Guide|Particles%20Nodes|_____2


7/28

QuickTime Processing

The way that Nuke and Hiero handle QuickTime clips has been overhauled, allowing you to change various read and

write options.

Nukes Read node attempts to select the best fit combination by reading an extended list of metadata key/value

pairs from the QuickTime header, including nclcatom, gama atom, and ProRescodec headers.

Nuke also writes out user metadata depending on the specific settings used (outside of the nclc and gama atoms

and ProResheader) and Hiero has been set to use these if it finds them in the.movfiles written, instead of the

atoms mentioned above. If Hiero doesn't find this user metadata, it falls back to using the atoms/header data.

You can manually override the following mov Optionsin the Read node properties panel:

ycbcr matrix- sets the way YCbCr isconverted to RGB. You can choose to use the new Rec 601 and Rec 709 or

the Legacy encoding methods, which are the methods used previously in Nuke.

codec- sets the codec used to read the QuickTime file. The codec dropdown defaults to a codec appropriate for th

QuickTime in question, where available, and only lists those that declare themselves able to read the file.

pixel format- sets the read and write pixel format, which includes bit-depth, colorspace, pixel packing, and range

This setting defaults to the best format accepted by the codec, allowing Nuke to perform the conversion to RGB

without the use of an unknown QuickTime transform, where possible. RGB pixel types rely on QuickTime to do th

conversion from YCbCr when dealing with a non-RGB codec.

Setting the Write node properties file typeto movallows you to override the same QuickTime controls as the Read

node, except that the pixel formatdropdown is populated depending on the codec chosen.

ScanlineRender

Nukes ScanlineRender node now supports Deep output allowing to connect Deep nodes directly downstream of

ScanlineRender nodes.

Additionally, the render dropdown for 3D objects now contains all displaytypes, allowing you to render

wireframe, solid+wireframe, and textured+wireframe.

Text

Nukes Text node has been reworked to include more text options and attributes for individual characters:

Make group and individual character selections in either the Viewer or properties panel.

Adjust single characters in a text string including individual or group character transforms.

NOTE: The font dropdown includes system fonts by default. If you don't want access to the local system

fonts, go to the Project Settings>Fonttab and disable include system fonts.



8/28

Text can be found in the Draw menu. Click here to launch the online help page.

Miscellaneous

New virtual sliders have been added to all numeric controls. Hover over a control, click the middle mouse button,

then drag the field to adjust the associated control. Hold Shiftto increase slider sensitivity. Three new filters have been added to all filter menus. The new filters are especially useful for down-scaling images

without excessive softening:

Lanczos4- good for scaling down with minor sharpening.

Lanczos6- good for scaling down with some sharpening.

Sinc4- a box windowed Sinc filter, good for scaling down with a lot of sharpening.

The filter numbers at the end ofthe filter name denote the width of the filter, similar to the naming scheme used

by PRMan (http://www.renderman.org/RMR/st/PRMan_Filtering/Filtering_In_PRMan.html).

NOTE: All three filters have negative lobes and can produce values outside the range of the input pixels.They exhibit increased ringing as the filters become sharper.

In-panel color picker dropdowns have been added to nodes that feature the regular floating color picker panel.

A new luminance mixslider has been added to the ColorCorrect and HueCorrect nodes, allowing you to dissolve

between the cooked/output luminance at 0 and the original/raw luminance at 1.

A new Capture this Viewer button has been added to write the contents of the current Viewer to a .jpgfile.

Capture this Viewer is located in the Viewer pane, adjacent to the Flipbook this Viewer button.

The Viewer now has a full frame processing mode. When enabled, Nuke does not skip scanlines when rendering in

the Viewer.

A Wireframe shader has been added, which overlays an adjustable wireframe on any geometry at render time.

Wireframe can be found in the 3D>Shader menu.

BUG ID 13458 - ScanlineRender: The render dropdown for 3D objects now contains all displaytypes, allowing yo

to render wireframe, solid+wireframe, and textured+wireframe.

BUG ID 32324 - Monitor Output: Nuke has adopted Hieros monitor out functionality, adding support for SDI out

on Linux.

NOTE: AJA monitor out cards are not currently supported on Linux.

BUG ID 36378 - MergeMat: A new also mergedropdown has been added to the properties panel allowing you tomerge additional channel sets.

BUG ID 38750 - Nuke now ships with Courier and Charter, Courier, and Utopia default fonts. Copyrights belongs t

Bitstream Inc., IBM Corp., and Adobe Systems Inc., respectively.

BUG ID 38765 - Alembic: Ogawa support has been added read and write operations.

http://help.thefoundry.co.uk/nuke/8.0/Default.html#reference_guide/draw_nodes/text.html?TocPath=Reference%20Guide|Draw%20Nodes|_____17http://www.renderman.org/RMR/st/PRMan_Filtering/Filtering_In_PRMan.htmlhttp://www.renderman.org/RMR/st/PRMan_Filtering/Filtering_In_PRMan.htmlhttp://www.renderman.org/RMR/st/PRMan_Filtering/Filtering_In_PRMan.htmlhttp://help.thefoundry.co.uk/nuke/8.0/Default.html#reference_guide/draw_nodes/text.html?TocPath=Reference%20Guide|Draw%20Nodes|_____17


9/28

Feature Enhancements GPU acceleration for certain nodes is now available with a standard Nuke license. See Requirements for GPU

Acceleration on page 1 for more information. BUG ID 18040 - CameraTracker now includes a selection of common film back options.

BUG ID 24080 - The Sony S-Gamut (S-Log) colorspace primaries have been added to the Colorspace node.

BUG ID 29804 - VectorGenerator, Kronos, and MotionBlur now fall back to the CPU if a GPU render fails due to

lack of memory.

BUG ID 32179 - ModelBuilder: The Viewer now has a visual reference when operations are in progress, such as

extrude and bevel.

BUG ID 32248 - ZDefocus now includes the option to use a flat depth channel.

BUG ID 32899 - DeepMerge: A new drop zero threshold control has been added to DeepMerge, allowing you to

discard holdout samples below a certain threshold.This control can help filter out samples with low alpha values caused by floating point inaccuracy.

BUG ID 34656 - DeepRead: You can now use custom file extensions for Deep .exr files in the same way as

standard files.

For example, adding an odzReader.tcl fileto your .nukedirectory containing the lines:

load exrReader.so

add_file_extension_alias odz exr

Allows Nuke to read .odzfiles using the .exr reader.

BUG ID 35330 - The default 3D Viewer camera position is now x=3.5, y=3.5, z=3.5 and is rotated so that the

camera is oriented towards the Viewer origin. BUG ID 35522 - Nukes Read node now disregards Deep data from OpenEXR 2.0 files, allowing clips to be opened

normally without the use of DeepRead.

BUG ID 35563 - Added ACES primaries to the Colorspace node.

BUG ID 36248 - Added a note about pre-rendering from IBKColor to the Reference Guide.

BUG ID 37016 - Kronos, MotionBlur, and VectorGenerator now produce identical output from the same image

when processed on both the CPU and GPU.

BUG ID 37108 - Keyframes on the timeline now update when temporal nodes, such as TimeOffset, are

manipulated in the Dope Sheet.

BUG ID 37391 - Text: The Viewer toolbar now includes keyframe +/- and edit textmode controls. BUG ID 37749 - EXPTool has been renamed to Exposure.

BUG ID 37908 - ModelBuilder: You can now flip object or face normals in object and face selection mode by right-

clicking in the Viewer and selecting flip face normals.

BUG ID 38388 - CameraTracker: A new Update Track button has been added, allowing you to retrack a range of

frames within an existing set, instead of retracking the entire sequence.



10/28

1

BUG ID 38390 - CameraTracker: A new Update Solvebutton has been added, allowing you to resolve a range of

frames within an existing solve, instead of recalculating the entire sequence.

BUG ID 38455 - MatchGrade: A new Outputdropdown has been added to the properties panel allowing you to

select what is displayed in the Viewer:Source, Target, or Matched.

BUG ID 38708 - A new channels control in the Copy node (and various others) allows you to create channels into

built-in layers.

BUG ID 38928 - Tracker: The default add tracking anchor hotkey, Shift, has been changed to Ctrl/Cmd+Altin-line

with CameraTracker.

Bug Fixes BUG ID 3326 - Increasing the Viewer downrezcaused Flare and Sparkles to appear magnified.

BUG ID 6429 - The file browser did not collapse sequential files when they did not have a file extension, such as

image.001, image.002, image.003, and so on.

BUG ID 10884 - Text: Closing the properties panel did not hide the transform jack overlay in the Viewer.

BUG ID 15561 - Channel adds were generated during saves even when the channels were not referenced in the

script.

BUG ID 16404 - The 3D Viewer did not use Camera win_translateor win_scalecontrols.

BUG ID 16484 - QuickTime: Valid rgba alpha channels were not included in alpha-supporting Quicktime codecs,

such as Prores 4444 and Animation.

BUG ID 16855 - Metadata was not updated duinrg rendering.

BUG ID 18206 - SplineWarp: Persistent preview always showed rgb when applied to other channel sets.

BUG ID 19819 - PrmanRender: Particle systems could not be rendered. BUG ID 21314 - Roto: Selecting no animation on all knobsadded a keyframe on the current frame.

BUG ID 21370 - Nuke crashed in terminal mode when calling the Preferences file.

BUG ID 21839 - Denoise: White alpha channels were created from rgb only inputs.

BUG ID 22179 - Denoise: Moving the analysis region updated before you finished moving it.

BUG ID 22335 - The Vview indicator didnt disappear after unsplitting controls.

BUG ID 23213 - ReadGeo: Enabling all objectsin the properties panel showed objects in the Viewer with either a

translate or rotate offset.

BUG ID 24138 - ReadGeo: Changing the file typefrom a static.fbxto an .obj sequence caused unexpected

behavior.

BUG ID 26089 - Expression link arrows were only drawn halfway between nodes in the Node Graph.

BUG ID 26129 - Vectorfield: Selecting file type>cmswhen the actual LUT file type was different caused Nuke to

crash.

BUG ID 26142 - The AlexaV3LogC LUT in root LUTs was an older version than the one in the Colorspace node.

BUG ID 26234 - Setting the ContactSheet nodes row control to negative values caused Nuke to crash.

BUG ID 27622 - ModelBuilder: The F hotkey did not center on the selected object in the 3D Viewer.



11/28

BUG ID 27800 - The Text node was using more memory than expected.

BUG ID 28887 - ModelBuilder: Selecting an object in the Viewer did not select the corresponding entry in the in th

Scenelist and vice versa.

BUG ID 29048 - OCIO: Using the ocionuke library in terminal mode resulted in an error.

BUG ID 29279 - ModelBuilder: Selecting the current shape from the shape menu didnt initialize the shape adding

tool.

BUG ID 29564 - ModelBuilder: Snapping transform handles to the object surface automatically caused problems

with the scaling behavior.

BUG ID 29952 - RotoPaint: Keyframes specific to individual views appeared in all views.

BUG ID 29966 - RotoPaint: Keyframes on the stereo offsetcontrol were not displayed in the VIewer timeline.

BUG ID 30659 - Polygon clipping was incorrect in the Displacement node.

BUG ID 31718 - CameraTracker: Camera sensor presets were not scriptable.

BUG ID 32143 - Playback did not reach 24 fps for geometry attached to a TimeOffset with reverse inputenable

BUG ID 32328 - Dope Sheet: The unkeyable Readfilecontrol was exposed incorrectly. BUG ID 32334 - RotoPaint: Drawing a spline in proxy mode resulted in unexpected behavior.

BUG ID 32364 - Tracker: RotoPaint toolbars and overlays disappeared when a Tracker node's properties panel wa

open andthe Viewer was displaying and error.

BUG ID 32369 - QuickTime: Converting from 16-bit scaled incorrectly.

BUG ID 32457 - RotoPaint: In multi-view scripts, cutting and pasting a split shape did not work as expected.

BUG ID 32472 - RotoPaint: Undoing the transform on a shape with modified points locked Nuke.

BUG ID 32475 - RotoPaint: Moving a shape's transform handle occasionally moved only a single point on the

shape.

BUG ID 32520 - ModelBuilder: The source image appeared until a refresh was forced with unlocked cameras.

BUG ID 32552 - Mac OS X only: Moving multiple RotoPaint points and shapes while changing frame occasionally

caused Nuke to crash.

BUG ID 32569 - Textured objects occasionally disappeared during playback when using DisplaceGeo and

PositionToPoints nodes.

BUG ID 32592 - ModelBuilder: When Preferences>Control Panel >expand/collapse panels in Properties

bin to match selectionwas enabled, baking geometry created empty ModelBuilderGeo nodes.

BUG ID 32752 - Dragging a roto point, 3D object, or the Viewer playhead behind a floating window displaced the

object randomly.

BUG ID 32832 - ParticleEmitter: Emitting from faceswith emit order set to uniformlyor in order caused colorfrom textureto be ignored.

BUG ID 32851 - ParticleEmitter: Enabling color from texturedid not apply the color properly when the incoming

bbox did not match the format.

BUG ID 32992 - RotoPaint:toolbar_paint_sourcereverted to default when switching tools.

BUG ID 32996 - ModelBuilder: There was no visible indication of which shape was selected in the scene tree.



12/28

BUG ID 33536 - Entering an empty string in a Merge nodes label field caused an error if the red, green, or blue

channels for that node were disabled.

BUG ID 33623 - Opening a certain script generated for a Hiero transcode caused Nuke to crash.

BUG ID 33663 - RotoPaint: Handles were offset while transforming Roto shapes when in down-rez mode.

BUG ID 33696 - Kronos/MotionBlur/VectorGenerator: Results differed depending on the number of cores used fo

rendering.

BUG ID 33796 - Mac OS X only: Switching the Viewer right-click Stereo Modescontrol away from OpenGL stere

modeand back again caused Nuke to crash on MacBook Pros with Retina displays.

BUG ID 33952 - The Relight example in the Nuke User Guideshowed a misleading image.

BUG ID 34281 - A customer script displayed 'Shuffle.in: Can't select rgba.alpha; it conflicts with other selected

channels' during rendering.

BUG ID 34332 - r3dReader: It was not possible to undo the changes made by clicking Metadata.

BUG ID 34334 - r3dReader: Clicking Metadata did not update the label correctly.

BUG ID 34357 - Tracker: Lock-ups when adjusting translateor rotatevalues in a Transform upstream of a

Tracker.

BUG ID 34495 - Dope Sheet: Attempting to scale three or more keyframes at once caused the scale handles to get

stuck when dragging.

BUG ID 34508 - GridWarp: Maintaining selection when switching between source and destination grids was

inconsistent.

BUG ID 34525 - Suppress bad channels was not working properly.

BUG ID 34617 - Deep: Crash opening a script with two HoldOuts and viewing the deep channel.

BUG ID 34664 - Deep nodes provided incorrect resolution information in expressions.

BUG ID 34725 - Assist: Splinewarp handles were not visible.

BUG ID 34770 - ModelBuilder: Connecting PoissonMesh node caused Nuke to crash.

BUG ID 34948 - There was no information on GeoReaderFormat in the Nuke developer documentation.

BUG ID 35647 - BlendMat: The blend control was always set to over when converting Deep data.

BUG ID 36110 - ReadGeo: Invalid vertex, uv, or normal indices in an .obj file caused Nuke to crash.

BUG ID 36133 - DeepRead: Leaving the_formatHintvariable null caused the DeepRead plug-in to crash.

BUG ID 36249 - ColorLookup: Entering an xexpression then viewing it caused Nuke to crash.

BUG ID 36523 - ZDefocus:Heightdid nothing in thesizecontrol.

BUG ID 36571 - Sony S-Log LUT in root LUTs and the Colorspace node did not take the black point offset into

account.

BUG ID 36673 - Kronos/MotionBlur/VectorGenerator: Results differed depending on the operating system used.

BUG ID 36827 - Stereo: The Viewer didnt update correctly when switching between Single/Interlaced modes.

BUG ID 37137 - Rendering multiple Write nodes simultaneously occasionally displayed a 'Reader did not set

bounding box' error due to too many open files.

BUG ID 37197 - Denoise: The Smoothnesscontrol was not scaled correctly.



13/28

1

BUG ID 37457 - ZDefocus: A customer script crashed when scrubbing in the Viewer at x1 zoom level when the

ZDefocus node was set to use CPU.

BUG ID 37981 - The crwReader leaked file handles, resulting in errors opening .cr2files.

BUG ID 37996 - ModelBuilder: Right-click actions were applied to hidden objects.

BUG ID 38035 - DeepRead: The discreteandpremultiplycontrols were wired up the wrong way around.

BUG ID 38440 - Alembic: Camera horizontal and vertical film back offsets were not measured in cm.

BUG ID 38549 - The right-click Set key on all knobsoption caused buttons to execute.

BUG ID 38682 - Mac OS X Mavericks only: Creating a B-Spline in a Roto node caused Nuke to crash.

BUG ID 38705 - TimeOffSet didnt work with Deep data.

BUG ID 38725 - Alembic: Exports used Acyclic time sampling.

BUG ID 38751 - Alembic: Including custom information in .abcfiles caused Nuke to crash when reading the file.

BUG ID 38791 - Particles: The progress bar showed the wrong amount of progress with a ParticleSettings node in

the tree.

BUG ID 38806 - ZDefocus: The filter aspect ratio slider did not range from 0.5 to 2.

BUG ID 38873 - The Matrix node's ? tooltip was misleading.

BUG ID 38914 - Alembic: Results from alembic cameras looked different in Nuke and Maya, unless you set an

expression on the window_translate.u control.

BUG ID 39001 - Alembic: Changing frame on exported particles caused Nuke to crash.

BUG ID 39209 - Mac OS X 10.9 only: The RotoPaint tools were slow with multiple strokes in the Viewer.

BUG ID 39648 - ModelBuilder: Changing the separationvalue using the virtual slider caused Nuke to crash.

Known Issues and WorkaroundsThis section covers known issues and gives workarounds for them, where appropriate.

Known Issues Specific to 8.0

BlinkScript

BUG ID 39592 - Kernel parameters with spaces in their names do not work when the kernel is reloaded.

As a workaround, remove any spaces in the parameter names. For example, change this line in the kernel:

defineParam(showDetail, "Show Detail", false);

to this

defineParam(showDetail, "ShowDetail", false);

BUG ID 39485 - The Kernel Source textentry field currently loses focus when the cursor moves to another pan



14/28

1

CameraTracker

BUG ID 39606 - Stereo: After placing User Tracks, clicking Autotrack does not track on the first frame.

BUG ID 39604 - The zoom window doesn't always update correctly when moving between frames.

BUG ID 39511 - CameraTracker cannot currently solve lens distortion on single frame.

As a workaround, use the ProjectionSolver by pressing Xin the Node Graph and enteringProjectionSolver as a

TCL command.

BUG ID 39509 - On the AutoTrackstab, clicking Delete Rejected does not remove all rejected tracks.

As a workaround, you can remove the rejected tracks manually by right-clicking them in the Viewer and selecting

tracks>delete selected.

BUG ID 39507 - The enabled/disabled state of tracks in the User Tracks table is inconsistent.

BUG ID 39506 - After solving the camera, the Alt+previous/next keyframe hotkeys do not work

for User Tracks.

BUG ID 39505 - When a track is selected in the Viewer, no hover-over track info is available.

BUG ID 39501 - Increasing AutoTrack threshold controls do not currently allow rejected tracks to be included.

BUG ID 39215 - It is not possible to copy XYZ position values from the User Tracks table unless the track is marked

as a survey point.

BUG ID 39201 - Holding Shiftand clicking User Tracks in the Viewer doesn't add to the current selection.

BUG ID 38381 - Drag selecting and moving multiple User Tracks is not currently possible.

BUG ID 38361 - In Source>Stillsmode, tracking ignores theGlobal frame range specified.

BUG ID 37411 - Sequences containing an alpha channels display the alpha premultiplied by the image in reference

thumbnails, rather than just the RGB values.

In-panel color picker

BUG ID 39373 - Modifying the value of the red channel affects green, blue, and alpha as well when the controls ar

expression linked.

Dope Sheet

BUG ID 39426 - Undoing individually animated text characters removes their keys completely from the Dope

Sheet.

BUG ID 39338 - Clicking the Movebutton for a selection and then undoing the move does not work as expected.

BUG ID 39156 - Keys remapped with descending TimeWarp lookup curves don't snap to frames when frame sna

is enabled.

BUG ID 38910 - Keys from Viewer buffers not currently being viewed are still visible.

BUG ID 38630 - Read and TimeClip representations disappear in the Dope Sheet if they are set to have a non-

empty frame expression.

BUG ID 37869 - The Dope Sheet is not updated correctly when a Retime's speed control is animated.



15/28

BUG ID 37815 - Multiple instances of the same clip within one AppendClip are only represented once in the Dope

Sheet.

EditGeo

BUG ID 38954 - The transform handle of selections in the Viewer is not updated between frames on geometry witanimation baked into its vertices.

To update the transform handle, toggle the axis alignment control between objectandaverage normal.

BUG ID 38699 - Changing the visibility of objects within an Alembic Scene Graph causes geometry to ignore the

EditGeo node.

BUG ID 38670 - Setting a keyframe can be slow to update the Viewer with the appropriate keyframe marker.

BUG ID 36094 - Setting axis alignmentto average normal displays the axis incorrectly on edge and corner

vertices.

Import Nuke BUG ID 38963 - Calling import nuketerminates the Python session if no applicable license is available.

Linux only

BUG ID 39537 - Using a Blackmagic Decklink Extreme 2 card causes Nuke to become unresponsive.

Mac OS X only

BUG ID 39429 - Crash Reporting: The 'save to' dialog is hidden behind the crash report dialog when you click Save

Report.

BUG ID 39350 - Mavericks only: Imported User Tracks are not currently added to the Viewer correctly.

Monitor out

BUG ID 37707 - Viewing 4k footage through a Blackmagic Design DeckLink 4k Extreme causes Nuke to crash.

BUG ID 37700 - AJA Kona LHe+ 2K formats are not displayed correctly.

ParticleCache

BUG ID 39210 - Error messages displayed when read from fileis toggled on and off are not reliably cleared when

rendering through ScanlineRender.

Pixel Analyzer and Scopes

BUG ID 39479 - PixelAnalyser: Switching modeto full framedisables color picking for all color controls in Nuke.

As a workaround, selectmode>pixel selectionbefore using the color picker.



16/28

1

BUG ID 39180 - Scopes: Switching to a layout with a scope window, whilst rendering, forces the Viewer bounding

box to 1x1 for that frame.

BUG ID 36508 - Scopes do not currently update when zooming into the Viewer.

BUG ID 36491 - Scopes clip color values between 0 and 1 when Preferences>Scopes>Include viewer color

transformsis enabled.

Python

BUG ID 39672 - Calling nuke.Layer()currently returns an empty list for built-in channels.

BUG ID 39308 - Accessing a node's x and y positions using the xposand yposcontrols reports incorrect values.

As a workaround, either call nuke.Node.xpos()or nuke.Node.ypos()first, or ensure no nodes are currently

selected in the Node Graph.

BUG ID 38994 - nuke.Node.screenWidth()and screenHeight()are incorrect when a node is first created if it

has an autolabel.

BUG ID 38591 - The update to Python 2.7 was not compiled with SSL support enabled.

QuickTime improvements

BUG ID 39405 - The ProRes422(HQ) codec with pixel formatset to RGBA_16-bit (b64a)is currently reading in

Gamma2.2, rather than the Gamma1.8colorspace.

BUG ID 38908 - Using the ProRes4444 codec with a pixel formatof either YCbCrA 8-bit 444 Biased (r408) or

YCbCrA 32-bit 444 Float (r4fl) does not produce the alpha channel correctly.

As a workaround you can use either the RGBA 8-bit or RGBA 16-bit (b64a)pixel format.

ScanlineRender

BUG ID 38329 - Deep renders from ScanlineRender currently ignore the ScanlineRender's bginput.

BUG ID 38205 - Deep: Depth, motion, position, and normals information is occasionally incorrect in semi

transparent areas.

BUG ID 37967 - Deep: Geometry with alpha 0 renders black when the deep output is converted to an image.

Text

BUG ID 39556 - In text editmode, it is not currently possible to edit text attributes when the Viewer overlay is

disabled.

BUG ID 39552 - Transforming animation groups using an expression-linked Transform node does not work as

expected.

As a workaround, expression link the translate xandycontrols separately.

BUG ID 39483 - Highlighting text in the messagefield and Viewer is not always synchronized correctly.

As a workaround, scrub the playhead to a different frame to update the highlighted text.

BUG ID 39414 - Text entry in the messagefield occasionally requires multiple undo operations to remove text.



17/28

BUG ID 39291 - Splitting the transform control on the Group tab splits all controls.

BUG ID 39271 - Japanese characters cannot be entered directly in the Viewer.

As a workaround, enter characters using the messagefield.

BUG ID 39239 - Transforming a character generated from an expression, and then going to a frame where the

character no longer exists, results in the transformation being lost.

BUG ID 39130 - Splitting the messagefield does not work as expected.

BUG ID 38789 - Viewer toolbar controls steal cursor focus.

BUG ID 38425 - The undo history becomes unreliable when the panel focus changes.

BUG ID 37119 - Typing text in the properties panel messagefield always uses the default font settings.

BUG ID 36372 - Selecting a TCL expression in the messagefield doesn't always select the result in the Viewer.

Tracker

BUG ID 39200 - Holding Shiftand clicking tracks in the Viewer doesn't add to the current selection.

BUG ID 38356 - The zoom window occasionally doesn't update correctly when scrubbing between frames.

Windows only

BUG ID 39394 - CameraTracker: Importing a User Track created on another operating system causes Nuke to

become unresponsive.

Exporting from Windows to other operating systems works as expected.

BUG ID 35800 - Scopes: The alpha channel doesn't update correctly when modified through a node, such as

Primatte or Shuffle, even after the node is removed from the Node Graph.

Miscellaneous known issues

BUG ID 39651 - Adding MotionBlur after a Convolve with no filter causes Nuke to crash.

BUG ID 39637 - Adding a Transform node downstream of certain .exr Read nodes and enabling auto alpha or

raw data in the Read properties causes Nuke to crash, if the the Transform is scaled on both the x and y axis.

BUG ID 39557 - Writing .exrs with 200+ layers, when interleaveis set to channels, can be sluggish.

BUG ID 39459 - Virtual Sliders: Clicking the left mouse button, while holding down the middle mouse button,

pastes values into the control.

BUG ID 39407 - Project3D: The node class name has changed to Project3D2. As a result, the NukeMari bridge

won't work unless all instances of Project3D are renamed appropriately in the mari_bridge.pyfile.

BUG ID 39287 - Plug-ins: Loading scripts with plug-ins compiled against older versions removes the nodes from

Node Graph.

BUG ID 39165 - ReadGeo: When reading in .fbxfiles, the transform/scale state can become incorrect whilst

toggling the read transform from filein combination with all objectsand/or read on each frame.

BUG ID 39122 - Switching the Viewer to wipemode and wiping between inputs with different format sizes causes

corruption and constant refreshing in the Viewer.



18/28

1

BUG ID 38929 - File Browser: Items in the favorites/file list get highlighted incorrectly on mouse over.

BUG ID 38713 - Capture: Roto opacity and feather settings are not included in captured images.

BUG ID 35661 - Capture: Capturing the Viewer with a custom file path saves the file path in the script, resulting in

error when the path doesn't exist:

Flipbook render failed: viewerCaptureOp: Cannot write to specified path

BUG ID 35659 - Capture: Capturing a 3D scene containing lights produces Viewer flashes in the captured images.

BUG ID 35614 - For EXR 2.0 files to be backwards compatible with earlier readers, the layer names must not excee

32 characters in length.

As a workaround, open the .exr in Nuke 8.0 and manually (or Pythonically) truncate the names to allow for legal

backwards compatibility.

BUG ID 35611 - Writing .exrs with the Write node's interleavecontrol set to channelsadds a superfluousmain

view.

Other Known Issues

AudioRead

BUG ID 18924 - Changes to the ratecontrol value are not honored whenratesourceis toggled between fileand

custom.

BUG ID 18666 - Changing the sample rate has no effect on playback in a Flipbook.

BUG ID 18465 - The time rangecontrol doesnt limit the range when anendtimeis specified.

BUG ID 18451 - Flipbooking doesn't honor the time range knob.

BUG ID 18217 - Redo keyframe generation doesn't replace the keys. BUG ID 18213 - Changing Draw Stylein the Curve Editor or Dope Sheet doesn't redraw the curves correctly.

FrameCycler

BUG ID 17199 - There aren't appropriate LUTs in 6.2v3 for flipbooking some colorspaces including rec709, Gamm

1.8, Gamma 2.2, Panalog, REDLog, ViperLog and REDSpace. As a workaround, you need to selectBurn in the LU

in FrameCycler for an authentic color reproduction.

BUG ID 15204 - There are currently some graphical glitches occurring when flipbooking certain images. The

workaround is to change the cache precision in FrameCycler. To do this, bring up the settings menu in FrameCycle

(press S), go to Options>Cacheand change theCache precisionoption to either 16 bit floator 8 bit int + 16bit float.

BUG ID 15046 - Flipbooking to FrameCycler with images greater than 4K in width, and with a non-1 pixel aspect

ratio, skews the images (in FrameCycler). This is an issue with FrameCycler 2009, and we are awaiting a fix.

We direct FrameCycler to write to the users Nuke temp directory (NUKE_TEMP_DIR) for its user settings files. You

can redirect this by modifying the FrameCycler/settings/Global_Settings.xml file that can be found within your

Nuke installation.



19/28

1

Flipbooking with FrameCycler 2009 may not work on some older Intel and AMD processors with certain graphics

card configurations. You can set the FC_PATH environment variable to point to a previous version of FrameCycler

(that is FrameCycler 2008 found in Nuke 6.0v7). For information on setting environment variables, please refer to

the Configuring Nukechapter in the NukeUser Guide.

For example, you can point FC_PATH to the following locations (check the correct path to the installation on your

machine):

Mac:

/Applications/Nuke6.0v7-32/Nuke6.0v7.app/Contents/MacOS/FrameCyclerOSX/bin/FrameCycler

Windows:

Program Files\Nuke6.0v7\FrameCycler\Windows\bin\FrameCycler.exe

Linux:

/usr/local/Nuke6.0v7-32/FrameCyclerCentOS4.4/bin/framecycler

NOTE: Please [email protected] if you need older versions of The Foundry software.

Linux only

BUG ID 31431 - Linux only: The current version of the FFmpeg library used by Nuke reads the height of HD.mov

files at 1088, rather than 1080.

As a workaround, use a Reformat node to force the input to the correct format.

Mac OS X only

BUG ID 39288 - QuickTime: Limiting the number of helper processes, using the Preferences>QuickTime>reader subprocess limitdropdown, can cause read errors.

BUG ID 38686 - Enabling Use GPU if available on supported nodes, such as Kronos, in more than one instance of

Nuke at the same time, can cause display corruption and/or entire system freezes. This seems particularly likely to

occur on GPUs with low amounts of RAM, such asthe GeForce GT 650M.

As a workaround, only enable GPU acceleration in one instance of Nuke at a time.

BUG ID 35123 - PrmanRender: If you're using Mac OS X 10.8 (Mountain Lion) or above, make sure X11 is installed

on your system. Unlike previous versions of OS X, 10.8 and above do not have X11 installed by default.

For more information, see http://support.apple.com/kb/HT5293 .

BUG ID 34697 - Launching Nuke from a network shared drive causes Nuke to crash on launch.As a workaround, either:

tarball the installation from Mac OS X and unzip it on the alternate file system (using NFS or Samba, dependin

on source), or

using the command line, copy the installation from Mac OS X to the network location using the same file

system as the destination.

BUG ID 33970 - Using a node, such as Grade, as a custom viewer process outputs a blank Viewer.

http://support.apple.com/kb/HT5293mailto:[email protected]


20/28

2

As a workaround, adjust the Viewer gaincontrol to refresh the Viewer.

BUG ID 22062 - Nuke doesn't currently give the option to restore the autosave of an unsaved script, except when

Nuke is run from the command line.

BUG ID 13638 - The following graphics cards are not currently supported for Mac:

ATI Radeon X1600

ATI Radeon X1900

Users with these cards will be able to render from the command line, but in GUI sessions, the Node Graph will

render incorrectly due to a requirement of OpenGL 2 drivers.

BUG ID 12048 - Nuke crashes if you activate screen sharing when there is no screen plugged in.

BUG ID 11776 - Node text appears aliased, unclear, or garbled at certain zoom levels.

ModelBuilder

BUG ID 33053 - Using the Face Selectiontool in the 3D Viewer disables the Scale handles (Ctrl/Cmd+Shift).

As a workaround, press F to fit the contents to the Viewer and then move the Viewer to a different angle before

activating the Scale handles.

Particles

BUG ID 18268 - Enabling color from texturealways renders a solid white alpha for the texture.

BUG ID 17520 - Geometry representation textures are displayed even when displayis set to off.

BUG ID 17243 - Using sprites instead of geometry representations causes particles to render behind the 3D grid

lines.

PlanarTracker

BUG ID 33254 - PlanarTrackers Roto node defaults to the Select all tool rather than Bezier. If you click on the

Viewer, then change the tool and draw a shape, your shape is added to the rootlayer instead of

PlanarTrackerLayer1. This means its not considered for tracking, and tracking fails.

The workaround is to:

make sure PlanarTrackerLayer1is selected in the Roto properties,

change to one of the shape tools before attempting to draw in Viewer, and

in the Roto properties, make sure a purple rectangle appears in the PTcolumn to indicate that the shape is

considered for tracking.

BUG ID 19683 - After adjusting the planar surface using the Correct PlaneViewer button, you have to undo twic

for the planar surface to return to its original position.

BUG ID 19563 - Detected or tracked features are not offset by the origin of the input image's bounding box.

To avoid this, you can add a Crop node before PlanarTrackers associated Roto node.

BUG ID 19240 - When Viewer downrezis greater than 1, theclearTrackDataForward button currently offsets

bezier shapes to fit the root format.



21/28

To return the shape to its original size and position, advance the sequence one frame.

PrmanRender

BUG ID 27648 - After a security update for Mac OS X, Nuke is unable to load the PrmanRender plug-in when in GU

mode.See http://support.apple.com/kb/HT5281 for more information.

As a workaround, set the following environment variables:

export RMANTREE=/Applications/Pixar/RenderMan.app/Versions/RenderManProServer-15.1

export DYLD_LIBRARY_PATH=$RMANTREE/lib

Then launch Nuke from the command line.

In the Nuke camera, the window roll control is not yet mapped to RenderMan.

Python

BUG ID 8063 - Creating many new nodes with nuke.createNode()and the in-panel argument at default(True)

may crash when too many node control panels are created too quickly. The workaround is to pass the in-panel

argument as Falseor else use nuke.nodes.NodeClass() (where NodeClass is the type of node to create) to creat

the node and then connect it to the currently selected node manually.

BUG ID 6455 - You should not call the Python command nuke.restoreWindowLayout()from the Script Editor a

that can cause Nuke to crash. Instead, you can use the same command from your menu.py, restore layouts by

selecting Layout>Restore Layout, or use a custom menu or toolbar item.

Nuke sometimes reports errors in Groups and Gizmos, appearing similar to the following:

groupName.NodeName.knobname: unexpected 'k' in '0.knobname'

The problem is most likely that there is an expression that is using the input TCL command and doesn't validate

that there is an input connected. An example expression:

[input parent 0].translate.x

The input command returns 0 when it can't find the requested input, which generates an expression of

'0.knobname' that doesn't refer to anything. The fix is to restructure the expression to use the value TCL

command and specify a default value to return in the case that the expression is invalid. It takes the form:

[value [input parent inputnumber].knob defaultValue]

Here is the modified example:

[value [input parent 0].translate.x 0]

The modified example returns 0 in the event that there is no input 0, and no longer result in an error message.

There is a Python syntax conflict when assigning knob names on the fly with nuke.nodes.()if the knob is

called 'in'.

For example, this gives a syntax error:

nuke.nodes.Shuffle(in = 'depth')

while this works because 'in' is a string here and not a keyword:

sh = nuke.nodes.Shuffle()

http://support.apple.com/kb/HT5281


22/28

2

sh['in'].setValue('depth')

QuickTime ProRes 4444

BUG ID 17360 - Some customers have experienced unexpected shifts in chroma values when using the ProRes

4444.movcodec.A possible workaround is to modify the GlobalSettings.csvfound in the following locations:

NOTE: Please be aware that this workaround is not reliable in every case.

Mac OS X

/Applications/Nuke7.0v6/Nuke7.0v6.app/Contents/Resources/

Windows

C:\Program Files\Nuke7.0v6\

Add the following lines to the bottom of the .csv file:# Apple ProRes 4444

encode,ap4h,appl,any,any,512

decode,ap4h,appl,any,any,512

Render codecs

There have been issues where rendering with certain codecs makes Nuke crash. Due to this, we recommend the

following:

If you're using the Sorensen Video codec, it's recommended you use the Sorensen Video 3 codec instead. If you're

unable to switch to Sorensen Video 3, try using a format smaller than 2K for better performance.

If you're experiencing crashes with Cineform HD, try updating your Cineform codec to version 5 or above. You ma

need to download the Neoplayer athttp://estore.cineform.com/neoplayer.aspx.

If you're using Avid Meridien, you should only write out in NTSC and PAL.

Roto/RotoPaint

BUG ID 32459 - RotoPaint: Undoing a point move that created a keyframe doesn't currently undo the keyframe

creation.

BUG ID 32450 - RotoPaint Stereo: Attempting to undo mulitple split-control transforms on the same shape revertthe shape to its original position.

BUG ID 31552 - Point handles for paint strokes, whose lifetime doesnt extend to the current frame, disappear

when drag-selected.

As a workaround, select the shape in the curveslist to re-display the points.

BUG ID 30920 - Expression linking extra matrices in the Transform tab doesnt work as expected.

http://estore.cineform.com/neoplayer.aspx


23/28

2

NOTE: This also applies to SplineWarp matrices.

BUG ID 30551 - Several levels of smoothing applied to one shape are carried over to subsequent shapes for a

single smooth operation.

BUG ID 29170 - The cut, copy, and paste keyboard shortcuts don't work for entries in the curveslist.

BUG ID 28838 - Gizmos from Nuke 6 containing Roto/RotoPaint nodes should be recreated in Nuke 8, but bear in

mind that they wont be backwards compatible with Nuke 6 once converted, unless you follow the instructions

below:

Nuke 6 scripts containing Roto display a conversion prompt when you open them in Nuke 8:

Click Save Asto convert the script to the Nuke 8 Roto format, or

Click Ignoreto load the Nuke 6 format into Nuke 8. You might select this option if:

- You don't intend to make any changes, or

- You want to overwrite the file with a Nuke 7 and 8 only Roto format when saving.

If you want Nuke 8 scripts to load in Nuke 6, use the convertToNuke6or convertDirectoryToNuke6Pythonfunctions when running Nuke 8 in terminal only mode:

NOTE: The conversion functions cannot convert stereo-split curves as they are not supported by Nuke 6.

To convert individual .nk scripts:

convertToNuke6(fromScript, toScript, overwrite = False)

To convert all .nk scripts in a given directory:

convertDirectoryToNuke6(fromDir, toDir, matchPattern =.*\.nk, overwrite = False)

NOTE: The pattern is a regular expression.

An example single script conversion and rename to the same directory, from the command line (terminal):

$ /Nuke8.0v1 -t

>>> import nuke.rotopaint

>>> nuke.rotopaint.convertToNuke6(/tmp/myRoto8.nk, /tmp/myRoto6.nk)

BUG ID 26855 - The undo and redo buttons in the properties panel didnt work as expected and have been

disabled.

The workaround is to use the undo (Ctrl/Cmd+Z) and redo (Ctrl/Cmd+Y) hotkeys or the Editmenu instead.

BUG ID 11524 - Adding strokes/shapes in RotoPaint is slow when there is another RotoPaint after it.

BUG ID 9238 - Painting on Mac OS X and Linux is slower when the paint cursor is near the edges of the screen.

The foreground onion skin overlay updates as you paint. This will change so the overlay only updates with the new

stroke on pen up.

It is not currently possible to clone RotoPaint nodes.

Interactivity of laying down strokes/shapes in the Viewer may be faster when motion blur is disabled on the layer

you are working in.



24/28

2

Tracker

BUG ID 39225 - Moving tracking anchors is occasionally unresponsive and jerky.

BUG ID 32353/32359 - Right-clicking on a point in the Viewer doesnt always update the available Link to >

Tracker linking dialogor Tracker options.As a workaround, close and re-open the Roto/RotoPaint Properties panel to update the Link to menu.

BUG ID 30116 - Adding tracking anchors with an OFlow node upstream of the Tracker causes Nuke to become

unresponsive.

BUG ID 29382 - Tracking keyframes with different sized patterns doesnt work as expected.

As a workaround, keyframe patterns should, where possible, be of comparable sizes.

Warpers

BUG ID 32340 - SplineWarp:Ctrl/Cmd drag-creating rectangles and ellipses doesn't display an overlay until pen-u

BUG ID 32083 - SplineWarp: Deleting all but one point on a curve resets its correspondence points to 0,0, which

cannot be undone.

BUG ID 32082 - SplineWarp: Correspondence points are too sensitive to when control points are removed.

BUG ID 32079 - SplineWarp: Moving correspondence points on curves with no keyframes cannot currently be

undone.

BUG ID 30429 - SplineWarp: Transform links are not maintained when the source curve is moved to a new layer.

BUG ID 31322 - SplineWarp/GridWarp: Preview doesn't handle upstream transforms correctly.

BUG ID 20000 - GridWarp: When using cropped input, moving control points causes the Viewer to display the

cropped image and the black area between the crop box and the format when merged over a background.

BUG ID 19995 - GridWarp: Locked source and destination grids still allow adding and removing grid lines.

BUG ID 19835 - SplineWarp/GridWarp: The Viewer LUT is incorrect in morphmode, when mixis set at an

intermediate value.

BUG ID 19755 - SplineWarp: Placing correspondence points at each end of an open spline causes rendering

problems.

BUG ID 19565 - GridWarp: The Viewer does not show the correct mix amount when in morphmode with mixset

at an intermediate value.

BUG ID 19386 - GridWarp: All keyframes are removed from the Dope Sheet after undoing, rather than just the

latest, and the keyframes remain on the timeline and in the Properties pane.

BUG ID 19148 - SplineWarp: Rendering fails if a curve is reduced to a single point.

BUG ID 19079 - SplineWarp: The C hotkey does not currently select the Add Correspondence Pointtool.

BUG ID 18712 - GridWarp: The timeline currently shows both source and destination keyframes, even if a grid is

not visible in the Viewer.

BUG ID 18709 - GridWarp: Rotating the transform jack with both grids selected, but in different positions, does no

undo as expected.

BUG ID 18342 - SplineWarp: The spline keyframe + button does not add keys to the Curve Editor or Dope Sheet.



25/28

2

BUG ID 18304 - GridWarp: Existing control point keyframes are not cleared when you draw a new grid using the

Draw BoundaryViewer button.

BUG ID 18019 - GridWarp: You cannot select all grid points in the Curve Editor using Ctrl/Cmd+A shortcut.

BUG ID 18012 - GridWarp: The grid can flicker between white and grey when zooming in and out of the Viewer,

particularly when the grid is subdivided.

BUG ID 17697 - GridWarp: In stereo mode, the right view is labelled as defaultwhen you split controls into

separate views.

Windows only

BUG ID 35284 - Exiting Nuke can be unacceptably slow, causing issues for render farms.

Set the environment variable NUKE_USE_FAST_ALLOCATOR to 1 to workaround this issue.

BUG ID 30903 - Some scripts render significantly slower on Windows than on Linux.

Set the environment variable NUKE_USE_FAST_ALLOCATOR to 1 to workaround this issue.

BUG ID 28921 - Changing the 3D selection mode does not update until you click in the Viewer.

Miscellaneous known issues

BUG ID 39365 - The Viewer properties headlamp control can not currently be managed using expression links.

BUG ID 39260 - Custom knobs on Groups and NoOp nodes cannot be retimed.

BUG ID 35976 - Some CUDA code runs in render mode, even when the --gpuargument is omitted.

You can disable all CUDA code by setting the FN_NUKE_DISABLE_CUDA environment variable to 1.

BUG ID 33863 - FBX geometry: Faces on geometry read in from .fbxfiles are not connected to neighboring faces,

leaving gaps in certain circumstances.This issue is particularly visible when using the EditGeo node, which should not allow you to remove faces from th

geometry.

BUG ID 32856 - PositionToPoints: Textures occasionally disappear during playback or when mousing over the

Viewer.

BUG ID 32666 - FrameHold nodes have no effect on Deep nodes.

BUG ID 32628 - DeepToPoints: Command line rendering appears to calculate renders even when render is set to

off.

BUG ID 32497 - The R3D parameter labels in Nuke arent entirely consistent with REDCINE-X and Hiero.

BUG ID 32219 - DepthToPosition: Reading depth information from the same layer as the output layer producescorrupt output.

As a workaround, shuffle the depth information to an alternate layer.

BUG ID 32118 - Card3D: When motionblur is enabled in the properties panel, FrameHold and TimeOffset nodes

are ignored when connected to the cam or axisinputs.

BUG ID 31803 - Using Shift+drag on a controls animation icon only copies the value for the current frame, not th

entire expression.



26/28

2

BUG ID 31714 - In the Viewer settings, enabling 3D>show_prim_bboxdoes not display individual bounding

boxes for polymesh primitives.

BUG ID 31310 - TimeOffset: Checking reverse inputdoesnt affect cameras, lights, or axes.

BUG ID 31238 - RAM cache: Any action that changes a frames hash value, its unique identifier, causes the cache t

release. Actions such as adjusting the Viewer Gamma, Gain, or channelsdropdown affect the frame hash.

BUG ID 30502 - Copying and pasting spline keys does not work as expected in the Dope Sheet.

NOTE: This known issue only applies to Roto and SplineWarp keys.

BUG ID 30256 - Script Editor: Flagging a control as invisible using setFlag()is not honored when the node is

copy/pasted in the Node Graph.

BUG ID 30173 - Manipulating 3D handles in the 2D Viewer is unreliable.

BUG ID 29677 - Connecting a FrameHold node to an animated Camera and connecting both to a Scene node only

displays the animated Camera in the Viewer. There should be two cameras: one static and one animated.

BUG ID 29083 - Using Create Camera in the 3D Viewer only sets position and rotation. The focal lengthof thenew camera does not match that of the Viewer camera.

BUG ID 29048 - OCIO: Using the ocionuke library in terminal mode results in an error.

BUG ID 28291 - Nuke crashes on startup if the disk cachelocation set in thePreferencesis no longer available.

BUG ID 27211 - Alembic: The state of the Viewer Lock Framecontrol is not always honored for .abcfiles.

As a workaround, ensure thatReadGeo >read on each frameis enabled.

BUG ID 21663 - Read: After reading in a stereo/multiview .exr file and choosing not to add new views to the

project, subsequent reads of any stereo/multiview .exr files wont give the option to add new views.

BUG ID 20431 - CameraTracker: Its not possible to pick colors in the Viewer with the control panel open.

BUG ID 20204 - Multitexturing: When Preferences>Viewers>Multiframeis enabled, increasing downrezinthe Viewer toolbar can cause textures to flicker in the 3D Viewer.

You can switch back to Classicmode or avoid using proxy in 3D to workaround this issue.

BUG ID 19933 - ReadGeo: Geometry occasionally doesn't display as a solid until you click in the Viewer.

BUG ID 19185 - Attaching an FBX ReadGeo to the Viewer occasionally causes a slight graphical glitch in the

Properties pane.

BUG ID 18649 - The transform jack is currently scaling incorrectly from the corner pivot point.

BUG ID 12505 - Motion Vector output has been improved, but still doesn't work properly because some large

polygons are clipped by the front camera plane.

You can minimize this effect by increasing the geometrytessellation maxparameter.

BUG ID 12424 - Ultimatte: Overlays are not updating correctly or reverting when panning or zooming.

BUG ID 11620 - In the 3D Viewer, there is currently a conflict between 3D geometry selection and points drawn

with RotoPaint. This only occurs if you have two Viewers open, one in 2D mode and the other in 3D mode, and yo

have the panel for the RotoPaint visible.

BUG ID 9521 - Currently, the Nuke Viewer cannot cache very large plate sequences in float. The limit per frame is

50MB. If your frames are larger than this, you may need to switch to proxy mode for the caching to work.



27/28

2

BUG ID 5922 - At the moment, cloning does not work properly with all OFX nodes. This affects, but is not restricte

to, any nodes that have an analysis pass.

BUG ID 5690 - Windows run-time libraries are not packaged properly with Nuke.

Nuke runs correctly from a network install on Windows without specifically installing the run-time libraries, though

we still recommend that you do so as there will still be some minor problems without them. For details, please see

Installation on Windowsin the Installation and Licensingchapter of the Nuke User Guide.

BUG ID 5083 - Flipbooking the output of the Anaglyph node asks which view you want to render. This question is

unnecessary as the result is an anaglyph image. Irrespective of what view you choose, the flipbook output is the

same.

File types in Windows and Mac OS X are associated with the standard version of Nuke by default, so if you save a

script on NukeX using features that are only included in NukeX (such as CameraTracker or FurnaceCore) and then

double-click on the script icon to open it, it will open in standard Nuke instead of NukeX.

If you have trouble with FBX files, it may be because they were written with an older version of FBX. If they load

very slowly, it is also possible that they are ASCII rather than binary. To get around these problems, you can use th

FBX converter on the Autodesk web site. It converts between various different formats, including older FBXversions, ASCII, and binary, and is available on Windows, Mac OS X, and Linux.

To download the FBX converter:

1. Go to http://usa.autodesk.com/adsk/servlet/pc/item?siteID=123112&id=10775855.

2. Scroll down to FBX Converter and click on one of the links to start the download.

CameraTracker: Canceling lens distortion initialization results in corrupt tracks.

3D Camera: If you want to navigate through the 3D point cloud created by the CameraTracker node when using

Create Scene:

Select the Camera that was created in the 3D view when using the Create Scenebutton.

Press F to focus on the selected Camera. You can now navigate around the cloud. Do not try to focus (using F) onthe point cloud. The resulting tumble camera movement is likely to be jumpy.

Plug-ins installed using the Nuke Plug-in Installer may not work correctly as they were complied against an earlier

version of Nuke.

Developer Notes

Here are the changes relevant to developers.

NOTE: SeeHelp >Documentationfrom the Nuke menu bar for more information.

New Features Nuke now includes the Blink API enabling you to use the Blink framework inside an NDK plug-in. For more

information, see the following resources:

http://usa.autodesk.com/adsk/servlet/pc/item?siteID=123112&id=10775855http://usa.autodesk.com/adsk/servlet/pc/item?siteID=123112&id=10775855http://usa.autodesk.com/adsk/servlet/pc/item?siteID=123112&id=10775855http://usa.autodesk.com/adsk/servlet/pc/item?siteID=123112&id=10775855


28/28

2

The Blink API: Available from a Nuke install in /Documentation/Blink/index.html

Blink Kernels: http://docs.thefoundry.co.uk/nuke/80/BlinkKernels/

Feature Enhancements BUG ID 39309 - You can now access private variables to subclasses of NukeWrapper.

Bug Fixes BUG ID 15737 - nuke.Node.screenWidth()and screenHeight()were zero when a NoOp node was first created

BUG ID 21471 - Calling nuke.cancel() in a Write nodesbeforeFrameRender field produced corrupt output whe

writing .exr files.

BUG ID 26136 - Calling nukescripts.create_read()didnt detect deep sequences as deepRead.

BUG ID 28510 - Calling nuke.menu('Nodes').shortcut()caused Nuke to crash.

BUG ID 29712 - RotoPaint: Calling_curveknob.Layer.insert() inserted in the wrong location.

BUG ID 32947 - Setting views with Python returned no result when deleting all of the views, then add a single view

BUG ID 33310 - Calling nuke.cancel() in a Write node did not cancel the current render operation when writing

.exr files.

BUG ID 33872 - Windows only: ZDefocus and Convolve FFTs were single-threaded.

BUG ID 34003 - Calling nuke.localiseFilescaused Nuke to crash.

BUG ID 34337 - Calling File_Knob.evaluatecaused a segmentation fault with view=None.

BUG ID 36273 - Calling nuke.root().setName( name )crashed Nuke when a script didnt have a name.

http://docs.thefoundry.co.uk/nuke/80/BlinkKernels/

Documents

Nuke 8.0v1 ReleaseNotdes