® Avid Interplay ® What’s New in Version 3.
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.
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.
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.
Contents Chapter 1 What’s New in Interplay Production Version 3.0 . . . . . . . . . . . . . . . . . . . . . . 7 Chapter 2 Support for Group Clips in Interplay Production V3.0. . . . . . . . . . . . . . . . . 12 Chapter 3 Support for Restrictions in Interplay Production V3.0 . . . . . . . . . . . . . . . . 14 Chapter 4 Using AMA Material in Interplay . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18 Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Chapter 9 Configuring a Workgroup to Use Multiple Archive Engines . . . . . . . . . . . 49 Check List for Configuring and Using Multiple Archive Engines . . . . . . . . . . . . . . . . . . . 49 Required Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50 Terminology . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50 Creating Profiles . . . . . . . . . . . . . . . . . . . . .
1 What’s New in Interplay Production Version 3.0 This guide provides information about the new features in Interplay Production version 3.0. n For the latest information about new features and documentation changes, see the Avid Interplay ReadMe on the Avid Customer Support Knowledge Base. Support for Interplay Sphere on Macintosh Interplay v3.0 provides full support for Avid Interplay Sphere on Macintosh systems.
Interplay Access now includes a Restrictions tab in the Object Inspector. For more information, see “Support for Restrictions in Interplay Production V3.0” on page 14. Support for AMA Media in Interplay Interplay v3.0 supports checkin and dynamic relink of AMA (Avid Media Access) material. For more information, see “Using AMA Material in Interplay” on page 18. Changes in Media Indexer There are three major changes for Media Indexer v3.
64-Bit Applications The Interplay Engine and other Interplay components have been re-engineered to run as 64-bit applications. See “Support for 64-Bit Applications” on page 48. Interplay Components Qualified on Windows 8 Interplay components and Interplay Sphere components have been qualified on computers running the Microsoft Windows 8 operating system. See “Interplay Components Qualified on Windows 8” on page 61. Media Services Features Media Services v3.
• Interplay Administrator v3.0 introduces a new option to the InterplayRestore tool that lets you select an incremental backup to use for the restore process, without restoring the complete database. For more information, see “Performing a Partial Restore of an Interplay Production Database” on page 83. • A Central Configuration Server (CCS) can be used for more than one Interplay Engine. Starting with Interplay V3.0, a CCS that is created on an Interplay V3.
Changes to the Interplay Installers • The Interplay v3.0 Client Installer is now available for Macintosh systems as a downloadable DMG file. In previous versions of Interplay you needed to copy a folder of individual installers from the installation media. • Pro Tools Plug-Ins for Interplay are no longer delivered on the Interplay Client Installer. For more information about using Pro Tools with Interplay, go to the Knowledge Base page titled “Avid Interplay Requirements With Pro Tools.
2 Support for Group Clips in Interplay Production V3.0 Group clips are created in Media Composer and other Avid editing applications by using MultiCam features to sync a group of clips based on common source timecode, auxiliary timecode, or marks placed in the footage. A user working in an Avid editing application can check group clips in to and out from an Interplay Production database. Interplay Access users can view information about group clips, including master clip relatives.
Support in Interplay Access In previous versions of Interplay Access, if you selected a sequence that contained a group clip, the Relatives tab in the Object Inspector displayed the master clips that composed the group clip, but did not display the group clip itself. Beginning with Interplay Access v3.0, the Relatives tab shows the group clip. The following illustration shows a selected sequence that contains one group clip. The group clip icon is grayed out because it is a referenced-only asset.
3 Support for Restrictions in Interplay Production V3.0 A restriction is a type of locator that Interplay Assist and Interplay Central users can add to a clip to indicate that use of the clip is restricted in some way, such as a requirement to pay for its use. Previous versions of Interplay preserved restrictions when you used an Avid editing application to check out and check in a clip before sending it to an Interplay Production service. For Interplay v3.
Note the following limitations: • A restriction includes a color value (used for its markers) and the username of the creator. These values are supported in the local workgroup. However, after a clip is transferred to another workgroup or restored from archive, the values default to color = white and username = the login name of the user requesting the job. • A sequence that includes a master clip with restrictions uses a copy of the master clip.
The Restrictions tab is shown for master clips and stereoscopic clips. Sequences and subclips do not contain restrictions but they can reference master clips that include restrictions. These sequences and subclips are indicated in the DRM column, but the Restrictions tab is not displayed. n An Interplay administrator might need to enable display of the DRM column in the Property Layout view. For more information, see the Avid Interplay Engine and Avid Interplay Archive Engine Administration Guide.
An Interplay Access user can override these global settings in the View Settings tab of the Options dialog box, as shown in the following illustration.
4 Using AMA Material in Interplay This chapter contains the following topics: • Overview • AMA on Interplay Workflow • Viewing AMA Clips in Access • How the Media Indexer Works with AMA Material • Configuring the Media Indexer to Index AMA Overview Interplay v3.0 and later supports checkin and dynamic relink of AMA (Avid Media Access) material.
AMA on Interplay Workflow AMA on Interplay Workflow The following illustration shows a basic AMA workflow for Interplay. Interplay Engine Media Composer NewsCutter ICS Server e Playback Transcoded Material Check in to Interplay q q Copy Avid ISIS 5000/7000 w Link to AMA t Transcode ISIS 2000 Parking Storage QuickTime Interplay Central y Hi-Res Consolidate Access to AMA r Media Composer NewsCutter The following sections describes these numbered portions of the AMA workflow for Interplay.
AMA on Interplay Workflow a high ratio of shooting versus footage used in the final production. In this scenario you would have a multiple ISIS setup; one for the original AMA material and one for your production material. Create a folder structure in the ISIS parking area that organizes the material by project and use a unique name for each new folder.
AMA on Interplay Workflow n Before you begin to check the AMA files into Interplay, you must manually create the top level folder for the .spaaf files and configure the Media Indexer to index that folder. Avid recommends that you dedicate a specific workspace for the spaaf files. See “Configuring the Media Indexer to Index AMA” on page 27. The SPAAF workspace on ISIS must be mounted and accessible by the editing user on the editing machine.
Viewing AMA Clips in Access Viewing AMA Clips in Access After you check an AMA clip into Interplay you can search for or navigate to the clip in Access. The following illustration shows an AMA clip in the Access Object Inspector.
Viewing AMA Clips in Access The following information is specific to using Access with AMA material. • There is a new column in the Assets view named AMA Media Status. This allows you to determine whether the object you are looking at contains AMA material. The column displays one of the values described in the following table.
Viewing AMA Clips in Access To turn on the display of the AMA Media Status column and search fields in Access: 1. Open the Interplay Admin tool. 2. Open the Properties Layout view in the Site Settings area. 3. Select the three columns for AMA Media Status and click Apply. 4. In Interplay Access, select Properties from the View Presets menu in the Assets view. 5. Select AMA Media Status and click Apply.
How the Media Indexer Works with AMA Material How the Media Indexer Works with AMA Material In releases prior to Interplay v3.0, the Media Indexer was not able to index AMA material. This limitation is related to the difference between AMA material (OP-1A format) and the OP-ATOM format associated with .mxf material. The following illustration compares OP-1A and OP-ATOM material. AMA AAF (OP-1A) Avid AAF (OP-ATOM) C C One file ID containing three descriptors. One descriptor per channel. D.V1 D.A1 D.
How the Media Indexer Works with AMA Material Checking AMA Media Into Interplay - Comparing OP-ATOM and OP-1A Avid AAF (OP-ATOM) Format The example in the previous illustration uses a clip with one video channel and two audio channels. The top portion of the Avid AAF section is a representation of what you can see in an Avid editing system bin for digitized MXF material. The metadata contains the following: • A clip ID • Three file IDS, one for each video and audio track.
Configuring the Media Indexer to Index AMA Configuring the Media Indexer to Index AMA You use the Media Indexer web interface to connect to AMA material. To open the web interface, enter the following in a browser window: http://:8888/mi/ where 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.
Configuring the Media Indexer to Index AMA 3. Click Apply Configuration. To identify the location of the AMA media files: 1. Click the Storage Locations tab. The system displays the locations of .mxf media on shared storage as well as any previously defined AMA storage locations. The AMA locations are identified with a folder icon. n The Media Indexer needs to know the location of the AMA media files but it does not index those files. The Media Indexer indexes the related .
Configuring the Media Indexer to Index AMA 4. Click OK. The AMA storage location appears in the list of storage locations. A folder icon identifies it as an AMA storage location. n Do not mix .mxf media files and AMA media files in the same storage location.Also, do not mix .spaaf files and AMA media files in the same location. To identify the location of the .spaaf files on the Interplay Admin tool: 1.
Configuring the Media Indexer to Index AMA n Avid recommends that you set up a specific workspace for the .spaaf files. Do not add .mxf files to this workspace. 3. Click Apply Changes. Viewing Statistics about AMA Media You can view information about AMA files using the Media Indexer Statistics page and Storage Browser. Note that this information is not available until you check the AMA media into the Interplay database. To view storage statistics about AMA files: 1. Click the Statistics tab. 2.
Configuring the Media Indexer to Index AMA Note that the Total size provided in the statistics and the Storage Browser window for AMA relates to the size of the .spaaf files. The size of the AMA media files is not known to the Media Indexer. To obtain the total file count for the Media Indexer: t n Add the Files values from the “Storage Statistics” and “AMA Storage Statistics” panes together to obtain the number of files that the Media Indexer is indexing. Recall that a separate .
Configuring the Media Indexer to Index AMA Using the Storage Browser Starting at Interplay v3.0, the Storage Browser window contains separate sections for MXF media and AMA media. To view information about AMA media in the Storage Browser: 1. Click the Storage Browser tab. The Storage Browser window opens to show separate folders for MXF and AMA media. You can use the storage browser to see how the AMA media files are organized.
5 Media Indexer Changes for Interplay v3.0 This chapter covers the following topics: • Increased Monitoring Capacity • Configuring Media Indexers for Interplay v3.0 • Configuring Media Indexer Servers and Clients For information specific to using AMA material in Interplay, see “Configuring the Media Indexer to Index AMA” on page 27. Increased Monitoring Capacity Starting at Interplay v3.
Configuring Media Indexers for Interplay v3.0 Check List for Connecting Media Indexer Servers and Clients Task Section Reference Uninstall previous versions of the Media Indexer on Media Indexer servers and clients. Then install Avid Service Framework v1.6 or later and Media Indexer v3.0 or later on the Media Indexer servers and Windows Avid editing clients. Install ASF v1.
Configuring Media Indexers for Interplay v3.0 Check List for Connecting Media Indexer Servers and Clients Task Section Reference Note that the following applications automatically See “Identifying the Media Indexer in the use the Media Indexer URL entry in the Interplay Interplay Administrator Tool” on page 39. Administrator tool to connect to the MI.
Configuring Media Indexer Servers and Clients 5. Configure the Media Indexer servers and clients as described in the following section. Configuring Media Indexer Servers and Clients Starting at Interplay v3.0, the Avid Service Framework (ASF) is no longer used to make the connection between the Media Indexer servers and the Avid editing applications.
Configuring Media Indexer Servers and Clients 2. Click the Configuration tab and then click the Cache and HAG Information tab. The following illustration shows a completed section. 3. Click the Join High Availability Group check box. 4. Enter the Name of the HAG and enter the weight of this Media Indexer in the HAG. In this example, the name of the HAG is “HAG.” The Media Indexer with the highest weight is the leader of the HAG.
Configuring Media Indexer Servers and Clients The following illustration shows an MI configured with several .mxf and AMA storage locations. The AMA locations are represented by a folder icon. Adding an Additional Media Indexer to the HAG You can use the MI web interface or the Service Configuration tool to add Media Indexers to the HAG for redundancy. To use the web interface to add an additional Media Indexer: 1. Open the web interface for the second MI server. 2.
Configuring Media Indexer Servers and Clients Identifying the Media Indexer in the Interplay Administrator Tool The following applications use the Server MI Connection URL setting in the Interplay Administrator tool to locate the Media Indexer servers.
Configuring Media Indexer Servers and Clients 4. Add the name of the MI server and click Apply Changes. 5. If you have more than one MI in the HAG, add the other MI servers also. Note that additional Media Indexer servers must join the HAG in order to connect to the URL. The system creates a URL for the Media Indexer server and displays the URL below the MI Servers window. The URL contains the MI server name and port 61717. This is the default port used to connect to the Media Indexer server.
Configuring Media Indexer Servers and Clients Configuring the Local Media Indexer on an Avid Editing System You do not need to explicitly add the local Media Indexer to the HAG. If the “Server MI Configuration URL” is correctly set in the Interplay Administration tool, the Avid editing application will automatically connect to the HAG when you log into Interplay. Do not use the “Connect to AMQ server MI” button on the web interface to make an explicit connection to the Media Indexer HAG.
Configuring Media Indexer Servers and Clients The system displays the storage locations for the Media Indexer server as shown in the following illustration. Note that mxf file locations are displayed but AMA file locations are not displayed in this section. Using the Avid Service Framework on a Mac OS X System You do not have to connect to the Avid Service Framework (ASF) in order to connect to the Media Indexer HAG.
Configuring Media Indexer Servers and Clients To run the configure.sh script: 1. Open a terminal window and navigate to the bin folder as follows: cd /Applications/Avid/Media\ Indexer/bin Note that the back slash ( \ ) is used to add a space to the path name. 2. Type the following command: sudo ./configure.sh enter the workgroup name and the name of the system running the Lookup Service separated by a space. For example: sudo ./configure.
Configuring Media Indexer Servers and Clients n When you click Apply in the Workstation Properties tool, the system asks whether you want to restart the services. However, it does not restart the services automatically on a Mac. You must restart the Media Indexer service manually. After you exit the application, the system displays a message about the Logging Subsystem. You can ignore the message.
6 XAVC-Intra Resolutions Supported in Interplay Interplay v3.0 supports workflows for clips and sequences that use XAVC-Intra resolutions. You can work with XAVC-Intra material in an Avid editing application, check it in and out of the Interplay database, and transcode it to other resolutions through Interplay Transcode. These resolutions are supported only as sources for Interplay Transcode. The following table lists the supported resolutions.
7 Enabling Interplay Synced Projects Interplay Synced Projects provide you with a way to link your bins and projects in Media Composer or NewsCutter with the folder structure for assets stored in your Avid Interplay database. Before you can use synced projects, you need to enable the Synced Projects setting in Interplay. Folders for Interplay Synced Projects are indicated by a synced project icon. Media assets in these folders update as users modify the projects in Media Composer and NewsCutter.
To enable synced projects: 1. In the Site Settings section of the Interplay Administrator window, click the Synced Project Settings icon. The Synced Project Settings view opens. 2. Select Enable, and then click Apply. The application enables synced projects for the selected workgroup.
8 Support for 64-Bit Applications The Interplay components listed in the following table have been re-engineered to run as 64-bit applications. Interplay Component Qualified Server and Operating System Interplay Engine v3.0 AS3000 Dual-Processor 12 GB RAM, running Windows Server 2008 R2 SP1 Standard 64-bit Interplay Archive Engine v3.0 AS3000 Dual-Processor 12 GB RAM, running Windows Server 2008 R2 SP1 Standard 64-bit Interplay Engine Failover Cluster v3.
9 Configuring a Workgroup to Use Multiple Archive Engines Avid Interplay v3.0 and later lets you configure a workgroup to use more than one Interplay Archive Engine. A workgroup can be configured to archive to and restore from a maximum of three Archive Engines.
Required Software Required Software The following Interplay Production software is required for using multiple Archive Engines: • Access v3.0 This release is required on any workstation that initiates archive or restore operations in a multiple-archive workgroup. • Interplay Archive 3.0, Interplay Restore 3.0. Install these services from the Avid Interplay v3.0 Server installer. n For Interplay V3.0, service description files and providers are automatically registered.
Creating Profiles Creating Profiles After you install the software, you can create profiles as described in the Avid Interplay Media Services Installation and User’s Guide. The Interplay Archive and Interplay Restore services include the following new profile settings: c • Avid Interplay Archive Service profile: An Archive profile includes one new setting: Archive Engine Name, which lets you specify which archive engine you want to use for the profile.
Creating Profiles n When upgrading the services, all existing profiles are saved. The new settings are added to all existing profiles and are marked with a caution icon, as shown in the following illustration. This icon indicates that the profile might require information for the new settings. Examples The profiles in the following examples use BSI-AM1 as the Archive Engine for low-res media, and BSI-AM2 as the Archive Engine for high-res media.
Creating Profiles Two Profiles: One for Low Res, One for High Res In the first profile, low-res H.264 1080i proxy media is archived to BSI-AM1. In the second profile, high-res HD 1080i media is archived to BSI-AM2.
Creating Profiles One Profile: Subjob for Low Res, Subjob for High-Res The following profile is an example of using subjobs to archive low-res and high-res versions of the same clip. The first illustration shows subjob 1, in which the lowest available resolution is archived to BSI-AM1. The second illustration shows subjob 2, in which the highest available resolution is archived to BSI-AM2.
Configuring Asset Tracking Configuring Asset Tracking Asset tracking is a feature in Interplay Access that lets you display information for assets that are shared by different workgroups. You can use asset tracking to determine if assets that are stored in one workgroup are correctly archived in an archive workgroup. Information is displayed in the Tracking column and the Tracking Details tab.
Configuring Asset Tracking The following illustration shows the Tracking Details tab. It shows the low-res media archived and online on BSI-AM1 and the high-res media archived and online on BSI-AM2. Media is offline on BSI-ENG1, the Interplay Engine.
Configuring Asset Tracking 3. Type the hostname for the secondary Archive Engine in the Configured hosts field, then click Add. The hostname is displayed in the Configure Hosts text box.
Configuring Asset Tracking You do not need to add the hostname for the primary Archive Engine. It is already specified in the Archive and Restore Settings section. 4. (Optional) Repeat this action for the tertiary Archive Engine, if you are using one. 5. Click Apply Changes. n To track a remote workgroup, you need to specify the remote workgroup and its Lookup Locator in the Avid Interplay Workgroup Properties.
Configuring Asset Tracking Adding the Tracking Column to the Assets Pane If you want to display the Tracking column, you need to make it available in the Interplay Administrator. To add the Tracking column to the Assets pane: 1. In the Site Sections section of the Interplay Administrator window, click the Property Layout icon. 2.
Configuring Asset Tracking Updating the Status of Selected Assets Before you display tracking details, make sure you update the status of the assets you want to track. To update the status of selected assets: 1. In Interplay Access, connect to the servers for which you want to view assets. 2. Select an asset, a folder, or multiple assets and folders 3. Select Tools > Update Asset Tracking. The status of the selected assets is updated. Displaying Tracking Details To display tracking details: 1.
10 Interplay Components Qualified on Windows 8 The following Interplay components are qualified on computers running the Microsoft Windows 8 operating system: • Avid Service Framework • Interplay Access • Interplay Media Indexer • Interplay Transfer client for Avid editing systems The following Interplay Sphere components are also qualified on Windows 8: • Interplay Remote Upload Service • Interplay Media Services for Interplay Sphere • Interplay Delivery for Interplay Sphere • Interplay Tran
11 New Features for Media Services V3.0 • Automatic Registration of Services and Providers • Automatically Connecting to the Media Services Engine • Multiple Transcode Providers on the Same Server • Copying Rendered Effects and File Assets • Specifying User Credentials in a Delivery Profile Automatic Registration of Services and Providers Interplay Media Services v3.0 makes configuration easier by automatically registering services and providers.
Automatically Connecting to the Media Services Engine In Media Services v3.0, you only need to perform step 2. A Media Services v3.0 provider automatically generates a name for the provider that it displays in the Provider Settings dialog box.The name uses the syntax __, for example “AvidInterplay1_Restore_9558.
Multiple Transcode Providers on the Same Server Multiple Transcode Providers on the Same Server Interplay Transcode v3.0 and later is qualified to run as multiple instances on the same server. Up to four providers are supported, depending on the total amount of CPU used. Determining the Number of Providers to Install To determine the optimum number of providers to install on a server, check the system resources currently used for your Transcode workflows.
Multiple Transcode Providers on the Same Server Installation The Interplay Transcode v3.0 installation program includes a new option that lets you select the number of instances of the Transcode provider that you want to install. Select the number of transcode providers specified in your license and dongle. The installation program installs executable files for the number of providers you selected, named DMSTranscode.exe, DMSTranscode 2.exe, and so on. It also installs one Service Description file (.
Copying Rendered Effects and File Assets Copying Rendered Effects and File Assets Interplay Copy v3.0 and later supports copying of media for rendered effects (precomputes) and file assets (non-Avid assets) through settings in the Interplay Copy Service profile. • Copy Precompute Media is a new profile setting. • File Asset was a setting in previous releases but is now fully functional.
Specifying User Credentials in a Delivery Profile To clear the database property for copying of rendered effects: 1. Log into Interplay Access as an administrator. 2. In the Assets browser, right-click the root database node (AvidWG) and select Advanced > Get/Set Property. 3. In the Get/Set Property tab, type copyPrecomputeMedia in the Name field. 4. Make sure the Value text box does not have a value. 5. Click Apply. 6. Click OK.
Specifying User Credentials in a Delivery Profile 6. Click OK. The name appears in the Profiles list and an empty template appears in the Parameters area. 7. In the Parameters area, specify the required information, including the Destination_Name and Destination_Password. When you type the password, asterisks are displayed in place of the password. 8. Click Save in the Profiles area. The Save Profile dialog box opens. 9. Click Yes to save your changes.
Specifying User Credentials in a Delivery Profile 69
12 New for Interplay Transfer v3.0 This chapter contains the following topics: • 64-bit Version of Interplay Transfer • Support for DNxHD 444 Ingest and Playback • Background Processes for Interplay Transfer • Creating Transfer Engine Tape IDs for STP Transfers 64-bit Version of Interplay Transfer Starting at Interplay Transfer v3.0, the Transfer Engine runs as a 64-bit application.
Background Processes for Interplay Transfer Background Processes for Interplay Transfer Starting at Interplay Transfer v3.0, Interplay Transfer runs the following as background processes: • Playback • Ingest • DET This technique is also referred to as “out of proc.” (out of process). The system creates a separate process for each playback, ingest, or DET job.
Background Processes for Interplay Transfer The following illustration shows the background processes running in the Windows Task manager. You normally do not need to be concerned about these processes. They are added here for troubleshooting purposes.
Creating Transfer Engine Tape IDs for STP Transfers Creating Transfer Engine Tape IDs for STP Transfers A new setting has been added to the Transfer Engine “Playback Device” configuration, which allows tape ID names to be modified by the Transfer Engine before issuing the Send To Playback Request. In the case of Generic FTP Send To Playback, this will result in the renaming of the asset to the new format when writing out to the FTP server.
Creating Transfer Engine Tape IDs for STP Transfers 4. Type a string in the Tape ID field as follows: n a. Select a tag from the Add menu. For additional information, see “Using the TapeID Format String” on page 74. b. Add any additional text before or after the tags you select. Text that is not contained between angle brackets will be added to the tape ID name. The illustration above shows an example string. The field is blank by default. To clear the string, delete the text and click OK. 5.
Creating Transfer Engine Tape IDs for STP Transfers Tape ID Examples The following examples show how to use the Tape ID format string. Clip created on the Media Composer with tape ID Bruins001 Tape ID Format String: - Resultant Tape ID on the Playback device: Bruins001-060a2b340101010101010f0013-000000-4ea6b88b890a0547-060e2b347f7f-2a80.
Creating Transfer Engine Tape IDs for STP Transfers 4. Leave the following fields blank as shown in the above illustration: - Profile Name - Service Host - Service port 5. Enter the profile name in the Device Name field. 6. Configure the Tape ID field as described earlier and click OK.
13 New License Types and Usage Starting with Interplay version 2.7, customers can buy two types of client licenses: • Interplay Central Base license • Interplay Central Advance license The names of these licenses include Interplay Central, but the licenses themselves are used for all Interplay client applications.
License Types Currently Used for Interplay Production License Type Key Application or Product Central Base Client KEY-J • Digidesign™ Pro Tools®Integration • Interplay Access • Interplay Assist • Interplay Central, access to iNEWS only or Interplay Production only. Limited feature set. See the Avid Interplay Central Administration Guide for details.
The Interplay Engine uses “smart licensing” to manage Base and Advance licenses to allow optimum usage of free licenses. It assigns an Advance license to a Base client if a Base license is not available. It switches the assignment if an Advance client needs a license and a Base license becomes available. For example: 1. Client 1 requires a Base license, and is assigned the last free Base license. Client workstation 2 requires a Base license, but only an Advance license is available.
License Types Previously Used for Interplay Production Applications Prior to Interplay version 2.7, customers purchased licenses for individual products. The following table lists how these legacy licenses relate to current license types, how they are displayed in the Interplay Administrator Licenses view, and which applications they license.
Legacy license types Current license types Current license types and legacy license types 81
If a facility is using a mix of legacy licenses and current licenses, the Interplay Engine first looks for an appropriate legacy license. If none are available, it looks for an appropriate current license. For example: 1. An Assist client logs on. The Interplay Engine looks for an Assist license (KEY-XL) 2. If it does not find one available, it looks for a Base license (KEY-J). 3.
14 Performing a Partial Restore of an Interplay Production Database Interplay Administrator v3.0 introduces a new option to the InterplayRestore tool that lets you select an incremental backup to use for the restore process, without restoring the complete database. Restoring from one or more incremental backups is referred to as a partial restore. Prior to this release, the InterplayRestore tool always restored the complete database, even if you selected to restore from an incremental backup.
Backup restore chain 0. Test_2013-02-04_16-39 full 1. Test_2013-02-04_16-42 incremental 2. Test_2013-02-04_16-44 incremental The InterplayRestore tool gives you an option of selecting a partial restore. If you type “y,” you are asked to select which file in the restore chain from which to start the restore. In the example, backup file 1 (Test_2013-02-04_16-42) is selected.
Non-interactive mode: InterplayRestore /metadata F:\Workgroup_Databases\Test /backupdir F:\Workgroup_Databases\Test\_Backup /printchain Interactive mode: InterplayRestore /printchain In either case, you are asked to choose a backup starting point. Choose a backup to restore from: [1] [2] [3] [4] 04 04 04 24 February February February February 2013 2013 2013 2013 16:39:00 16:42:00 16:44:00 01:00:00 full incremental incremental full Choose an entry ( 1 - 4 ): 3 Backup restore chain 0.
0. Test_2013-02-04_16-39 full 1. Test_2013-02-04_16-42 incremental 2. Test_2013-02-04_16-44 incremental Is this a partial restore (y/n): y Choose an entry in the restore chain to start from ( 1 - 2 ): 1 Choose how many entries to restore ( 1 - 2 ): 2 Project Test already locked Restoring to F:\Workgroup_Databases\Test\ Beginning restore from F:\Workgroup_Databases\Test\_Backup\Test_2013-02-04_16-42\ This is a incremental backup Copying streamed properties...
15 Additional Documentation The following sections provide corrections to or additional documentation for features in earlier releases. Avid Instinct Does Not Support STP Encode “Performing Send-to-Playback as a Background Process from an Avid Editing Application” in the Avid Interplay Media Services Setup and User’s Guide stated that the option “PWT” is referred to as “High Priority” in Interplay Assist and Avid Instinct. STP Encode is supported in Interplay Assist, but not in Avid Instinct.
Note the following: • Starting with version 2.6, the Interplay Transcode service and the STP Encode service require you to choose during installation how ISIS workspaces are mounted: by drive letter or by UNC path. For multiple ISIS workgroups, select UNC paths if the number of workspaces required for the client exceeds the available drive letters. Mount the workspaces before you start the service. You use the ISIS Client Manager or MediaNetwork Connection Manager to mount drives.
Copying metadata: Interplay Copy copies metadata from the source folder to the destination folder. If a clip already exists in the target folder, Interplay Copy overwrites the clip's metadata, and any new properties are merged. For example, you are copying clips from WG1 to WG2 and the same master exists in both workgroups. There is a custom property called Director for this master clip in WG1 but not in WG2. After copying from WG1 to WG2, the master clip in WG2 will have the property Director.
Relinking Partially Delivered and Partially Restored Assets The grayed-out reservation indicates a duplicate resolution. In this case, the same user has previously added a reservation on a child folder of the selected folder, so the parental reservation is grayed out. Relinking Partially Delivered and Partially Restored Assets Interplay Restore in partial mode lets you restore from archive only portions of the media that is used in a subclip, sequence, or shotlist.
Creating a Metadata-Only Backup for Customer Support Creating a Metadata-Only Backup for Customer Support In some support situations, Avid customer support might request a metadata-only backup of your Interplay Production database. A metadata-only backup creates copies of database files in the _Database folder, but not streamed properties files in the _PropertyStore folder. To create a metadata-only backup file: 1.
Creating a Metadata-Only Backup for Customer Support The backup file is created in specified backup location, for example: AvidWG\_Backup\AvidWG_2013-02-12_01-00 To distinguish between a metadata-only backup and the other types of backups, open the backup folder and check if a _PropertyStore folder exists. A metadata-only backup does not contain a _PropertyStore folder. 5. Use an archive program like 7-Zip to create a compressed file to send to customer support.
