avid unity mediamanager v4.5.15...
TRANSCRIPT
a
Important Information
Avid® recommends that you read all the information in this ReadMe file thoroughly before installing or using any new software release.
Important: Search the Avid Knowledge Base 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, supported client information, and summary information on system and memory requirements. This document also lists hardware and software limitations.
Overview
Use this ReadMe file to supplement the install process of the Avid Unity MediaManager software, described in the Avid Unity MediaManager Installation and Setup Guide.
Revision History
Date Revised Changes Made
September 12, 2007 Revised supported versions of Avid Unity ISIS product, support for v1.4 when released. See “Supported Avid Unity ISIS Media Network” on page 18..
This document is more up-to-date than the file on the application CD.
Avid Unity™ MediaManagerVersion 4.5.15 ReadMe
2
Contents
If You Need Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
Symbols and Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
Changes in v4.5.15. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
Features Added in v4.5.x . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
Hardware and Software Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
Installing Internet Explorer on MediaManager Clients . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
Changes to Installing MediaManager Server and Client Software . . . . . . . . . . . . . . . . . . . 23
Upgrade Information. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
Suggestions for Optimum Performance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
Special Notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
Documentation Changes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
Accessing Online Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
Fixed in v4.5.15 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
Fixed in v4.5.14 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
Fixed in v4.5.13 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35
Fixed in v4.5.10 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35
Fixed in v4.5.8 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36
Fixed in v4.5.7 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36
Fixed in v4.5.6 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36
Limitations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37
Technical Support Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48
If You Need Help
3
If You Need Help
If you are having trouble using Avid Unity MediaManager:
1. Retry the action, carefully following the instructions given for that task. It is especially important to check each step of your workflow.
2. Check the Knowledge Base for latest information that became available after the documentation was published. You can find the latest version of the ReadMe file or Release Notes for your product at www.avid.com/readme.
3. Check the documentation that came with your Avid application or your hardware for maintenance or hardware-related issues.
4. Visit Avid Online Support at www.avid.com/onlineSupport/. 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 or join online message-board discussions.
Symbols and Conventions
ReadMe documents use the following symbols and conventions:
Symbol or Convention Meaning or Action
n A note provides important related information, reminders, recommendations, and strong suggestions.
c A caution means that a specific action you take could cause harm to your computer or cause you to lose data.
w A warning describes an action that could cause you physical harm. Follow the guidelines in this document or on the unit itself when handling electrical equipment.
> This symbol indicates menu commands (and subcommands) in the order you select them. For example, File > Import means to open the File menu and then select the Import command.
t This symbol indicates a single-step procedure. Multiple arrows in a list indicate that you perform one of the actions listed.
Italic font Italic font is used to emphasize certain words and to indicate variables.
Courier Bold font Courier Bold font identifies text that you type.
Ctrl+key or mouse actionk+key or mouse action
Press and hold the first key while you press the last key or perform the mouse action. For example, k+Option+C or Ctrl+drag.
4
Changes in v4.5.15
Support has been added for the new dongle manager application. The DongleDumper utility has been replaced with DongleManager. The DongleManager is located in:
Program Files\Avid\<Product>\Utilities\DongleManager
Features Added in v4.5.x
Features added and changes made to Avid Unity MediaManager v4.5.x include the following:
• Provides support for Avid iNEWS Instinct. See “Workgroup Settings for Avid iNEWS Instinct” on page 5
• Provides support for Avid Unity ISIS™ media network
• MXF/AAF support for several Avid DNA editors in a workgroup environment. See “MXF/AAF File Format Support” on page 7.
• You can choose to associate a MediaManager Catalog with a playback device. When performing a send to playback, the catalog will contain clips of the media and all its relatives, including the .transfer sequences, that successfully transfer to the playback device. For configuration information on associating a playback device with a catalog, see the Avid Unity TransferManager v2.9.19 Release Notes.
n The playback catalog feature is not available with AirSpeed®.
• Setting up Extended Searches is less time consuming. The Extended Search window, by default, does not generate value lists. A check box is provided that lets you display a list of values. See “Enhancing Value Lists in Extended Search” on page 14.
• Performing an Extended Search includes a “Does Not Contain” operator for several attributes to help you refine your search. See “Extended Search “Does Not Contain” Operator” on page 14.
• The Frame Chase editing feature lets an Avid editor view and edit clips when capturing from a supported external device. The Avid editing system must be a client in an MXF workgroup that includes Avid Unity TransferManager. See “Using Frame Chase Editing” in the MediaManager Help.
• A MediaManager client can use Relink without enabling MDB Manager.
Features Added in v4.5.x
5
Workgroup Settings for Avid iNEWS Instinct
MediaManager provides support for the Avid iNEWS Instinct story-building application. MediaManager settings for the Avid iNEWS Instinct can only be changed by an administrator. These settings are stored on the MediaManager server used by the Avid iNEWS Instinct when retrieving media objects managed by MediaManager.
To select Avid iNEWS Instinct workgroup settings:
1. Log in to the MediaManager server as an administrator.
2. Click Administration in the mode selector.
3. Click the iNEWS Instinct Workgroup icon in the Functions list.
The iNEWS Instinct Workgroup Settings window opens.
4. Select options as described in the following table.
6
5. Click Save.
Avid iNEWS Instinct Workgroup Settings
Option Description
Video Format Sets the media format to NTSC 30i, PAL 25i, or Either. Select Either to let iNEWS Instinct users work in either format.
iNEWS Word Length Sets the character count strategy for timing stories. The value you enter must match the value of the wordlength parameter in the /site/system file on the iNEWS server. The default value is 0, where each word is counted once. Values other than 0 indicate the number of characters that are considered a word.
Audio: - Source Audio Patching
Natural Sound Lets you map the source natural sound (NAT) track (A1 - A8) and name the track using the text box.
Sound on Tape Lets you map the source Sound-on-Tape (SOT) track (A1 - A8) and name the track using the text box.
Voice Over Lets you map the source voice-over track (A1 - A8) and name the track using the text box.
Audio: - Storyline Audio Patching
Natural Sound Lets you map the sequence natural sound (NAT) track (A1 - A4).
Sound on Tape Lets you map the sequence Sound-on-Tape (SOT) track (A1 - A4).
Voice Over Lets you map the sequence voice-over track (A1 - A4).
Audio:
Audio Rate Lets you select the audio rate, 48kHz.
Ducking Lets you set the default ducking in -dB.
Target WorkSpace Lets you select the location for the voice-over.
n In an Avid Unity ISIS environment, when recording a voice over using iNEWS Instinct, do not select workspaces that contain the euro currency symbol in the workspace name. Selecting a target VO workspace that contains the euro symbol will cause the voice over to fail during the countdown process.
Sample Bit Depth Lets you set the audio sample size to match the target device, when you are using Send to Playback. Default is 16.
Features Added in v4.5.x
7
MXF/AAF File Format Support
Previous MediaManager releases supported the check in of OMF media with OMF metadata. MediaManager v4.5.1 or later also supports an MXF/AAF workgroup environment. MXF media and AAF metadata created and edited with a supported Avid editing application can be shared in an Avid MXF workgroup with other Avid MXF capable devices, such as Avid Media Composer® Adrenaline™ HD editors.
n The MXF/AAF workgroup mode does not support all Avid editing applications with MXF capability. For a list of the supported Avid editing applications, see the table in “Understanding the Workgroup Modes” on page 8.
An MXF/AAF workgroup is backward compatible, meaning you can check out legacy OMF metadata and use legacy OMF media files in sequences. However, after you modify the OMF metadata and check in the media object, the OMF metadata is converted to AAF metadata. Only Avid editing systems that are MediaManager clients in an MXF workgroup can access the OMF files.
In addition to providing an MXF/AAF workgroup, there is also an OMF workgroup mode to allow continued support of OMF media and OMF metadata. A workgroup environment containing Avid products that are not fully supported in an MXF/AAF workgroup must use the OMF workgroup mode.
c By default, the workgroup mode is set to OMF. An administrator can change the workgroup mode to AAF; however, once the data format is set to AAF you cannot change the workgroup mode back to OMF. For information about setting the workgroup mode, see “Setting the Workgroup Mode to MXF/AAF” on page 8.
For compatibility issues when working in either an OMF or MXF/AAF workgroup, see “Understanding the Workgroup Modes” on page 8.
There are two workgroup modes:
• AAF—MXF media files and AAF metadata; supports HD workflows and SD MXF workflows. See “Working in MXF/AAF Workgroup Mode” on page 10.
• OMF—OMF media files and OMF metadata; supports SD workflows. The OMF workgroup mode also supports HD workflows in MXF. However, there are limitations as to which Avid editing application can work in an OMF workgroup with MXF media. See “Working in an OMF Workgroup Mode” on page 11.
8
Understanding the Workgroup Modes
The workgroup mode is set to OMF mode by default during installation of the MediaManager server. An administrator can change the workgroup mode to AAF. Once a workgroup is set to MXF/AAF it cannot be changed back to an OMF workgroup. For instructions on how to change to an MXF/AAF workgroup, see “Setting the Workgroup Mode to MXF/AAF” on page 8.
It is important to understand the differences between working in an OMF workgroup and an MXF/AAF workgroup before you change to an MXF/AAF workgroup, as there are compatibility issues with some previous versions of Avid products.
The following sections provide detailed information about each mode:
• “Working in MXF/AAF Workgroup Mode” on page 10
• “Working in an OMF Workgroup Mode” on page 11
The following table outlines the supported media in each of the workgroup modes when using the various Avid editing applications.
Setting the Workgroup Mode to MXF/AAF
By default the workgroup mode is set to OMF. An administrator can change the workgroup mode to MXF/AAF; however, once the workgroup is switched to MXF/AAF it cannot be changed back to OMF mode.
EditorOMF Workgroup ModeMedia Supported
MXF/AAF Workgroup ModeMedia Supported
Avid Meridien™ editing applications
8-bit SD OMF media Not supported
Media Composer Adrenaline v1.6.1 or later, NewsCutter® Adrenaline v5.6 or later, NewsCutter XP v5.6 or later
8-bit SD OMF media Not supported
Media Composer Adrenaline HD v2.1.5 or later, v2.2.2 or later, NewsCutter Adrenaline v6.1.5 or later, v6.2.2 or later,NewsCutter XP v6.1.5 or later, v6.2.2 or later
8-bit SD OMF media10-bit 1:1 SD MXF mediaHD MXF media
8-bit SD OMF mediaa
All MXF
a. For backward compatibility, when you check out OMF media with OMF metadata and then check it back into MediaManager with one of these Avid editing applications, it is checked in as OMF media with AAF metadata. For more details, see “Working in MXF/AAF Workgroup Mode” on page 10.
Features Added in v4.5.x
9
To set the workgroup to MXF/AAF mode:
1. Log in to the MediaManager server as an administrator.
2. Click Administration in the mode selector.
3. Click the System Setup icon in the Functions list.
The System Setup window opens.
4. Select Data Format > AAF.
c You cannot switch the Data Format back to OMF after you select AAF.
5. Click Submit.
6. Restart the MediaManager server.
Data Format menu
10
Working in MXF/AAF Workgroup Mode
When a workgroup is set to AAF mode, all new media checked into the workgroup is in MXF format with AAF metadata. All editors and applications included in the MXF/AAF workgroup must support the ability to read and write MXF media and AAF metadata. If existing OMF media is checked out by an editor and modified, when it is checked back in the media is in OMF format with AAF metadata. Media with AAF metadata cannot be checked out by Avid products that are not fully supported in an MXF/AAF workgroup.
n The MXF/AAF workgroup mode does not support all Avid editing applications with MXF capability. For a list of the supported Avid editing applications, see the table in “Understanding the Workgroup Modes” on page 8.
Consider the following about MXF/AAF workgroup mode:
• New media is checked in as MXF media and AAF metadata.
• Avid editing applications must support MXF/AAF format, therefore Avid Meridien editors and some versions of the Avid DNA editors are not supported in an MXF/AAF workgroup. For a list of supported Avid editing applications, see the table in “Understanding the Workgroup Modes” on page 8.
• MXF/AAF workgroup mode is backward compatible with OMF media. OMF objects might be present in the workgroup that has legacy media and metadata. You can check out OMF metadata, but after modifications to the clip it is checked in as AAF. OMF master clips can be checked out and included in new sequences. When an OMF master clip is modified by adding locators or comments, it is checked in as AAF metadata but the associated media files remain in OMF format.
• When performing a resync on OMF media files, all metadata is checked in to MediaManager in AAF format and is not available to Avid editing applications that do not support MXF, such as Avid Meridien editors.
• In an MXF/AAF workgroup, OMF media files are identified with the text OMF in the file name.
• Avid MediaFiles/MXF is the media destination folder for MXF media files.
• MDB Manager does not support MXF media.
• Editing clips when capturing media using the Avid editing application’s Capture tool is not supported. For more information, see “Using Frame Chase Editing” in the MediaManager Help.
Features Added in v4.5.x
11
Working in an OMF Workgroup Mode
The OMF workgroup mode provides a workgroup environment that supports OMF media and OMF metadata. If your workgroup contains any Avid products that do not support MXF or that have limited support for MXF media, you must use the OMF workgroup mode. The OMF workgroup has limited support for video MXF media. Only MediaManager clients that support HD or 10-bit MXF media can work with the MXF media in an OMF workgroup.
n Some Avid editing applications with MXF capability are not supported in an MXF/AAF workgroup mode and must use the OMF workgroup mode. For a list of the supported Avid editing applications, see the table in “Understanding the Workgroup Modes” on page 8.
The following editors can check in HD and 10-bit 1:1 SD MXF media:
• Media Composer Adrenaline HD v2.1.5 or later, v2.2.2 or later
• NewsCutter Adrenaline v6.1.5 or later, v6.2.2 or later
• NewsCutter XP v6.1.5 or later, v6.2.2 or later
Consider the following about OMF workgroup mode:
• OMF is the default workgroup mode.
• OMF workgroup mode supports Avid editing applications that support OMF format, such as Avid Meridien editors.
• OMF workgroup mode supports versions of the Avid DNA editors that support HD and SD 10-bit MXF media.
• OMF media is checked in as OMF media and OMF metadata.
• HD and SD 10-bit MXF media is checked in as MXF media and AAF metadata.
• Audio MXF media is not supported and is not allowed by the Avid editing application.
• In an OMF workgroup, MXF media files are identified with the text AAF in the file name.
• The Media Creation File Format setting in the Avid editing application is changed to OMF when any project is opened by a supported Avid editing application in an OMF workgroup. You can change the setting to MXF when working with HD and 10-bit 1:1 SD MXF media.
• OMF workgroup mode supports any media format allowed by the Avid editing application on non-shared media drives. However, to share the media in a workgroup you must consolidate or transcode the media from the non-shared drive to OMF on a shared drive. Consolidation and transcode both automatically check in new media to the MediaManager at the time of creation.
12
Working with P2 Media in an Avid Unity Workgroup
You can share P2 MXF media files in either an MXF workgroup or an OMF workgroup. However, you need to transcode or consolidate the P2 media files using an Avid editing application before using the files in an Avid workgroup.
• In an MXF workgroup, you can either consolidate or transcode P2 clips to a workspace. If you transcode, you must transcode P2 MXF files to another MXF resolution.
• In an OMF workgroup, you must transcode P2 clips to a workspace. You must transcode P2 MXF files to OMF files.
Consolidating or transcoding clips to an Avid Unity workspace automatically checks all related metadata into MediaManager, making the clips readily accessible to other users.
n Some card slots of the P2 drive might require drive letters that have already been assigned to existing network drives. If your computer does not display all five card slots as drives, reassign the network drives or restart your system.
For information about transcoding or consolidating files, and about P2 support, see the Help for your Avid editing application.
Workflow: Sharing P2 Media in an OMF Workgroup
P2 media is native MXF/AAF media that requires a conversion to use P2 media in an OMF workgroup. The following workflow provides steps for working with P2 media in an OMF mode workgroup.
1. Unmount any shared workspaces by exiting Avid Unity Connection Manager.
2. Mount the P2 drive as described in the Help for your Avid editing application.
3. Start Avid Unity Connection Manager and mount the workspaces you want to work with.
4. Start the Avid editing application and open a new project. You should use this project for P2 transcode only.
5. Make sure you are not logged into MediaManager.
MediaManager in an OMF workgroup prevents the check in of MXF/AAF media.
6. In the Avid editing application’s Media Creation Settings dialog box, set the File Format to MXF.
7. Open the Media Tool and select the P2 volumes.
You might need to Refresh Media Directories and perform a Mount All.
8. Drag the P2 media files from the Media Tool to a bin.
Features Added in v4.5.x
13
9. In the Avid editing application’s Media Creation Settings dialog box, set the File Format to OMF.
10. Log into MediaManager.
11. Select the P2 media files in the bin and select Bin > Consolidate/Transcode.
12. Select the Transcode options, select a target drive, and select a video resolution.
13. Make sure you are set up to transcode to OMF.
14. When the transcoding is complete, all related metadata is automatically checked into MediaManager, making the clips readily accessible to other users.
Workflow: Sharing P2 Media in an MXF Workgroup
P2 media is native MXF/AAF media. To share P2 media in an Avid Unity MXF/AAF workgroup, you need to consolidate the media. The following workflow provides steps for working with P2 media in an MXF/AAF mode workgroup.
1. Unmount any shared workspaces by exiting Avid Unity Connection Manager.
2. Mount the P2 drive as described in the Help for your Avid editing application.
3. Start Avid Unity Connection Manager and mount the workspaces you want to work with.
4. Start the Avid editing application and open a project.
5. Open the Media Tool and select the P2 volumes.
You might need to Refresh Media Directories and perform a Mount All.
6. Drag the P2 media files from the Media Tool to a bin.
7. Select the P2 media files in the bin and select Bin > Consolidate/Transcode.
8. Select the Consolidate options, select a target drive, and select a video resolution.
9. When the consolidate is complete, all related metadata is automatically checked into MediaManager, making the clips readily accessible to other users.
14
Enhancing Value Lists in Extended Search
The Extended Search window allows you to specify complex search criteria to find exactly the objects you need. The Value element of the Extended Search window can display a list of values depending on the Attribute Name and Operator selected. By default, the list of values is not generated, as it might be time consuming for the system to create the list. A check box is provided that lets you display a list of values. You can then select a value from the list instead of typing a value in the text box.
To display a Value list in the Extended Search window:
1. In the Extended Search window, click the check box at the right of the Value text box to clear the check mark.
A list is generated in the Value text box.
n The check box is available depending on the Attribute Name and Operator selected.
2. Select a value from the list.
For more information about extended searches, see “Performing Extended Searches” in the MediaManager Help.
Extended Search “Does Not Contain” Operator
A “Does Not Contain” operator is available when you perform an extended search. This operator lets you search for all clips that do not include the value you specified. All clips are returned in the search results when the Does Not Contain operator is used with the following attributes:
• Bin Name
• Project Name
• Catalog Name
• Production Name
• Incoming Folder
For example, if you perform an extended search using the Bin Name attribute, and the Does Not Contain operator, and if you specify Monday as the value, the search result returns all clips associated with any project that do not have Monday as the Bin Name.
All clips are returned in the search results when any operator is used with any of the following attributes:
Bin Name Check-in Date Incoming Folder Production Name Status
Catalog Name Data Format In-Use Project Name Type
Hardware and Software Requirements
15
Hardware and Software Requirements
This section describes the hardware and software requirements for the MediaManager server and client platforms. For information on installing the software, see the Avid Unity MediaManager Installation and Setup Guide.
MediaManager Server Hardware Configuration
The following table lists the hardware and operating system requirements for the Avid Unity MediaManager server. For the most up-to-date information about hardware and software requirements, go to the Avid Unity MediaManager products page at www.avid.com and click on Specifications.
Installing the Intel PRO/1000MT Card
When configuring a MediaManager (SR2200) server in an Avid Unity ISIS environment, you need to add an Intel PRO/1000 MT (copper) card into the MediaManager server. Insert the Intel PRO/1000 card into slot 3 (the top slot) of the MediaManager SR2200 server. Follow the directions supplied with the card.
After you install the Intel PRO/1000 Server Adapter and restart your system, a message might appear, looking for the Intel PRO/1000 driver.
Hardware Requirements for the MediaManager Server
Hardware Description
Platform Dual 3.2 GHz CPU (SR2400)
Dual 1.3 GHz CPU (SR2200)
Dual 800 MHz CPUs (ISP2150) - only supported with Avid Unity MediaNetwork
System memory - RAM 2 GB
Monitors 1024 x 768, 17-inch minimum
Network Ethernet
Shared storage ATTO™ FC card for connection to Avid Unity MediaNetwork or LANshare EX
Intel® Gigabit Ethernet® connection to Avid Unity ISIS media network
16
To install the Intel PRO/1000 driver:
1. Open the C:\Intel10.0 folder.
2. Click the Autorun.exe file.
The Intel Pro Network Connections window opens.
3. Click Install Drivers.
4. Click Finish.
Supported MediaManager Client Platforms
MediaManager v4.5.15 supports the following minimum versions of client platforms:
n Avid editing applications installed on Macintosh® systems are not supported in an Avid Unity ISIS environment.
Supported MediaManager Clients
Client - Avid EditorMinimumVersion
Workgroup Mode Supported
Avid iNEWS Instinct v1.0 MXF workgroup
Avid Symphony™ Nitris® v1.0 MXF workgroupOMF workgroupa
Avid Symphony v5.5 (Windows)v5.0.9 (Macintosh)
OMF workgroup
Avid Media Composer Adrenaline HD v2.1.9, v2.2.1 MXF workgroupOMF workgroupa
Avid Media Composer Adrenaline v1.6.7 OMF workgroup
Avid Media Composer v12.5 (Windows)v12.0.9 (Macintosh)
OMF workgroup
Avid Film Composer® v12.5 (Windows)v12.0.9 (Macintosh)
OMF workgroup
Avid NewsCutter Adrenaline v6.1.9, v6.2.1 MXF workgroupOMF workgroupa
Avid NewsCutter Adrenaline FX v5.6 OMF workgroup
Avid NewsCutter XP (Avid Mojo® or software)
v6.1.9, v6.2.1 MXF workgroupOMF workgroupa
Hardware and Software Requirements
17
Supported Players
The following supported players have been tested with MediaManager v4.5.15:
• MediaManager Browser Player v2.5.14
• MediaManager ProLog Player v2.5.14
• Avid Player v2.5.14 (Windows)
• Avid Player v2.0.3 (Macintosh)
Avid NewsCutter XP (Avid Mojo or software)
v5.6 OMF workgroup
Avid NewsCutter v4.5 OMF workgroup
Avid NewsCutter XP v3.8.13 OMF workgroup
Avid Media Station XL v12.5 OMF workgroup
Avid DS Nitris v7.6 Limited functionality with MediaManager v4.5.x
Avid Unity TransferManager v2.9.9 MXF workgroupOMF workgroup
Avid Media Browse™ v2.8.3.38, v2.7.1.1 MXF workgroupOMF workgroup
a. Limited support in an OMF workgroup. See the table in “Understanding the Workgroup Modes” on page 8.
Supported MediaManager Clients (Continued)
Client - Avid EditorMinimumVersion
Workgroup Mode Supported
18
Supported Operating Systems on MediaManager Clients
The following operating systems are supported on the MediaManager clients:
• Microsoft® Windows® XP with Service Pack 2
• Microsoft Windows 2000 with Service Pack 4
• Macintosh OS X (v10.3.8 for Avid DNA editors, v10.2.6 for Avid Meridien editors)
Software Requirements
The following software is already installed on the MediaManager server system:
• Microsoft Windows 2000 Service Pack SP4
SP4 might not be installed on your MediaManager server. Avid provides a copy of SP4 on the MediaNetwork CD-ROM or you can update the Windows 2000 operating system by clicking the Start button and selecting Windows Update. Follow the installer instructions.
• Microsoft Internet Explorer 6.0 SP1
• Microsoft SQL Server 2000 SP4
SP4 might not be installed on your MediaManager server. Avid provides a copy of SP4 in the Utilities folder on the Install CD-ROM.
Supported Avid Unity ISIS Media Network
If your workgroup environment is an Avid Unity ISIS media network, you need to install the Avid Unity ISIS media network client software on your MediaManager server. You must install the Avid Unity ISIS client software prior to installing the MediaManager software.
The supported versions of Avid Unity ISIS media network client are:
• Avid Unity ISIS client v1.1B, v1.2, v1.3a, v1.4
For information on installing the Avid Unity ISIS client software, see the Avid Unity ISIS ReadMe and the Avid Unity ISIS System Setup Guide.
Supported Avid Unity MediaNetwork
If your workgroup environment is an Avid Unity MediaNetwork, then you need to install the Avid Unity MediaNetwork client software on your MediaManager server. You must install the Avid Unity MediaNetwork client software prior to installing the MediaManager software.
Hardware and Software Requirements
19
Supported Avid Unity MediaNetwork client versions for MediaManager server and MediaManager clients:
• Upgrade installation: Avid Unity MediaNetwork client v3.5.7, v4.1.5
• New installation: Avid Unity MediaNetwork LP client v4.2.2 or later
• Macintosh OS v10.4 (Tiger): Avid Unity MediaNetwork client v4.1, v4.1.2
For new installations, see the Avid Unity MediaNetwork Release Notes and the Avid Unity MediaNetwork Windows Fibre Channel Client Setup Guide.
For information on upgrading from an earlier version of MediaNetwork client, see the Avid Unity MediaNetwork Release Notes and the Avid Unity MediaNetwork Upgrade Notes.
Name Resolution
A Domain Name System (DNS) maps machine names to Internet addresses. Use the HOSTS file or create a HOSTS file if there is no DNS on your network. It is also convenient to place frequently used name-to-address mappings in this file.
n Each host on your network that uses HOSTS file services must have the file resident on the disk. Each client and server should be added to the HOSTS file so that every computer can see every other computer by name.
The syntax of the HOSTS file is:
<name> <type> <data> [<comment>]
name is the name assigned to a host or domain on the Internet.
n If you do not have a valid domain name, enter a fake domain name.
type is A (address) or CNAME (canonical name).data is determined by the type specified:
• If type = A, the data field contains an Internet address.
• If type = CNAME, the data field contains the alias name for an Internet address.
comment allows you to add a comment to the entry.
n Any combination of tabs and spaces can be used as a delimiter between each item in a line. Lines end with the return and linefeed characters.
CNAME entries are not required. They might make it easier to access an Internet address by using more common names.
20
Example Entries in a HOSTS File (Windows)
<IP Address> <name1> <name2> <nameN> [# <comment>]
The IP Address is in the period-delimited format, and spaces separate the name fields as in the following example:
192.102.73.6 myeditor1.xco.com myeditor1 fred #system in the front office
Example Entries in a HOSTS File (Macintosh)
myeditor1.xco.com A 128.8.1.1
fred CNAME myeditor1.xco.com ;system in front office
In this example, you could ping the address 128.8.1.1 by using myeditor1.xco.com or myeditor1. You could also use the alias name fred to access the same Internet address.
Updating the HOSTS File (Windows)
Microsoft TCP/IP can be configured to search the local host table file, HOSTS, for mappings of remote host names to IP addresses. For example, the entry for a computer with an address of 192.102.73.6 and a host name of myeditor1.xco.com looks similar to this:
192.102.73.6 myeditor1.xco.com
Edit the sample HOSTS file that is created when you install TCP/IP to include remote host names and their IP addresses for each computer with which you will communicate. This sample file also explains the syntax of the HOSTS file.
A host name always corresponds to an IP address that is stored in a HOSTS file or a name service such as DNS. A host name can be used in place of an IP address when using ping or other TCP/IP utilities.
A single entry consists of an IP address corresponding to one or more host names.
n Perform this procedure only if you do not have a DNS on your network.
To update the HOSTS file:
1. Double-click the WINNT folder.
2. Double-click the SYSTEM32 folder.
3. Double-click the DRIVERS folder.
4. Double-click the ETC folder.
5. Double-click the HOSTS file.
Hardware and Software Requirements
21
6. Make the necessary changes to the HOSTS file.
For example, to connect to the myeditor1.xco.com at the IP address 192.102.73.6, make the entry in the HOSTS file:
192.102.73.6 myeditor1.xco.com
n You can edit the HOSTS file with any word processor as long as you save it as Text Only without formatting commands. Make sure the HOSTS file does not have a file name extension (such as .txt). The HOSTS file will not work if there is a file name extension.
Updating the HOSTS File (Macintosh)
To create HOSTS files for network users, create a text file using SimpleText, adding text that defines name-to-address mappings for your particular network configuration.
n Perform this procedure only if you do not have a DNS on your network.
To create a HOSTS file:
1. Open a text editor such as SimpleText.
2. Add names and Internet addresses in the syntax specified in “Name Resolution” on page 19.
c TCP/IP protocols do not allow the use of international and graphics characters. Some word processors and editors do allow these characters; however, using them can cause unpredictable results.
3. Save the file as HOSTS, and place the file in the System folder.
4. Select Apple P menu > Control Panel > TCP/IP.
5. Select Edit > User Mode.
6. Select Advanced.
7. Click OK.
8. In the TCP/IP window, click Select HOSTS File.
9. Select the HOSTS file that you named in step 3.
10. Click Open.
11. Click OK.
12. Close the TCP/IP window.
13. Save the changes.
22
Installing Internet Explorer on MediaManager Clients
For MediaManager clients on a Windows system, Internet Explorer 6.0 is required to browse MediaManager.
For MediaManager clients on a Macintosh OS X system, Internet Explorer 5.2.2 or 5.2.3 is required to browse MediaManager. You can download Internet Explorer from the Microsoft Web site (www.microsoft.com).
Avid recommends the following Internet Explorer settings.
To select the Internet Explorer settings:
1. Open Internet Explorer.
2. Select Tools > Internet Options.
3. Click the General tab.
4. Click Settings in the Temporary Internet Files pane.
5. Select “Automatically” or “Every Time you Start Internet Explorer” in the “Check for Newer Versions of Stored Pages” pane. Do not select “Never,” as this setting might cause problems maintaining Select List Creator permissions while you are logged into MediaManager or when you are logging out of MediaManager.
Internet Explorer’s text font size might appear too large with MediaManager clients on a Macintosh system.
Changes to Installing MediaManager Server and Client Software
23
To change the font size, use the Internet Explorer’s Preferences settings. The following table provides suggested font sizes for various monitor resolutions.
Changes to Installing MediaManager Server and Client Software
The Avid Unity MediaManager Installation and Setup Guide describes how to install the MediaManager software. This section lists changes to the MediaManager installation for this release.
n After installing the latest version of MediaManager, if you decide to reinstall an older version, make sure you uninstall the latest version before reinstalling the older version. When uninstalling the latest version, you should use the Add/Remove programs in the Control Panel. The system automatically restarts after the uninstall is complete.
Installing IIS Lockdown Tool
The Microsoft Internet Information Services (IIS) Lockdown tool is an optional software package that improves the security on the system running the MediaManager server application. It closes unused doors that hackers could exploit. The tool does not affect the MediaManager server application in any way. It is not necessary to run this tool on new MediaManager servers, as that task is performed at the factory.
n If the MediaManager server is currently running the IIS Lockdown tool, it is not necessary to install version v2.1. If you want to install IIS Lockdown v2.1, you need to run the original IIS Lockdown tool to unlock the previous settings, then reinstall the MediaManager server application, and then install and run IIS Lockdown v2.1.
Internet Explorer Font Size (Macintosh)
Monitor Resolution Font Size
640 x 480 11 or 12
800 x 600 11 or 12
832 x 624 11 or 12
1024 x 768 9 or 10
1056 x 792 14
1280 x 1024 16
1600 x 1200 18
24
If you decide to install the IIS Lockdown tool, use the following procedure instead of the procedure in the “Installing IIS Lockdown” section of the Avid Unity MediaManager Installation and Setup Guide. If you install the software incorrectly it can prevent you from running MediaManager. If the system displays Microsoft 404 errors when you attempt to access the MediaManager application, reinstall the IIS Lockdown tool.
Installing the IIS Lockdown Tool
After you install the MediaManager server software, install the Microsoft Internet Information Services (IIS) IIS Lockdown v2.1 tool on the MediaManager server.
To install the IIS Lockdown tool:
1. Download the IIS Lockdown v2.1 executable file from the Microsoft Web site.
a. Go to www.microsoft.com.
b. Search for IIS Lockdown.
c. Follow the download procedure on the Microsoft Web site.
2. Double-click the IISLockd.exe file that you downloaded.
The IIS Lockdown installation wizard opens.
n If the “This Server was Already Configured” dialog box opens, click Cancel to exit the installation. The MediaManager server is already running IIS Lockdown. If you want to install IIS Lockdown v2.1, you need to run the original IIS Lockdown tool to unlock the previous settings, then reinstall the MediaManager server application, and then install and run IIS Lockdown v2.1.
3. Click Next to begin the installation.
4. Click Next to accept the license agreement.
5. In the Select Server Template window, select Dynamic Web server (ASP enabled) and click Next.
Changes to Installing MediaManager Server and Client Software
25
26
6. In the URLScan window, deselect “Install URLScan filter: on the server” and click Next.
7. Continue clicking Next in the following windows.
8. Click Finish.
Installing the Browser Player and ProLog Player Software
The Browser player and ProLog Player software installer now includes a window for choosing a country.
Accessing the ReadMe File
The Avid Unity MediaManager Installation and Setup Guide indicates you can access the Avid Unity MediaManager ReadMe file from the last window of the installation shield. You can now access the ReadMe file from the first window of the installation shield.
You can access the most up-to-date ReadMe file from the Avid Customer Support Knowledge Base.
Upgrade Information
27
Upgrade Information
Before installing MediaManager v4.5.15, you must run Database Upgrade from the installation CD. Avid recommends that you back up the entire MediaManager database before you upgrade. For information on backing up the MediaManager database, see the Avid Unity MediaManager Installation and Setup Guide.
Upgrading to v4.5.15 requires that your MediaManager server is at v4.0.x or above. If you are at a prior release, you must first upgrade the MediaManager server to v4.0.x; you can then upgrade to 4.5.15. The clients can upgrade directly from a prior release to v4.5.15.
Before upgrading to MediaManager v4.5.15, use the Add/Remove Program in the Control Panel to remove the Sentinel System Driver v5.39.2. When you install MediaManager v4.5.15 the Sentinel Protection Installer v7.0.0 is installed.
If this is your first time installing the software, see the Avid Unity MediaManager Installation and Setup Guide.
Installing SQL Server 2000 Service Pack 4
If you are upgrading your MediaManager system you must update to the SQL Server 2000 Service Pack 4 (SP4).
The SQL Server memory usage tends to increase up to the available limit if the option for dynamically adjusting the amount of memory used is selected. (This is the default option.) When this option is selected, the memory used by the SQL server tends to increase and this could slow down the system. This could potentially lead to a situation where the SQL Server consumes the amount of virtual memory available. When this happens, the operating system tries to increase the paging file size. If the available free space on the drive on which the paging file exists is not sufficient for increasing the paging file size, a dramatic system slowdown might occur.
Recommendation: SQL Server properties should be changed to limit the amount of memory that gets under the control of SQL Server. Limit the memory allowance for SQL Server to about 70% of the available physical memory.
28
To install the service pack:
1. Copy the SQLService pack 4 files from the Avid Unity MediaManager CD-ROM.
a. Insert the Avid Unity MediaManager CD in your MediaManager CD-ROM drive.
b. Double-click SQLService pack 4 that resides in the Utilities folder on the MediaManager CD-ROM.
c. Select the default location.
2. On the MediaManager system, navigate to the following folder:
C:\SQL2KSP4\x86\setup
3. Double-click setupsql.exe.
4. At the Welcome screen, click Next.
5. Click Yes to accept the license agreement.
6. Click Next in the Instance Name window.
7. Select “The SQL Server system administrator login information (SQL Server Authentication).”
8. Enter your SQL administrator’s password for the sa account.
9. Click Next to continue.
10. In the Start Copying Files window, click Next.
11. If a Shutting Down tasks window opens, click Next.
12. Click Finish.
13. Click OK to the backup your database message.
14. Click Finish to restart your system.
Suggestions for Optimum Performance
This section contains important information about MediaManager performance. Avid recommends that you consider the following when you are using MediaManager:
• You should back up the MediaManager database only when user activity is light because it can take a long time and uses a significant amount of CPU resources.
• You should resync media only when user activity is light because it can take a long time and uses a significant amount of CPU resources.
• SQL Server memory usage tends to increase up to the available limit if the option for dynamically adjusting the amount of memory used is selected. (This is the default option.) When this option is selected, memory used by SQL server tends to increase and this could slow down the system. This could potentially lead to a situation where SQL
Special Notes
29
Server consumes the amount of virtual memory available. When this happens, the operating system tries to increase the paging file size. If the available free space on the drive on which the paging file exists is not sufficient for increasing the paging file size, a dramatic system slowdown might occur.
Recommendation: SQL Server properties should be changed to limit the amount of memory that gets under the control of SQL Server. Limit the memory allowance for SQL Server to about 70% of the available physical memory.
• If you enable MDB Manager, you might experience slower performance if your two largest workspaces together total more than 30,000 files. If you experience slower performance and you have MDB Manager enabled, check your workspaces and clean up or reorganize your workspaces to reduce the file count. If you are experiencing slower than normal performance on the MediaManager system, check the Windows Task Manager for the amount of memory MDB_Agent.exe is using. If memory usage exceeds 1.5 GB, significant activity likely is occurring on MediaManager. You might want to reduce the number of transactions to MediaManager until the MDB Manager is able to catch up with the workload.
Special Notes
International Character Support
MediaManager contains international character support (ICS). ICS allows you to display and input characters in languages other than English.
For the latest information on ICS, search for the International Character Support document on the Avid Knowledge Base. You can access the Knowledge Base from the Avid Web site at www.avid.com.
Documentation Changes
Documentation is organized in the following Help systems and guides:
• Avid Unity MediaManager Help
• Avid Player Help
• Avid Unity MediaManager Administrator’s and User’s Guide
• Avid Unity MediaManager Installation and Setup Guide
Search the Avid Knowledge Base for the most up-to-date version of the Avid Unity MediaManager Installation and Setup Guide, which contains the latest installation information that became available after the documentation was published.
t Go to www.avid.com/onlineSupport.
30
Automating MediaManager Database Backups Using Microsoft SQL
The “Automating MediaManager Database Backups Using Microsoft SQL” section of the Avid Unity MediaManager Administrator’s and User’s Guide was changed after the guide was printed. Replace the complete section with the following information:
The recommended procedure to backup the MediaManager database is to use the MediaManager browser. If you want to automate backups to occur in off hours when usage is low, you can use the SQL Server tools.
c Avid recommends that you have a good understanding of SQL Server tools before using SQL for backup and restore.
Set up a database maintenance plan to automate your backups, using the Microsoft SQL-Enterprise Manager. The SQL Server Agent must be running for an automated backup plan to execute.
Turning on SQL Server Agent
For an automated backup plan to work, the SQL Server Agent must be running. The recommended method is to make the service start automatically in Windows Services.
To start the SQL Server Agent:
1. Right-click My Computer and select Manage.
2. Click Services and Applications.
3. Double-click Services.
4. In the right pane, make sure SQLServerAgent displays the following:
- Status - Started
- Startup Type - Automatic
5. If “Started” is not displayed, right-click the SQLServerAgent and select Start.
6. (Option) To set other options, you can right-click the SQLServerAgent and select Properties.
Documentation Changes
31
Creating a Database Maintenance Plan to Automate Backups
You can use the Microsoft SQL-Enterprise Manager to set up a database maintenance plan to automate your backups.
You should back up your database to an external drive, such as a USB or Firewire drive. This avoids the potential for running out of disk space on internal drives and causing database corruption. This also makes it possible to back up a database and mail the drive to Avid, in case extensive troubleshooting is required.
c When backing up to a disk, make sure the target disk has enough disk space for the backup. Check the size of your database and compare the size to the free space available on the target disk. Running out of disk space during a backup might corrupt the database.
When selecting a backup location, select a backup drive that does not contain the main MediaManager database.
To set the database backup schedule:
1. Click Start and select Programs > Microsoft SQL Server > Enterprise Manager.
The Console Root\Microsoft SQL Servers window opens.
2. In the left pane, click Microsoft SQL Servers > SQL Server Group > (local) (Windows NT) > Management.
3. Right-click Database Maintenance Plan and select New Maintenance Plan.
The Database Maintenance Plan Wizard opens.
4. Click Next.
The Select Databases window opens.
5. Make sure the “These databases” option is selected and select the database you want to back up or create a maintenance plan for.
6. Click Next.
7. You may skip the next window, Update Data Optimization Information.
8. Click Next.
You may also skip the next window, Database Integrity Check.
9. Click Next.
The Specify the Database Backup Plan window opens.
32
10. Select the following options:
a. Back up the database as part of the maintenance plan
b. Verify the integrity of the backup when complete
c. Location to store the backup file: select Disk
c When backing up to a disk, make sure the target disk has enough disk space for the backup. Check the size of your database and compare the size to the free space available on the target disk.
d. Click Change.
The Edit Recurring Jobs Schedule window opens.
e. Enter the values for your automated backup.
n Make sure the Enable schedule option is set.
f. Click OK to return to the Specify Database Backup Plan window.
g. Click Next.
The Specify Backup Disk Directory window opens.
11. Select the appropriate drive letter and directory.
Make sure the backup file extension is entered as BAK and decide how long you want to keep backups by selecting and entering values in "Remove Files Older Than." Remember, available disk space is a consideration.
12. You may skip the next two windows: “Specify the Transaction Log Backup Plan” and “Reports to Generate.”
13. In the Maintenance Plan History window, check both boxes in the local server pane and limit rows in the table to 1000.
14. Click Next.
The Wizard window opens again.
15. In the Completing the Database Maintenance Plan Wizard window, select a name for your plan and verify the information in the pane below it.
16. Click Finish.
If the SQL Server Agent is not running, a message indicates you must turn it on before the scheduled maintenance. It is recommended to keep the SQL Server Agent running at all times. See “Turning on SQL Server Agent” on page 30.
Documentation Changes
33
Finding Shared Clips and Unshared Clips in a Project
You can list the clips in a project that are shared by other projects. The list of shared clips includes shared clips that originate in the selected project and clips that originate from other projects that are used in the selected project. Identifying the clips that are shared with other projects assists you when deleting items from a project. You can delete media files depending on the MediaManager delete settings and user permissions. For more information about Delete settings and Delete rules, see “Deleting Media Objects and Media” in the Help.
There is also an unshared command that provides a list of the clips in a project that are not used by any other project.
To identify clips in a project that are shared by other projects:
1. Click Projects in the mode selector.
2. Select a project, and select Show Shared Clips from the shortcut menu. See “Accessing the Shortcut Menus” in the Help.
The results frame lists any clips in the selected project that are used in other projects. It also lists any clips in the selected project the are shared with other projects.
To identify clips in a project that are not shared by other projects:
1. Click Projects in the mode selector.
2. Select a project, and select Show Unshared Clips from the shortcut menu. See “Accessing the Shortcut Menus” in the Help.
The results frame lists all clips in the selected project that are not used by any other projects.
Obtaining Detailed Object Information
The “Obtaining Detailed Object Information” section in the Avid Unity MediaManager Administrator’s and User’s Guide includes a procedure for adding comments to media objects. The names of the buttons on the Clip Information dialog box were changed as follows: the Update button is now the OK button, and the Close button is now the Cancel button.
The procedure should read as follows:
To add comments to media objects:
1. Right-click the media object in the result frame and select About This Item.
The Clip Information dialog box opens.
2. Type your comments in the Comments text box.
34
3. Do one of the following:
t Click OK to save your comments and close the dialog box.
t Click Cancel to close the dialog box without saving your comments.
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:
t Go to www.avid.com/onlineSupport.
Fixed in v4.5.15• Restored clips sometimes do not come online with the first attempt. This has been fixed.
• After a resync .aaf and .omf files appear in the System32 folder. This has been fixed.
Fixed in v4.5.14• Can not delete (old) empty project or full project from left hand part of Microsoft
Internet Explorer on Avid Unity ISIS. This has been fixed.
• New PMR tool works only with Avid MediaFiles folder. This has been fixed.
• Regular user cannot delete from private project from MediaManager. This has been fixed.
• Can't delete more than 490+ clips at a time from MediaManager when SQL Database becomes too large. This has been fixed.
• Clean install of MediaManager fails to do the desktop check-in function. This has been fixed.
• MediaManager v4.5.10 - Loses connection to media with 3rd party integration. This has been fixed.
• Clips are restoring with no names in MediaManager. This has been fixed.
• 'MM client push checkout error' while checking out certain clips from MediaManager. This has been fixed.
Fixed in v4.5.13
35
Fixed in v4.5.13• TransferManager transfers fail in a clean install environment. This has been fixed.
• Resync sometimes changes the creation date of the resulting clips. This has been fixed.
• Send to Playback from Browser Player contributes to memory loss on MediaManager server for Inet. This has been fixed.
• Avid Prolog Player generates invalid sub clips -- intermittent problem. This has been fixed.
• Resync does not check-in / find pre-computes. This has been fixed.
• Delay initializing editor application or opening video in Browser Player when TransferManager is unavailable. This has been fixed.
• File size in MediaManager is incorrect after check in. This has been fixed.
Fixed in v4.5.10• Cannot check in one or more files when using P2 clips. This has been fixed.
• MediaManager handle count for inetinfo.exe goes up resulting in rebooting the system to fix the problem. This has been fixed.
• Doing numerous check-in/checkout to and from MediaManager causes memory leaks in MediaManager. This has been fixed.
• OMF MediaManager log shows every event with ERROR: : NumberFormatException: This has been fixed.
• MediaManager is not showing the right values for file sizes while using extended searches. This has been fixed.
• MediaManager database restore timeouts before completion when restoring 20GB database. This has been fixed.
36
Fixed in v4.5.8• Error dragging clip from MediaManager to editor bin if clips were added to
MediaManager by desktop check in. This has been fixed.
• Profile DHM does not work with standalone TransferManager and 7AAA Dongles. This has been fixed.
• Tape name is not maintained in the workgroup components. This has been fixed.
• MediaManager v4.5.7 Database Updater fails. This has been fixed.
• Unable to check in complex sequences to MediaManager. This has been fixed.
• C++ runtime errors on inetinfo.exe. This has been fixed.
Fixed in v4.5.7• SGL reports issues archiving subclip’s to Flashnet server. This has been fixed.
• Avid Unity ISIS storage under heavy load causing latencies which generate pixel salad flash frames in v2.5.6 ProLog player. This has been fixed.
• MediaManager deletion "based on WS rights" does not allow to delete MediaFiles only from bin. This has been fixed.
• Deleting a Select List immediately after performing an Extended Search causes Internet Explorer to lockup. This has been fixed.
• Unified Search from MediaManager to Nearchive returns all items using simple search criteria. This has been fixed.
• DET - Sequence metadata is not being checked into MediaManager after a Restore from Flashnet. This has been fixed.
Fixed in v4.5.6• Subclips when part of a sequence, are not getting recognized by MediaManager after a
workgroup to workgroup transfer. This has been fixed.
• Unable to add a locator on an In or Out mark when creating a subclip and a locator at the same time using the Avid Prolog Player. This has been fixed.
• Sequences that contains master clips with names containing special characters like ‘/’ do not check in correctly at the destination workgroup while doing a Workgroup to Workgroup transfer. This has been fixed.
• JFIF JPEG images do not load on Avid Prolog Player. This has been fixed.
• Avid Player burn-in text is in the middle of the screen despite MediaManager configuration settings. This has been fixed.
Limitations
37
Limitations
➤ Precomputes to contribute to a sequence's online status in MediaManager.Resynced clips sometimes come back with Project and bin associations.
➤ Some Workgroup components which install Javasoft, might give an error during install if the installer is run from a network location or from the desktop of the local system (due to the file location path being too long). The error is ‘cannot install Javasoft’.
Workaround: Copy the installer to the root of the C drive and then run it from there. This is not consistently reproducible.
➤ When you use Batch Capture or Batch Import with a sequence containing subclips or group clips, you need to manually check into MediaManager the subclips and group clips after the media is online. This prevents the subclips and group clips from being offline when checked out by another system.
➤ If you start an Avid editing application without first mounting the shared volumes, any bins created in a shared project do not contain the Lock. This is not a supported workflow.
Workaround: Always mount shared volumes before opening the Avid editing application.
➤ Avid iNEWS Instinct cannot use sequences as source.
➤ In MediaManager, when listing the contents of a workspace’s incoming folder, the bottom of the Results frame refers to the workspace name as Catalog instead of Workspace.
➤ When you are checking out a sequence that contains a Euro currency symbol in the title, the Avid editing application checks in the symbol as a Generic currency symbol.
Workaround: To use the Euro currency symbol in a sequence title, hold down the Alt key and type 0128.
➤ In a bin, you cannot change the font size or style of shared objects that contain ICS characters in their names (such as Simplified Chinese). If you try to change the font or style of these object names, and then check out more objects that contain ICS characters into the bin, the names contain incorrect characters. However, in MediaManager, the correct characters remain in the original object names.
38
➤ In an OMF workgroup, you cannot transfer an item to be conformed through MediaManager from an Avid Adrenaline editing system to an Avid DS Nitris editing system. This limitation occurs because the Avid DS Nitris cannot check out OMF media, and the Avid Adrenaline editing system does not support the “Check into MediaManager as AAF” function in an OMF workgroup.
Workaround: Export the sequence or clip as AAF or AFE to a shared workspace and then conform it in the Avid DS Nitris editing system.
➤ MXF workgroup only - If you import clips into a Media Composer Adrenaline bin that were created with an Avid DS Nitris editing system, and then you perform a relink, the clips do not relink to the media on the Avid Unity workspace. The reason relink does not work in this case is because MediaManager now controls relinking of media files instead of using the MDB Manager, and since the Avid DS Nitris does not check media into MediaManager the clips are not relinked to the media.
➤ Sequences with rendered Timewarp effects that are checked in and then checked out of MediaManager might have the effects appear as unrendered.
Workaround: Check the sequence out of MediaManager using another Avid editing system. The Timewarp effects remain rendered.
➤ Avid doesn’t recommend using shared projects and shared bins in a managed workgroup. In a managed workgroup, the MediaManager provides safer and easier ways of sharing and managing media and metadata. If you move or copy items from a locked shared bin to another bin, you might get a check-in error message. The bin data is not lost, but the check in that accompanies the appearance of the item in the destination bin fails. The next check in, whether manual or automatic, succeeds.
➤ If the name of a shared bin is changed that contains a clip referenced by a sequence in another bin, when you open the sequence and perform a match frame and find bins, you might see the error message, “Bin binname is not in the project” or “Exception: BIN_NOT _FOUND”. This error message might also appear without changing the bin name.
Workaround: To edit this clip, use the Show Reference clips in the Set Bin Display dialog box of the bin containing the sequence.
➤ Consolidated sequences checked into MediaManager might inaccurately display the status as offline (blue) after you delete another consolidated sequence’s media.
Workaround: Manually update the status on the sequence. It becomes online (green).
Limitations
39
➤ When sending a job to ProEncode that contain non-English characters, the job might fail.
Workaround: Change the name to all English characters and resubmit the job.
➤ If you use MediaManager to delete files that are being used by an editor, MediaManager does not send an automatic message to the editor to indicate that the files are no longer available. The editor might still list the files as online. This is true even if you execute a File > Refresh Media Database command. The editor shows the files in the bin as available, but when you attempt to play the clips, the system displays a media offline message.
The editor refers to the TransferManager media directory’s PMR database files to determine if files are available. TransferManager does not update its database to reflect MediaManager deletions until TransferManager restarts.
Workaround: Stop TransferManager and delete the PMR and MDB database files in the TransferManager media directory. Then restart TransferManager. Close and then reopen the bin on the editor and it sees the updated TransferManager database.
➤ When deleting media files, if you select Show Media Relatives and then use the Browser’s Select All Clips button to select the clip you want to delete, the Delete key does not work.
Workaround: After selecting the clips you want to delete, right-click and select Delete from the menu.
➤ If you delete a clip and then transfer the same clip from Nearchive before the PMR is updated, the clip indicates it is offline when an Avid editing application checks it out. After the TransferManager updates the PMR, the clip comes online.
➤ MediaManager does not recognize MetaSync™ tracks in a sequence. If a sequence that contains MetaSync tracks is checked in, the sequence is unusable.
Workaround: When checking in a sequence that contains MetaSync tracks, remove the MetaSync tracks, and then check in the sequence.
➤ You might notice incorrect results when performing an extended search using In-Out attributes. MediaManager requires all fields to have a value when searching for timecode. For example, to perform an extended search for a timecode, the In-Out value needs 00:00:01:20. If the Avid editing application used 1:20, the extended search returns incorrect results.
40
➤ When you select Category as an Attribute in the Extended Search window, the values listed are not updated when new categories are created.
Workaround: To update the list of Categories, refresh the Extended Search window by pressing F5.
➤ If you close the Extended Search window while a large Value list is generating, you might get a runtime error message.
➤ When checking out or checking in a large number of clips from or to MediaManager with a MediaManager client on a Macintosh OS X system, you might receive an error message or experience slow response times on all MediaManager clients, on both Macintosh and Microsoft Windows systems.
Workaround: Retry the check in or check out.
➤ After performing a saved search and then switching to Production mode, the search results might not appear in the lower portion of the split screen.
Workaround: Enter split screen mode before performing a saved search and switching to Production mode.
➤ Locators might not display on a clip that is checked out of MediaManager if the locators were added by another MediaManager client.
Workaround: Delete the clip from the bin, and then import the clip again from MediaManager.
➤ If a saved search includes searching a remote server, you cannot remove the remote server from the search. After a remote server is selected, all saved searches you run search the remote server, regardless of whether the saved search includes remote servers.
Workaround: Perform a Simple Search or Extended Search without selecting a remote server.
➤ When using Extended Search, the value list might display Incoming folders for workspaces that were previously deleted. The deleted Incoming folders remain even after performing an Update Users/Workspaces.
Limitations
41
➤ When performing a Unified Search on a remote server that is configured by its IP address instead of its host name, you need to set the Internet Properties on the system logging into MediaManager to allow access to the remote server. The following error message displays when the remote server’s IP address is not allowed access: “Session has timed out on Remote MediaManager - Press Search button to re-login.”
To allow access of a remote server that is configured by its IP address:
1. From the Internet Explorer tool bar, click Tools > Internet Options.
2. Click the Privacy tab.
3. Click Edit in the Web Sites pane.
4. In the Address of Web site text box, type the IP address of the remote server you want to search.
5. Click Allow.
The IP address of the remote server is added to the Managed Web sites list.
➤ Check in times into Media Manager from an Avid editing client vary depending on how many bins or objects in the bins are being checked in. For example, when you are checking in all bins in a project or checking in several large bins that contain numerous objects, there might be a delay of as much as 10 minutes depending on the size of the bins being checked in.
➤ (Macintosh only) In browser-to-browser transfers, the Create New Catalog icon is missing from the Workgroup Transfer dialog box.
Workaround: Create new catalogs before performing a browser-to-browser transfer.
➤ After performing a Unified Search on a remote MediaManager server across WAN, the transfer moves from a pending state to a running state but does not complete. The progress bar does not indicate the transfer is in process.
➤ When copying clips from another project’s bin (that were not checked in to MediaManager) into a current project’s bin, error messages display even though the clips check in as expected.
➤ Make sure you close the MediaManager window by clicking Logout to release the license after using Unified Search. If you close the MediaManager window using the close box the license remains in use.
➤ When you are creating folders, the description text field is not saved.
42
➤ You can create a maximum of four subfolders in Catalog mode. However, an error message might display when you try to create a fourth subfolder.
Workaround: Make sure the third folder is open (folder displays an arrow) before you right-click the folder name to create the fourth folder.
➤ When working with a MediaManager client on a Macintosh OS X system and the host file does not have uppercase MediaManager server names, you cannot drag a clip out of a bin. The error message “Exception: Can’t login, server not running” is displayed.
Workaround: You must enter the MediaManager server name in uppercase characters in the MMHost setting dialog box. The host file of the Macintosh system must have the IP address resolved to the name of the MediaManager server.
To add the MediaManager’s IP address to the host file:
1. Double-click Terminal in the Utilities folder.
The user currently logged into the Macintosh is displayed.
2. Type the following into the Terminal window exactly as it appears, including the spaces:
sudo /Applications/TextEdit.app/Contents/MacOS/TextEdit /etc/hosts
You need an administrator password to edit the file.
The host file opens in the TextEdit window.
3. Type the IP address and the host name of the MediaManager server. For example:
192.168.0.10 avid-mediamanager
192.168.0.10 AVID-MEDIAMANAGER
4. Save the host file.
5. Close the TextEdit window and the Terminal window.
➤ The duration field in MediaManager displays non-drop-frame timecode regardless of the timecode type. Durations are accurate despite the incorrect timecode type displayed for drop-frame clips and sequences.
➤ When you are working with an Avid editing client on a Macintosh system, do not drag clips from MediaManager to bins while the editor is playing a sequence.
➤ When you save a search criterion that includes searching remote workgroups, you cannot change the remote workgroups listed in the search criterion.
Workaround: Delete the search and re-create the search criterion using the new remote workgroups.
Limitations
43
➤ Do not rename an Avid Unity volume during the middle of a capturing or recording session. The files that were initially checked in before the name change might not be accessible.
➤ If you are working on currently ingesting media in Media Composer and perform a “Media Update,” you overwrite any locators (or breadcrumbs) you just created.
The MediaManager copy of the metadata replaces the current bin data, which causes the overwrite. This also causes the subclips, created on a TWR media, to be overwritten or erased. These subclips then cannot be played on MediaManager Select.
➤ If the default project access control for MediaManager is set to Private and sequences are created in Media Browse and checked in to MediaManager, only an administrator can see the project or sequences. A regular user cannot see the sequence in MediaManager.
Workaround: To fix the problem, in the System Setup window change the default project access control to Public.
➤ When there is a discrepancy between the Avid Unity and the MediaManager passwords, the login options might differ. For example, you could have Select List Creator privileges when logging in with the MediaManager password but not with the Avid Unity password, or media not playing correctly or suddenly going offline.
Workaround: Always create Avid Unity user accounts with the same names and passwords as MediaManager user accounts.
➤ If you try to adjust the audio levels of a chunked media clip still being recorded, you might receive the following error message:
“Audio:PMM_INSUFFICIENT MEDIA () Player version of duration is longer
than actual.”
n If you try to adjust the audio levels, you will not be able to play the clip in MediaManager Select.
Workaround: Wait for the entire clip to finish recording before you adjust the audio levels.
➤ Checking out a Desktop check-in file creates a clip with an internal file name and incomplete clip information.
You might see this error if you do the following:
1. Check in a file from your desktop.
2. From search results, select the desktop check-in file and drag it to a bin on your editing system.
44
3. From MediaManager, query clips from the last 10 minutes. You might see a clip with a name such as F082600.8345. This is part of the desktop check-in clip.
4. Save the bin in your editing system. This forces a check in to MediaManager.
5. In MediaManager, search for the desktop check-in clip. The clip name is correct, but some information such as Creation date and Duration is missing. If you try to select this clip and drag it to the bin, an error message appears: “Asset ID not found.”
Workaround: From your editing application, manually check in the clip. The check-in information is rewritten, and the erroneous information goes away.
➤ Changing a file name extension might cause problems with desktop check in and check out.
Workaround: When performing a desktop check in, do not change the file name extension.
➤ After you upgrade from MediaManager v3.7 to MediaManager v4.0, the Show Tracks Details for master clips allows only one option to delete all three tracks. There are no separate check boxes to delete them individually.
Workaround: Check in the clip again; the option for the separate tracks appears.
➤ Show Relatives does not display motion effects.
➤ When using Internet Explorer on a Macintosh system, you cannot save certain files (for example, .fs and .wav) to the desktop just by clicking the link.
Workaround: To save the file, press and hold the Option key and click the file link.
➤ In Shared Projects, a bin copy made from a locked bin does not automatically check in to MediaManager. When you have a locked bin to which you make changes, you must save it as a copy to keep the changes. When you do, the copy of the bin is not automatically checked in to MediaManager.
n Avid recommends you do not use shared bins when using MediaManager.
Workaround: Select the bin, and then select File > Check In Open Bins in Project. This checks in the bin and its media to MediaManager.
➤ If Sync Media is running on a client and then another Macintosh client starts the Sync Media process, the Macintosh client receives a dialog box that says it is connecting to the server. This dialog box must be closed manually.
Limitations
45
➤ Occasionally, you might need to check that MediaDataBaseService is running properly.
To check whether MediaDataBaseService is running properly:
1. On drive C, open the MDBLogDirectory folder.
2. Check the dates of the log files. If they have not been updated after known activity, then the MediaDataBaseService is probably not working properly. You can verify this by opening the Windows Task Manager. If the MDB Agent is present but not using any CPU cycles, it is probably frozen.
3. Double-click the MDB_Stop application. (This shortcut resides on your desktop after installation of MediaManager software.)
4. Open the Task Manager, and verify that the MDB_Agent has disappeared from the list. This might take a few minutes.
5. Once MDB_Agent has disappeared, double-click the MDB_Start application. (This shortcut also resides on your desktop after installation of MediaManager software.)
6. Return to the Windows Task Manager, and verify that the MDB Agent is now using cycles. (Anything from 5% to 99% is normal.)
To restart the MDB Agent after an “Exception” error:
1. Close the Exception dialog box.
2. Double-click the MDB_Start application. (This shortcut resides on your desktop after installation of MediaManager software.)
3. Return to the Windows Task Manager, and verify that the MDB Agent is now using cycles. (Anything from 5% to 99% is normal.)
➤ Illegal characters on Avid Unity can cause errors in the Project window. This error occurs if you try to open a project from the Select User and Project dialog box, and the directory containing the project contains a file created on a Macintosh system and named with Windows illegal characters (\ / : * ? " < > |). Windows can see the file but cannot open the file.
Workaround: Access a Macintosh system on the network, and rename the file.
➤ Attempting to check in clips containing Sound Designer II™ audio to MediaManager causes an error: CANT_EXPORT_MEDIA_AS_SD2. This is not due to a problem with MediaManager; it occurs because the Sound Designer II audio format is not supported in either OMF2 or OMM export on Windows clients.
Workaround: Before attempting to check in the clips to MediaManager, export clips with Sound Designer II audio to a format that is fully supported on Windows clients.
46
➤ On initial MediaManager startup, the MediaDataBaseService needs to scan the media files on the Avid Unity system. This can be time consuming. On subsequent startups, scanning every file is not necessary, and, therefore, startup will not be time consuming.
➤ In a shared workgroup environment, you can move a locked bin within a Project window shared between projects. If one client locks a bin and shares that project on Avid Unity, a second client can move that locked bin’s location within the Project window; this changes the directory location for the bin on the hard drive.
n Avid recommends you do not use shared projects when using MediaManager.
➤ If you quit MediaManager but still have a function dialog box open, the next time you open MediaManager and try to access that function dialog box, it does not open. It is in the taskbar.
Workaround: Open the dialog box from the taskbar. Close the dialog box, and then access that function dialog box again. It should open properly.
➤ On Mac OSX IE 5.2, the description text of a saved backup database does not display in the description box when selected. This feature is enabled in the PC version of the browser.
➤ On Mac OSX IE 5.2, selecting an invalid database to restore does not post a message indicating that the selected database is invalid and that it does not match the current version of Media Manager. This feature is enabled in the PC version of the browser.
➤ The Context window of a clip in Search Result window creates an empty white bar at the bottom of the window. Instead of 6 lines, there are 7 in the window, which creates an empty white bar at the bottom of the window. Similar space is displayed in Clip Relatives view.
➤ Do not use special characters in MediaManager server names.
Workaround: Use only standard characters for MediaManager server names. Standard characters include letters (A_Z, a-z), digits (0-9), and hyphens (-).
➤ When MediaManager contains more than 2000 catalogs, some dialog boxes (for example, Extended Search) take a long time to open.
Workaround: Avid supports only 2000 catalogs on Macintosh systems.
Limitations
47
➤ All clips now contain a unique identifier number, displayed in the “About this item” window. You may be confused the first time you see it, but this number can be useful when dealing with customer support.
1. Open MediaManager, and select a clip.
2. Right-click, and select About this Item.
The Clip Information window opens, and the title bar contains a unique identifier number; for example, Clip 42.1041357729.43290 (16).
➤ When you perform a search based on “last 10 minutes,” the search is based on check-in time. The results display the creation time, so it might appear that the search is returning old material.
Workaround: Searches for “last 10 minutes” are based on check-in times, not creation times. To search for Creation Date, use the Extended search feature.
➤ Media Composer users can, through MediaManager, delete files created by a Media Browse server. These deleted files might display as Disk File Not Found in Media Composer. This is a limitation of the Persistent Media Record (PMR) file in MediaBrowse, which does not check for files deleted by editor clients.
Workaround: Delete the Media Browse PMR file and restart TransferManager; this forces the PMR to rebuild. An administrator can delete the PMR file using OS filesystem tools, from either the command line or Windows Explorer. PMR files have a .pmr extension and are located in the media directory of each workstation or server.
➤ ICS characters are not translated to the Avid Player. The burn-in field in MediaManager does not support French and Chinese characters.
➤ Desktop Checkin files do not show creation dates. For a Desktop Checked-in file, the creation date is not available in search, catalog window, or when viewing “About this item” in the context menu.
➤ Problems with the MediaManager browser client on Macintosh systems:
• Macintosh browsers display check-in times as one hour earlier than Windows 2000 browsers.
• Clicking Refresh on the Macintosh browser does not display items checked in during the last 10 minutes.
• Two saved searches are created when regular users save one search.
• Initial display of Projects and Bins sometimes appears on a single line.
• ProLog Player is not supported with MediaManager on a Macintosh system.
48
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.
For more information regarding Avid’s service offerings, visit www.avid.com/onlineSupport 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.
Technical Support Information
49
Copyright and DisclaimerProduct 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.
Avid products or portions thereof are protected by one or more of the following United States Patents: 4,746,994; 4,970,663; 5,045,940; 5,267,351; 5,309,528; 5,355,450; 5,396,594; 5,440,348; 5,452,378; 5,467,288; 5,513,375; 5,528,310; 5,557,423; 5,577,190; 5,584,006; 5,640,601; 5,644,364; 5,654,737; 5,715,018; 5,724,605; 5,726,717; 5,729,673; 5,745,637; 5,752,029; 5,754,851; 5,799,150; 5,812,216; 5,828,678; 5,842,014; 5,852,435; 5,987,501; 6,061,758; 6,223,211; 6,301,105; 6,532,043; 6,546,190; 6,636,869; 6,747,705, 6,763,523; 6,813,622. Other patents are pending.
This document is protected under copyright law. An authorized licensee of Avid Unity MediaManager may reproduce this publication for the licensee’s own use in learning how to use the software. This document may not be reproduced or distributed, in whole or in part, for commercial purposes, such as selling copies of this document or providing support or educational services to others. This document is supplied as a guide for Avid Unity MediaManager. Reasonable care has been taken in preparing the information it contains. However, this document may contain omissions, technical inaccuracies, or typographical errors. Avid Technology, Inc. does not accept responsibility of any kind for customers’ losses due to the use of this document. Product specifications are subject to change without notice.
Copyright © 2007 Avid Technology, Inc. and its licensors. All rights reserved.
Attn. Government User(s). Restricted Rights LegendU.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.
Trademarks888 I/O, Adrenaline, AirPlay, AirSPACE, AirSPACE HD, AirSpeed, AniMatte, AudioSuite, AudioVision, AutoSync, Avid, Avid DNA, Avid DNxcel, Avid DNxHD, AVIDdrive, AVIDdrive Towers, Avid Mojo, AvidNet, AvidNetwork, AVIDstripe, Avid Unity, Avid Unity ISIS, Avid Xpress, AVoption, AVX, CamCutter, ChromaCurve, ChromaWheel, DAE, D-Fi, D-fx, DigiDelivery, Digidesign, Digidesign Audio Engine, Digidesign Intelligent Noise Reduction, DigiDrive, Digital Nonlinear Accelerator, DigiTranslator, DINR, DNxchange, D-Verb, Equinox, ExpertRender, FieldPak, Film Composer, FilmScribe, FluidMotion, HIIP, HyperSPACE, HyperSPACE HDCAM, IllusionFX, Image Independence, Intraframe, iS9, iS18, iS23, iS36, LaunchPad, Lo-Fi, Magic Mask, make manage move | media, Marquee, Matador, Maxim, MCXpress, Media Composer, MediaDock, MediaDock Shuttle, Media Fusion, Media Illusion, MediaLog, Media Reader, Media Recorder, MEDIArray, MediaShare, Meridien, MetaSync, MissionControl, NaturalMatch, Nearchive, NetReview, NewsCutter, Nitris, OMF, OMF Interchange, OMM, Open Media Framework, Open Media Management, ProEncode, Pro Tools, QuietDrive, Recti-Fi, RetroLoop, rS9, rS18, Sci-Fi, Softimage, Sound Designer II, SPACE, SPACEShift, SpectraGraph, SpectraMatte, Symphony, Trilligent, UnityRAID, Vari-Fi, Video Slave Driver, VideoSPACE, and Xdeck are either registered trademarks or trademarks of Avid Technology, Inc. in the United States and/or other countries.
iNEWS, iNEWS ControlAir, and Media Browse are trademarks of iNews, LLC.
Macintosh is a trademark of Apple Computer, Inc., registered in the U.S. and other countries. Microsoft and Windows are either registered trademarks or trademarks of Microsoft Corporation in the United States and/or other countries. All other trademarks contained herein are the property of their respective owners.
Avid Unity MediaManager v4.5.15 ReadMe • 0130-06355-01 Rev. H • September 2007 • 09/12/07 17:49
m a k e m a n a g e m ove | m e d i a ™ Avid ®50