Avid CaptureManager Revision History Date Revised Changes Made 24 September 2010 Added Known Incompatibilities section: Windows Vista 64 bit, Windows 7 (any version), Windows Server 2008 (any version) are not supported for use with CaptureManager. 14 July 2010 Added a known limitation about recording at the midnight transition 13 May 2010 Added Microsoft Windows Vista, 32 bit support for the CaptureManager workstation v4.2.1 9 November 2009 Added changes between 4.2.0 and 4.2.1 19 August 2009 Added changes between 4.1.1 and 4.2.0 19 June 2009 Added changes between 4.1.0 and 4.1.1 8 April 2009 Added Regional & Language requirements for proper Unicode display in Known Limitations 12 Feb. 2008 Added changes between CaptureManager v4.0.7 & v4.1.0, namely AirSpeed Multi Stream support information 17 Sept. 2008 Added new registry setting information for grid color 2 June 2008 Added changes between CaptureManager v4.0.6 & v4.0.7 1 May 2008 Added changes between CaptureManager v4.0.5 & v4.0.6 24 July 2007 Added changes between CaptureManager v4.0.4 & v4.0.5 Important Information Avid recommends that you read all the information in this ReadMe file thoroughly before installing or using any new software release. Note: Search the Avid Knowledge Base (http://www.avid.com/onlinesupport) for the most up-to-date ReadMe file, which contains the latest information that might have become available after the documentation was published. This document describes compatibility issues with previous releases, hardware and software requirements, software installation instructions, and summary information on system and memory requirements, when applicable. This document also lists any hardware and/or software limitations.
Contents Compatibility Notes and Issues... 4 CaptureManager 4.2.1 Software Requirements... 4 Known Incompatibilities... 4 CaptureManager with Avid Unity ISIS: Requirements and Guidelines... 5 CaptureManager with SQLServer 2005 or 2008... 5 CaptureManager Controlling an Avid AirSpeed... 5 CaptureManager Controlling an Avid AirSPACE... 5 Java Virtual Machine... 6 Hardware and Software Changes... 6 Changes between CaptureManager 4.2 and 4.2.1... 6 Avid Multi Stream Integration... 6 Avid Router Control 2.0 support... 7 Changes between CaptureManager 4.1.1 and 4.2... 7 Avid Multi Stream Integration... 7 Changes between CaptureManager 4.1.0 and 4.1.1... 8 New option for Multi Stream Integration... 8 Changes between CaptureManager 4.0.7 and 4.1.0... 9 New support for Multi Stream... 9 Changes between CaptureManager 4.0.6 and 4.0.7... 10 New Registry Setting... 10 New Options in User Profile Settings... 10 Protect Checkbox removed from Instant Record Dialog Box... 10 Changes between CaptureManager 4.0.5 and 4.0.6... 10 New Options in User Profile Settings... 10 New Options in the Instant Record Dialog Box (for v.4.0.6 only)... 12 Recording Durations... 12 Changes between CaptureManager 4.0.4 and 4.0.5... 13 Recording Durations... 13 Media Browse Unity Video Service Installation... 13 CaptureManager Server Upgrade... 13 Changes between CaptureManager 4.0.3 and 4.0.4... 13 Changes between CaptureManager 4.0.2 and 4.0.3... 14 Changes between CaptureManager 4.0.1 and 4.0.2... 14 Changes between CaptureManager 4.0.0 and 4.0.1... 14 2
New Features in Release 4.0.4... 14 CaptureManager Can Steer AirSpeed Capture to a Particular Workspace... 14 Unity Video Service has Configurable Interplay Access Polling Interval... 15 Known Limitations... 16 Recording at the Midnight Transition... 16 CaptureManager Client Limitations... 16 Regional and Language Options... 16 Context Sensitive Menus... 16 ActiveX Add-in Tab... 18 Comments Tab... 18 The VTR Record Dialog... 18 Durations of Device Capture Recordings... 18 Automatic Software Updates of the CaptureManager Client... 18 CaptureManager Client Longevity... 18 Channel Configuration... 19 Media Browse Monitor limitations... 19 System Tab, License Button... 19 Technical Support Information... 20 Accessing Online Support... 20 Copyright and Disclaimer... 21 3
Compatibility Notes and Issues CaptureManager 4.2.1 Software Requirements Software Operating System (CaptureManager System / Data Server) Operating System (CaptureManager Serial Control Server) Operating System (CaptureManager Workstation ) SQL Database Management System Thomson Grass Valley Profile XP PVS 1100 5.4.8.1248 Microsoft Java Virtual Machine (VM) 5.0.3810.0 Microsoft DirectX Microsoft Media Player Version Microsoft Windows Server 2003 SP2 Microsoft Windows XP Professional SP3 Microsoft Windows Vista 32 bit, and Microsoft Windows XP Professional SP3 Microsoft SQL Server 2005 or Microsoft SQL Server 2008 9.0c (already included if Windows Service Packs and Windows Updates are current) 9.0 (already included if Windows Service Packs and Windows Updates are current) Microsoft XML Parser 3.0 or later (already included with IE 6.0) Windows Update Critical Patches Through 11/9/09 Note: Contact Avid Customer Support for details on using the Windows XP firewall with Media Browse. Known Incompatibilities Windows Vista 64 bit, Windows 7 (any version), Windows Server 2008 (any version), are not supported for use with CaptureManager. 4
Installation Notes and Issues CaptureManager with Avid Unity ISIS: Requirements and Guidelines The following is a requirement for Capture Manager in an Avid Unity ISIS environment. The computer running the following Media Browse service must be in the ISIS VLAN: Media Browse Unity Video service The following are guidelines for Capture Manager in an ISIS environment: Given the above requirements, all CaptureManager Servers may be placed in the ISIS VLAN. The Media Browse System service inside the ISIS VLAN is unable to "discover" CaptureManager Workstations or services running outside the ISIS VLAN; therefore, a restart of the Media Browse System service or a reboot of the Media Browse System service computer will require restarts of those services and workstations running the client software outside the ISIS VLAN after the Media Browse System service is running. CaptureManager with SQLServer 2005 or 2008 CaptureManager requires SQL Server 2005 or 2008. If upgrading to CaptureManager 4.x from a previous version of Media Browse that is running with SQL Server 2000, the following steps must be taken prior to upgrading the CaptureManager server software: 1. Stop all Media Browse Services. 2. Use "Enterprise Manager" to detach 'MediaBrowse', 'resolver', and 'MBUserProfiles' databases. 3. Copy (or cut) the associated six files from the SQL data folder to another folder or network location: MediaBrowse.mdf, MediaBrowse.ldf, resolver.mdf, resolver.ldf, MBUserProfiles.mdf, and MBUserProfiles.ldf. 4. Uninstall SQL Server 2000. 5. Reboot. 6. Install SQL Server 2005 or 2008. 7. Copy (or cut) the files from step 3 from the folder or network location into the data folder for SQL Server 2005 or 2008. The master.mdf file will already be in this folder. 8. Using Microsoft SQL Server Management Studio, attach the three databases. 9. Restart the Media Browse services. The above must consist of an uninstallation of SQL Server 2000 and an installation SQL Server 2005 or 2008. CaptureManager Controlling an Avid AirSpeed The following must be installed prior to installing CaptureManager Server software on the CaptureManager server if an Avid AirSpeed is to be controlled by CaptureManager: Avid I/O Peripherals (the following components): o Pilot o Flight Plan o Editor Ingest and Playback Support CaptureManager Controlling an Avid AirSPACE The following must be installed prior to installing CaptureManager Server software on the CaptureManager server if an Avid AirSPACE is to be controlled by CaptureManager: Avid SPACEnet Applications o LaunchPad o MissionControl 5
Avid Interplay Transfer Client Java Virtual Machine The proper version of Microsoft Java Virtual Machine is installed on the CaptureManager workstation before installing the client software; otherwise, warnings will appear during the install process. To avoid that, ensure you have the correct version (provided earlier in this ReadMe in the Compatibility Notes and Issues section. To find out what version of Java VM is on a computer: 1. Open a Command Prompt. 2. Type jview and press Enter. You should see something similar to the following: Microsoft Windows [Version 5.2.3790] (C) Copyright 1985-2003 Microsoft Corp. [MADCM-1] C:\WINDOWS\system32>jview Microsoft (R) Command-line Loader for Java Version 5.00.3810 Copyright (C) Microsoft Corp 1996-2000. All rights reserved. If you do not have the correct version of Java VM, you can install it from the CaptureManager installation CD. To ensure the correct Java VM is installed prior to CaptureManager installation: 1. On the CaptureManager installation CD, locate and run MS Java VM version 5.0.3805. (This is the full version. If you already have this version installed, go to step 3.) 2. When prompted for a reboot, do the reboot. 3. Locate and run MS Java VM upgrade version 5.0.3810. 4. Reboot again when prompted. You can now run the installation program for the CaptureManager client software. Hardware and Software Changes The following section contains information on any changes related to hardware and/or software within CaptureManager. Changes between CaptureManager 4.2 and 4.2.1 Avid Multi Stream Integration In this version of CaptureManager, fail-over support was added for when an AMS loses its network connectivity to the ISIS VLAN over which CaptureManager was communicates with AMS. The capture service failover process will take approximately 45 seconds from the time of loss of network connectivity to complete. Any in-progress recordings at the time of an AMS network failure will finish recording successfully but they will not be reported as being successful within CaptureManager. Any scheduled recordings that start their cuing process after the networking failure but before the capture service failover has completed, will fail. 6
This failover support requires AirSpeed Multi Stream version 1.3.0 or later, and AirSpeed Multi Stream Device Service 2.5.0 or later. The VLAN that CaptureManager is running in must have network routes to both of the AMS ISIS VLANs. Avid Router Control 2.0 support Avid Router Control 2.0 is supported in this version of CaptureManager. It is recommended that Router Control 2.0 be used for all new installs of Router Control into CaptureManager sites for which it has released route controller and protocol plug-ins. See the most current Router Control 2.0 readme for the most recent list of supported controllers and protocols. Follow these steps for the installation of Router Control 2.0 with a CaptureManager system: 1. Install and configure Router Control 2.0 in an Avid Service Framework workgroup per the Router Control 2.0 documentation. 2. Configure the CaptureManager Bridge setting in Router Control 2.0 to specify the CaptureManager server name where the CaptureManager System Service is running. 3. Confirm that Avid Router Control 2.0 appears in the Services tab of the CaptureManager Monitor application. 4. Once Router Control 2.0 service is confirmed to be present in CaptureManager you can then configure the route destinations in CaptureManager. There are no differences in the way that Router Control 2.0 route destinations are configured in CaptureManager channel than with Router Control 1.0, the channel route destinations are done in the exact same way. CaptureManager can only support one Router Control service at a time. Do not attempt to run both Router Control 1.0 and 2.0 on the same CaptureManager system. Switching between Router Control 1.0 and 2.0 on a CaptureManager system is possible, but it will require that all the route destinations in the channel configurations, and any scheduled recordings on the system be redone. This can be a time consuming process depending on the number of channels, and how many scheduled records that there are. Unless there are compelling reasons to do so otherwise, it is generally better to stay with a properly working Router Control 1.0 configuration on an existing CaptureManger system than to systematically upgrade to Router Control 2.0. Before attempting to run Router Control 2.0 and its supporting Avid Service Framework components on an existing CaptureManager server consult with Avid customer support to verify that the existing hardware has enough hardware resources to support Router Control 2.0. Changes between CaptureManager 4.1.1 and 4.2 Avid Multi Stream Integration CaptureManager users can now designate shared storage workspace with AMS like CaptureManager users with AirSpeed video servers. In order to utilize the new behavior, the user enters a destination template name in the Video ID field, followed by a slash. A video ID can follow the slash, but this is normally not required for AMS, because one will be generated internally. In the AirSpeed case, as usual, the ID will be generated from the "Name" field if one is not specified. For Airspeed Multi Stream, if the designated template name is missing or does not exist, then the default destination template on the recording channel is used. 7
Changes between CaptureManager 4.1.0 and 4.1.1 New option for Multi Stream Integration A new option is available in the Device Information dialog box in Capture Manager related to Avid AirSpeed Multi Stream. The Timecode Source drop-down list let you select either TOD for Time of Day (such as the AMS s PC clock) or VITC, which is timecode that may be present with the input video signal. 8
Changes between CaptureManager 4.0.7 and 4.1.0 New support for Multi Stream New integration between Capture Manager and Avid AirSpeed Multi Stream required a change to the Device Information dialog box in Capture Manager. A new button called Avid AirSpeed MS provides access to configuration device settings as shown in the following graphic: Field Hostname Channel Interplay Adapter Hostname Route Description The host name must be a DNS resolvable.name of the Multi Stream device. Set to the record channel number to be used on the Multi Stream for this CaptureManager channel.. This is the host name of the server running the Interplay Adapter. When a Route service is installed and running, then a route destination that is cabled to this device channel must be indicated. This is set to <none> if the source feeding this Multi Stream is not controlled by a Route service. 9
Changes between CaptureManager 4.0.6 and 4.0.7 New Registry Setting In previous versions of Capture Manager, an entry for a recording in the scheduling grid would turn black after the recording finished and the low-res part of the recording had failed. In version 4.0.7 (or later) a new registry setting is now available to change the grid behavior to display gray instead of black when there is a partial recording failure where the lo-res recording has failed but the hi-res recorded successfully. This new behavior by default is not enabled. It may be enabled by changing this registry setting on the server running the Capture service to the setting shown here: HKEY_LOCAL_MACHINE\SOFTWARE\iNEWS\Media Browse\Media Browse Capture Service Low-Res record failures are warnings, not errors = 1 New Options in User Profile Settings One new default administration settings are available in the Media Browse User Profile Settings dialog box. Delay Route Source Until Cue- If set to True then the requested route will not occur until the Cue button is pressed. If set to False then the requested route will occur as soon as it is selected in the Source Route drop down. Protect Checkbox removed from Instant Record Dialog Box The new Protect checkbox feature added in version 4.0.6, and documented in the next section of this ReadMe, has been removed from the UI in version 4.0.7. Changes between CaptureManager 4.0.5 and 4.0.6 New Options in User Profile Settings Two new default administration settings are available in the Media Browse User Profile Settings dialog box. Can Change Route Source During Recordings If set to false, then the new Protect checkbox in the Instant Record dialog box will appear selected and users will be unable to deselect the option. If set to true, then the Protect checkbox is enabled to allow users to turn off route source protection. Reset default duration on Cue If set to true, the new Reset Default Duration on Cue checkbox in the Instant Record dialog box is selected by default. If set to false, the checkbox is not selected by default. 10
11
New Options in the Instant Record Dialog Box (for v.4.0.6 only) Two new checkboxes are available in the Instant Record dialog box: Protected and Reset Default Duration on Cue. The Reset Default Duration on Cue checkbox, when selected, forces the duration to reset each time a user clicks the Cue button in the Instant Record dialog box. If not selected, then the duration will equal the previous recording. The Protected checkbox that was introduced in 4.06 has been removed. The purpose and function that it was implemented for is now more effectively covered by the new Delay Route Source Until Cue setting under User Profiles. When the Protected checkbox is selected, the Route Source selection cannot be changed during a recording. This checkbox is selected by default, thus protecting recordings from inadvertent changes. However, a user with proper permissions can deselect the checkbox if he or she wants to change the route. Recording Durations In previous versions, Avid Low-Res encoders would continue to record after the scheduled end under some circumstances during Device Captures if there were segments scheduled within timecode breaks of the source tape. This issue is fixed. 12
Changes between CaptureManager 4.0.4 and 4.0.5 Recording Durations The computations are improved for determining the exact start and end times for a recording when an Avid Low-Res device is present in a CaptureManager channel. The calculated durations of the recordings are also more accurate with these improvements. Media Browse Unity Video Service Installation The text of the Media Browse Unity Video Service installation dialog box requesting the interface to the Avid Interplay Engine now requests the host name of the computer running the 'Avid Interplay Adapter', which more accurately reflects the actual configuration required. CaptureManager Server Upgrade When installing CaptureManager support services, the Media Browse Server installer (required for the installation of CaptureManager support services) starts all of the installed Media Browse services so that no further user intervention is required to bring the Media Browse/CaptureManager Server to a functional state after a new or upgrade installation. Changes between CaptureManager 4.0.3 and 4.0.4 The user profile setting within the Media Browse Administration section, "Can Change Route Source During the Recordings", should now restrict a users capability to change a source route during a recording when made false. The Media Browse Unity Video Service is now able to continue to remain functional even after encountering a thread lock condition that previously caused the Media Browse Unity Video Service from checking in metadata to Interplay Access. The dependency requiring a Transfer Manager client to be installed on a CaptureManager server has been eliminated. Media on an AirSpeed that needs to have the transfer reinitiated through CaptureManager will now be consistently transferred successfully, and the CaptureManager related assets will be updated properly. Single or multiple Media Browse Unity Video Services may now be deployed to check in assets to the same Interplay Engine via distributed Interplay Adapters. For every Interplay Adapter installed, a Media Browse Unity Video service may also be deployed that points at that Interplay Adapter. When installing multiple Media Browse Unity Video services, the following configurations must be completed: 1. If an Interplay Adapter is installed and running on a computer other than the Interplay Engine computer, the mmserver.ini (location e.g. C:\Program Files\Avid\Avid Interplay Adapter\jakarta-tomcat\omm\RAM) must be edited to point at the Interplay Engine by adjusting this value: env.abserver=. 2. All AirSpeeds that are to use that Interplay Adapter to checkin assets must have its Asset Manager (on the Send tab of the Setup section) configured to be the location of the Interplay Adapter. 3. All CaptureManager channels with an AirSpeed device, must have the Media Manager Host Name for the AirSpeed device, configured to be the same as the Asset Manager for the AirSpeed. 4. The Interplay Server requested during the installation of the Media Browse Unity Video service should be made the location of the Interplay Adapter. The value may also be adjusted in the registry at the following location: [HKEY_LOCAL_MACHINE\SOFTWARE\iNEWS\Media Browse\Media Browse Unity Video Service] "Media Manager Host Name"="" 13
NOTE: The scenario exists in which the Interplay Adapter could be installed on the same computer as the Media Browse Unity Video service, in which case all configurations for AirSpeed asset manager, the Media Manager Host Name setting in the AirSpeed device configuration in CaptureManager channel, and the Interplay Server (Media Manager Host Name) for the Media Browse Unity Video service would all be the same computer name. Changes between CaptureManager 4.0.2 and 4.0.3 Previously, if an instant recording was being attempted on a channel configured with an AirSpeed device and the recording was left in a cued state for more than 75 seconds, transfer errors for that recording would begin to appear. Now, an instant recording can be left in a cued state without the appearance of transfer errors. Changes between CaptureManager 4.0.1 and 4.0.2 The Media Browse VTR service will no longer stop functioning if a recording is attempted using a VTR that has no serial connection to the Serial Control Server on which the Media Browse VTR service is running. Changes between CaptureManager 4.0.0 and 4.0.1 The Record button in the Instant Record dialog will no longer become inappropriately active while initiating a recording that is between the Ready and Recording states. New Features in Release 4.0.4 CaptureManager Can Steer AirSpeed Capture to a Particular Workspace Any AirSpeed recording initiated via CaptureManager can utilize any stored template on an AirSpeed to direct the captured media to a particular workspace. An AirSpeed template name can be inserted by a user into the Video ID field for ingest, as follows: <template name>/<video ID>. If the template name is missing, then the active template is assumed. If the designated template name does not exist on the AirSpeed, then the active template is used. During the recording, Media Browse temporarily changes the AirSpeed s active template to the template specified in the Video ID and then resets the active template to its previous value. The template name is stripped off for other devices, in particular: GVG Profile and Avid AirSPACE. The following example shows additional AirSpeed workspace templates stored with the names 4, 5, 6, and 7. 14
In the CaptureManager Instant Record dialog (shown below), the AirSpeed recording would be steered to the workspace for which the 6 template corresponds by the presence of the 6/ before the Video ID of st: Unity Video Service has Configurable Interplay Access Polling Interval The Unity Video service checks in metadata (such as comments, PreventAutoArchive setting, Project location, etc.) associated with a particular Interplay Access asset for which CaptureManager is controlling the capture. That asset must exist in Interplay Access prior to the metadata being updated. The Unity Video Service will check Media Interplay Access for the asset to ensure its existence in Interplay Access prior to attempting any metadata updates. The frequency at which the Unity Video service will perform checks for the appearance in Interplay Access of assets CaptureManager is creating through its capture process can be adjusted by making changes to the following entry in the Windows registry for the Unity Video service: [HKEY_LOCAL_MACHINE\SOFTWARE\iNEWS\Media Browse\Media Browse Unity Video Service] "First Checkin Check Interval (seconds)"="60" Caution: Generally, it is best to avoid making changes to the registry. Only edit the registry when it is absolutely necessary. Incorrectly editing the registry may severely damage your system. Before making any changes to the registry, Avid recommends backing up any valued data. The value of First Checkin Check Interval (seconds) is the number of seconds between Unity Video service checks for CaptureManager captured material in Interplay Access after an initial series of checks. The default value is 60. The value of this entry along with the value of the Short Chunking Period, configured directly on an Avid AirSpeed, will determine how quickly CaptureManager created metadata will be reflected in Interplay Access after the beginning of a CaptureManager initiated AirSpeed recording. (For more information on configuring the Short Chunking Period, see Chunking in the Avid AirSpeed Installation and User s Guide.) If users want to have CaptureManager recordings to be checked into Interplay Access in the CaptureManager designated folder (project in Interplay Access) with other CaptureManager generated metadata very soon after the recording begins, the First Checkin Check Interval (seconds) value should be made small, such as 5 seconds, along with a small Short Chunking Period on the AirSpeed, such as 15 seconds. 15
If users want to minimize impact to Interplay Access Engine and Interplay Adapter, the First Checkin Check Interval (seconds) value should not be significantly shorter than the Short Chunking Period and may even be made longer than the Short Chuncking Period to ensure minimal non-existent asset errors are dealt with by Interplay Access Engine and Interplay Adapter. Known Limitations This section provides information on known limitations that were not addressed in this release. Any available workaround procedures are also documented, when possible. Note: For limitations related to compatibility of this release with previous versions/other products, see the section of this document entitled, Compatibility Issues. Recording at the Midnight Transition The CaptureManager system requires a minimum of 2 minutes of lead time for all scheduled recordings.this ensures that CaptureManager has time enough to correctly process the recording. When a recording is to begin at midnight, it is important to schedule the recording to start prior to midnight so that CaptureManager can process the recording before the actual start time. This step is required because of the schedule grid's limitation for crossing a date boundary. Also, a recording that crosses over midnight will only appear on the previous days schedule grid. CaptureManager Client Limitations Regional and Language Options Font must be changed in certain locations for Unicode characters to be displayed. If the regional and language options are not set correctly in Windows, then channel names containing Unicode characters will not be displayed correctly in some areas of Capture Manager. To ensure proper character display, set in the Windows Control Panel the regional and language options to the correct language for your location, such as Japanese, as shown in the following graphics: Context Sensitive Menus The Open context sensitive menu item for an asset on the assets tab is non-functional 16
When an asset is selected on the Assets tab of the CaptureManager client, a right-click produces a context sensitive menu that contains a non-functional Open option. The Play context sensitive menu item for an asset on the Feed Capture tab is nonfunctional When an asset is selected on the Feed Capture tab of the CaptureManager client, a right-click produces a context sensitive menu that contains a non-functional Play option. 17
ActiveX Add-in Tab The ActiveX add-in tab will not display even with proper user profile configuration settings The ActiveX add-in tab will not display even when the user profile setting Media Browse Client > Visible Components > Show ActiveX Add-In Page is set to true. Comments Tab On the Assets tab, the Meta section contains a Comments tab for each asset that contains a non-functional TC>> button. The VTR Record Dialog VTR Record dialog contains a preview window which contains sub-windows and controls that are non-functional When the Acquire button from the Device Capture tab is selected, the VTR Record dialog is presented. This dialog contains the following elements that are not functional in the CaptureManager client: A Preview box (which does contain VTR controls that are still needed) and the items not needed from the current "Preview" box are: a. A Video (disabled) and Audio (enable) check boxes b. An established video window (a black area reserved for video playback) c. A volume control d. The statement about the Preview lagging behind Durations of Device Capture Recordings When a Device Capture recording is ended early, the new durations are not reflected in the CaptureManager client. If a Device Capture recording is ended early by a CaptureManager user who stopped the recording manually, the durations on the Device Capture tab and in the Assets tab for that recording will show the original, intended duration/out time, instead of the adjusted, correct duration/out time. Automatic Software Updates of the CaptureManager Client Client does not check for available software updates A CaptureManager client of a different software version can be launched against a CaptureManager server running the software distribution service and the improper CaptureManager client version will not be updated. Workaround: When Start > Programs > Avid > CaptureManager > Administrative Tools > CaptureManager Software Update is run, the software update process will be run. CaptureManager Client Longevity A CaptureManager client can become unresponsive A CaptureManager client can become unresponsive while possibly consuming large amounts of virtual memory if running for an extended period of time Workaround: End the CaptureManager.exe process. Solution #1: A possible cause of the unresponsive condition is when the network interface card (NIC) on the computer is allowed to sleep or go into a low-power mode. Disable all sleeping and low-power consumption features of the NIC. Solution #2: A possible cause of the unresponsive condition is CaptureManager Client attempting to write diagnostic logging to the CaptureManager Monitoring service. The writing of this logging information 18
should be disabled for this release of CaptureManager. To disable logging to the CaptureManager logging service, make the following Windows registry entry false on all CaptureManager computers: [HKEY_LOCAL_MACHINE\SOFTWARE\iNEWS\Media Browse\Media Browse Protocol] "Send Log Message Notifications"="false" Channel Configuration Adding an Avid Interplay Low-Res Encode Device To add an Avid Interplay Low-Res Encode Device to a CaptureManager channel, the category of device in the Device Information dialog that must be selected is Avid Low-Res. Media Browse Monitor limitations System Tab, License Button The License Usage dialog box does not accurately reflect CaptureManager client license usage. 19
Technical Support Information Most products feature a number of coverage options. Avid Assurance service offerings are designed to facilitate your use of Avid solutions. Service options include extended telephone coverage, automatic software maintenance, extended hardware warranty, and preferred pricing on replacement parts. Offerings and options may vary by product and are not available for all products. For more information regarding Avid s service offerings, visit www.avid.com/support or call Avid Sales at 800-949-AVID (800-949-2843). Program availability and details might vary depending on geographic location and are subject to change without notice. Contact your local Avid office or your local Avid Reseller for complete program information and pricing. However, if you need help locating an Avid office or Avid Reseller near you, please visit www.avid.com or call in North America 800-949-AVID (800-949-2843). International users call 978-275-2480. Accessing Online Support Avid Online Support is available 24 hours per day, 7 days per week. Search the Knowledge Base to find answers, to view error messages, to access troubleshooting tips, to download updates, and to read/join online message-board discussions. To access Avid Online Support: Go to www.avid.com/onlinesupport. Note: Supplemental documentation for this release, if available, is provided on the Knowledge Base. For the latest up-to-date information, browse the Knowledge Base at Avid Online Support. 20
Copyright and Disclaimer Product specifications are subject to change without notice and do not represent a commitment on the part of Avid Technology, Inc. The software described in this document is furnished under a license agreement. You can obtain a copy of that license by visiting Avid's Web site at www.avid.com. The terms of that license are also available in the product in the same directory as the software. The software may not be reverse assembled and may be used or copied only in accordance with the terms of the license agreement. It is against the law to copy the software on any medium except as specifically allowed in the license agreement. No part of this document may be reproduced or transmitted in any form or by any means, electronic or mechanical, including photocopying and recording, for any purpose without the express written permission of Avid Technology, Inc. Copyright 2010 Avid Technology, Inc. and its licensors. All rights reserved. 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 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, Axiom, Beat Detective, Beauty Without The Bandwidth, Beyond Reality, BF Essentials, Bomb Factory, Boom, Bruno, C 24, CaptureManager, ChromaCurve, ChromaWheel, Cineractive Engine, Cineractive Player, Cineractive Viewer, Color Conductor, Command 24, Command 8, Conectiv, Control 24, Cosmonaut Voice, CountDown, d2, d3, DAE, Dazzle, Dazzle Digital Video Creator, D- Command, D-Control, Deko, DekoCast, D-Fi, D-fx, Digi 003, DigiBase, DigiDelivery, 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, DPP-1, D-Show, DSP Manager, DS-StorageCalc, DV Toolkit, DVD Complete, D-Verb, Eleven, EM, 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, HyperControl, HyperSPACE, HyperSPACE HDCAM, iknowledge, Image Independence, Impact, Improv, inews, inews Assign, inews ControlAir, Instantwrite, Instinct, Intelligent Content Management, Intelligent Digital Actor Technology, IntelliRender, Intelli-Sat, Intelli-sat Broadcasting Recording Manager, InterFX, Interplay, intone, Intraframe, is Expander, ISIS, IsoSync, is9, is18, is23, is36, ISIS, IsoSync, KeyRig, KeyStudio, LaunchPad, LeaderPlus, LFX, Lightning, Link & Sync, ListSync, LKT-200, Lo-Fi, Luna, MachineControl, Magic Mask, Make Anything Hollywood, make manage move media, Marquee, MassivePack, Massive Pack Pro, M-Audio, M-Audio Micro, Maxim, Mbox, Media Composer, MediaDock, MediaDock Shuttle, MediaFlow, MediaLog, MediaMatch, MediaMix, Media Reader, Media Recorder, MEDIArray, MediaServer, MediaShare, MetaFuze, MetaSync, MicroTrack, MIDI I/O, Midiman, Mix Rack, MixLab, Moviebox, Moviestar, MultiShell, NaturalMatch, NewsCutter, NewsView, Nitris, NL3D, NLP, Nova, NRV-10 interfx, NSDOS, NSWIN, Octane, OMF, OMF Interchange, OMM, OnDVD, Open Media Framework, Open Media Management, Ozone, Ozonic, Painterly Effects, Palladium, Personal Q, PET, Pinnacle, Pinnacle DistanTV, Pinnacle GenieBox, Pinnacle HomeMusic, Pinnacle MediaSuite, Pinnacle Mobile Media, Pinnacle Scorefitter, Pinnacle Studio, Pinnacle Studio MovieBoard, Pinnacle Systems, Pinnacle VideoSpin, Podcast Factory, PowerSwap, PRE, ProControl, ProEncode, Profiler, Pro Tools HD, Pro Tools LE, Pro Tools M-Powered, Pro Transfer, Pro Tools, 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, Scorefitter, ScriptSync, SecureProductionEnvironment, Serv LT, Serv GT, Session, Shape-to-Shape, ShuttleCase, Sibelius, SIDON, SimulPlay, SimulRecord, Slightly Rude Compressor, Smack!, Soft SampleCell, Soft-Clip Limiter, Solaris, SoundReplacer, SPACE, SPACEShift, SpectraGraph, SpectraMatte, SteadyGlide, Streamfactory, Streamgenie, StreamRAID, Strike, Structure, Studiophile, SubCap, Sundance Digital, Sundance, SurroundScope, Symphony, SYNC HD, Synchronic, SynchroScope, SYNC I/O, Syntax, TDM FlexCable, TechFlix, Tel-Ray, Thunder, 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, Torq, Torq Xponent, Transfuser, Transit, TransJammer, Trigger Finger, Trillium Lane Labs, TruTouch, UnityRAID, Vari-Fi, Velvet, Video the Web Way, VideoRAID, VideoSPACE, VideoSpin, VTEM, Work-N-Play, Xdeck, X-Form, Xmon, XPAND!, Xponent, X-Session, and X-Session Pro are either registered trademarks or trademarks of Avid Technology, Inc. in the United States and/or other countries. All other trademarks contained herein are the property of their respective owners. All other trademarks contained herein are the property of their respective owners. CaptureManager v4.2.1 ReadMe 0130-07908-01 Rev M 24 September 2010 This document is distributed by Avid in online (electronic) form only, and is not available for purchase in printed form. 21