Tracks, Range, and Handles Settings

The tracks, tags, and handles controls in the Export dialog allow you to select the frame range or shots to export.

Set the Version number for the export, if applicable. Use the arrows to increment the version number and the +/- buttons to increase or decrease the padding. You can also type directly into the numeric field.

Note: See Using Versions for more information on how versioning works in Nuke Studio.

Select Tracks for this export by enabling or disabling the tracks in the list. Nuke Studio exports all tracks by default.

Enable or disable tags using the Filter by tag panel. Click the checkbox to cycle through the available tag states.

If you're exporting a sequence, set the Range controls as required:

• Select Whole Sequence or In/Out Points to export only the selected frames.

• Set how clip Start Frames are derived using the dropdown menu:

• Sequence - use the sequence’s start frame.

• Custom - specify a start frame for all clips using the field to the right.

If you're exporting shots, set the Handles controls as required:

• Clip Length - exports the full clip length available, as if the clip was opened as a Viewer.

• Cut Length - exports only the cuts included on the timeline.

Note: Selecting Cut Length allows you to add handles to each clip, up to the maximum available source clip length.

• Check Apply Retimes to export any retimes present on the timeline.

Note: When Apply Retimes is disabled, which is the default state for Create Comp, any TimeWarp soft effects are not included in the resulting Nuke script. When the new shot is created through Create Comp or Build Track from Export Tag, TimeWarp soft effects are copied from the original shot to the new one.

• Set how clip Start Frames are derived using the dropdown menu:

• Source - use the source clip’s start frame.

• Custom - specify a start frame for all clips using the field to the right.

Set how Nuke Studio should render your export using the Render with dropdown. Nuke Studio provides the following options:

• Frame Server - uses multiple Nuke processes to speed up render times and shares a render queue with any Nuke Comp renders in the timeline, improving resource management.

See Using the Frame Server on Render Machines for more information.

• Single Render Process - uses a single Nuke process to render your export. Rendering QuickTimes falls back to this setting, but it's also used when a problem is detected with the Frame Server.

• Custom Render Process - uses a custom render process. Nuke Studio requires a Python script to pass exports to your render farm of choice. Scripts must be located in specific directories, dependent on platform, as listed in Loading Gizmos, NDK Plug-ins, and Python and Tcl Scripts. If no scripts exist, the dropdown only contains the default render processes.

Click Export.

The Export Queue window displays an estimate of how long each component of the export is expected to take.

Once the export is complete, the file structure specified in the shot template is created. You can then import the Nuke clips on a separate track when they’re ready.

Tip: Click the magnifying glass icon to reveal the file structure in a browser window.

When clips are exported from Nuke Studio, they are marked with a Nuke tag flagging which clips have an export history. Clips tagged in this way can be used to build VFX tracks quickly as described in Building VFX Tracks and Comp Clips.