Contact Us

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. The conversion functions cannot convert stereo-split curves as they are not supported by Nuke 6. Nuke 6 scripts containing Roto display a conversion prompt when you open them in Nuke 8: When enabled, Nuke does not skip scanlines when rendering in the Viewer. Attempting to undo mulitple split-control transforms on the same shape reverts the shape to its original position.

Ask a Question

Unconnected sets of still frame thumbnails were not highlighted in the Viewer. Dragging and dropping a. It was not possible to solve single frames from survey points with rotation only.

Placing User Tracks before setting reference frames in stills sequences ignored the frames containing the User Tracks during tracking. Solving known survey points using rotation only failed to match any points.

Clicking Solve added keyframes to all frames, even when the solve failed. Clicking Update Track failed to solve new tracks in certain stills sequences.

Solving a single frame with Camera Motion set to Rotation Only failed and displayed a Failed to calculate all frames for the shot warning. User Tracks did not update when Undistort Input was enabled.

The trial license dialog prompted for a username rather than email address. Nudging points using the numeric pad arrow keys caused Nuke to crash. The Use Server field did not behave consistently with other fields in the Licensing dialog. Requesting output for a single channel, other than forward.

The Swirlomatic example in the documentation caused Nuke to crash. SSL was not working in QT webview. It can be used to get information from QuickTime files including the video's width, height, and video frame count, as well as the file and codec metadata and per-frame SMPTE M camera position data stored in ProRes files: PyZMQ and zeromq have been added to the Nuke bundle.

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: You must install a floating license and additional software on the license server to use this option.

This change has been reverted to restore compatibility with Nuke 8. The ReadGeo use geometry color control did not default to disabled. There were two pages missing from the bundled documentation regarding Sample Source Code.

On Windows, you may have to add a firewall program or port exception to view the most up-todate help from our website. If the connection is blocked, Nuke falls back to the local copy. Developer Notes Here are the changes relevant to developers.

New Features There are no new features in this release. Layer returned an empty list for built-in channels. Please see the Nuke User Guide Appendices for more information. Nuke's Write node now includes a Truncate channel names control for. When enabled, layer names are truncated to 32 characters for backward compatibility with EXR 1. The warning message regarding non-connected frames in Stills tracking mode has been improved. 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. After saving your preferences, close and then re-open the BlinkScript properties panel to apply the changes. 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.

ReadGeo now has a use geometry colors control. When enabled, geometry color attributes are read from. The addition of this control may cause differences in rendered output when compared to previous versions of Nuke. If this occurs, enable use geometry colors in the ReadGeo properties panel. Alpha was automatically added on Mac and Windows when it shouldn't be. Painting in the Tracker window caused Nuke to crash. Typing text in the properties panel message field always used the default font settings.

When the pixel format control was set to default for the Animation codec , the ycbcr matrix control was not disabled. Selecting an animation group did not highlight characters in the Viewer or message field. Drag selecting and moving multiple User Tracks was not possible. Undistorting the input in Proxy mode stretched the features overlay abnormally.

The b64a pixel format did not behave as expected. Exporting certain data to a Tracker node was unreliable. Holding Shift and clicking User Tracks in the Viewer didn't add to the current selection. It was not possible to copy XYZ position values from the User Tracks table unless the track was marked as a survey point. User Track paths did not update in the Viewer when deleting keyframes.

Importing a CameraTracker User Track created on another operating system caused Nuke to become unresponsive. Creating a ModelBuilder node without a NukeX license displayed warnings about missing knobs. The Kernel Source field lost focus when the cursor moved to another panel. When a track was selected in the Viewer, no hover-over track info was available. The Blackmagic RGB 10 bit r codec did not default to the b64a pixel format.

DirectDraw Transfer codecs were not blacklisted for 2vuy codecs. Transform handles required multiple undos in scripts containing QuickTime Read nodes. Kernel parameters with spaces in their names did not work when the kernel was reloaded.

Changing the separation value using the virtual slider caused Nuke to crash. Survey solves on single frame reported 'insufficient frames' if the survey points were keyed on a different frame. Adding a Transform and reversed Retime after a Text node containing an expression caused Nuke to become unresponsive. Character transformation information was not saved properly when an expression was present in an animation group. 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.

Keyframe selections were occasionally lost when scaling keys in the Dope Sheet. Navigating to a frame outside the rendered frame range caused Nuke to crash. Clicking Breakout Layers for a. Clicking Capture this viewer did not work as expected.

Geometry imported from Maya did not carry over the correct vertex colors. Moving data between Tracker and Roto occasionally produced odd glitches and random values in certain controls.

Marquee selecting multiple points on an animated curve caused the points to revert to their original positions. Changing the cursor position in the Viewer didn't update the cursor position in the message field. Certain Alembic geometry rendered black. Using the Avid DNxHD codec with certain pixel formats caused darkening or frame locking when the timeline was scrubbed. Nuke displayed the old icons for the Applications menu and desktop shortcut icons.

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. Click here to launch the online help page. BlinkScript A new BlinkScript node has been added. It streamlines plug-in development workflow significantly, as you no longer have to exit Nuke to compile your code. The Publish button, on the Kernel Parameters tab, 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 node, 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 Publish button, 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.

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. Crashes in terminal mode are automatically submitted when crash handling is enabled.

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: You also assign User Tracks as 3D Survey Points to improve solve accuracy or link solves to the same world coordinates.

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? 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.

You can still display the tooltip by hovering over the? Click here to launch the online help. The keyframes are displayed in context, allowing you to shift keys more easily within the Dope Sheet from their remapped positions. EditGeo Nuke now includes an EditGeo node allowing you to select and edit geometry or point cloud vertices and faces in the 3D Viewer. Import Nuke A new import nuke function 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. The Foundry cannot provide customer support for third-party Python interpreters. Blur to add a Blur node available in the interpreter. 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.

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.

First set the matching task then key reference frames that pick out the characteristic colors in each sequence. Then click Analyze Reference Frames to calculate the grade. Select Auto-analyze per frame when the task is set to Match Graded Source to enable this.

There is the option to manually set CDL parameters and recalculate the best fit transform. MatchGrade can be found in the Color menu.

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.

Multi-part EXRs allow you to read individual channels, layers, and views within an EXR file without unpacking all the parts contained within it. ParticleCache The ParticleCache node allows you to write particle systems to file and read them back in to alleviate the constant reevaluation 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 padding control to set the number of frames to extend the sequence by, at both start and end.

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 Particles menu. Pixel Analyzer and Scopes A Pixel Analyzer panel has been added to the contents menu, allowing you to collect color information from pixels in the Viewer.

The analyzer has three modes: You can drag the marquee around to sample different areas and adjust its size using the handles in the Viewer. Click here to launch the online help page for the Pixel Analyzer or here for the Scopes help.

Nuke also writes out user metadata depending on the specific settings used outside of the nclc and gama atoms and ProRes header and Hiero has been set to use these if it finds them in the. You can manually override the following mov Options in the Read node properties panel: You can choose to use the new Rec and Rec or the Legacy encoding methods, which are the methods used previously in Nuke.

The codec dropdown defaults to a codec appropriate for the QuickTime in question, where available, and only lists those that declare themselves able to read the file. 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.

Setting the Write node properties file type to mov allows you to override the same QuickTime controls as the Read node, except that the pixel format dropdown is populated depending on the codec chosen. The font dropdown includes system fonts by default.

Hover over a control, click the middle mouse button, then drag the field to adjust the associated control. Hold Shift to increase slider sensitivity. The new filters are especially useful for down-scaling images without excessive softening: The filter numbers at the end of the filter name denote the width of the filter, similar to the naming scheme used by PRMan http: 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. Capture this Viewer is located in the Viewer pane, adjacent to the Flipbook this Viewer button. When enabled, Nuke does not skip scanlines when rendering in the Viewer. AJA monitor out cards are not currently supported on Linux. A new also merge dropdown has been added to the properties panel allowing you to merge additional channel sets. Copyrights belongs to Bitstream Inc.

Ogawa support has been added read and write operations. The Viewer now has a visual reference when operations are in progress, such as extrude and bevel. 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. You can now use custom file extensions for Deep. For example, adding an odzReader.

You can now flip object or face normals in object and face selection mode by rightclicking in the Viewer and selecting flip face normals. 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.

A new Update Solve button has been added, allowing you to resolve a range of frames within an existing solve, instead of recalculating the entire sequence. A new Output dropdown has been added to the properties panel allowing you to select what is displayed in the Viewer: Source, Target, or Matched. Closing the properties panel did not hide the transform jack overlay in the Viewer. Valid rgba alpha channels were not included in alpha-supporting Quicktime codecs, such as Prores and Animation.

Persistent preview always showed rgb when applied to other channel sets. Particle systems could not be rendered. Selecting no animation on all knobs added a keyframe on the current frame.

White alpha channels were created from rgb only inputs. Moving the analysis region updated before you finished moving it. Enabling all objects in the properties panel showed objects in the Viewer with either a translate or rotate offset. Changing the file type from a static.

The F hotkey did not center on the selected object in the 3D Viewer. Selecting an object in the Viewer did not select the corresponding entry in the in the Scene list and vice versa. Using the ocionuke library in terminal mode resulted in an error.

Snapping transform handles to the object surface automatically caused problems with the scaling behavior. Keyframes specific to individual views appeared in all views. Keyframes on the stereo offset control were not displayed in the VIewer timeline.

Camera sensor presets were not scriptable. The unkeyable Read file control was exposed incorrectly. Drawing a spline in proxy mode resulted in unexpected behavior. RotoPaint toolbars and overlays disappeared when a Tracker node's properties panel was open andthe Viewer was displaying and error.

Converting from bit scaled incorrectly. In multi-view scripts, cutting and pasting a split shape did not work as expected. Undoing the transform on a shape with modified points locked Nuke. Moving a shape's transform handle occasionally moved only a single point on the shape. The source image appeared until a refresh was forced with unlocked cameras. Moving multiple RotoPaint points and shapes while changing frame occasionally caused Nuke to crash. Emitting from faces with emit order set to uniformly or in order caused color from texture to be ignored.

Enabling color from texture did not apply the color properly when the incoming bbox did not match the format. There was no visible indication of which shape was selected in the scene tree.

Handles were offset while transforming Roto shapes when in down-rez mode. Results differed depending on the number of cores used for rendering. It was not possible to undo the changes made by clicking Metadata. Clicking Metadata did not update the label correctly.

Lock-ups when adjusting translate or rotate values in a Transform upstream of a Tracker. Attempting to scale three or more keyframes at once caused the scale handles to get stuck when dragging.

Maintaining selection when switching between source and destination grids was inconsistent. Crash opening a script with two HoldOuts and viewing the deep channel. Splinewarp handles were not visible. Connecting PoissonMesh node caused Nuke to crash. The blend control was always set to over when converting Deep data. Invalid vertex, uv, or normal indices in an. Entering an x expression then viewing it caused Nuke to crash.

Height did nothing in the size control. The node class name has changed to Project3D2. Loading scripts with plug-ins compiled against older versions removes the nodes from Node Graph. Roto opacity and feather settings are not included in captured images. Capturing the Viewer with a custom file path saves the file path in the script, resulting in error when the path doesn't exist: Capturing a 3D scene containing lights produces Viewer flashes in the captured images.

As a workaround, open the. The workaround is to change the cache precision in FrameCycler. This is an issue with FrameCycler , and we are awaiting a fix. For information on setting environment variables, please refer to the Configuring Nuke chapter in the Nuke User Guide. As a workaround, use a Reformat node to force the input to the correct format. If you're using Mac OS X Unlike previous versions of OS X, For more information, see http: As a workaround, either: As a workaround, adjust the Viewer gain control to refresh the Viewer.

If you click on the Viewer, then change the tool and draw a shape, your shape is added to the root layer instead of PlanarTrackerLayer1. The workaround is to: To return the shape to its original size and position, advance the sequence one frame. As a workaround, set the following environment variables: The workaround is to pass the in-panel argument as False or else use nuke. NodeClass where NodeClass is the type of node to create to create the node and then connect it to the currently selected node manually.

Instead, you can use the same command from your menu. 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: For example, this gives a syntax error: A possible workaround is to modify the GlobalSettings. Please be aware that this workaround is not reliable in every case. Due to this, we recommend the following: If you're unable to switch to Sorensen Video 3, try using a format smaller than 2K for better performance.

You may need to download the Neoplayer at http: Undoing a point move that created a keyframe doesn't currently undo the keyframe creation. Attempting to undo mulitple split-control transforms on the same shape reverts the shape to its original position. As a workaround, select the shape in the curves list to re-display the points. This also applies to SplineWarp matrices. Nuke 6 scripts containing Roto display a conversion prompt when you open them in Nuke 8: You might select this option if: The conversion functions cannot convert stereo-split curves as they are not supported by Nuke 6.

The pattern is a regular expression. An example single script conversion and rename to the same directory, from the command line terminal: This will change so the overlay only updates with the new stroke on pen up.

As a workaround, keyframe patterns should, where possible, be of comparable sizes. Deleting all but one point on a curve resets its correspondence points to 0,0, which cannot be undone. Correspondence points are too sensitive to when control points are removed. Moving correspondence points on curves with no keyframes cannot currently be undone.

Transform links are not maintained when the source curve is moved to a new layer. Preview doesn't handle upstream transforms correctly. 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. Locked source and destination grids still allow adding and removing grid lines.

The Viewer LUT is incorrect in morph mode, when mix is set at an intermediate value. Placing correspondence points at each end of an open spline causes rendering problems. The Viewer does not show the correct mix amount when in morph mode with mix set at an intermediate value.

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.

Rendering fails if a curve is reduced to a single point. The C hotkey does not currently select the Add Correspondence Point tool. The timeline currently shows both source and destination keyframes, even if a grid is not visible in the Viewer. Rotating the transform jack with both grids selected, but in different positions, does not undo as expected.

Existing control point keyframes are not cleared when you draw a new grid using the Draw Boundary Viewer button. The grid can flicker between white and grey when zooming in and out of the Viewer, particularly when the grid is subdivided. In stereo mode, the right view is labelled as default when you split controls into separate views. Faces on geometry read in from. This issue is particularly visible when using the EditGeo node, which should not allow you to remove faces from the geometry.

Textures occasionally disappear during playback or when mousing over the Viewer. Command line rendering appears to calculate renders even when render is set to off. Reading depth information from the same layer as the output layer produces corrupt output.

As a workaround, shuffle the depth information to an alternate layer. When motionblur is enabled in the Properties panel, FrameHold and TimeOffset nodes are ignored when connected to the cam or axis inputs. Actions such as adjusting the Viewer Gamma, Gain, or channels dropdown affect the frame hash. This known issue only applies to Roto and SplineWarp keys.

There should be two cameras: The focal length of the new camera does not match that of the Viewer camera. Using the ocionuke library in terminal mode results in an error.

The state of the Viewer Lock Frame control is not always honored for. You can switch back to Classic mode or avoid using proxy in 3D to workaround this issue. Geometry occasionally doesn't display as a solid until you click in the Viewer. You can minimize this effect by increasing the geometry tessellation max parameter.

Overlays are not updating correctly or reverting when panning or zooming. This only occurs if you have two Viewers open, one in 2D mode and the other in 3D mode, and you have the panel for the RotoPaint visible. 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. This affects, but is not restricted to, any nodes that have an analysis pass.

Copyright © 2017 · All Rights Reserved · Maine Council of Churches