avid interplay captureresources.avid.com/supportfiles/attach/broadcast/whats...avid ® interplay ®...

Avid® Interplay® CaptureNew for Capture v1.7 and Router Control v2.4

Revision History

Purpose and Audience of This Document

This document provides the Interplay Capture Administrators and users with a description of the Capture v1.7 features.

Contents

Capture to Multiple Interplay Environments . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2

Capturing to Multiple ISIS Systems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19

Changing Capture Settings from Drop Frame to Non-Drop Frame . . . . . . . . . . . . . . . . . . . . . . . . . . . 26

Using 422 Serial Router Control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29

Support for Harris Platinum Router. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40

Date Revised Changes Made

06/25/2013 Initial version.

Capture to Multiple Interplay Environments

2


Starting at Interplay Capture v1.7, you can use one Capture server to initiate recordings on two different Interplay environments at the same time. For example, this allows you to create a duplicate copy of a recording in a second Interplay environment in the same time sync/time zone facility.

How a Multi Interplay Capture Works

The following illustration shows how the multi Interplay capture process works. In this example there is a router in each Interplay environment and the AirSpeed 5000s are capturing multi res clips to ISIS workspaces.

The following list matches the numbers in the illustration:

1. Capture sends a message to Router Control to select a crosspoint for each router so it can make connections to the two AirSpeed 5000s.

2. Capture tells the AirSpeed 5000s in each Interplay environment that they have a recording that lasts a particular duration and instructs them both to start recording.

Capture A

Interplay A

ISIS 1A

AS5K A

Interplay B

ISIS 1B

AS5K B

Router A Router B

R Control A

ISIS 2A ISIS 2B

qq

ww

ee

rr

ww

ee

AS5K Metadata/Media Checkin – HiRes/LoRes different Workspaces - ISISControlCapture Metadata Checking


3

n The AirSpeed 5000 configuration determines where the recording occurs. A given AirSpeed 5000 can only be assigned to one Interplay environment at a time.

3. The AirSpeed 5000s start recording at the same time. They begin adding device clips to ISIS and check them into the Interplay database. Interplay keeps track of the name, location, and size of the growing device clips. When the AirSpeed 5000 completes the recording, Interplay marks the device clips as done.

4. Capture monitors the Interplay database. When it sees that new device clips have been created, it checks in a corresponding capture clip (master clip) to the Interplay database. As the device clips grow, Capture updates the capture clip. When Capture sees (in Interplay) that the device clips are finished recording, it updates the capture clips as completed.

Router Details for Capture to Multiple Interplay Environments

The following lists important information for router connections:

• For this release, only one Router Control is supported and it must be in the primary Interplay Capture environment.

• Avid supports one Router Control with one router or one Router Control with two routers. If using a dual router configuration, both routers must be patched source identical. For example, a specific feed would go to src1 on BOTH routers.

n Setting up and maintaining multiple routers in a multiple Interplay environment requires a complete understanding of the wiring and system configuration.

Configuring a Capture Server to Recognize a Second Interplay

Each Capture server must have a primary Interplay environment that is defined when you set up and configure the Capture server. Use the following procedure to add a secondary environment.

To add a second Interplay environment to a Capture server configuration:

1. Start the Interplay Administrator tool, open the Capture Settings view, and click the Interplay tab.

In this example, the name of the server running the Interplay Engine on the primary Interplay environment is bur-shi-acr2 as shown in the following illustration.


4

The AirSpeed area shows the AirSpeed devices that are associated with this Interplay environment. AirSpeed devices that are associated with the Secondary Interplay are grayed out. See “Setting Up Avid Service Framework for Multiple Interplay Capture” on page 6.

2. If necessary, select the AirSpeed devices that you will be using in the Primary Interplay environment.

3. Click the Add button at the bottom of the Secondary Interplays area. Then add the host name of the second Interplay Engine and the database name. Enter AvidWG for the database name.

The following illustration shows the completed fields for this example. Note that there is one AirSpeed device configured for this Interplay environment. The devices on the primary Interplay environment are grayed out.


5

4. Click the Apply button in the bottom right corner of the Capture Settings window.

The system restarts the Capture service and the Clip Manager service. After the services restart, the Capture system is aware of both Interplay environments.

Matching Settings in the Two Interplay Environments

The following components must be installed and configured for a Multi Interplay Capture:

• You must have the same Capture Admin user on both Interplay environments. The password and user name must match exactly (case sensitive password).

• Interplay SES Notifications must be installed on the Interplay Engine in both environments. In addition, Interplay notifications must be turned on for the Capture server. See the Interplay Capture Installation and Administration Guide for details on installing and configuring notifications.

The following illustration shows the Interplay notifications check box in the Service Configuration tool. Note that the name of the Capture workgroup in this example is shire-capture0. The primary Interplay server is bur-shi-acr2 which has its own workgroup named shire-capture1.


6

• The Device clips folder used by Capture must be the same on both Interplay environments. By default the folder is Projects/Device. In this example the default folder is /projects/ian.

Setting Up Avid Service Framework for Multiple Interplay Capture

Avid recommends that you set up the Capture server in a separate workgroup as shown in the following illustration. The term LUS refers to the Avid Service Framework Lookup Service and ASF refers to Avid Service Framework.

Separate Capture workgroup

Primary Interplay environment

Secondary Interplay environment

Contains LUS for secondary Interplay environment

Capture server and LUS

Contains LUS for primary Interplay environment


7

The following table lists the Avid Service Framework components that you must modify for an environment that contains a Capture server in its own separate workgroup.

The following illustration shows the Device Settings for an AirSpeed Multi Stream device associated with the secondary Interplay environment named shire-capture2.

ASF Settings for Separate Capture Workgroup Configurations

Component Workgroup Properties Service Configuration

Capture server Add workgroup name and LUS of the secondary environment.

Note that the primary workgroup name and LUS of the primary Interplay environment are added when you first set up the Capture workgroup.

No change

LUS on primary and secondary Interplay environments

No change. No need to identify the LUS of the other Interplay environment.

No change

AirSpeed Multi Streams on primary

Add workgroup name and LUS of the secondary environment.

Add the Capture workgroup name to the Device Service as a second workgroup

AirSpeed Multi Streams on secondary

Add workgroup name and LUS of the primary environment.

Add the Capture workgroup to the Device Service as a second workgroup


8

The following table lists the names of the workgroups and AirSpeed devices used in this example.

After you configure the Service Framework, the AirSpeed Multi Stream systems for the primary and secondary environments appear in the Service Configuration of the Capture workgroup. The Service Configuration tools on the primary and secondary environments only see the Air Speed Multi Streams for their own environment.

Preparing for a Multiple Interplay Recording

In this example there is one Evertz Quartz router and two AirSpeed Multi Stream recording devices. The procedures in this section are basic Interplay Capture operations. See the Interplay Capture User Guide for details.

Workgroup Workgroup Name Associated AirSpeed Device

Capture shire-capture0

Primary Interplay shire-capture1 bur-shi-ams14

Secondary Interplay shire-capture2 bur-shi-ams2


9

Define the Destinations

In this example, one Evertz Quartz router is used to route recordings to both Interplay environments. You could also have a separate router in each environment. The following illustration shows the two AirSpeed Multi Stream devices set up as recording destinations for the Evertz router.

In this example, destination aliases containing “ams14” are in the primary Interplay environment and destination aliases containing “ams2” are in the secondary Interplay environment. Note that there are 4 channels associated with each device.


10

Define the Channels

To define the channels, start the Interplay Administrator tool and open the Capture Settings view. The following illustration shows the channels that are configured for the AirSpeed Multi Stream devices in this example.

In the above illustration, the Name field identifies the individual AirSpeed Multi Stream device and channel. The Destination field is the alias of the routing destination. You define a channel by associating a device with a routing destination.

n The recording devices from the secondary Interplay environment do not show up as available channels until you configure the Avid Service Framework on the individual devices.

Create a Channel Team

This example uses a Channel team consisting of two AirSpeed Multi Stream systems. One device is in the primary Interplay environment and the other is in the secondary Interplay environment. The example uses channel 6 of each device.The following illustration shows the Channels being added to the team.


11

Create a Channel Pool

Next, create a channel pool that uses the channel team. The following illustration shows a pool named multiTEAM6. You select the Channel pool when you begin the recording.


12

Matching the number of audio tracks in Capture and the recording device

The following illustration shows the bottom portion of the Channel Pool tab. In this example there are 4 tracks of audio: two from each AirSpeed device.

It is important to configure the Channel Pool to use the same number of audio tracks as defined in the AirSpeed devices. On an AirSpeed Multi Stream you can check this value in the Record template in the Service Configuration tool. The following illustrations show the Record template for the AirSpeed Multi Stream bur-shi-ams2 on the secondary Interplay environment. To check the value, select the AirSpeed device on the left and select the Avid AirSpeed Multi Stream Integration Service.


13

This AirSpeed device uses two channels of PCM-24 audio. In this example, the device on the primary Interplay environment also uses two channels.

Performing a Multi-Interplay Recording

To perform a recording to two separate Interplay environments:

1. Start the Interplay Admin tool and open the Capture Settings view.

2. Start the recording. For example, press CTRL-N or choose File > New.

The Choose Template dialog box opens.

3. Either select a template and click Open or click Skip to open a recording without a template.

n The template browser shows the primary and secondary Interplay folders but you can only select a template from the primary Interplay folder.

4. Select a channel pool for the recording and click the Add Sources button.


14

The Choose Sources dialog box opens as shown in the following illustration.

5. Select a source and click OK. This source will feed both channels.

6. Name the recording and extend the recording in the timeline to the desired length.

7. Click the Save button in the top right portion of the Capture window.

When the recording begins, each AirSpeed Multi Stream starts recording material to its corresponding Interplay environment.


15

Viewing the Captured Material in Interplay Access

This section describes how to view the captured material.

To view the captured material in Access:

1. Open Interplay Access and search for the new material. The following illustration shows the parameters for a search for masterclips created in the past hour. In this example, the search is performed on the primary database.

2. Click the File Locations tab in the Object Inspector.

The following illustration shows the search results in Access. Note that Access treats both device clips and Capture clips as masterclips.


16

The following table shows a comparison between the items in the two Interplay environments. To view the Get/Set Properties window, select either the Capture clip or the device clip and choose Advanced > Get/Set Properties. Then click the All Properties tab.

File Mob ID ISIS Path and MXF file nameCapture clip Device clip

Video ID

ElementValues on both Interplay environments Comments Viewable in Access

Capture clip name identical Checked into Interplay in both environments as the master clip.

Search pane

Capture Recording ID identical need info on this. Available only for Capture clip.

Get/Set Properties: CaptureRecordingID

Source MOB ID identical Links all of the master clip content together. Available only for Capture clip.

Get/Set Properties: QMSSourceMobID

Device clip name identical Created by individual AirSpeed Multi Stream

Search pane


17

Note that the duration and head frames of the Captured clips may be different in each Interplay environment depending on when the associated recording device starts recording. If both recording devices are receiving the same master clock signals, the timecode on corresponding frames should match even though the clips have different durations.

Alternate Channel Pool Configuration

The previous example uses a team consisting of one AirSpeed Multi Stream from each Interplay environment. This section describes an alternate method of recording to two Interplay environments.

Capture Master Clip MOB ID

identical Associates the device clip with the Capture clip. Available only for Device clip.

Get/Set Properties: CaptureMasterClipMobID

Video ID different Created by the individual AirSpeed Multi Stream. Available only for Device clip.

Search pane

File Mob IDs different Identify the individual video and audio layers

File Locations tab

mxf file names different Different files on different systems.

File Locations tab

path name in ISIS different Different files on different systems.

File Locations tab

ElementValues on both Interplay environments Comments Viewable in Access


18

Recording to Devices in Two Separate Pools

The following illustration shows two selected pools. Each pool contains one AirSpeed Multi Stream. The pool ams14_1 uses one channel from an AirSpeed device on the primary Interplay environment. The pool ams2_1 uses one channel from an AirSpeed device on the secondary Interplay environment. Each pool could also contain multiple AirSpeed Multi Stream devices as long as all of the ones in a given pool were part of the same Interplay environment.

The following recording makes use of both of these pools. This example records one channel to the primary Interplay environment and one to the secondary environment. This technique allows you to create teams “on the fly”.

Capturing to Multiple ISIS Systems

19


Capture v1.7 supports recording to multiple ISIS systems from a single Interplay environment. The following are typical uses:

• Capturing high resolution to one ISIS such as an ISIS 5000 or ISIS 7000, and capturing a proxy resolution to a second ISIS such as an ISIS 2000.

• Creating a backup version of a recording on a second ISIS as part of a failover workflow.

n This feature is only supported on AirSpeed 5000 (AS5000) capture devices.

The example in this section captures high resolution to one ISIS and proxy resolution to a second ISIS.

To configure an AS5000 to capture to multiple ISIS systems:

1. Open the management console of the AS5000 system and select Destination Template. Then select a destination template from the list or create a new template.

2. Identify the target workspaces on each ISIS system for this destination template. The following illustration shows the target workspaces for the destination template named Dual Nearline. The two system directors are named A51-WG2-SD1 and BSI-Nearline.


20

3. Click Record on the AS5000 management console and identify the destination template and record templates for the channels that will be used. The following illustration uses the AVCi_1080i60 record template and the Proxy to Nearline destination template for channels 1 and 2.

n Two channels are used in this example because we are going to use the Mirror feature in the Capture interface. When you select Mirror you must specify two channels. One for the primary recording and one for the mirror (backup) recording.


21

4. Select Record Template and select a template from the list or create a new template. This template is named AVCi_1080i60.

5. Define the Record template. The following illustration shows the values for the AVCi_1080i60 Record template.


22

c This AS5000 template defines a recording that contains 8 tracks of audio: 4 tracks on channel one and 4 tracks on channel two. It is important to configure the Capture channel pool to use the same number of audio tracks.

For additional information on configuring an AS5000, see the AS5000 Setup and User’s Guide.

To set up and use a channel pool for a multiple ISIS recording:

1. Open the Capture interface in the Interplay Admin tool and set up the channel pool. The following two illustrations show the channel pool definition for this recording.


23

The following table shows the values used in this example.

Column Description

Name The name of the channel pool. In this example, the name is Pool1_AMS4_2ch.

Primary The target ISIS System Director and workspace for the primary recording.

Mirror The target ISIS System Director and workspace for the primary mirror recording. This example uses a second workspace on the same ISIS system. Note that you must have two channels in the AS5000 Record template and at least two channels in the Channel pool when you use the Mirror feature.

Enable proxy Enables proxy recording. This example creates a high res on one ISIS and a proxy on the second ISIS.

Proxy Primary The target ISIS System Director and workspace for the proxy recording.

Proxy Mirror The target ISIS System Director and workspace for the proxy mirror recording. This example uses a second workspace on the same ISIS system. Note that you must have two channels in the AS5000 Record template and two channels in the Channel pool when you use the Mirror feature.


24

2. Make sure you match the number of audio tracks in the Channel pool with the number of audio tracks in the AS5000 Record template (see earlier illustration of the Record template). The following illustration shows the bottom of the Channel Pools tab where you must enter this information.

3. Start the recording using the defined channel pool. The following illustration shows the primary and proxy workspaces selected for the Pool1_AMS4_2ch channel pool. Select “Workspace” and click to open a pop-up dialog that reflects the chosen ISIS workspaces. You can reassign the workspaces in the dialog.


25

4. (Option) Open Interplay Access, select the recorded clip, and view details about the clip on the File Locations tab in the Object Inspector.

Changing Capture Settings from Drop Frame to Non-Drop Frame

26


Capture defaults to using drop frame timecode for NTSC 29.97 and 59.94 frames per second (fps). If you have a non-drop frame environment, you can make a change to the Registry settings on the Capture server. For example, a non-drop frame NTSC environment uses 30 fps and 60 fps instead of 29.97 fps or 59.94 fps.

If you have a non-drop frame environment and do not make these changes, the AirSpeed Multi Streams will create non-drop frame clips but Interplay and Capture will treat them as drop frame. This results in clips being off by a few frames and can cause a problem referred to as “blue clips.”

n PAL environments do not need to make any changes. They are defined as non-drop frame by default.

n Changes to the Windows Registry should only be made by qualified personnel. Check with your Avid representative if you have any questions on this procedure.

There are two registry settings to change. The format of the settings is as follows:

timecode|29.97|<Drop Frame>timecode|59.97|<Drop Frame>

where: “drop frame = false” means non-drop frame and “drop frame = true” means drop-frame.

To use the Registry Settings to change from Drop Frame to Non-Drop Frame:

1. Run Capture at least once after an installation to populate the registry settings.

2. Start regedit from the Start menu.

3. Use Edit > Find or CTRL-F to open the Search window.

4. Search for the text string “timecode 29.97”.

Regedit displays the folder that contains the settings as shown in the following illustration.


27

The following illustration shows the values to change. The default values for each are true.


28

5. Right-click timecode 29.97 and select Modify.

The system shows the current value as shown in the following illustration.

6. Change true to false as shown in the following illustration.

c Do not remove the delimiters “|” and do not add or remove spaces in the string.

Using 422 Serial Router Control

29

7. Click OK.

The setting changes from true to false as shown in the following illustration.

The 29.97 timecode has been changed to be non-drop frame.

8. Perform the same operation on the value for “timecode 59.94”.

9. Close Regedit and restart the Capture Service.


In previous releases, each VTR was associated with a specific 422 router connection. Now you have the option of associating a 422 connection with any available VTR source. The VTR Source tab allows you to define VTR source as follows:

• Define a VTR source that is directly connected to a 422 COM source. This is the way you defined VTR source for previous releases.

• Define a VTR source and specify a separate 422 router source. The system will use the 422 COM source to control the video.

n The 422 Serial Router Control feature was added in Capture v1.6 but the user interface has been improved for Capture v1.7.

The following illustration shows the VTR Source tab in the Interplay Administrator tool, Capture Settings view. The Channel Group menu allows you to switch between direct routing and 422 routing.


30

To define a VTR with an associated 422 connection:

1. Select Direct VTR Sources from the Channel group menu.

2. Click the Search button in the Direct VTR Channels area.


31

The system displays the Available Channels dialog box.


32

3. Select an available channel and click OK.

The system displays the parameters for the channel as shown in the following illustration.

4. Select a router source from the video router source menu.


33

The system displays the configured VTR channel.

To define a video source with a separate 422 COM port:

1. Select Routed VTR Sources from the Channel group menu.

2. Click the Add button in the Routed VTR Channels area.

The system displays the Available VTR sources dialog box.


34

3. Select a router source and click OK.

4. Select a video router source from the video router source menu.


35

The system displays the completed Routed VTR channel as shown in the following illustration.


36

5. Click the Search button in the 422 Channels area near the bottom of the window.

The system displays the available channels.


37

6. Select a router source and click OK.

The system adds the router source and adds the channel number to the name.


38

7. Select a destination from the 422 router crosspoint menu.


39

The system adds the adds the router crosspoint and fills in the name as shown in the following illustration.

Support for Harris Platinum Router

40

Support for Harris Platinum Router

Router Control v2.4 that works with Capture v1.7 supports the Harris Platinum Router. The following table lists the supported protocols,

Controller Type Model Communication Protocol

Tested Controller Software

Harris Broadcast Platinum Ethernet LRC v9.99.b1

Placeholder

41

Placeholder

avid interplay captureresources.avid.com/supportfiles/attach/broadcast/whats...avid ® interplay ®...

Documents