Specifications

Using the AAF Encoder

Using the Avid AAF Encoder with Interplay

Avid Integration Guide

Required Information

When designing and implementing AAF encoder workflows, you should have the

following information at hand:

• Avid shared storage (ISIS) username and password

• Avid shared storage (ISIS) workspace/directory

• Interplay Web Services host name and port number

• Interplay username and password (might not match the ISIS username/password.)

• Avid Service Framework Workgroup (ASF Workgroup) name.

Note: When you are installing software or otherwise modifying Avid programs or

systems, always confer and coordinate with your Avid systems administrator to make

these changes, including restarting any systems. Always refer to Avid documentation

if you have questions about the use of Avid products.

Creating Interplay Master Assets

When using the AAF encoder in an Interplay environment, you can generate master

assets in two ways. Each method creates the master clip and MOB-IDs used in the AAF

Encoder. The first method uses a Notify action prior to any AAF Encoder Flip action in

the workflow. The second method uses the first AAF Encoder Flip action to auto-

generate the required MOB IDs in the first AAF Encoder Flip action of a workflow. Each

method has benefits and limits.

Using Notify to Create a Master Asset Prior to an AAF Encoder

Flip Action

This type of workflow uses a Notify action preceding all AAF Encoder Flip actions. The

Notify action’s Create Master Clip function (Interplay Notifier Notification type) will

create a master clip in Interplay and return the Master and Source MOB IDs as two

variables, to be used by downstream AAF Encoder Flip actions or other actions that

require them.

The benefit of this method is that you can generate multiple media resolutions, all

associated with the same master asset, in parallel. This is possible since the Notify

action immediately passes the master asset's MOB-ID variables to all downstream

actions.

With a Vantage array and sufficient Transcode services, all of the encoding can be

performed faster than real-time, thus making the workflow time as short as possible. In

this type of workflow—using Notify to create the master asset—Edit While Ingest /

Frame Chase editing is not supported.

If you want transcoding speed at the expense of Edit While Ingest / Frame Chase

editing, implement your workflow using this method.

See example workflows for details.