Specifications

Using the AAF Encoder
Overview
32
Avid Integration Guide
Overview
The AAF encoder is implemented in the Flip action to produce single and multi-
resolution assets consisting of Avid-compatible MXF OP-Atom media. The AAF encoder
features integrated delivery to Media Composer and check-in to Interplay using Web
Services. The AAF encoder may also be used in Avid environments without Interplay.
In single-resolution workflows, Edit While Ingest is supported. SMPTE 436 data is also
supported. In multi-resolution workflow, when the files are ingested into Avid, an
operator can switch low-res format to conduct edits.
The AAF encoder can be configured to integrate with Interplay and Media Composer.
• Interplay—the asset’s media file sets are delivered to the ISIS workspace in an Inter-
play environment and checked in automatically.
• Media Composer—the asset’s media file sets are delivered to a Media Composer-
accessible file system (local drive, SAN/NAS or share) via a Transport action (Move
or Copy). You import the asset into Media Composer to link media to an active edit-
ing project.
To create multi-resolution assets, multiple Flip actions can be used in a single workflow,
either in parallel or in serial. It is common to place three Flip actions in a workflow in
parallel: two configured with the AAF encoder to produce a high-resolution file and a
proxy file. The third Flip action is configured with the Keyframe encoder to extract and
save a JPEG file, for display as a headframe in Interplay Access.
Note: Telestream recommends that you only use the AAF encoder with Transcoder
version 2014.11 or later.