Specifications

Using the AAF Encoder

Configuring the AAF Encoder

Avid Integration Guide

• In Multiple Resolution Workflows: For workflows that generate multiple resolutions

in parallel it is required that the MOB-IDs be generated by a preceding Notify action

configured with the Create Master Clip function and then passed to the Flip action’s

AAF encoder as a variable. For workflows that generate multiple resolutions serially,

the MOB-ID fields can be auto-generated from the first AAF encoder Flip action and

then passed to any downstream action that requires them (see sample workflows

for details).

• In Single Resolution Workflows: For workflows that generate a single resolution, the

MOB-IDs can be generated automatically by leaving the value blank or can be pop-

ulated with the MOB-ID values passed via variables. MOB-ID variables can be popu-

lated by using a Notify action or other actions that have extracted them from a

previous AAF Encoder Flip action (see sample workflows for details).

Note: MOB ID’s are dynamically generated by Avid Interplay, and should only be

entered manually under unique circumstances—for example, to correct a one-time

file error in an existing asset.

Tape —Specifies the tape name to be added to this asset’s metadata.

Drop Frame Timecode Format—When checked, specifies media as a drop-frame

timecode asset.

Figure 10. Physical File Locations Configuration Panel

AAF File Location—Specifies the UNC path to shared storage to which the AAF file will

be written.

MXF File Location—Specifies the UNC path to shared storage to which the selected

codec’s MXF OP-Atom media files will be written.

Delete Avid AAF and XML Support Files—When checked, the AAF and XML support files

deleted from their physical location after the media has been checked into Interplay.

Figure 11. Physical Directory Control Configuration Panel

Physical Directory Control—When enabled, determines the maximum number of MXF

files per directory. When the maximum is reached, a new directory is created with a

numerical suffix (<dirname>.1, etc.), to store the next set of files.