Product specifications

Standalone Transfer Engine Overview

When AirSpeed 5000 is configured with a standalone Transfer Engine it operates in

environments where you have local storage without Interplay. In a Standalone environment, the

Transfer Engine (TM) application uses FTP functionality to act as the transfer agent between the

Avid editors and the AirSpeed 5000 Remote Console application.

With a Standalone Transfer Engine configuration, AirSpeed 5000 uses only its own internal

storage or local Avid editor storage for storing clips and supports playing out to air via drag and

drop using the AirSpeed 5000 Remote Console.

In this configuration, clips are visible through Remote Console event listings and can be used to

drag and drop files in environments where multiple video servers are used. The standalone

configuration supports playout automation applications such as iNEWS ® Command, DNF

controllers and other solutions using VDCP or AMS API.

Interplay Transfer Engine does not support Studio playout.

When configured with a Standalone Transfer Engine, the transfer of clips from AirSpeed 5000

(via the Remote Console) to the Editor must be done manually.

Video servers configured with a Standalone Transfer Engine support the standard features of

your video server model (AirSpeed 5000) with the exception of the features listed below:

• Avid Studio Playout

• Interplay Capture

• CaptureManager

• Frame Chase™ Editing

• Edit While Capture (EWC) functionality with Avid Editor systems

• H.264 media transfers to the Editor (not for Standalone or Team)

• DNxHD 85/100 support