(a) Framerate box (b) Output Bit Depth box (c) File Format box (d) Compression box
Select the framerate for the clip to be output from the Framerate box.
The Framerate box is disabled if the format you selected does not support the frame rate to be specified in the file header. For example, JPEG files do not support frame rate specifications in the file header, while DPX files do. In the latter case, Framerate is available.
Output Bit Depth box
Select the bit depth for the clip to export.
File Format box
Select an export format for the clip to export.
Frame Pad field
Define the padding of the frame number appended to the file name (represented by # in the Path field).
For example, 6 indicates that each frames's file name has its frame identifier padded with a number of zeroes required to make it a 6-digit number: frame 1 is written as 000001, frame 22 as 000022, frame 55555 as 055555, and so on.
Define any timecode offsets for the processed clip.
Select a preset of format-specific compression parameters. The option box varies according to the selected export format.
Clip Data Settings
Create Clip Data button
Enable to create a Gateway clip file, which includes extended clip data with the exported files.
Include Setup button
Enable to include the Batch setup alongside the exported clip. This also includes a reference to this setup in the generated Gateway clip.
Enable to version the processed exports, using a Gateway clip. The resulting Gateway clip has versions you can access through the Gateway Import node, using the Clip Versions box.
The Version field sets the version identifier, which automatically increases at each subsequently processed export. Or you can set the version value manually. Resetting the field (Ctrl+click) sets the next available value. Using a previously used Version value overwrites that version with the new export.
NoteEditing the Path field creates a new Gateway Clip at export, and therefore restarts versioning at 1.
Use the <version> token in the Naming field to include the version identifier in the path/name of the processed media files. If you do not include at least one occurence of the <version> token, Flame automatically adds one to the exported media files. It appears as _v<version> in the Path field.
Version Pad field
Select how the version number is left-padded with zeroes.
Defining the Export Destination
Displays where the exported files are saved. Click to edit. Appended to this path is the content from the Naming field. The Gateway clip file (created when Create Clip Data is enabled) is stored at the edited path level, not at the appended path where media files are created. In the examples below, Gateway clip files are created in path a.
(a) Path edited by clicking the field (b) Content of the Naming field
Defines how the processed media files are named, and where they are located. Use the Naming field to build a dynamic naming scheme using the clip name, version (when available), and date of processing, as opposed to the path defined in Path field which is static. Use any of the characters allowed in a Linux file name. Flame creates folders using the slash ( / ) character.
Flame automatically appends the frame number (#) and the extension of the file format selected for the export.
The frame number format is defined using the Frame Pad field.
Clip Name button
Inserts in the Naming field the <name> token, which stands in for the export node's name, minus the brackets and node numerical identifier.
Inserts in the Naming field the <version> token. This token stands in for the value of the Version field. The <version> token is ignored if either the Version or the Create Clip Data buttons are disabled.
If there is no <version> token in the Naming field but the Version button is enabled, Flame automatically adds the value of the Version field to the name of the exported media files, prefixed by v_.
Inserts in the Naming field the <data> token, which stands for the current date, formatted as YYYY_MM_DD.