Hiero allows you to import your EDL, OTIO, XML, or AAF sequences in one of two ways, depending on your preferences. Either:
• Navigate to File > Import EDL/XML/AAF or Import OTIO (Beta) and then use the browser to locate the EDL, OTIO, XML, or AAF, and then select the file and click Open to import the sequence,
• Drag-and-drop the EDL, OTIO, XML, or AAF files directly from a file browser into the interface.
If you’re importing an EDL, bear in mind that there is no guaranteed frame rate information included in the file, so an Import Options dialog displays.
|Select the correct frame rate and use the following check boxes, if required:
• Drop Frame - when enabled, the EDL is assumed to contain drop file information. SeeTimeline Playback Tools for more information.
• Assume differences in source/destination durations indicate a retime - when enabled, any disparity between the source clip (Src) and shot (Dst) duration is treated as a retime.
|Click OK to import.
OTIO, XML and AAF files imported into Hiero support transform, crop, and retime edit decisions implemented in third-party applications, such as Adobe Premiere, Apple Final Cut Pro, and Avid Media Composer. The information in the .otio, .xml, or .aaf is interpreted using soft effects, such as Transform and Crop. Non-linear retimes are represented by TimeWarp effects. Constant linear retimes are handled in the same way as in previous versions of Hiero. See Notes on AAF Sequences for more information.
Note: Non-linear animation curves from .otio or .xml may not appear as expected when imported. As a result, you may need to adjust the handles on curves to match footage between keyframes in the Curve Editor or Dope Sheet.
Additionally, Premiere Pro .xml exports only support constant, linear retimes. As a result, retimed shots on the Nuke Studio timeline may not match those on the Premier Pro timeline, because certain non-linear retime data is not written into the exported .xml file.
After importing the EDL, OTIO, AAF, or XML the Conforming workspace displays and the spreadsheet and timeline are populated with offline clips - media with an unknown location.
Note: The Event column represents the clip’s position on the timeline, not its event number from the edit.
Notice that clicking entries in the spreadsheet highlights the corresponding shots on the timeline?
The spreadsheet, timeline, and Viewer are linked together when viewing sequences. If suitable screen real estate exists within the current workspace, double-clicking a sequence forces the associated panel to open automatically. If you want to close a single panel in a linked group, hold the Alt modifier while closing the linked panel, otherwise all panels in the group are closed.
Note: If you imported an XML sequence, you may find that Hiero has automatically matched media for you.
Any transform, crop, or retime edit decisions from third-party software .otio, .xml or .aaf files are represented using soft effects. These effects are imported along with the shot to which they're associated.
Avid Media Composer supports retimes using curves that map frame to frame or frame to speed. Hiero handles the import differently depending on the retime method.
• frame to frame - describes the retiming in relative terms, such as 'at frame 100 in the output clip, display frame 50 of the source clip'.
• frame to speed - describes the retiming in terms of overall output duration. For example, half speed doubles the duration of the clip.
Hiero's TimeWarp effect only supports frame to frame mapping, which means that frame to speed retimes from .aaf files requires some curve-fitting to describe the required retime. As a result, the keyframes generated in Hiero don't match those in Avid, but the resulting curve should match the original very closely.
Note: Hiero currently only supports Fixed Keyframes from Avid Media Composer.
Tip: If you need to adjust the handles on curves, see https://learn.foundry.com/nuke/content/getting_started/using_interface/animating_parameters.html for more information.
Hiero's TimeWarp effect supports the following Spline types when importing .aaf files: