FAQ Interplay Capture

Imprimer
Note des utilisateurs: / 0
MauvaisTrès bien 
Tous ce que vous avez toujours voulu savoir sans oser le demander (:o))
Retrouver ci dessous une FAQ exaustive des différentes Questiosn posées sur le produit.

What are some common Troubleshooting topics for Avid Interplay Capture?
AVID Interplay Capture Cheat Sheet
 
Avid Interplay Capture is a newsroom ingest tool that enables automated recordings. It is comprised of individual applications, which allow you to schedule and monitor recordings, and to capture video from a video feed or VTR. Capture stores its schedule and other metadata in the Interplay database, which allows for easy access to the captured material within the Interplay work environment.
 
The Capture system works with Avid Service Framework applications and services. These applications and services provide health monitoring, diagnostics, and discovery so users and system administrators can monitor the system and sub-system health, as well as the health of connected devices and channels.
 
Common Troubleshooting Topics
 
Network Time Protocol
NTP (Network Time Protocol) is crucial in Interplay Capture. Most issues reported to Avid Support, tend to be related to multiple time sources to lock to or time being off between several systems.
 
System Diagnostics Tools  
For more information on AVID System Diagnostic Tools … Click Here
 
Avid may request that you use the System Diagnostics Tools (previously known as Collect
Tool) to collect configuration and usage data from your Avid Interplay platform in order to
diagnose concerns that you may have with your system. Though similar in name, this is
different from the Avid Diagnostics application found in the Avid Service Framework
product line. Avid recommends using System Diagnostics Tools only under the direction of
Avid personnel.
 
When it comes to troubleshooting with Avid Interplay Capture, the most useful tool that can be provided to
Avid Support is an Avid Service Framework Diagnostic log.  In Interplay Capture, these logs are being generated constantly, but they do overwrite after a few days, so in the case of log collecting for Avid Support, gathering these logs as quickly as possible is the best practice.
 
Collecting Logs from Avid Interplay Capture:
 
Make sure you are in the correct Work Group. .
1) Open Avid Diagnostics (Start – Programs – Avid – Avid Framework – Avid Diagnostics).
2) Click the Wand icon (Package Remote).
3) Under the tree on the left, click problem Capture server with the green dot. Select the Avid Interplay Capture service. 
On the AMS, select the AMS Device Service. 
It is important to do this step before steps 5-6, or it will not collect the logs correctly.
4) Click the 3-dot (...) button, browse to the Desktop, enter a file name, and click Open.
5) If you are collecting log files that are over 24 hours old, change the start time so that it starts earlier.
The end time is the time when you opened the Package Remote dialog. 
If the problem happened between 1300 – 1330, put a little cushion in on both ends by adding a hour, covering between 1200 – 1430.
6) Click OK to start collecting/zipping process.
7) Email the files to Avid Support.
 
Along with the logs, it is important to note the name of the recording and the approximate time of the failure. Screenshots of the client are also helpful.
 
Master Clips and Device Clips
During a recording, two types of clips are checked into Interplay: device clips and master
clips. Device clips are created by the ingest devices, such as AirSpeed, AirSpeed MultiStream,
and the Low-resolution encoder. The Interplay Capture master clip is created in the
specified Interplay folder for that recording after Capture detects that a device clip was
created for the recording.
 
The Interplay Capture master clip automatically associates itself with each device clip for
the recording. For instance, a mirrored multi-resolution recording could have four associated
device clips in the Capture master clip. Capture writes all of the recording’s metadata (such
as, recording name, tape name, video, comments, aspect ratio) to the master clip.
 
Distinguishing between the device clip and master clip can be difficult because the clip names are the same. Two added criteria to the recent media search can help distinguish between the two.
• Narrow your search to folders where recordings are saved.
• Search for clips created by the Capture user (The Capture service logs in to Interplay as
a single user – all of the Capture master clips are created by this user. If the user account
is unique to only Capture, the search for recent media created by that user would return
only Capture master clips).
Capture has a global setting to direct where, under the projects folder, device clips are
created. This device clip folder is searched periodically by Capture. When a new or updated
device clip is detected, Capture creates or updates the master clip. For optimal performance,
it is important that no other users or devices are writing clips to this folder or its subfolders.
Only ingest devices, under the control of Capture, should be writing their clips to this device
clip folder.
 
Master Clip Creation
The creation of the master clip happens the first time Capture detects an ingest device clip
for a recording that was checked in to Interplay. Typically, ingest devices are setup to check
into Interplay approximately 30 seconds from the start of the recording. Capture searches
Interplay in the device clips folder, defined in Interplay for new clips about every 30
seconds. When the first clip is found, the master clip is created in the Interplay folder
specified for the recording.
• For mirrored and multi-resolution recordings, where there are multiple ingest device
clips that are added to the same master clip, the additional device clips are associated
with the same master clip.
• Channel failure and channel failover can result in multiple device clips that are added to
the same master clip.
• Retransferred clips are appended to the original master clip, if that clip still exists in
Interplay. If the original master clip does not exist, a new one is created and the
retransferred clip is associated with the new master clip.
• Multi-cam (multi-source) recordings result in separate master clips for each source
specified in Interplay Capture.
• Segmented recordings (for example: 24 hour recording with 1 hour segments) result in
separate master clips for each segment.
 
Failed Transfers
Permission conflicts can result in failed transfers. Capture does not give write permissions to
an AirSpeed, Avid Multi Stream, or Low-resolution encoder. The account used to log into
the shared storage service, should share the same permissions as that of the shared storage
user accounts for the AirSpeed, Avid Multi Stream, or Low-resolution encoder.
 
VTR Media
Batch recording has many variables that can affect the success of the recordings. The result
in some scenarios can be media loss. The following are some examples of things that can
cause media loss in Batch recordings.
The mark-in point of a VTR clip is not found on the tape—In this case, the VTR clip
and all following VTR clips are not created, and the recording ends.
The mark-out point of a VTR clip is not found on the tape—In this case, the current
VTR clip records to the end of the tape.
An ingest channel goes offline—the feed recording workflow requests a new channel
and starts it recording as soon as possible. It does not stop the VTR playout and back up
to start again.
The VTR clip exceeds the max clip duration—Some media may be lost as
segmentation is forced.
The tape timecode jumps backward during recording more than 5 seconds—the
VTR clip is stopped and the next VTR clip is started.
The tape timecode jumps forward further than 5 seconds—The VTR clip is stopped
and the next VTR clip started.
 
VTR Timecode
Where timecode is concerned, there are two aspects to consider for VTR Recording, one is
the timecode on the source VTR and the other is the timecode recorded to the destination
clip.
 
Source VTR
Batch and Quick recordings are the two different workflow types used for source VTR
Recordings. During either a Batch or Quick VTR recording, the timecode from the source
VTR is monitored. Capture requires continuous and forward advancing timecode for VTR recordings. This means while Capture is monitoring timecode on the source VTR, if a large jump in timecode is detected (either forward or backwards), the clip currently being recorded is aborted.
If the clip was part of a Batch recording Capture attempts to cue the next clip and continue
recording. If the clip was a Quick recording, the recording is aborted. In the event of an
aborted recording, an event log can be reviewed to see what caused the recording to abort.
For Batch VTR recordings, when Capture is required to Cue a VTR deck to a specific
timecode, as long as the deck continues advancing in the same direction, the cue does not
timeout. After the tape starts cueing in the opposite direction (due to end of tape or timecode
jump), a 30 second timeout period begins, and Capture stops the cue and aborts the
recording, if the 30 second timeout is reached. The event log for the recording indicates a
failure to locate a VTR clip.
For either Batch or Quick VTR recordings, before the tape begins playing, destination
channels must be cued. This cue action has a timeout of 60 seconds. At the 60 second mark, if
no destination channels are available for the recording, the recording is aborted.
 
Clips From Source VTR Recordings
For timecode recorded on the destination channel, regardless of what the source tape reads
as the timecode, the user may select either the LTC or VITC method of ingest for timecode
on the destination channels. This allows a site to develop a workflow where one of the
methods may have tape timecode and the other has time of day (TOD), or maybe both have
tape timecode, but it may differ depending on what was recorded on the tape. There are two
main workflows for destination timecode. The workflow used is determined
by the way in which the timecode is delivered; over LTC or both VITC and LTC.
 
Tape Timecode over VITC and Time of Day (TOD) Timecode over LTC
When tape timecode is delivered over VITC and time of day (TOD) timecode is delivered
over LTC, there is some flexibility as to whether or not to keep timecode that was originally
recorded with the tape's contents, or overwrite the timecode with a new track that is TOD
when the clips are recorded. In this workflow, the administrator could designate VITC as
 the primary (default) timecode source for VTR channels. When a user creates a VTR recording,
 VITC is selected by default as the timecode source. If this selection is not changed, tape timecode
 is recorded into the destination clip. If the user decided they do not want to preserve tape timecode,
they could change from VITC to LTC and record TOD timecode
 
Tape Timecode is on VITC and LTC and May Differ
When the tape timecode is delivered over both VITC and LTC the timecodes may or may not
match one another. This workflow assumes LTC is routed as another level on the router
and that the destination channels can use either VITC or LTC from the source VTR deck.
In this workflow, the administrator can specify the default timecode to be used by the
channel. Usually, the site has a default location for timecode on which it can relay. When
using this workflow, it is far less likely for the user to want to change the timecode source. If
the timecode is broken or wrong on a particular tape, this option allows the user to change
the timecode source to the other timecode source.
 
Avid Interplay Capture Monitor
The Avid Interplay Capture Monitor application allows a system administrator to monitor
channels and, in an automated routing configuration, the Avid Route Engine service. The
application is comprised of a menu bar and various panels, which can be arranged and
configured according to your working preferences.
 
Opening the Monitoring application
You can easily monitor the activities of your Avid Interplay Capture processes and
routing using the Avid Interplay Capture Monitor application.
 
To open Avid Capture Monitor:
1. Do one of the following:
-If one has been created, click the shortcut icon, for the Monitor application from the
desktop.
-Click the Start button and, select:
All Programs > Avid > Avid Interplay Capture > Avid Interplay
Capture Monitor
The Avid Interplay Capture Monitor login dialog box opens.
2. Enter the required information.
-Select your Interplay workgroup from the drop-down list.
-Select a Capture system from the drop-down list. The Capture Servers running in
your workgroup automatically appear in the list.
-Enter your User name.
-Enter your Password.
3. Click the Login button.
The Avid Interplay Capture Monitor application opens.
The Interplay Capture Monitor application contains a straight forward menu bar to help you
make the most of its features.
 
Status Bar
The Status bar shows connectivity and health of the Capture system and subsystems,
including the Capture service, record controller, and shared storage.
 
Customizing the Interplay Capture Monitor Application
The Interplay Capture Monitor application is customizable so it can be configured according
your working preferences. You start with the default configuration and from there decide the
layout of the panels in your workspace.
 
Router Crosspoints Panel
The Router Crosspoints panel is available in the Avid Interplay Capture Monitor application
and displays information and messages about crosspoints. The cells in the table display the
sources that are routed to the level of a destination.
If the router supports protection and it is enabled, a system administrator can protect (lock)
or unprotect (unlock) routes using the Router Crosspoints panel. For instance, a user may
have protected (locked) a route during a recording so that other users may not access it. If
something goes wrong while recording, the system administrator can unprotect (unlock) the
source video.
 
Channels Panel
The Channels panel is available in the Interplay Capture Monitor application and displays
information and messages about Channels. The cells in the table display the channels, their
health, transport status, recording information (start time, duration, sources), and the channel
pools to which the channels belong.
 
Viewing Details and Clearing Alerts
The Alerts panel is available in both the Interplay Capture Schedule and Monitor
applications and provides a list of recent alerts. The panel contains the following information
about the alerts:
• Alert type
• Time of alert
• Title (short summary of the alert)
• Text (optional-Alert information displayed in the lower portion of the panel.)
 
Each alert appears along with a timestamp for when the alert was issued.
If the summary shown in the alert’s title column extends beyond the size of the panel, resize
the panel or mouse over the alert to view the entire title in a tooltip. A user can also select
any alert and view additional details as well as clear alerts from the list.
To view details, do one of the following:
-Select an alert and view the details below the list area.
-Right-click on an alert to view details specific to that alert in a Diagnostics dialog box.
To clear alerts:
-Right-click and select Clear Alerts.
Alert Status Icon Description
Critical
Warning
Delete Protected Information
Succeeded
 
Channel Failure
There are three channel failure scenarios.
• Ingest channel fails to start on time – When this happens, the master clip shows a
MEDIA OFFLINE state in the editor, from the expected start of the recording up to the
time an ingest channel started recording. Interplay Access reports the master clip as
PARTIALLY ONLINE.
• Ingest channel fails in the middle of a recording and recovered before the end of the
recording – When this happens, the master clip shows a MEDIA OFFLINE state in the
editor, between the time the ingest channel failed, and when the channel recovered to
continue the recording. Interplay Access reports the master clip as PARTIALLY
ONLINE.
• Ingest channel fails before the recording ended and never recovered – When this
happens, the master clip shows a MEDIA OFFLINE state at the point of the failure
through the end of the recording. Interplay Access reports the master clip as
PARTIALLY ONLINE.
 
Channel Failover
Channel pools and automated routing make channel failover possible, if needed, during a
recording. If a channel fails part way through a recording, with the help of automated
routing, Capture can switch to another channel in the pool and continue the recording,
(generally in less than 2 seconds) with minimum loss of media. When this happens, the
ingested device clip is associated with the same master clip and the master clip shows a
MEDIA OFFLINE state in the editor between the time the ingest channel failed, and when
the new channel started and continued the recording. Interplay Access reports the master clip
as PARTIALLY ONLINE.
 
Starting the Route Monitor
Avid Route Monitor is an Avid Router Control application which provides status
information about source and destination route paths. If the router supports it, a system
administrator can also protect (lock) and unprotect (unlock) routes using the Avid Route Monitor.
 
To start Avid Route Monitor:
1. Click the Start button and select All Programs > Avid > Router Control> Avid
Route Monitor. The Select Workgroup dialog box appears.
2. Select the workgroup name.
When the Avid Route Engine Crosspoints Monitor window opens, along with the window’s
name, the title bar displays the router group name and the host in the workgroup to which
the Route Engine service belongs. The first time that the Route Monitor is started, the Router
Group must be selected in the Avid Route Engine Crosspoints Monitor window from the Edit menu.
Doing this enables the Route Monitor to automatically select this Router Group on subsequent startups.
The Route Monitor window displays information in two panels. The upper Information
panel shows information about the crosspoints and the lower Message panel shows
messages about the actions of the Avid Route Engine service. The information and
messages are continually refreshed while the session is open.
If the router supports protection and it is enabled, a system administrator can protect
(lock) and unprotect (unlock) routes using the Avid Route Monitor. For instance, a user
may have protected (locked) a route during a recording so that other users may not
access it. If something goes wrong while recording, the system administrator can
unprotect (unlock) the source video using the Avid Route Monitor so that the route is
available for others to use.
 
For more information on Avid Interplay Capture terminology, installation and troubleshooting…
Please see the Avid Interplay Capture Installation and Administration Guide (Click Here)

Partager cette page