Interplay | Production

Whats New in Version 3.1

Legal Notices
Product specifications are subject to change without notice and do not represent a commitment on the part of Avid Technology, Inc.
This product is subject to the terms and conditions of a software license agreement provided with the software. The product may
only be used in accordance with the license agreement.
This product may be protected by one or more U.S. and non-U.S patents. Details are available at www.avid.com/patents.
This document is protected under copyright law. An authorized licensee of Avid Interplay may reproduce this publication for the
licensees own use in learning how to use the software. This document may not be reproduced or distributed, in whole or in part, for
commercial purposes, such as selling copies of this document or providing support or educational services to others. This document
is supplied as a guide for Avid Interplay. Reasonable care has been taken in preparing the information it contains. However, this
document may contain omissions, technical inaccuracies, or typographical errors. Avid Technology, Inc. does not accept
responsibility of any kind for customers losses due to the use of this document. Product specifications are subject to change without
notice.

Copyright 2014 Avid Technology, Inc. and its licensors. All rights reserved.
The following disclaimer is required by Apple Computer, Inc.:
APPLE COMPUTER, INC. MAKES NO WARRANTIES WHATSOEVER, EITHER EXPRESS OR IMPLIED, REGARDING THIS
PRODUCT, INCLUDING WARRANTIES WITH RESPECT TO ITS MERCHANTABILITY OR ITS FITNESS FOR ANY PARTICULAR
PURPOSE. THE EXCLUSION OF IMPLIED WARRANTIES IS NOT PERMITTED BY SOME STATES. THE ABOVE EXCLUSION
MAY NOT APPLY TO YOU. THIS WARRANTY PROVIDES YOU WITH SPECIFIC LEGAL RIGHTS. THERE MAY BE OTHER
RIGHTS THAT YOU MAY HAVE WHICH VARY FROM STATE TO STATE.

The following disclaimer is required by Sam Leffler and Silicon Graphics, Inc. for the use of their TIFF library:
Copyright 19881997 Sam Leffler
Copyright 19911997 Silicon Graphics, Inc.
Permission to use, copy, modify, distribute, and sell this software [i.e., the TIFF library] and its documentation for any purpose is
hereby granted without fee, provided that (i) the above copyright notices and this permission notice appear in all copies of the
software and related documentation, and (ii) the names of Sam Leffler and Silicon Graphics may not be used in any advertising or
publicity relating to the software without the specific, prior written permission of Sam Leffler and Silicon Graphics.
THE SOFTWARE IS PROVIDED AS-IS AND WITHOUT WARRANTY OF ANY KIND, EXPRESS, IMPLIED OR OTHERWISE,
INCLUDING WITHOUT LIMITATION, ANY WARRANTY OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
IN NO EVENT SHALL SAM LEFFLER OR SILICON GRAPHICS BE LIABLE FOR ANY SPECIAL, INCIDENTAL, INDIRECT OR
CONSEQUENTIAL DAMAGES OF ANY KIND, OR ANY DAMAGES WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR
PROFITS, WHETHER OR NOT ADVISED OF THE POSSIBILITY OF DAMAGE, AND ON ANY THEORY OF LIABILITY, ARISING
OUT OF OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE.

The following disclaimer is required by the Independent JPEG Group:

This software is based in part on the work of the Independent JPEG Group.

This Software may contain components licensed under the following conditions:
Copyright (c) 1989 The Regents of the University of California. All rights reserved.
Redistribution and use in source and binary forms are permitted provided that the above copyright notice and this paragraph are
duplicated in all such forms and that any documentation, advertising materials, and other materials related to such distribution and
use acknowledge that the software was developed by the University of California, Berkeley. The name of the University may not be
used to endorse or promote products derived from this software without specific prior written permission. THIS SOFTWARE IS
PROVIDED ``AS IS'' AND WITHOUT ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, WITHOUT LIMITATION, THE
IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE.
Copyright (C) 1989, 1991 by Jef Poskanzer.
Permission to use, copy, modify, and distribute this software and its documentation for any purpose and without fee is hereby
granted, provided that the above copyright notice appear in all copies and that both that copyright notice and this permission notice
appear in supporting documentation. This software is provided "as is" without express or implied warranty.
Copyright 1995, Trinity College Computing Center. Written by David Chappell.
Permission to use, copy, modify, and distribute this software and its documentation for any purpose and without fee is hereby
granted, provided that the above copyright notice appear in all copies and that both that copyright notice and this permission notice
appear in supporting documentation. This software is provided "as is" without express or implied warranty.

Copyright 1996 Daniel Dardailler.

Permission to use, copy, modify, distribute, and sell this software for any purpose is hereby granted without fee, provided that the
above copyright notice appear in all copies and that both that copyright notice and this permission notice appear in supporting
documentation, and that the name of Daniel Dardailler not be used in advertising or publicity pertaining to distribution of the software
without specific, written prior permission. Daniel Dardailler makes no representations about the suitability of this software for any
purpose. It is provided "as is" without express or implied warranty.
Modifications Copyright 1999 Matt Koss, under the same license as above.
Copyright (c) 1991 by AT&T.
Permission to use, copy, modify, and distribute this software for any purpose without fee is hereby granted, provided that this entire
notice is included in all copies of any software which is or includes a copy or modification of this software and in all copies of the
supporting documentation for such software.
THIS SOFTWARE IS BEING PROVIDED "AS IS", WITHOUT ANY EXPRESS OR IMPLIED WARRANTY. IN PARTICULAR,
NEITHER THE AUTHOR NOR AT&T MAKES ANY REPRESENTATION OR WARRANTY OF ANY KIND CONCERNING THE
MERCHANTABILITY OF THIS SOFTWARE OR ITS FITNESS FOR ANY PARTICULAR PURPOSE.
This product includes software developed by the University of California, Berkeley and its contributors.

The following disclaimer is required by Nexidia Inc.:

2010 Nexidia Inc. All rights reserved, worldwide. Nexidia and the Nexidia logo are trademarks of Nexidia Inc. All other
trademarks are the property of their respective owners. All Nexidia materials regardless of form, including without limitation,
software applications, documentation and any other information relating to Nexidia Inc., and its products and services are the
exclusive property of Nexidia Inc. or its licensors. The Nexidia products and services described in these materials may be covered
by Nexidia's United States patents: 7,231,351; 7,263,484; 7,313,521; 7,324,939; 7,406,415, 7,475,065; 7,487,086 and/or other
patents pending and may be manufactured under license from the Georgia Tech Research Corporation USA.

The following disclaimer is required by Paradigm Matrix:

Portions of this software licensed from Paradigm Matrix.

The following disclaimer is required by Ray Sauers Associates, Inc.:

Install-It is licensed from Ray Sauers Associates, Inc. End-User is prohibited from taking any action to derive a source code
equivalent of Install-It, including by reverse assembly or reverse compilation, Ray Sauers Associates, Inc. shall in no event be liable
for any damages resulting from resellers failure to perform resellers obligation; or any damages arising from use or operation of
resellers products or the software; or any other damages, including but not limited to, incidental, direct, indirect, special or
consequential Damages including lost profits, or damages resulting from loss of use or inability to use resellers products or the
software for any reason including copyright or patent infringement, or lost data, even if Ray Sauers Associates has been advised,
knew or should have known of the possibility of such damages.

The following disclaimer is required by Videomedia, Inc.:

Videomedia, Inc. makes no warranties whatsoever, either express or implied, regarding this product, including warranties with
respect to its merchantability or its fitness for any particular purpose.
This software contains V-LAN ver. 3.0 Command Protocols which communicate with V-LAN ver. 3.0 products developed by
Videomedia, Inc. and V-LAN ver. 3.0 compatible products developed by third parties under license from Videomedia, Inc. Use of this
software will allow frame accurate editing control of applicable videotape recorder decks, videodisc recorders/players and the like.

The following disclaimer is required by Altura Software, Inc. for the use of its Mac2Win software and Sample Source
Code:
19931998 Altura Software, Inc.

The following disclaimer is required by Ultimatte Corporation:

Certain real-time compositing capabilities are provided under a license of such technology from Ultimatte Corporation and are
subject to copyright protection.

The following disclaimer is required by 3Prong.com Inc.:

Certain waveform and vector monitoring capabilities are provided under a license from 3Prong.com Inc.

The following disclaimer is required by Interplay Entertainment Corp.:

The Interplay name is used with the permission of Interplay Entertainment Corp., which bears no responsibility for Avid products.
This product includes portions of the Alloy Look & Feel software from Incors GmbH.

This product includes software developed by the Apache Software Foundation (http://www.apache.org/).
DevelopMentor

This product may include the JCifs library, for which the following notice applies:
JCifs Copyright 2004, The JCIFS Project, is licensed under LGPL (http://jcifs.samba.org/). See the LGPL.txt file in the Third Party
Software directory on the installation CD.
Avid Interplay contains components licensed from LavanTech. These components may only be used as part of and in connection
with Avid Interplay.
Interplay Production Streaming Server includes Live555, which is covered by the GNU Lesser General Public License. Live555 is
Copyright (c) 1996-2011, Live Networks, Inc. and is licensed under the terms of the GNU Lesser General Public License, which is
included with this product.
This product includes software developed by Indiana University Extreme! Lab (http//:www.extreme.indiana.edu/)/

Attn. Government User(s). Restricted Rights Legend

U.S. GOVERNMENT RESTRICTED RIGHTS. This Software and its documentation are commercial computer software or
commercial computer software documentation. In the event that such Software or documentation is acquired by or on behalf of a
unit or agency of the U.S. Government, all rights with respect to this Software and documentation are subject to the terms of the
License Agreement, pursuant to FAR 12.212(a) and/or DFARS 227.7202-1(a), as applicable.

Trademarks
003, 192 Digital I/O, 192 I/O, 96 I/O, 96i I/O, Adrenaline, AirSpeed, ALEX, Alienbrain, AME, AniMatte, Archive, Archive II, Assistant
Station, AudioPages, AudioStation, AutoLoop, AutoSync, Avid, Avid Active, Avid Advanced Response, Avid DNA, Avid DNxcel, Avid
DNxHD, Avid DS Assist Station, Avid Ignite, Avid Liquid, Avid Media Engine, Avid Media Processor, Avid MEDIArray, Avid Mojo, Avid
Remote Response, Avid Unity, Avid Unity ISIS, Avid VideoRAID, AvidRAID, AvidShare, AVIDstripe, AVX, Beat Detective, Beauty
Without The Bandwidth, Beyond Reality, BF Essentials, Bomb Factory, Bruno, C|24, CaptureManager, ChromaCurve,
ChromaWheel, Cineractive Engine, Cineractive Player, Cineractive Viewer, Color Conductor, Command|24, Command|8,
Control|24, Cosmonaut Voice, CountDown, d2, d3, DAE, D-Command, D-Control, Deko, DekoCast, D-Fi, D-fx, Digi 002, Digi 003,
DigiBase, Digidesign, Digidesign Audio Engine, Digidesign Development Partners, Digidesign Intelligent Noise Reduction,
Digidesign TDM Bus, DigiLink, DigiMeter, DigiPanner, DigiProNet, DigiRack, DigiSerial, DigiSnake, DigiSystem, Digital
Choreography, Digital Nonlinear Accelerator, DigiTest, DigiTranslator, DigiWear, DINR, DNxchange, Do More, DPP-1, D-Show, DSP
Manager, DS-StorageCalc, DV Toolkit, DVD Complete, D-Verb, Eleven, EM, Euphonix, EUCON, EveryPhase, Expander,
ExpertRender, Fader Pack, Fairchild, FastBreak, Fast Track, Film Cutter, FilmScribe, Flexevent, FluidMotion, Frame Chase, FXDeko,
HD Core, HD Process, HDpack, Home-to-Hollywood, HYBRID, HyperSPACE, HyperSPACE HDCAM, iKnowledge, Image
Independence, Impact, Improv, iNEWS, iNEWS Assign, iNEWS ControlAir, InGame, Instantwrite, Instinct, Intelligent Content
Management, Intelligent Digital Actor Technology, IntelliRender, Intelli-Sat, Intelli-sat Broadcasting Recording Manager, InterFX,
Interplay, inTONE, Intraframe, iS Expander, iS9, iS18, iS23, iS36, ISIS, IsoSync, LaunchPad, LeaderPlus, LFX, Lightning, Link &
Sync, ListSync, LKT-200, Lo-Fi, MachineControl, Magic Mask, Make Anything Hollywood, make manage move | media, Marquee,
MassivePack, Massive Pack Pro, Maxim, Mbox, Media Composer, MediaFlow, MediaLog, MediaMix, Media Reader, Media
Recorder, MEDIArray, MediaServer, MediaShare, MetaFuze, MetaSync, MIDI I/O, Mix Rack, Moviestar, MultiShell, NaturalMatch,
NewsCutter, NewsView, NewsVision, Nitris, NL3D, NLP, NSDOS, NSWIN, OMF, OMF Interchange, OMM, OnDVD, Open Media
Framework, Open Media Management, Painterly Effects, Palladium, Personal Q, PET, Podcast Factory, PowerSwap, PRE,
ProControl, ProEncode, Profiler, Pro Tools, Pro Tools|HD, Pro Tools LE, Pro Tools M-Powered, Pro Transfer, QuickPunch,
QuietDrive, Realtime Motion Synthesis, Recti-Fi, Reel Tape Delay, Reel Tape Flanger, Reel Tape Saturation, Reprise, Res Rocket
Surfer, Reso, RetroLoop, Reverb One, ReVibe, Revolution, rS9, rS18, RTAS, Salesview, Sci-Fi, Scorch, ScriptSync,
SecureProductionEnvironment, Serv|GT, Serv|LT, Shape-to-Shape, ShuttleCase, Sibelius, SimulPlay, SimulRecord, Slightly Rude
Compressor, Smack!, Soft SampleCell, Soft-Clip Limiter, SoundReplacer, SPACE, SPACEShift, SpectraGraph, SpectraMatte,
SteadyGlide, Streamfactory, Streamgenie, StreamRAID, SubCap, Sundance, Sundance Digital, SurroundScope, Symphony, SYNC
HD, SYNC I/O, Synchronic, SynchroScope, Syntax, TDM FlexCable, TechFlix, Tel-Ray, Thunder, TimeLiner, Titansync, Titan, TL
Aggro, TL AutoPan, TL Drum Rehab, TL Everyphase, TL Fauxlder, TL In Tune, TL MasterMeter, TL Metro, TL Space, TL Utilities,
tools for storytellers, Transit, TransJammer, Trillium Lane Labs, TruTouch, UnityRAID, Vari-Fi, Video the Web Way, VideoRAID,
VideoSPACE, VTEM, Work-N-Play, Xdeck, X-Form, Xmon and XPAND! are either registered trademarks or trademarks of Avid
Technology, Inc. in the United States and/or other countries.
Adobe and Photoshop are either registered trademarks or trademarks of Adobe Systems Incorporated in the United States and/or
other countries. Apple and Macintosh are trademarks of Apple Computer, Inc., registered in the U.S. and other countries. Windows
is either a registered trademark or trademark of Microsoft Corporation in the United States and/or other countries. All other
trademarks contained herein are the property of their respective owners.

Avid Interplay Version 3.1 Whats New June 2014 Updated 9/17/14 This document is distributed by Avid in
online (electronic) form only, and is not available for purchase in printed form.

Contents
Chapter 1

Whats New in Interplay | Production Version 3.1 . . . . . . . . . . . . . . . . . . . . . 7

Chapter 2

Interplay | Media Services Changed to Windows Services . . . . . . . . . . . . . 10

Installation and Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
Editing the .ini File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
Upgrading Existing Service Providers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
Troubleshooting Service Providers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14

Chapter 3

Selecting Audio Formats for Copy, Move, and Deliver . . . . . . . . . . . . . . . . 15

Chapter 4

New for Interplay Transcode Profiles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18

Interplay Checkin Folder . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
DATAEXTRACT Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
Limitations for DATAEXTRACT Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21

Chapter 5

New in Interplay Administrator V3.1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22

New Database Maintenance Tools . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
Specifying Interplay Transfer Engines for Direct Transfers. . . . . . . . . . . . . . . . . . . . . . . 24
Configuring a Workgroup for Direct Transfer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
Creating a Transfer Preset . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
Performing a Direct Transfer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29

Chapter 6

Port Usage and Media Composer | Cloud . . . . . . . . . . . . . . . . . . . . . . . . . . . 31

Changing the Port Used By the Interplay Sphere Media Services Engine Service . . . . 31

Chapter 7

AMA Workflow Changes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33

Media | Director Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
Third-Party Storage Licenses . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34

AMA Related Changes In Interplay | Access . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38

AMA Online Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38
AMA Source File Locations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38
Deleting AMA Clips in Interplay Access . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40
Locating the .spaaf Files Associated with a Clip . . . . . . . . . . . . . . . . . . . . . . . . . . . 43
AMA Support and Interplay | Media Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48

Chapter 8

Interplay | Transfer Changes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49

Configuring OP1A/XDCAM Profiles for Catalog Checkins . . . . . . . . . . . . . . . . . . . . . . . 49
Writing to a Temp File with Generic FTP profiles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51

1 Whats New in Interplay | Production

Version 3.1
Revision History
Date Revised

Changes Made

September 17, 2014 Removed references to Interplay Transcode as service.

June 19, 2014

First publication

For the latest information about new features and documentation changes, see the Avid Interplay
ReadMe on the Avid Customer Support Knowledge Base.
Rebranding of Avid Products

For Interplay Production V3.1, several components have been rebranded or renamed. The
following table shows the old name and the new name. The table also shows related product
names.

Old Name

New Name

Interplay Production

Interplay | Production

Interplay Media Services

Interplay | Production Services

Interplay Archive, Interplay Transcode, and other

services

Interplay | Archive, Interplay | Transcode, and so on

Interplay Sphere

Media Composer | Cloud

Interplay Central

Avid MediaCentral Platform, Avid

MediaCentral | UX

Interplay Pulse

MediaCentral | Distribute

The pipe character is used in Avid product names, such as Interplay | Production. In
documentation, the pipe is used in product names when they are in book titles, headings, or at
their first use in text.

Interplay | Production Services Now Windows Services

See Interplay | Media Services Changed to Windows Services on page 10

Selecting Audio Formats for Copy, Move, and Delivery

See Selecting Audio Formats for Copy, Move, and Deliver on page 15.
New Options for Transcode Profiles

See New for Interplay Transcode Profiles

New Interplay | Production Services

Two new services have been introduced in Interplay Production v3.1:

Production Services Automation

Interplay Consolidate

Currently, these services are used only for MediaCentral | UX Delivery. For more information,
see the Avid MediaCentral | Users Guide and the Avid MediaCentral Platform Services
Installation and Configuration Guide.
New in Interplay Administrator

See New in Interplay Administrator V3.1 on page 22.

Production Engine Bus Connector

The Production Engine Bus Connector service (PEBCo) runs on the Interplay Engine and
communicates with the MediaCentral Platform bus. This communication enables the Interplay
Production database to be part of a multi-zone Media | Index.
For more information, see the Avid MediaCentral | Users Guide and the Avid MediaCentral
Platform Services Installation and Configuration Guide.
Roaming Profiles Not Supported

Roaming profiles are not supported in an Avid Interplay environment.

Changing Port Usage for the HyperSQL Database on Media Composer Cloud Client

You can now change the port used by the HyperSQL Database Engine on a Media Composer
Cloud client. See Changing the Port Used By the Interplay Sphere Media Services Engine
Service on page 31.

AMA Changes

See AMA Workflow Changes on page 33.

Interplay | Transfer Changes

See Interplay | Transfer Changes on page 49.

2 Interplay | Media Services Changed to

Windows Services
Starting with Interplay Media Services v3.1, service providers (such as Interplay Archive)
operate as Windows services, rather than as Windows applications. As a result, they can be
managed like other Windows services. An advantage to this new feature is that all services are
started automatically and restart automatically after a system reboot or crash.

Interplay Transcode and STP Encode operate as Windows applications, not as Windows
services.
Because service providers are no longer applications, they are no longer listed in the Start menu
and no longer have a user interface window. They are listed with other Windows services in the
Services tab of the Computer Management window. The descriptions of the services have been
changed to display the new branding. The following illustration shows the Interplay Delivery
service installed and running.

Delayed Start

Services are scheduled for automatic delayed start. Automatic (Delayed Start) specifies that a
service should be started approximately two minutes after the system has completed starting the
operating system. The Automatic (Delayed Start) startup type is preferred over the Automatic
startup type because it helps reduce the effect on the systems overall boot performance.
If you restart the service, you need to refresh the window to show the current status.
If you reboot your system, wait two minutes before you check the status of the service in the
Providers tab of the Media Services and Transfer Status tool. See Upgrading Existing Service
Providers on page 13.

Installation and Configuration

Log Files

Messages that used to be displayed in the user interface window are now written in one of two
log files:

Error log file: This file contains errors, such as unable to connect to broker, or no dongle.

Output log file: This file contains informational messages.

The following table lists the default locations of the log files.
Service

Paths

Log Files

Interplay | Archive

C:\Program Files\Avid\Interplay Archive

Provider\ArchiveService

ArchiveServiceError.log
ArchiveServiceOutput.log

Interplay | Consolidate

C:\Program Files\Avid\Interplay
Consolidate\TranscodeService

InterplayConsolidateError.log
InterplayConsolidateOutput.log

Interplay | Copy

C:\Program Files\Avid\Interplay Copy\CopyService

CopyServiceError.log
CopyServiceOutput.log

Interplay | Delivery

C:\Program Files\Avid\Interplay Delivery\bin

DeliveryServiceError.log
DeliveryServiceOutput.log

Interplay | Media
Services Automation

C:\Program Files\Avid\Interplay Media Services

Automation\

MSAutomationError.log
MSAutomationOutput.log

Interplay | Move

C:\Program Files\Avid\Interplay Move\MoveService

MoveServiceError.log
MoveServiceOutput.log

Interplay | Restore

C:\Program Files\Avid\Interplay Restore

Service\RestoreService

RestoreServiceError.log
RestoreServiceOutput.log

Installation and Configuration

You install services in the same way as in previous versions, through the Interplay Production
Servers installation program. A service is started automatically by the installer after the
installation is complete.

11

Installation and Configuration

The following topics provide specific information about installation and configuration:

Editing the .ini File on page 12

Upgrading Existing Service Providers on page 13

Editing the .ini File

Information about the service is included in an .ini file.

If you are performing a new installation, the installed .ini file uses localhost as the name of
the associated Media Services Engine. This is appropriate if you are installing the service on
the same system as the Media Services Engine. If you are installing the service on a different
system, you need to change the default hostname by editing the .ini file.

If you are upgrading from a previous version, the existing .ini file is copied to the
appropriate new folder. If the associated Media Services Engine remains the same, no
further configuration is needed.

The .ini file includes an automatically generated provider name. You can change the
provider name if you want.

To edit the .ini file for a service:

1. Locate the .ini file and open it in a text editor, such as Windows Notepad.
The following table lists the Media Services with the path for the .ini file and the log files.
Service

Path for .ini File

Interplay | Archive

C:\ProgramData\Avid\Archive Service\DMSArchive.ini

Interplay | Consolidate

C:\ProgramData\Avid\Consolidate Service\DMSConsolidate.ini

Interplay | Copy

C:\ProgramData\Avid\Copy Service\DMSCopyMedia.ini

Interplay | Delivery

C:\ProgramData\Avid\Delivery Service\DMSIDService.ini

Interplay | Media Services

Automation

C:\ProgramData\Avid\Media Services Automation\DMSCMService.ini

Interplay | Move

C:\ProgramData\Avid\Move Service\DMSMoveMedia.ini

Interplay | Restore

C:\ProgramData\Avid\Restore Service\DMSRestore.ini

2. Substitute the hostname of the Media Services Engine.

12

Installation and Configuration

Following is an example of a Copy service .ini file with the default hostname localhost:
#Mon May 05 11:34:54 EDT 2014
@5%?MaxJobs=1
@2%tMedia_Services_Engine_Hostname=localhost
@1%tProvider_Name=a51-dev_Copy_4080

Following is the same .ini file, edited to use the hostname a51-ms_engine.
#Mon May 05 11:34:54 EDT 2014
@5%?MaxJobs=1
@2%tMedia_Services_Engine_Hostname=a51-ms_engine
@1%tProvider_Name=a51-dev_Copy_4080

Existing .ini files include the line @3%yAutomatically_Connect=TRUE. This line is no longer
applicable, because all services are now automatically connected.
3. A default name for the provider is automatically created by the provider software using the
following syntax:
<hostname>_<servicename>_<unique#>
The provider name in the previous example is a51-dev_Copy_4080.
Accept the default name or type a new name. This name appears in the Media Services and
Transfer Status tool. The provider name in the previous example
4. Save and close the .ini file.
The service automatically reads the .ini file and tries to connect to the Media Services
Engine. If the service fails to connect, it continues to try to connect every thirty seconds.

The .ini file includes a line that sets the maximum number of simultaneous jobs. Each type
of provider can handle a different maximum number. Do not change this value unless
specifically instructed by Avid Professional Services or Customer Success. For more
information, see Maximum Number of Simultaneous Jobs in the Interplay Media Services
Setup and Users Guide.

Upgrading Existing Service Providers

The following procedure summarizes the steps required to upgrade an existing service provider.
This is a one-time configuration. For more details, see the Interplay Production Software
Installation and Configuration Guide and the Interplay Media Services Setup and Users Guide.
To upgrade an existing service provider:

1. Delete the existing service using Windows Control Panel.

2. Install the new service using the Interplay Production Servers installer.
3. Reboot the provider system.
13

Installation and Configuration

4. Edit the *.ini file, as described in Editing the .ini File on page 12
5. Restart the service in the Computer Management window.
6. Confirm that the service is running in the Providers tab of the Media Services and Transfer
Status tool.

Troubleshooting Service Providers

If the service is not running in the Providers tab, do the following:

Make sure a dongle is attached.

Check the .ini file to make sure the Media Services Engine hostname is correct.

If a job fails:

Check the error log.

If you want to stop a service, use the Services tab of the Task Manager. If you end a process
using Windows Task Manager, the Providers tab of the Media Services and Transfer Status tool
still displays the provider as connected. Windows will detect that the process has ended in
approximately one minute and will automatically restart the service.

For more information, see the Troubleshooting chapter of the Interplay Media Services Setup
and Users Guide.

14

3 Selecting Audio Formats for Copy, Move,

and Deliver
In earlier versions of Interplay Copy, Interplay Move, and Interplay Delivery, transfer of audio
files depended on whether the Include Audio option was selected in the profile. With the option
selected, all audio associated a video clip was transferred with the clip. If the option was not
selected, no audio was transferred with the clip.
Starting with version 3.1, you have the option of selecting which audio formats you want to
include in the operation.

If you are performing a Copy or Move operation from Interplay Access, and you do not use a
profile, the behavior is not changed. Transfer of audio files depends on whether you select the
Include Audio option. A Delivery operation requires a profile.
The following illustration shows the Move profile settings, with a new setting named
AudioQuality. The default option is All.

Option

Audio Formats Included

All

All audio formats associated with the selected asset or assets.

None

No audio included with the selected asset or assets.

Uncompressed

Only high-quality audio formats associated with the selected asset or assets,
for example, PCM or WAV.

Proxy

Only proxy-quality audio formats associated with the selected asset or assets,
for example, MPEG1 Layer 2.

Note the following:

For audio-only clips, the TargetVideoQuality setting is not applicable. The selection is
ignored.

The AudioQuality setting is supported when the Media Services provider is connected to a
Media Services Engine v3.1 or later. The setting is also supported in the Media Services
Status tool in Interplay Access v3.1 when Access is connected to a Media Services Engine
v3.1 or later.

16

If a pre-v3.1 version of Interplay Access is connected to a Media Services Engine v3.1,

Service Description files are already installed on the Media Services Engine, but the
AudioQuality setting is only displayed if you upgrade to v3.1 of Interplay Access.

After the components are upgraded to v3.1, the AudioQuality setting will be displayed in
any existing Copy, Move, or Delivery profiles. It will be marked by a caution icon until you
make a selection from the menu and save the profile.

Data tracks (D tracks) are always included in a Copy, Move, or Delivery job.

17

4 New for Interplay Transcode Profiles

There are two new options for Interplay Transcode profiles:

Interplay Checkin Folder

DATAEXTRACT mode

Interplay Checkin Folder

You can specify the folder where the transcoded assets are stored in the Interplay database. This
applies to the following Transcode profile modes:

DATAEXTRACT

MIXDOWN

DUALMIXDOWN

CROSSRATE

To specify an Interplay Checkin folder:

1. Open and log in to the Media Services and Transfer Status tool. For example, in Interplay
Access, select View > Interplay Media Services Status.
2. Click the Profiles tab.
3. In the Service menu, select Avid Interplay Transcode Service.
4. Click Add in the Profiles area and name the new profile.
5. In the Parameters area, add the name of the Checkin folder. Use a forward slash (/) to add a
folder level as shown in the following illustration.

DATAEXTRACT Mode

You must not set the Interplay Checkin Folder as a top-level folder under AvidWG. Instead,
create the check-in folder at least one level down from the top-level folder.
6. Select the other parameters for the profile, and click Save in the Parameters section.
When you run a transcode job with this profile, the new assets will be created in the
specified folder. If you do not specify a folder name, the default is to create the new assets in
the same folder as the source file.
The following illustration shows the Interplay folder created by the profile in this example.

DATAEXTRACT Mode
DATAEXTRACT mode allows you to extract the D1 track as a separate MXF file when you
transcode DNxHD media that contains embedded ancillary data.
This mode is specific to the Legacy method of handling ancillary data that uses DNxHD media
with the ancillary data embedded in it. It does not apply to the Data Track method where a
master clip contains an accompanying data (D1) track. If you attempt to process a master clip
with an accompanying D1 track, the Transcode operation fails.

19

DATAEXTRACT Mode

This mode is used in a workflow that exports a simplified AAF file using XDCAM HD media.
When you activate DATAEXTRACT mode in a profile, the resulting transcode operation
performs the following tasks:

Creates new transcoded video and audio .mxf files in the specified resolutions.

Isolates the embedded ancillary data in a separate .mxf file data track.

Creates a new clip that references the audio and video tracks plus the new data (D1) track.
The system appends the ,extract extension to the clip or sequence name to designate that
the media file set now contains an extracted D1 track.

The following illustration shows the Transcode profile Parameters area with DATAEXTRACT
mode selected. The illustration also shows an Interplay Checkin Folder field.

The following illustration shows the clip created in this example in Interplay Access.

The clip appears in the specified check-in folder. The system creates the folder if it does not
exist.

The clip name contains the added text ,extract,2.

A new .mxf file is created for the data track.

20

DATAEXTRACT Mode

Limitations for DATAEXTRACT Mode

DATAEXTRACT mode is new for releases later than Interplay Transcode v3.0.5. If you send a
profile specifying DATAEXTRACT mode to an Interplay Transcode v3.0.5 or earlier system,
Interplay Transcode defaults to WHOLE mode, which performs an ordinary transcode based on
the video and audio targets in the profile. The system does not create a D track and does not
report any D track-related errors.

21

5 New in Interplay Administrator V3.1

Interplay Administrator includes the following new features:

New Database Maintenance tools. See New Database Maintenance Tools on page 22.

Support for selecting a specific Interplay Transfer engine, through the Workgroup Transfer
Presets view. See Specifying Interplay Transfer Engines for Direct Transfers on page 24.

These features were introduced in patch releases Interplay Access v2.7.7 and Interplay Access
v3.0.6.

Production Engine Bus Connector View. This service runs on the Interplay Engine and
communicates with the MediaCentral Platform bus. This communication enables the
Interplay Production database to be part of a multi-zone Media | Index. For more
information, see the Avid MediaCentral Platform Services Installation and Configuration
Guide.

New Database Maintenance Tools

The Maintenance view in the Database section now includes the following tools:

Validate Property Objects: Use this tool to check for and repair issues with database
properties, for example, a SettingsNotRegisteredException exception when applying
Editing Settings in the Interplay Administrator.

Clean Up Parentless Objects: Use this tool to check for and repair database objects that do
not have a parent anymore. Hints that such objects exist can sometimes be obtained in the
NxNServer.log with ERRORs like root object has no parent. The presence of such objects
can cause issues such as incomplete search results. All objects in the database must have a
parent. This is true not only for Avid assets that are displayed in the browse tree but also for
all other objects, such as users and other system objects.

These tools are available only when the Interplay Administrator is connected to Interplay Engine
v.2.7.6 or later, or v3.0.6 or later.

New Database Maintenance Tools

The following tool can be run on when the Interplay Administrator is connected to Interplay
Engine v2.7 or later:

Validate AssignedRoles Table: Use this tool to check or fix (by removing) invalid entries in
the AssignedRoles table. This table keeps information about user roles that are assigned to
database objects. The tool verifies this table for integrity and fixes entries if needed.

You cannot cancel these maintenance tools after you have started them. The Validate Property
Objects tool and the Validate Assigned Roles Table tool usually run only for a few seconds,
regardless of the size of the database. The Clean Up Parentless Objects tool might run for an
hour on a very large database.
You can run the tools with or without the following options.

Tool

Options

Validate AssignedRoles Table

Remove Invalid Entries. Select this option to remove invalid entries from the
AssignedRoles table.
If you do not select this option, the tool reports problems but does not take
action to fix them.

Validate Property Objects

Fix Property Objects: Use this option to both check for and fix found issues
with property objects. The results dialog displays how many fixing operations
the tool will perform or has performed.
When this option is not selected, the tool only checks for and reports broken
property objects.

23

Specifying Interplay Transfer Engines for Direct Transfers

Tool

Options

Clean Up Parentless Objects

Clean up parentless objects and move them to the Lost&Found folder. Use
this option to both check for and fix parentless objects. The Interplay Engine
either deletes the parentless object (in case it is not valid or functional
anymore) or restores the object to a new parent folder named Lost&Found.
This folder is created on the database's root folder. The results dialog contains
information if objects were recovered (Restored n parentless objects to the
Lost&Found folder).
If the results dialog reports that it restored objects to Lost&Found, the
administrator should run the tool again. It is possible that the tool will find
additional parentless objects through the restored objects.
When this option is not selected, the tool only checks for and reports
parentless objects.

In rare cases, the read-only run of the tool reports that it found parentless
objects that should be deleted, but after a clean-up operation, the results
dialog does not report any deleted any objects. Subsequent read-only runs
will continue to report these objects to be deleted. (Administrators can find
entries in the Engine logs during the clean-up run that report skipped
objects.) This is not a problem. These objects are special because they do
not cause root object has no parent issues but are difficult to delete.

For complete information about using Database Maintenance tools, see the Avid Interplay
Engine and Avid Interplay Archive Engine Administration Guide.

Specifying Interplay Transfer Engines for Direct

Transfers
You can specify the local and remote Interplay Transfer Engines used during a
workgroup-to-workgroup transfer of Avid assets. This is referred to as a direct transfer.
The direct transfer feature is useful if you need to identify specific hosts that should perform
transfers. It is a way to reserve specific transfer engines for certain operations, thus ensuring
faster transfers. For example, you can specify a transfer engine in your broadcast facility that
only transfers media to a remote site covering a specific sporting event.

24

Specifying Interplay Transfer Engines for Direct Transfers

When creating a direct transfer preset, there are several combinations of Transfer Engines that
you can specify for the transfers:

Let any available local Transfer Engine handle the transfer and specify the remote Transfer
Engine.

Specify a local Transfer Engine to handle the transfer and let any available remote Transfer
Engine receive the transfer.

Specify a local Transfer Engine to handle the transfer and specify a remote Transfer Engine.

Specify a list of local Transfer Engines to handle the transfer and let any available remote
Transfer Engine receive the transfer.

Checklist for Direct Transfer

Use the following checklist to help you configure and perform a direct transfer.
Task

Section Reference

Add the local Transfer Engines to the local

workgroup.

Add the remote workgroup and Transfer

Engines to the local workgroup.

Configuring a Workgroup for Direct Transfer on

page 26
Configuring a Workgroup for Direct Transfer on
page 26

Create a Workgroup Transfer Preset.

Creating a Transfer Preset on page 28

Perform the direct transfer.

Performing a Direct Transfer on page 29

As soon as the first Workgroup Transfer Preset that uses the new options for Local
Transfer Engine or Remote Transfer Engine is stored in the database, an Access V3.0.5
or earlier client will not be able to parse any Workgroup Transfer Presets. After you select
Send to Workgroup, a Malformed serialized string message is displayed and the Send
To Workgroup dialog will not be displayed.
Previously Published Method for Direct Transfer

A procedure for direct transfer is currently documented in the Avid Interplay Transfer Setup and
Users Guide. This method relies on a specifically named Workgroup Preset that includes the
hostnames of the local and remote Transfer engines. Interplay Access v2.7.7 continues to support
this method and improves it through the following fixed bugs:

Bug Number: UDevC00180947. Dependability and usability are not reliable when doing
workgroup transfers with Interplay direct presets.

25

Specifying Interplay Transfer Engines for Direct Transfers

Bug Number: UDevC00180948. Using Direct Transfer Presets for WGtoWG transfers does
round robin model, but one Transfer Engine is specified as sender.

Bug Number: UDevC00180950. There needs to be the ability to set up and use aliases when
configuring Direct Transfer Presets.
The new procedure introduced in Interplay Access V2.7.7 does not rely on a specifically named
preset and is easier to configure and use.

Configuring a Workgroup for Direct Transfer

Before you can perform a direct transfer, you need to configure the workgroup for local Interplay
Transfer Engines and remote Transfer Engines.
To configure a workgroup for direct transfers:

1. Add the local Transfer Engines to the workgroup.

a.

In the Interplay Administrator, click Interplay Transfer Settings in the Site Settings area.
The Interplay Transfer Settings view opens.

b.

Configure the Interplay Transfer Settings as you would for adding Transfer Engines in a
workgroup. See Configuring an Avid Interplay Workgroup For Transfers in the Avid
Interplay Transfer Setup and Users Guide.
In the Transfer Engine Details area, select one of the following from the Workgroup
Transfers menu:
-

No: (Recommended) Removes the Transfer Engine from the pool of available
Transfer Engines and enables it to be used exclusively for direct transfers.

Send and Receive: Specifies that the Transfer Engine can be used for both send and
receive operations. Keeps the Transfer Engine in the pool of available Transfer
Engines, but also keeps it available for direct transfers.

Send Only: Specifies that the Transfer Engine can only be used for send operations.
Keeps the Transfer Engine in the pool of available Transfer Engines, but also keeps
it available for direct transfers.

26

Specifying Interplay Transfer Engines for Direct Transfers

2. In the local workgroup, register remote workgroups and remote Transfer Engines, using the
Interplay Administrator > Site Settings > Configure Remote Workgroups view. The
following illustration shows an example.

For information about the Configure Remote Workgroups view, see Configuring a Remote
Workgroup for Workgroup-to-Workgroup Transfers in the Avid Interplay Transfer Setup
and Users Guide.

The Server name you enter in the Configure Remote Workgroups view appears in the Access
Send to Workgroup dialog box. The Nickname field is not used for Direct Transfer.

27

Specifying Interplay Transfer Engines for Direct Transfers

Creating a Transfer Preset

Use the Interplay Administrator to create one or more transfer presets specifically for the direct
transfers.
To configure a transfer preset for direct transfer:

1. In the Site Settings area, click Workgroup Transfer Presets.

The Workgroup Transfer Presets view opens.

2. Click Add below the Presets list.

Untitled displays in the Name text box.
3. Type a name for the preset in the Name text box.
Type a descriptive name for the preset. This name will be displayed in the Send to
Workgroup dialog box.
4. Select the remote workgroup server from the Remote Workgroup menu.
28

Specifying Interplay Transfer Engines for Direct Transfers

The remote workgroup servers available from the Remote Workgroup menu are defined in
the Configure Remote Workgroups view in the Interplay Administrator.
To enable the option of selecting a remote Transfer Engine (step 6), you must select an
Interplay Engine server. If you do not need to use this option, you can select a Transfer
Engine server.
5. (Option) Select the local Transfer Engine from the Local Transfer Engine menu.
Select a local Transfer Engine if you want to use only the selected Transfer Engine for this
preset. If you do not select a specific Transfer Engine, any available Transfer Engine defined
in the Interplay Transfer Settings view will be used.
6. (Option) Select the remote Transfer Engine from the Remote Transfer Engine menu.
Select a remote Transfer Engine if you want to use only the selected Transfer Engine for this
preset. If you do not select a specific Transfer Engine, any available Transfer Engine defined
in the Configure Remote Workgroups view will be used.
This option is displayed only if you select an Interplay Engine server from the Remote
Workgroup menu (step 4).
7. (Option) Select Workspace and select a destination workspace for the media files from the
Workspace menu.
If you do not select a workspace, the default destination workspace is used.
8. (Option) Select Destination and select a destination folder in the remote workgroup database
for the metadata.
If you do not select a folder, the default destination folder is used.
9. Select Enabled to display this preset in the Send to Workgroup dialog box.
10. Click Apply to save your changes.

Performing a Direct Transfer

To perform a direct transfer from one workgroup to another workgroup:

1. Start Interplay Access by logging into your local workgroup.

2. Make sure your workgroup is configured for direct transfers as described in the previous
topic.
3. From the Content view, right-click on the Avid asset that you want to transfer.
4. Select Send to Workgroup.
The Send to Workgroup dialog box opens.

29

Specifying Interplay Transfer Engines for Direct Transfers

5. From the Destination preset menu, select the preset that you want to use for the direct
transfer.
The preset automatically selects the Destination folder and Workspace.
6. Click OK.
-

If the selected preset includes a destination folder and a direct Remote Transfer Engine,
or if the Remote Workgroup server is a Transfer Engine, you do not need to wait for the
destination folder and workspace to be displayed before you click OK.

If the selected preset does not include a destination or a Remote Transfer Engine, you
must select a destination and then click OK (selecting a workspace is optional). If you
receive an error that states Please select a destination, wait until the destination folder
and workspace are displayed, select your destination, and click OK again.

The transfer begins or is placed in the list waiting for transfer.

If you selected Launch Interplay Transfer Status window on the Send to Workgroup dialog
box, then the status window opens and displays the status of the transfer.

30

6 Port Usage and Media Composer | Cloud

The Interplay Sphere Media Services Engine service on a Media Composer | Cloud client uses
the HyperSQL Database engine. The default port used by HyperSQL on a Media
Composer | Cloud client is 9001. Starting with Interplay Production Services v3.1, you can
change the port based on your site requirements. For additional information on port usage, see
the Media Composer | Cloud Port Usage Guide on the Avid Knowledge Base.

Changing the Port Used By the Interplay Sphere

Media Services Engine Service
The following describes how to change the port on Windows and Mac OS X systems.
To change the port used by HyperSQL on a Windows system:

1. Navigate to the following folder on the Media Composer | Cloud system:

C:\Program Files\avid\Interplay Sphere Media Services Engine\Broker
2. Open the following file in a text editor, such as Windows Notepad.
InterplaySphereMSE.vmoptions
If the file does not exist, create it.
3. Locate or add the following line and change the port number to the number you want to use:
-Dcom.avid.dms.broker.db.hsql.port=9001
4. Save and close the file.
5. In the same directory, open the following file in Notepad:
server.properties
If the file does not exist, create it.
Note that you may have to turn on Show hidden files, folders, or drives to be able to view
the .properties extension.
6. Add or modify the following line and change the number to the port you want to use.
server.port=9001
7. Save and close the file.

Changing the Port Used By the Interplay Sphere Media Services Engine Service

8. Reboot the system and the new port number will be in effect.
To change the port used by HyperSQL on a Mac OS X system:

1. Navigate to the following folder:

/Applications/Avid/Interplay Sphere MSE/Broker/DBScripts
2. Copy the server.properties file to the desktop and open it in TextEdit.
3. Change the number in the following line to the port that you want to use:
server.port=9001
4. Save and close the file.
5. Drag the file back into the DBScripts folder. You will need to authenticate the move or copy
operation as follows:
a.

Click Authenticate in the first dialog box.

b.

Click Replace in the second dialog box to confirm that you want to replace the file.

c.

Enter your Administrator password when prompted.

6. Copy the following file to the desktop and open it in TextEdit:

RunInterplaySphereMSE.bash
7. Change the port number in the following line to the port that you want to use
-Dcom.avid.dms.broker.db.hsql.port=9001 -Xmx256m -Xss256k
8. Save and close the file. Then perform the same operation to move the file back into the
DBScripts folder.
9. Reboot the system and the new port number will be in effect.

32

7 AMA Workflow Changes

This chapter describes changes for working with Avid Media Access (AMA) material in an
Interplay environment. For details on working with AMA material, see the Interplay Best
Practices Users Guide. This chapter covers the following topics:

Media | Director Support

Third-Party Storage Licenses

AMA Online Status

AMA Source File Locations

Deleting AMA Clips in Interplay Access

Locating the .spaaf Files Associated with a Clip

AMA Support and Interplay | Media Services

Media | Director Support

Interplay Production v3.1 supports Media | Director v1.0.1. Media | Director is an optional
service for Interplay Production that allows workgroups to capture file-based footage shot in
various formats quickly by processing it against user-definable profiles that orchestrate copy,
naming and transcode processes via a powerful rules system.
With this option workgroups can dramatically reduce the time spent performing the following
tasks:

Capturing media from a wide variety of file based cameras

Normalizing various formats to create an efficient production workflow

Migrating multi-resolution media to make cost efficient use of tiered storage environments

Making the material available quickly to multiple editors within the Interplay environment

For additional information about Media | Director, see the Media Director Users Guide on the
Knowledge Base.

Third-Party Storage Licenses

Third-Party Storage Licenses

Interplay v3.1 supports third-party (non-ISIS) storage for parking storage of AMA material.
Parking storage is often used to store AMA sources or other material where real-time playback is
not required. For example, parking storage is used as part of a Media | Director workflow where
real-time playback is not required and/or where high-density storage offers a better value for
large files that may need to be stored for an extended period.
The third party storage must be defined as a network share that is publicly accessible. It must
appear on the network as a UNC path. Note that because the storage is shared, you can also
mount it as a letter drive.
To define the third party storage share:

1. Right-click the storage location you want to use as third party storage and select Properties.

The Storage Properties dialog opens.

2. Select the Sharing tab.

34

Third-Party Storage Licenses

3. Click Advanced Sharing. The Share Permissions dialog opens.

35

Third-Party Storage Licenses

4. Give Everyone full access to the share and click Apply and OK.
The share is ready to be added to the Interplay environment.
To obtain and configure a third-party storage license:

1. Purchase a Key-CI license from your Avid representative and add the license to your
Interplay system using the Licenses view in the Interplay Administration tool. See the
Interplay System Administration Guide for details on obtaining and installing a license.
2. Configure the network share for the license as described in the previous procedure.
3. Open the Third Party Storage view in the Server section of the Interplay Administrator tool.

4. Click Add and add the network share as a UNC path.

5. Click Apply.

36

Third-Party Storage Licenses

To register the third party storage with the Media Indexer:

1. Open the Media Indexer web interface in a browser as follows:

http://<MI system name>:8888/mi/
where <MI system name> can either be the name of the system running the Media Indexer or
its IP address. The string :8888 identifies the port that the Media Indexer system uses for
web communication.
2. Click the Configuration button at the top of the window and click Storage Locations.

3. Click Add AMA Storage Location and add the network share as a UNC path. Then click
OK.

The third-party storage location is added to the list of storage locations. Note that storage
locations with a 3rd party license associated with them are designated with a green E (stands
for explicit license) icon. Other storage locations have an I (implicit license).

37

AMA Related Changes In Interplay | Access

AMA Related Changes In Interplay | Access

AMA Online Status

AMA Source File Locations

Deleting AMA Clips in Interplay Access

Locating the .spaaf Files Associated with a Clip

AMA Online Status

In Interplay v3.0.x, the AMA status has only AMA media was shown with a red dot in Access.
Starting in Interplay v3.1, material that has only AMA media is identified with a purple dot as
shown in the following illustration.

Material associated with both AMA and non-AMA material (has AMA media linked) is shown
with a green dot.

AMA Source File Locations

The Interplay Object Inspector now shows the location of the associated AMA source file in the
File Path column of the File Locations tab. The following illustration shows a clip that only has
AMA media associated with it.

38

AMA Related Changes In Interplay | Access

The extension of the AMA source file depends on the AMA plugin used to create the file. For
example, QuickTime files have a .mov extension. Note that when you delete the AMA clip in
Access you delete the reference to this source file.
The following illustration shows the file locations for a clip that has both AMA media and proxy
media. The AMA source file is highlighted. Note that the AMA media is stored in a separate
workspace (named AMAfiles in this example). Following this best practice helps you to organize
your AMA material.

39

AMA Related Changes In Interplay | Access

Deleting AMA Clips in Interplay Access

When you delete an AMA clip from the Interplay database, you delete the reference to the AMA
source file. This reference includes a number of .spaaf files, one for each track in the AMA
source file. For additional information on .spaaf files, see the Interplay Best Practices Guide.
The following illustration shows two clips selected for deletion. Both clips have green dots
meaning they are associated with multiple resolutions. In this case the clips have associated
AMA and proxy media.

40

AMA Related Changes In Interplay | Access

The following illustration shows the delete dialog box for this example. The 18 media files that
will be deleted are associated with the proxy media. The two AMA references refer to the
Interplay database reference to the AMA source file. The reference to the source file will be
deleted along with the associated .spaaf files created when the AMA clip was checked into the
Interplay database. Note that there is no reference to the .spaaf files in the Delete dialog box.

41

AMA Related Changes In Interplay | Access

When you delete an AMA clip from the Interplay database the system does not delete the AMA
source files. It only deletes the reference to the AMA source file and the associated .spaaf files.

42

AMA Related Changes In Interplay | Access

Locating the .spaaf Files Associated with a Clip

The information in this section is not new for this release but it is useful for troubleshooting
purposes.
To use Access to locate the .spaaf files associated with a clip:

1. Right-click the clip in Access and select Advanced > Get/Set Properties.

2. Click the All Properties tab and scroll down to the Incoming Dependencies section.

43

AMA Related Changes In Interplay | Access

3. In the Physical_Mob_Dependency row, double-click the link that starts with the text
NXN_Server.
4. Select the All Properties tab and scroll down to the entry for ProxyLocatorPath. This
identifies the folder that contains the .spaaf files associated with this clip.

44

AMA Related Changes In Interplay | Access

The top level folder should correspond to the folder you identified for .spaaf files in the
Server Hostname Settings view of the Interplay Administrator tool. The following
illustration shows the corresponding setting for this example.

45

AMA Related Changes In Interplay | Access

To locate .spaaf files in the Media Indexer web interface:

1. Open the Media Indexer web interface in a browser as follows:

http://<MI system name>:8888/mi/
where <MI system name> can either be the name of the system running the Media Indexer or
its IP address. The string :8888 identifies the port that the Media Indexer system uses for
web communication.
2. Click the Storage Browser button and navigate to the AMA section on the bottom left of the
window.
3. Navigate to the workspace and folder that you are interested in. In this example we examine
the folder identified earlier in AMA Source File Locations on page 38.

46

AMA Related Changes In Interplay | Access

4. Scroll all the way to the right to see the .spaaf files associated with this folder.

47

AMA Support and Interplay | Media Services

AMA Support and Interplay | Media Services

Interplay | Transcode is the only Interplay Media Services provider that works with AMA source
media. Other providers such as Interplay | Move, Interplay | Copy, and Interplay | Deliver do not
support AMA source media.
If you want to use Media Services providers with AMA material you must transcode the material
first.

48

8 Interplay | Transfer Changes

This chapter describes new features for Interplay | Transfer v3.1:

Configuring OP1A/XDCAM Profiles for Catalog Checkins

Writing to a Temp File with Generic FTP profiles

Configuring OP1A/XDCAM Profiles for Catalog

Checkins
Interplay | Transfer v3.1 allows you to configure OP1A/XDCAM profiles for catalog checkins.
To configure OP1A/XDACM Profiles for Catalog Checkins:

1. Create an OP1A FTP profile in the FTP Server dialog box, as shown in the following
illustration. The profile name FTP1 refers to the FTP server with the hostname CET-FTP.

2. In the Playback Device dialog box, create a new playback device that references the OP1A
FTP server device configured in the FTP Server dialog box.

Configuring OP1A/XDCAM Profiles for Catalog Checkins

a.

Specify the Profile Name. This is the name that will appear in the editor as a playback
target.

b.

Specify the Device Name. This is the profile name of the OP1A FTP device configured
in the FTP Server dialog box.

c.

Leave the Service Host and Service Port fields blank.

d. Select Enable Playback Catalog Name and specify the Catalog name.
e.

Click OK.

(UDevC00184240) The first time you click OK, the Enable Playback Catalog Name option
becomes unchecked. Workaround: Select the Enable Playback catalog Name option again and
click OK.
3. Select the newly created Playback Device, not the original OP1A_EXPORT profile, as your
playback target in the editor.
Note the following:
-

The catalog checkin simply updates an asset in Interplay Access that has been
previously checked in to Access by the editing application or by STP Encode. This
feature relies on the XDCAM sequence having already been checked in to Access and
will not work if it has not.

A single OP1A device can be used to configure multiple Playback Devices with
different catalog names.

50

Writing to a Temp File with Generic FTP profiles

Writing to a Temp File with Generic FTP profiles

The Write to Temporary File playback profile option causes OP1A media files to be written to
a temporary file (.tmp extension) during the transfer. After the transfer is complete, the system
renames the file with an .mxf extension.
This is done to prevent automation systems from attempting to move the file while the file is still
being transferred. The following illustration shows how this option is enabled through the
Transfer Engine configuration tool.

51