Version 2.4.1 ReadMeresources.avid.com/SupportFiles/attach/ICS/MCS_V2... · 2/4/2016 · As of MediaCentral UX V2.3, the following browsers are no longer tested or supported: †

Avid® MediaCentral Platform Services Version 2.4.1 ReadMe

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 at www.avid.com/support for the most up-to-date ReadMe file, which contains the latest information that might have become available after the documentation was published.

Revision History

Contents

About MediaCentral Platform Services Version 2.4.1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2

Date Revised Changes Made

August 26, 2016 Update to JP-2525. For details, see “Fixed in Version 2.4.1” on page 38.

February 4, 2016 Updated and expanded information related to the RabbitMQ cluster.

January 12, 2016 Added a note about a fixed limitation for Media Distribute v2.4.2. See “Fixed in Version 2.4.1” on page 38.

November 10, 2015 Added steps to the cluster upgrade process for the RabbitMQ cluster.

November 6, 2015 Added a limitation: “User Management” on page 54.

Added Limitation regarding 2.3.0 upgrades on Dell servers. See RE-1065 in “Limitations and Defects Found in Version 2.4.0” on page 54 for details.

October 29, 2015 MediaCentral 2.4.1 Update

October 2, 2015 Additional Story bug descriptions added to Fixed in Version 2.4.0.

September 24, 2015 MediaCentral 2.4.0 First Publication

http://www.avid.com/support

2

Compatibility Notes and Issues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3

Security Updates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

Installing MediaCentral Platform Services Version 2.4.0 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14

Installing MediaCentral Platform Services Version 2.4.1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18

Installing the Media | Distribute Update . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29

New Features in MediaCentral | UX Version 2.4.0. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29

Fixed in Version 2.4.1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38

Fixed in Version 2.4.0 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40

Additional Documentation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45

Limitations and Defects Found in Version 2.4.1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53

Limitations and Defects Found in Version 2.4.0 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54

Limitations and Defects Found in Earlier Versions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56

Legal Notices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73

About MediaCentral Platform Services Version 2.4.1

MediaCentral Platform Services (MCS) v2.4.1 is a patch release that provides bug fixes. It requires prior installation of MCS v2.4.0. This ReadMe contains all information contained in the previously published MCS v2.4.0 ReadMe.

For more information, see the following topics:

• “Installing MediaCentral Platform Services Version 2.4.0” on page 14

• “Installing MediaCentral Platform Services Version 2.4.1” on page 18

• “Fixed in Version 2.4.1” on page 38

Documentation

For the latest information on MediaCentral Platform Services, see the 2.4.x documentation page of the Avid Knowledge Base:

http://avid.force.com/pkb/articles/en_US/readme/Avid-MediaCentral-Version-2-4-x-Documentation



3

Localized User Interface and Documentation

The MediaCentral UX user interface and Help are available in the following languages:

• English

• French

• German

• Italian

• Japanese

• Korean

• Simplified Chinese

• Spanish

• Arabic (user interface only)

• Turkish (user interface only)

The user selects the language for the user interface in the MediaCentral UX User Settings.

Translated documentation is located here:

http://avid.force.com/pkb/articles/en_US/readme/Avid-MediaCentral-Version-2-4-Documentation-Translated

Compatibility Notes and Issues

This section contains compatibility information for MediaCentral Platform Services (MCS) and its related products.

System Version Numbers

Use the following procedure to determine the version and build numbers of the installed MediaCentral Platform Services. The following procedure lists the build numbers for version 2.4.1.

To determine the version and build numbers for MediaCentral Platform Services:

1. Connect to the MediaCentral Platform Services server console as the root user.

2. Type the following command:

ics_version



4

3. Press Enter.

Version and build numbers are returned as follows:

UMS Version: 2.4.1.0-1.noarchICPS Version: 2.4.1.0-10373416AVID.x86_64ICPS manager Version: 2.4.21-1.noarchACS Version: 2.4.0-20150911.1537.x86_64System ID: xxxxxxxxxxxICS installer: 2.4.1 (Build 2)

n The System ID is an 11-digit number used in support calls, entered during system configuration.

To determine the version of the MAM Connector:

1. Connect to the MediaCentral Platform Services server console as the root user.

2. Type the following command:

rpm -qa | grep mam

3. Press Enter.

If installed, the version of the MAM Connector is returned. MAM Connector v2.4 will return:

avid-interplay-central-mam-2.4.0.v20150921_152258-1.noarch.rpm

iNEWS Client Version

MediaCentral includes an iNEWS client module with a version number that needs to be entered in the iNEWS SYSTEM.CLIENT.VERSIONS story. This version number is 2.4.1.2 for MediaCentral v2.4.1.

Compatibility: MediaCentral Platform

For version information on this and previous releases, see the “Compatibility Matrix: Interplay Production and MediaCentral” on the Avid Knowledge Base:

http://avid.force.com/pkb/articles/en_US/compatibility/Avid-Video-Compatibility-Charts


5

Operating Systems for Servers

The following table lists minimum supported versions for MediaCentral Platform servers.

Systems and Storage

The following table lists considerations when connecting to ISIS shared storage.

n The ISIS client is automatically installed with the MCS software. Do not update the ISIS client on the MediaCentral Platform server unless otherwise documented and approved by Avid.

For playback of group clips, a 10 GigE connection between the MCS server and the ISIS shared-storage system is required. For additional information on calculating bandwidth requirements, see the Avid MediaCentral Hardware Guide and the appropriate ISIS Performance Guide.

Server Version

MediaCentral Platform Red Hat Enterprise Linux (RHEL) 6.5 (64-bit) plus approved security patches. See “Security Updates” on page 13.

GlusterFS 3.6.4 (Required if file caching is used and you set up a cluster). See “Obtaining Gluster” on page 15.

MediaCentral Distribution Service (MCDS)

Microsoft Windows 7 64 bit or Windows Server 2012 64 bit

For additional information on MCDS, including installation best practices, see the MediaCentral Platform Services Installation and Configuration Guide.

Product Version

ISIS | 7500, ISIS | 7000 (System Director) • Mirrored workspace supported for all media formats

• RAID6 workspace supported for media formats up to 50 Mbps

• ISS 1000 (Gen 1 HW) GigE support only

• ISS 2000 (Gen 2 HW) GigE and 10GigE support

ISIS | 5500, ISIS | 5000 (System Director) • GigE and 10GigE support

ISIS | 2500, ISIS | 2000 (System Director) • GigE and 10GigE support

• Only supports real-time playback of proxy material that is 3Mb/s or less.

6

Browsers for MediaCentral | UX

MediaCentral Platform provides an Adobe® Flash® swf file, which delivers video player functionality that MediaCentral UX and Interplay MAM embed dynamically in their respective web-based interfaces. Adobe Flash must be installed on the client machine.

n If you are accessing MediaCentral UX through Google Chrome, an Adobe Flash plug-in is automatically installed and updated with Chrome. No separate installation is required.

As of MediaCentral UX V2.3, the following browsers are no longer tested or supported:

• All versions of Internet Explorer

• Safari 6 for Mac OS X 10.7 (Lion), Mac OS X 10.8 (Mountain Lion)

The minimum screen resolution for MediaCentral UX is 1280 x 1024 pixels. If the size of your browser window is smaller than 1280 x 1024, some UI elements might not be displayed.

Using browser controls to change the size of the contents of the MediaCentral UX window (for example, Ctrl + to enlarge the window and Ctrl – to reduce the window) is not supported. Using these controls does not work consistently and slows down the application.

Tablets for MediaCentral | UX Mobile Application

Version 2.4 of the MediaCentral UX Mobile application is not available for iOS or Android. Version 2.2 of the Mobile app can be used for iOS devices and version 2.3.1 can be used for Android devices to connect to 2.4 MCS servers.

iOS 8.x tablets include the iPad 2, iPad 3, iPad 4, iPad Air, iPad Mini, and iPad Mini 2.

Android tablets are supported in compatibility mode.

Phones for MediaCentral | UX Mobile Application

Version 2.4 of the MediaCentral UX Mobile application is not available for iOS or Android. Version 2.2 of the Mobile app can be used for iOS devices and version 2.3.1 can be used for Android devices to connect to 2.4 MCS servers.

iOS 8.x phones include the iPhone 4S, iPhone 5, iPhone 5C, iPhone 5S, iPhone 6, iPhone 6+. The iPod® 5 Touch is also supported.

n Support for the iPhone 6+ is in normal mode only (the display scales to the iPhone screen resolution). The MediaCentral UX mobile app does not yet support native resolution layouts.

n The iPhone 3GS, iPhone 4, iPhone 4S, iPad 2, iPad 3, and iPod 4 using iOS6.x are supported only by the legacy Avid Central client.

7

Avid has tested and supports the MediaCentral UX mobile app only on the following smart phones:

• Nexus 5

• Samsung Galaxy S4 mini

• Samsung Galaxy S5

To log in to your MediaCentral server from a remote location, you might need to use a virtual private network (VPN) app on your iOS or Android device. Avid tested the MediaCentral UX mobile apps using Cisco™ AnyConnect® VPN Client.

Avid Interplay Production Data Model Object Types

The following table lists which Interplay Production data model object types are supported for playback.

All rendered and checked-in effects are supported for playback.

Object Type Status

Master clips Supported

Subclips Supported

Freeze-frame clips Supported

Sequences (no effects) Supported

Sequences (dissolves only) Supported

Sequences (precomputes present for unsupported effects) Supported

Sequences (without precomputes for unsupported effects) Unsupported

Nested timelines Unsupported

Audio tracks with unrendered AudioSuite plugins Unsupported

Stereo tracks Unsupported

Group clips Supported†

Matte clips Unsupported

Motion effects Unsupported

Stereoscopic clips Unsupported

Multi-channel audio clips Unsupported

†Subclips created from group clips, group clips composed of subclips, and multigroup clips are currently not supported.

8

Media Formats Supported for Playback

The following tables list which media formats are supported for playback through the MediaCentral Playback Service for the following products:

• MediaCentral UX

• Media Composer Cloud

23.97 fps and 24 fps frame rates are supported in 1080i and 1080p formats. They are unsupported in 720p and standard definition (SD) formats.

If a format is described as “Media Composer Cloud Only,” MediaCentral can read and play back this video only at very low stream counts and might drop frames during playback.

DNxHD Format Support

Media Format Support for Playback

Supported with Interplay Production 2.6 and later

DNxHD 1080 36-45 All frame rates

DNxHD 1080 80-85-100 All frame rates



DNxHD 1080 175X-185X-220X All frame rates

DNxHD 720p 40 Not Supported

DNxHD 720p 45-50 25, 29.97 only

DNxHD 720p 60-75 25, 29.97 only

DNxHD 720p 90-110 25, 29.97 only

DNxHD 720p 90X-110X 25, 29.97 only

DNXHD 720p 85-100 50, 59.94 only

DNXHD 720p 120-145 50, 59.94 only

DNXHD 720p 185-220 50, 59.94 only

DNXHD 720p 185X-220X 50, 59.94 only

9

Additional formats supported with the Interplay Production 3.2, Media Composer Cloud 1.2.0, and later

DNxHD 1080p 75-90 50, 59.94 only

DNxHD 1080p 165-200 50, 59.94 only

DNxHD 1080p 240-290 50, 59.94 only

DNxHD 1080p 365-440 50, 59.94 only

DNxHD 1080p 365X-440X 50, 59.94 only

Other Format Support


1:1 8-bit, 10-bit All frame rates

Media Composer Cloud only

Apple ProRes Unsupported

AVC-Intra 50 1080i All frame rates

AVC-Intra 50 720p 50, 59.94 only

AVC-Intra 100 1080i All frame rates

AVC-Intra 100 720p 50, 59.94 only

XAVC Intra 50 1080i 50, 60, 23.98 only

XAVC-Intra 100 1080i 50, 60, 23.98 only

Avid JFIF 2:1, 3:1, 10:1, 20:1 25, 29.97 only

DV 25 411 25, 29.97 only

DV 25 420 25 only

DV 50 25, 29.97 only

DV100 HD 1080i (DVCPro HD) All frame rates

DV100 HD 720p (DVCPro HD) 50, 59.94 only

DNxHD Format Support(Continued)


10

Media Formats Supported for MediaCentral STP

Unless otherwise noted, the following table lists media formats supported for send to playback (STP) operations for MediaCentral UX.

H.263 (MPEG-1 Layer 2 proxy) 25, 29.97 only

H.264 (MPEG-1 Layer 2 proxy) 800 Kbps, 2 Mbps, 3 Mbps

25, 29.97 only

HDV 1080i All frame rates

HDV 720p 50, 59.94 only

JPEG 2000 No support

MPEG (IMX) 30 25, 29.97 only

MPEG (IMX) 40 25, 29.97 only

MPEG (IMX) 50 25, 29.97 only

MPEG-2 Long GOP 25, 29.97 only

RGB No support

XDCAM-HD 17.5/35/50 Mbps 1080i All frame rates

XDCAM-HD 50 Mbps 1080p All frame rates

XDCAM-HD 17.5/35/50 Mbps 720p 50, 59.94 only

XDCAM-EX 35 Mbps 1080i All frame rates

XDCAM-EX 35 Mbps 720p 50, 59.94 only

Other Format Support(Continued)


Media Format Frame Rate Notes

AVC-Intra 50 1080i 50, 59.94

AVC-Intra 50 720p 50, 59.94

AVC-Intra 100 1080i 50, 59.94

AVC-Intra 100 720p 50, 59.94

11

XAVC-Intra 50 1080i 50, 60 Not supported

XAVC-Intra 100 1080i 50, 60 Added in MCDS V3.3

DNxHD 1080 115-120-145 23.976, 24, 29.97, 50, 59.94

DNxHD 1080 175-185-220 23.976, 24, 29.97, 50, 59.94

DNxHD 1080 175X-185X-220X 23.976, 24, 29.97, 50, 59.94

DNxHD 720 60-75-145 23.976, 50, 59.94

DNxHD 720 90-110-220 23.976, 50, 59.94

DNxHD 720 90X-110X-220X 23.976, 50, 59.94

DV 25 411 25, 29.97

DV 25 420 25

DV 50 25, 29.97

DV100 HD 1080i (DVCPro HD) 50, 59.94 Added in ICDS V3.0

DV100 HD 720p (DVCPro HD) 50, 59.94 Added in ICDS V3.0

MPEG 30 (IMX) 25, 29.97

MPEG 40 (IMX) 25, 29.97

MPEG 50 (IMX) 25, 29.97

XDCAM-HD 35 Mbps 1080i 50, 59.94 Requires STP Encode

XDCAM-HD 50 Mbps 1080i 50, 59.94 Requires STP Encode

XDCAM-HD 50 Mbps 720p 50, 59.94 Requires STP Encode

XDCAM-EX 35 Mbps 1080i 50, 59.94 Requires STP Encode

XDCAM-EX 35 Mbps 720p 50, 59.94 Requires STP Encode

Media Format Frame Rate Notes

12

Bandwidth Requirements

The following table presents single-user bandwidth requirements for MediaCentral Platform playback. The table is provided for guidance, and is not an indication of performance guarantees.

Proxy Setting (16:9, 30 fps) Bandwidth Needs

Width Quality Value Peak Valley Typical

Good 40 5.400Mbps 2.520Mbps 3.440Mbps

348 px Better 60 6.600Mbps 2.840Mbps 4.380Mbps

Best 80 9.000Mbps 3.480Mbps 5.690Mbps



















13

The next table explains the contents in detail.

Security Updates

Three security updates for RHEL 6.5 have been tested and approved by Avid:

• Security update to address an OpenSSL vulnerability

• Security update to address a Bash code injection vulnerability

• Security update to address the glibc vulnerability (“GHOST in the machine”)

Open SSL Security Update

Red Hat has issued a security advisory addressing the OpenSSL vulnerability known as the “Heartbleed” bug, which affects RHEL v6.5. A complete description of the security vulnerability and solution is available at the Red Hat web site:

https://rhn.redhat.com/errata/RHSA-2015-0715.html

For information on installing this patch, see the following Knowledge Base article:

http://avid.force.com/pkb/articles/en_US/how_to/Patching-the-OpenSSL-vulnerability-known-as-Heartbleed

Item Description

Width 348 pixels is the minimum player width; 960 pixels is the max. Height depends on the aspect ratio. The table assumes an aspect ratio of 16:9.

Quality Refers to the quality setting in the Player set via the UI.

Value Each quality setting has a numeric value. In JPEG compression literature, these are often thought of as percentages of original image (e.g. 100% is equivalent to uncompressed; 1% represents a severely degraded image).

Peak Video with high color variation (e.g. wide shot of a crowd)

Valley Video with low color variation (e.g. half of frame consists of a clear blue sky)

Typical A wide range of footage (e.g. interiors, exteriors, interviews). The typical shot tends closer to valley values than peak values.

Audio All bandwidth figures include audio consisting of 44.1 kHz sample rate x 16-bit/sample x 2 tracks = 1.4 Mbps

https://rhn.redhat.com/errata/RHSA-2015-0715.html



14

Bash Code Security Update

Red Hat has issued a security update for the Bash code injection vulnerability known as “Shellshock.” This Red Hat vulnerability might affect both Interplay Central / MediaCentral and iNEWS servers running Red Hat Enterprise Linux. For information on installing this update, see the following Knowledge Base article:

http://avid.force.com/pkb/articles/en_US/faq/Bash-Code-Injection-Vulnerability-CVE-2014-7169

glibc Security Update

Red Hat has released a security update for the glibc vulnerability, known as “GHOST in the machine” (CVE-2015-0235). For information about installing this update, see the following Knowledge Base article:

http://avid.force.com/pkb/articles/en_US/faq/CVE2015-0235-glibc-security-update-for-Avid-products

Installing MediaCentral Platform Services Version 2.4.0

The MediaCentral Platform Services (MCS) v2.4.0 installation package is available as a full installation package, for upgrades or new installations.

• For systems running MediaCentral Services 2.3.x (or earlier), see the MediaCentral Platform Services Upgrading Guide.

• For new systems, see the MediaCentral Platform Services Installation and Configuration Guide.

Be sure to download the latest version of these documents from the Avid Knowledge Base:


For information about setting up multi-zone configurations see the MediaCentral Platform Services Installation and Configuration Guide.

For information about setting up Media Index, see the Media Index Configuration Guide, available internally.







15

Obtaining the MCS Installation Package

MediaCentral Platform Services installation packages are available from the Avid Download Center. Prior to performing any new installation or system upgrade, verify the compatibility of your software components against the Avid Video Compatibility Charts on the Avid Knowledge Base: http://avid.force.com/pkb/articles/en_US/compatibility/Avid-Video-Compatibility-Charts

MediaCentral installation package:

• MediaCentral_Services_2.4.0_Linux.zip

MediaCentral Closed Captioning Service installation package (if applicable):

• MediaCentral_ClosedCaptioning_Service_2.4.0_Linux.zip

MAM Connector installation package (if applicable):

• MediaCentral_MAM_Connector_2.4.0_Linux.zip

n See the MediaCentral Platform Services Installation and Configuration Guide for details on installing and upgrading the Closed Captioning Service and the MAM Connector.

Obtaining Gluster

MediaCentral Platform Services v2.4.0 includes and automatically installs the GlusterFS v3.6.4 packages as part of the MCS v2.4.0 installation and upgrade processes. A separate download and installation of GlusterFS is no longer required. If you are running a single server system, the packages are installed, but not activated. If you are installing a new clustered system, the packages are installed but manual configuration is still required. If you are upgrading to MCS v2.4.0 and are running an older version of GlusterFS, the packages are updated for you during the upgrade process.

Migrating User Settings from UMS to USS During an Upgrade

MediaCentral 2.0 introduced a new user database scheme. Upgrades of systems prior to 2.0 need to complete a user database migration using the supplied avid-uss-import script.

• For upgrades from 1.8.0 (RedHat 6.3) or earlier, a backup and restore of the MCS database is required. The user database migration must be completed after restoring the MCS database, but before logging in via the MediaCentral | UX user interface.

• For upgrades from 1.8.1 (RedHat 6.5), a backup and restore of the MCS database is not required. However, the avid-uss-import script must still be run before logging in via the MediaCentral | UX user interface.

n In a cluster, the user database migration script must be run once on the master node only.


https://www.avid.com/US/Account/Orientation?ReturnUrl=http://esd.avid.com/Login.aspx


16

For detailed backup and restore instructions, see the MediaCentral Platform Services Upgrading Guide.

Resetting Layouts After Upgrading from v2.0 or Earlier

Three panes used in MediaCentral UX v2.0 are not used in MediaCentral UX v2.4.x:

• Markers pane: redesigned as Logging pane.

• Search pane in Users Layout: replaced by Filter field.

After MediaCentral UX is upgraded to v2.4.x, users who had signed out with these panes open will see them when they sign in again, with the message: “No View implementation found for type undefined” in the pane. Users need to reset the panes.

This problem does not occur when upgrading from MCS v2.1.x or higher.

To reset the outdated panes, do one of the following:

t Close the outdated panes.

t Reset the layout by selecting “Reset Layout” from the Layout selector.

Resetting Layouts After Upgrading from ICS V1.6 or Earlier

After upgrading from Interplay Central Services V1.6 or earlier, users who had previously signed in will see the Assets pane and Search panes from their most recent session. However, the Assets tabs and Search panes are not usable.

This problem does not occur when upgrading from ICS V1.7 to MediaCentral Platform V2.4.x.

To reset the Assets pane and Search panes, do one of the following:

t Close all open Assets tabs and Search panes and reopen them.

t Reset the layout by selecting “Reset Layout” from the Layout selector.

Installing SSL Certificates

For instructions on eliminating the (Chrome) “your connection is not private” or (Safari) “Safari can’t identify the website” security warnings, see the following article in the Avid KB:

http://avid.force.com/pkb/articles/en_US/how_to/SSL-Certificates-for-server-to-browser-connections




17

Upgrading Multi-Zone and Media | Index Deployments

If your deployment is configured for multi-zone, note the following:

• Upgrade slave zones first. If you cannot bring all zones off-line at once, upgrade the slave zone(s) before the master zone.

An upgraded slave zone no longer has access to the centralized user management service (UMS), which is owned by the master zone. Users in the upgraded slave zone can continue to log in —the local, read-only copy of the UMS database is used — but you cannot create new users.

• After the master zone has been updated as last zone of the multi-zone setup, the /opt/avid/cluster/bin/pgpool_remote_start script needs to be run to enable the proper syncing of the user databases between all zones again. Please be aware that the script will restart some services on the systems in the remote zones. After the services are restarted, users will need to sign back into MediaCentral UX.

If your deployment is configured for Media Index, note the following:

• Systems configured for Media Index require additional steps for certain upgrade paths. Review and complete the following steps as appropriate for your installation:

If you are upgrading from MediaCentral v2.1 or earlier, you must delete the indexes in all zones before the upgrade. Deleting the indexes reverts the index table to a clean (empty) state. For instructions, see the Avid Media | Index Configuration Guide.

If you are upgrading from MediaCentral v2.2.x or later, the indexes are compatible with MediaCentral v2.4 and do not need to be deleted. However, a migration script must be run to update the indexes to include new features associated with MCS v2.4. For instructions, see the Avid Media | Index Configuration Guide.

• To configure the Production Engine Bus Connector (PEBCo) for Media Index on MCS v2.4.x, you must use the Interplay Administrator tool for Interplay Production v3.3 or later. PEBCo supports the Interplay Production Engine v3.1 and later.

18

Installing MediaCentral Platform Services Version 2.4.1

The following topics describe how to install the MCS v2.4.1 update release:

• “Upgrading the iNEWS Client Version” on page 18

• “Obtaining the MCS Installation Packages” on page 18

• “Copying Software to the MCS Server” on page 19

• “Updating a Single-Server System from MCS v2.4.0 to MCS v2.4.1” on page 22

• “Updating a Cluster System from MCS v2.4.0 to MCS v2.4.1” on page 23

c You must install MCS v2.4.0 before you install the MCS v2.4.1 update.

Upgrading the iNEWS Client Version

If your workflow includes integration with Avid iNEWS, ensure your iNEWS system is updated with the iNEWS Client Version for this release of MCS. See “Editing SYSTEM.CLIENT.VERSIONS” in the MediaCentral Platform Services Installation and Configuration Guide for instructions on adding the client version to the iNEWS system.

Obtaining the MCS Installation Packages

MediaCentral Platform Services (MCS) v2.4.1 is a cumulative update that provides bug fixes. MCS v2.4.1 requires prior installation of MCS v2.4.0. MediaCentral Platform Services installation packages are available from the Avid Download Center.

Prior to performing any system upgrade, verify the compatibility of your software components against the Avid Video Compatibility Charts on the Avid Knowledge Base: http://avid.force.com/pkb/articles/en_US/compatibility/Avid-Video-Compatibility-Charts

MediaCentral installation packages:

• MediaCentral_Services_Update_2.4.1_Linux.zip

MediaCentral Closed Captioning Service installation package (if applicable):

• MediaCentral_ClosedCaptioning_Service_2.4.0_Linux.zip

MAM Connector installation package (if applicable):

• MediaCentral_MAM_Connector_2.4.0_Linux.zip

n See the MediaCentral Platform Services 2.4 Installation and Configuration Guide for details on upgrading the Closed Captioning Service or the MAM Connector.




19

Copying Software to the MCS Server

At various times during the upgrade, you will need to copy software to the MCS server. This task can be performed using one of the following two methods:

• Using a Windows system and a SFTP tool such as WinSCP

• Connecting a USB drive directly to the server

To copy software using WinSCP:

1. Download and install the WinSCP software on a Windows system that has network access to the MCS server.

The WinSCP software can be found at: http://winscp.net.

2. Launch WinSCP.

3. Enter the Host name (or IP address) of your server, User name (root), and Password.

4. Click Login.

The following warning message is displayed: “Continue connecting and add host key to the cache?”

5. Click Yes.

The WinSCP interface is displayed. The left pane represents your source Windows system. The right pane represents your MCS server.

http://winscp.net

20

6. Navigate to the location of the downloaded MCS installation files in the left pane.

7. Navigate to the /media folder on the MCS server in the right pane.

8. Right-click in the right pane and select New>Directory.

9. In the “New folder name” field, type installers and click OK.

10. Double-click on the new installers folder in the right pane.

11. Drag and drop the files or folders you wish to copy from the left pane to the right. Depending on your WinSCP settings, you might see a dialog box asking if you want to copy the files to the remote directory. Click Copy.

n When copying the MCS installer to the MCS server, the installer should be contained in its own folder within the installers folder. Create sub-folders as necessary. Example: /media/installers/MCS_v2.4.1

12. After all desired files or folders have been copied, close WinSCP.

To copy software using a USB drive:

1. Insert the USB drive into the MCS server.

2. Verify the name of the device:

dmesg

Linux information relating to the hardware appears on the screen.

Information for the USB drive will appear near the end of the output, near the list of SCSI devices. The name of the USB drive is found inside square brackets (for example, sdc). This is the name you use to mount the drive.

3. If needed, create a mount point for the USB drive:

mkdir /media/usb

4. Mount the USB drive at the mount point you just created:

mount /dev/sdc1 /media/usb

Note the name of the USB drive, sdc (in this case) takes a 1 (one) in the mount command. This simply indicates a partition exists on the USB key. When the USB key was formatted, the partition was created.

The USB key is now mounted and available for use.

21

5. Verify the USB key has been mounted:

df -h

Information is displayed about all mounted filesystems and devices, and should include information about the USB drive, similar to the following (other output has been omitted, for clarity):

Filesystem Size Used Avail Use% Mounted on/dev/sdc1 7.5G 5.3G 2.2G 71% /media/usb

6. To change to the mount point:

cd media/usb

7. If needed, create a directory for the installer packages:

mkdir /media/installers

8. When copying the MCS installer to the MCS server, the file should be contained in its own folder within the installers folder. Create a sub folder for the MCS installer:

mkdir /media/installers/MCS_v2.4.1

9. Copy files to the MCS server:

For a single file: cp filename /media/installers/MCS_v2.4.1

For a folder: cp -R foldername /media/installers/MCS_v2.4.1

10. Once you have finished coping all necessary files, unmount the USB drive.

cd

n In Linux the cd command without any arguments takes you directly to the user’s home directory. If you are logged in as root, it takes you to the /root directory. You must be off the USB drive to unmount it.

umount /media/usb

If you receive an error message that the USB device is busy, it typically indicates the Linux ISO on the USB drive was automounted. Verify what is mounted using the df -h command or the mount command, or both. Then dismount the Linux ISO first, followed by the USB device:

umount /sysinstallumount /media/usb

Remove the USB drive from the server.

22

Updating a Single-Server System from MCS v2.4.0 to MCS v2.4.1

Installing MCS v2.4.1 on a server already running MCS v2.4.0 is a simple automated update of the affected packages. All MCS v2.4.0 system settings are preserved. There is no requirement to manually backup and restore any MCS system settings.

Expected downtime: 30 minutes.

To install MCS v2.4.1:

1. Log in as root.

2. Copy the installation package to the MCS server.

See “Copying Software to the MCS Server” on page 19.

3. Navigate to the directory containing the installer (example path below):

cd /media/installers/MCS_v2.4.1

4. Unzip the installation package:

unzip MediaCentral_Services_Update_2.4.1_Linux.zip

5. Although the upgrade is non-destructive, it is a good idea to backup the MCS settings and database. Back up the MCS settings and database using the backup script:

./system-backup.sh –b

6. Start the installation script:

./install.sh

n Be sure to use the dot-slash (“./”) notation, which tells Linux to look for the install script in the current directory. Otherwise you will receive the following error message:

-bash: install.sh: command not found

During the installation process, progress is displayed. The update completes with an indication of success:

INSTALLATION FINISHED

If any errors were encountered during the upgrade, you can obtain more information in the installation log at:

/var/log/MediaCentral_Services_<version>Build<number>_Linux.log

7. Check that the installation was successful using the ics_version script:

ics_version

For the correct version numbers, see “System Version Numbers” on page 3.

23

n If you receive a “command not found” error, logout and log back into the server or SSH session (PuTTY). This will refresh the login for the upgraded system and should allow the command to run properly.

8. (Multi-Zone configurations only) Once the master zone has been updated, run the following script from the master zone to re-enable the database syncing between all zones:

/opt/avid/cluster/bin/pgpool_remote_start

9. Check to make sure the avid-isis service is started:

service avid-all status

If avid-isis is reported as failed, restart all services:

service avid-all restart

Updating a Cluster System from MCS v2.4.0 to MCS v2.4.1

Installing MCS v2.4.1 on a cluster already running MCS v2.4.0 is a simple automated update of the affected packages. All MCS v2.4.0 system settings are preserved. There is no requirement to manually back up and restore any MCS system settings. All nodes must be brought off-line to perform the update.

Expected downtime: 1 hour for two servers, plus 30 minutes for each additional server.

The cluster update involves the following steps:

• “Backing Up the MCS Settings and User Database” on page 23

• “Identifying the Master, Slave and Load-Balancing Nodes” on page 24

• “Bringing the Cluster into Standby Mode” on page 25

• “Updating the Cluster” on page 26

• “Verifying the RabbitMQ Cluster” on page 27

• “Bringing the Corosync Cluster Online” on page 28

Backing Up the MCS Settings and User Database

Although the upgrade is non-destructive, it is a good idea to backup the MCS settings and database. This is completed using the system-backup script provided with the MCS software package. This is an optional, but recommended step.

To back up the database:

1. Log in as root.

2. Copy the installation package to the MCS server.

See “Copying Software to the MCS Server” on page 19.

24



4. Unzip the installation package:

unzip MediaCentral_Services_Update_2.4.1_Linux.zip

5. Back up the MCS settings and database using the backup script:

./system-backup.sh –b

6. Repeat this process on each node.

Identifying the Master, Slave and Load-Balancing Nodes

There are three types of nodes in a cluster: master, slave, and load-balancing. The master “owns” the cluster IP address. The slave assumes the role of master in the event of a failover. Any additional nodes play a load-balancing role, but can never take on the role of master

To identify the master, slave, and load-balancing nodes:

1. Identify the master node of the cluster through the Cluster Resource Monitor. Log in to any machine in the cluster as root and type:

crm_mon

2. To identify the master and slave, look for the line containing “Master/Slave Set.”

For example:

Master/Slave Set: ms_drbd_postgres [drbd_postgres]Masters: [ mcs-1 ]Slaves: [ mcs-2 ]

In this example, the master node is mcs-1 and the slave node is mcs-2.

3. To identify the load-balancing nodes, look for the line containing “Clone Set.”

For example:

Clone Set: AvidAllEverywhere [AvidAll]Started: [ mcs-1 mcs-2 mcs-3 mcs-4 ]

In this example, the load-balancing nodes are mcs-3 and mcs-4.

4. Exit crm_mon by pressing CTRL-C on the keyboard.

25

Bringing the Cluster into Standby Mode

Corosync and RabbitMQ maintain independent clustering mechanisms. Corosync clusters operate in a master/slave relationship whereas RabbitMQ clusters run in an Active/Active state where any node in the cluster could be the owner of a RabbitMQ “queue”. This means that the order in which the nodes disconnect and reconnect to the RabbitMQ cluster is particularly important.

n Take care to note the order in which nodes are taken offline. The node that is “last down” must be the node that is “first up”. Failure to do so may break the RabbitMQ cluster.

In the following process, you will put each node of the Corosync cluster into “standby” and you will stop the RabbitMQ service to pause its clustering functionality. Complete this process one node at a time, waiting 30 seconds between each node. Avid recommends starting with the final node first.

To bring the cluster into standby mode:

1. Begin by putting the Corosync load-balancing nodes into standby mode and then stopping the rabbitmq service. Complete this process one node at a time, waiting 30 seconds between each node:

crm node standby <node name>

service rabbitmq-server stop

Verify that the stop command returns a value of [OK]. If the service does not stop correctly, troubleshoot the issue before continuing.

2. Wait 30 seconds and put the Corosync slave node into standby:




3. Wait 30 seconds and put the Corosync master node into standby:




26

Updating the Cluster

Upgrade the nodes in the reverse order that you stopped the services. Start with the Corosync master node, followed by the slave node and finally the load balancing nodes.

To update the cluster:



2. Start the installation script:

./install.sh

n Be sure to use the dot-slash (“./”) notation, which tells Linux to look for the install script in the current directory. Otherwise you will receive the following error message:

-bash: install.sh: command not found

During the installation process, progress is displayed. The update completes with an indication of success:

INSTALLATION FINISHED

If any errors were encountered during the upgrade, you can obtain more information in the installation log at:

/var/log/MediaCentral_Services_<version>Build<number>_Linux.log

3. Check the installation was successful using the ics_version script.

ics_version

For the correct version numbers, see “System Version Numbers” on page 3.

n If you receive a “command not found” error, logout and log back into the server or SSH session (PuTTY). This will refresh the login for the upgraded system and should allow the command to run properly.

4. Proceed to the next node, and follow the same steps (1 through 3):

a. Navigate to the location of the installer package.

b. Run the install script.

c. Verify the installation using the ics_version script.

5. If additional components (e.g. Closed Captioning Service, MAM Connector, Media Distribute, etc.) require updating, complete those upgrades at this time. Failure to upgrade previously installed components may result in unexpected errors when testing the system.

27

Verifying the RabbitMQ Cluster

Prior to restoring the Cosrosync cluster, you should first verify that the RabbitMQ cluster is functioning normally. Complete the following two steps on each cluster node.

To verify the status of RabbitMQ:

1. Verify the status of the RabbitMQ service:

service rabbitmq-server status

The command will return a detailed string of data regarding the service. Example (partial only):[root@mcs-1 ~]# service rabbitmq-server statusStatus of node 'rabbit@mcs-1' ...[{pid,2064}, {running_applications, [{rabbitmq_federation_management,"RabbitMQ Federation Management", "3.3.5"}, {rabbitmq_management,"RabbitMQ Management Console","3.3.5"},

Review the output of the command and verify there are no obvious error messages such as “service is dead but pid (xxxxx) is running”.

2. Check the RabbitMQ cluster with the “rabbitmqctl cluster_status” command:

rabbitmqctl cluster_status

The following is an example of a 2-node cluster:

Cluster status of node 'rabbit@node-n1’ ...

[{nodes,[{disc,['rabbit@node-n1','rabbit@node-n2']}]},

{running_nodes,[ 'rabbit@node-n1','rabbit@node-n2']},

{cluster_name,<<"rabbit@node-n1">>},

{partitions,[]}]

The command should return information about each of the RabbitMQ cluster nodes. All available nodes should appear on both the “nodes” and “running_nodes” lines.

Verify that each node reports the same information about the RabbitMQ cluster (all nodes are known and running).

n The RabbitMQ cluster must be healthy prior to bringing the Corosync cluster back online. If you suspect there is a problem, see the following Avid Knowledge Base article for assistance:

http://avid.force.com/pkb/articles/en_US/troubleshooting/RabbitMQ-cluster-troubleshooting

http://avid.force.com/pkb/articles/en_US/troubleshooting/RabbitMQ-cluster-troubleshooting

28

Bringing the Corosync Cluster Online

The final step in the process is to bring the Cosrosync cluster back online and verify that the cluster is functioning normally.

To bring the Corosync cluster online:

1. Bring the cluster back online by reversing the process you used to take it offline.

a. Begin by bringing the master node back online:

crm node online <node name>

b. Wait 30 seconds and bring the slave node online:


c. Finally, bring the load-balancing nodes online:


n Versions of this process in prior documentation suggest using the reactivate-cluster script. While this is a valid method, it introduces the possibility of breaking the cluster configuration. This manual method for bringing the cluster online is preferred.

2. Verify the cluster status and cluster failover status:

crm_mon -f

a. Verify the master, slave, and load-balancing nodes have rejoined the cluster, as expected.

b. Verify the fail counts for the following resources (at a minimum): pgsqlDB, MongoDB, AvidACS, AvidIPC, AvidUMS, AvidUSS, Redis.

c. Verify the cluster status.

3. If there are fail counts listed, run the cluster resource manager cleanup command to reset them:

crm resource cleanup <rsc> [<node>]

<rsc> is the resource name of interest: AvidIPC, AvidUMS, AvidACS, pgsqlDB (or another)

<node> (optional) is the node of interest.

n You can address the services contained in the postgres resource group (postgres_fs, AvidClusterIP and pgsqlDB) individually, or as a group.

4. (Multi-Zone configurations only) Once the master zone has been updated, run the following script from the master zone to re-enable the database syncing between all zones.

/opt/avid/cluster/bin/pgpool_remote_start

29

Installing the Media | Distribute Update

Media Distribute v2.4.1 is a full plug-in installer. For installation instructions, see the Media | Distribute V2.4 Installation and Configuration Guide.

New Features in MediaCentral | UX Version 2.4.0

This topic provides an overview of the major new features in MediaCentral UX v2.4. For complete information see the MediaCentral UX documentation.

Closed Captions

Feature Description

Support for expanded character set The characters you can enter for closed captions have been expanded to include special characters in English, and characters used in the following languages:

• Danish

• French

• German

• Italian

• Portuguese

• Spanish

n These characters are listed in technical standard CEA-608-C.

You can mix characters and languages in a single closed caption or a set of closed captions.

All text is displayed in a single set of closed captions. You cannot currently switch between two sets of closed captions (for example, English and Spanish).

30

Multiple caption blocks on screen If two or more closed caption segments share a simultaneous time span, all captions are displayed in the Media viewer. For example, in a scene with two speakers, you can align one caption left and one caption right, as shown in the following illustration.

Text for each caption is entered on a separate segment in the Closed Captioning pane, with the desired alignment set in the Align column. The following example shows the Closed Captioning pane for the above illustration:

Note the following:

• If multiple captions share the same line (top, middle, or bottom), they will be merged into a single line as part of the repackaging or export process. To avoid this, change the alignment so each captions is on a different line.

• If multiple captions share the same line (top, middle, or bottom), the total number of characters per line is limited to 32.

• All segments must share the same In point and Out point. You cannot currently edit the In point and Out point of simultaneous segments after you have set them once.

• Multiple caption blocks are limited to a total of four rows. Additional rows are not displayed.

Feature Description

31

Import, edit, and export roll-up captions Captions created as roll-ups in SCC files can be imported, displayed, edited, and exported in SCC files. Captions are displayed as single row segments in the Closed Captioning pane, and are displayed in up to three rows in the Media viewer.

n Gaps between segments prevent roll-ups from displaying correctly. Use the Close Gap command in the Closed Captioning pane to correct this.

Support for PAL frame rates You can now add closed captions to sequences composed of clips in the following resolutions and frame rates:

• 1080i/50 (25 fps)

• 720p/50

Importing, extracting, editing, exporting, and repackaging of these sequences is supported. Send to playback is not currently supported.

Closed Captioning Service installation All closed captioning components are now installed using the Closed Captioning Service installer. In v2.3.x the user interface components (such as the Closed Captioning pane) were installed by the MediaCentral UX installer even if the Closed Captioning Service was not installed.

Scrolling Scrolling for items in the Closed Captioning pane has been improved. An item that you select is scrolled so that it is fully visible at the top, middle, or bottom of the pane.

Fixed limitations Spaces that were underlined or italicized as part of the caption were not recognized as spaces by MediaCentral UX and caused problems during editing. These spaces are now recognized as spaces.

When adding a space, you could not remove formatting by using the Italics button or the Underscore button. This has been fixed.

Feature Description

32

Interplay MAM

Feature Description

Filter association types with no related assets

The Associations pane lets you see all associations of the asset currently open in the pane. By default, the pane shows all association types that can be set for the asset. You can hide association types for which no associations are currently defined and show them again by using a Filter button.

Attach Interplay Production and iNEWS assets to MAM processes

Starting with MediaCentral UX version 2.4, you can also attach Interplay Production assets or iNEWS stories to a process if the process is configured accordingly in Interplay MAM. Use the same procedure for creating processes for MAM assets and assets from other systems.

Quick Send For a quick transfer of material to a certain destination, users of Interplay MAM Desktop can just set In and Out points and then initiate the transfer. Starting with version 2.4, MediaCentral UX also provides a “Quick Send” feature for Interplay MAM assets. Quick Send requires a specific configuration and adaptation of the sample Quick Send process delivered with Interplay MAM. If Quick Send is configured, the Media pane provides a Quick Send menu item for a fast process creation for an asset.

Browse Image assets in Media pane Interplay MAM supports assets of type “Image.” You can use the Media pane to preview Image browse proxies from an Interplay MAM database. Supported formats are PNG and JPG.

Indicators for MAM connectivity status in System Settings pane

After you provide the Registry Server settings for a MAM system in the System Settings pane, a basic system connectivity status check is triggered. This query checks if the most relevant settings for the MediaCentral connection are configured properly in the Interplay MAM configuration profiles. This check provides information about mis-configured settings that must be resolved in Interplay MAM System Administrator.

33

Layouts

Logging

Markers

MCS Server

Feature Description

MOS plug-ins available in Log and Cut layouts

Prior to MediaCentral UX v2.4, MOS plug-ins used with iNEWS workflows were only available in Rundown and Story layouts. MOS plug-ins are now available in the Log and Cuts layouts as well. If installed, MOS plug-ins are found at the bottom of the Panes menu.

Feature Description

Scrolling Scrolling in the Logging pane has been improved. An item that requires an operation is scrolled so that it is fully visible at the top, middle, or bottom of the pane.

Feature Description

Add markers to a group clip If you add markers to a group clip in MediaCentral UX, the markers are now saved with the group clip, so that a Media Composer user will be able to view the markers. Markers that were previously applied to angles are preserved.

n Restrictions are applied and saved to angles of a group clip.

Feature Description

GlusterFS now automatically installed GlusterFS software packages are now bundled and automatically installed with all MCS 2.4 installations and upgrades. If you have a new installation, manual configuration of Gluster is still required. If you are upgrading an existing MCS cluster, the GlusterFS packages will be upgraded if necessary.

n GlusterFS is a file replication system used with clustered installations. If you have a single server, the GlusterFS packages are installed, but no further action is required.

34

MediaCentral Distribution Service

Media | Index

Send to Playback

Feature Description

Updated configuration options MediaCentral Distribution Service v3.4 can now be co-installed on Interplay Production Transcode providers and STP Encode Providers.

Feature Description

Saved Searches You can save both indexed searches and federated searches to make it easy to access frequently searched assets.

Support for predefined criteria, such as legal lists of terms

You can use metadata values that are predefined to use as consistent values in your searches. These values display in the search criteria as a list of terms you can add to or exclude from your search. Legal lists are supported for Interplay MAM assets only.

Boolean operators in search Some search criteria allow you to select Boolean operators — for example, “true” or “false” — from a predefined criteria list.

Time Selection in Search Criteria You can modify the time values in your search criteria to specify an exact time in hours, minutes, and seconds.

Feature Description

Send master clips and subclips to a playback device

If you load a clip or a subclip in Asset mode, you can send the clip or subclip to a playback device (STP). This feature lets you send to playback without cutting a clip or subclip into a sequence. You use the same controls as when you send a sequence to playback.The resolution of the clip must match the resolution in the profile you select.

35

Settings

Feature Description

Language for user interface The user interface is now available in Arabic and Turkish. Select the language you want to display in the General User Settings.

Date and time format Administrators set the default date and time format in the General System Settings. This setting applies to most date and time displays in MediaCentral UX. Users can override this setting in the General User Settings.

For MediaCentral UX v2.4, system administrators and users can select one of the following formats for dates and times:

• MM/DD/YYYY hh:mm:ss A Z (U.S.)

• DD/MM/YYYY HH:mm:ss Z (European)

• YYYY-MM-DD HH:mm:ss Z (International)

• DD.MM.YYYY HH:mm:ss Z (Alternative)

hh = 12h formatA = AM or PMHH = 24h formatZ = Time zone (offset from UTC)

n The hour format (12h or 24h) is affected by the operating system setting, as a result of a browser limitation. For example, an editable time value in the Search pane (such as Modified) is displayed in the format selected in the operating system, but search results are shown in the MediaCentral UX setting. If the operating system is set for 24h, but MediaCentral UX is set for 12h, the 24h format is displayed in an editable field and the 12h format is shown in the search results.

36

Progress Pane

User Management

Avid MediaCentral | UX Desktop

Feature Description

Desktop notifications for jobs in the Progress pane

Notifications for jobs listed in the Progress pane are shown as browser alerts. This is useful if the browser running MediaCentral UX is minimized or hidden by other windows.

The first time you start MediaCentral UX, a message box asks you if you want to allow or block notifications from the MCS server. For complete information, see “The Progress Pane” in the MediaCentral UX User’s Guide.

Feature Description

Authenticate against multiple Windows domain servers

Administrators can set more than one Windows domain server for user authentication. This feature is useful for facilities that use mirrored LDAP servers, so that a backup is available if one server goes offline. In the Authentication Providers section in the Users layout, enter the computer names of the servers, separated by a comma but no space, in the Hostnames text box.

Feature Description

Access portal for MediaCentral UX MediaCentral UX Desktop is a client application capable of replacing a traditional web browser as an access portal to MediaCentral UX. Because Chrome v45 has removed support for NPAPI, this application allows customers that rely on MOS plug-ins for MediaCentral UX to continue to operate as normal.

For more information see the MediaCentral Platform Services Installation and Configuration Guide

37

Media | Distribute

Additional Documentation

Assigning the Administrator Role Directly: If you create a user in the Administrators group, sign in as the created user, assign the Administrator role directly, remove the Administrators group from Groups, and click Apply, the system signs you out and you need to sign in again as a different user. The user you created is deleted from the Administrators group and moved to the Unassigned group.

Length of Active Directory Fields for User Import: When users are imported into MCS, the user data is stored in the local user database. The fields in this database have a maximum limit of 255 characters. LDAP allows for some fields such as the “Distinguished Name” (DN) to be longer than 255 characters. If you find that some users do not import are not imported into MCS, verify that none of the fields associated with the domain user are longer than 255 characters.

Cannot Delete Domain Controller Groups: In the Users layout, an administrator cannot delete a domain controller group imported from an Active Directory system. You can delete all members of the group, but you cannot delete the group itself.

Browser Controls for Window Size: Using browser controls to change the size of the MediaCentral UX window (for example, Ctrl + to enlarge the window and Ctrl – to reduce the window) is not supported. Using these controls do not work consistently and slow down the application.

Feature Description

Support for publishing to the Ooyala online video provider

You can publish to Ooyala from MediaCentral UX.

Support for publishing to thePlatform video CMS

You can publish to thePlatform video CMS from MediaCentral UX. The profile settings for thePlatform include customized fields and a separate pane in the Media Distribute System Settings.

Support for the YouTube v3.0 API You can use the latest YouTube API for new profiles when publishing to YouTube.

38

Fixed in Version 2.4.1

The following bugs are fixed in version 2.4.1.

Assets

(JP-2151) In the Assets pane, if you select an asset, scroll down, and press Shift+click to select multiple assets, only one asset is selected.

Editing

(OS-2883) If roll-up captions are center-aligned or right-aligned, they might not be displayed correctly. For example, letters might be cut off.

(OS-2878) If you change from one type of caption to another (for example, from roll-up to pop-on or from pop-on to roll-up), the Media viewer does not change the display. For example, roll-up captions will be displayed as single-line pop-up captions.

(OS-2846) If you load a remote asset in the Media pane (Asset mode), load a local sequence in the Media pane (Output mode), and switch back to Asset mode, the following error message is displayed: “error 1102 Interplay asset was not found.” Switch back to Output mode and the following error message is displayed: “error 1102 Cannot load timeline.” Swtich back to Asset mode again and no asset is loaded.

(MA-2943) If a user is working on a locked story, another user can edit the associated sequence. See “Locking a Story Prevents Editing of the Associated Sequence” on page 53.

(PLAD-186, PLAD-190) You need the permission Create Locators enabled in the Interplay Administrator (Instinct/Assist Users view) to edit sequences that include markers. If you do not have this permission enabled, there are two situations in which if you try to save the sequence, an error message is displayed, and the sequence becomes uneditable:

• You edit a segment that contains markers into a sequence.

• You trim a segment in a sequence that contains markers, but do not trim away the markers.

In both cases the error message “net.nxn.JXDK.ServerCommandFailedException: Error message from the server: "Insufficient permissions". (0x89990301)” is displayed, the sequence is not saved, and the sequence becomes uneditable.

This is fixed so that the sequence remains editable. The user still requires the Create Locators permission to perform the edit and save the sequence without an error.

(MPLAY-2045) The Master timecode in the Media pane is displayed as the Absolute value (an offset of the first frame) rather than the actual timecode of the original asset.

39

MCS Server

(JP-2525, CORE-6963) On the MCS server, if avid-interplay-central service is stopped, the current connections to the Interplay Production Engine are not closed until the 10-minute timeout occurs. This prevents Interplay Production licenses from being released for ten minutes.

n (JP-2525, CORE-6963) This issue was incorrectly listed as fixed in the 2.4.1 ReadMe. The fix for this issue in present in MCS v2.4.2.3 and later.

Media Index

(JP-2467) If you open a saved indexed search when indexed search is not available, an empty search pane opens and you cannot open a new search pane or a saved federated search.

System Settings

(JP-2445) Safari on Mac OS does not support HTML time pickers. You need to enter the time value in the in 24-hour format HH:mm:ss.

(JP-2500) If MediaCentral UX is set to display Arabic or Turkish, Chinese symbols are displayed for AM and PM.

Installation

(RE-1038) For a single-node cluster, the Thesaurus service is not automatically started after an upgrade from v2.3 to v2.4.

Media | Distribute

(MPD-1303) Using Media Distribute to post video content to YouTube with a duration over 26 seconds failed. This has been fixed and you can post videos of any duration. This fix is available only in Media Distribute v2.4.2.

(MPD-1254) Media Distribute displays an error in the Packages pane when you post a media package to Facebook that includes a link to an online video provider (OVP) such as YouTube. The Facebook v2.4 API or later no longer supports these links. This has been fixed and you can now post video with OVP links to Facebook.

Player

(MPLAY-2072) When loading an asset that contains more than four audio tracks, users could encounter a delay up to 10 seconds before playback begins.

40

Search

(JP-2311) In the Add Criteria and Add or Remove Columns dialog boxes, the root element is not selected when all child elements are selected. For example, in the Add Or Remove Columns dialog box, “Common Properties” is not selected when all child elements are selected.

(JP-2518) Searching for “clip” (using the criteria “Asset type is clip”) might not display any results. This is fixed by selecting “Asset type contains clip.” The resulting search shows master clips and subclips.

(JP-2526) The date-time input field uses the operating system time zone instead of the time zone selected in the User Settings.

(JP-2539) The calender picker uses the operating system time zone instead of the time zone selected in the User Settings.

(JP-2541) The date slider might set the incorrect date when you slide more than one day back.

(JP-2560) When you select an end date, the time should be 23:59:59, regardless of the user’s time zone.

(JP-2523) You can save an Indexed search, leave the Search pane open, and sign out. If the Indexed search process becomes unavailable, and you sign in again, the Search pane appears broken, instead of displaying the saved search.

Interplay | MAM

(MPLAY-2058) MAM Video Analysis hangs on proxy files in which the audio duration exceeds the video by a few number of samples.

Documentation

Closed Captioning: The MediaCentral UX Help includes the latest information about closed captioning.

Translated Documentation: Translated versions of the MediaCentral UX Help are included in version 2.4.1. Translated guides in PDF form are available on the Avid Knowledge Base:


Fixed in Version 2.4.0

The following bugs are fixed in version 2.4.0.



41

Editing

(SPEC-683) You cannot load or edit a sequence created in Avid Instinct.

(OS-2808) If a sequence created in Instinct that includes markers is loaded in MediaCentral UX, the markers are not shown.

(OS-1701) Overwriting with a group clip angle that has padding between the In point and the Out point results in a one-frame clip.

(OS-2501) If loading of a remote asset is interrupted, for example, by switching from Asset mode to Output mode, the Asset mode timeline fails to display completely. Tick marks, and any In and Out marks, are not shown.

(OS-2595) If you add the same clip one or more times to a sequence, then add a restriction to the source clip, the Logging pane for the sequence shows duplicate restrictions for the same timecode.

(OS-2632) If you change the Main Title attribute of a MAM asset in the Metadata pane, the name of the asset is not changed in the Media and Sequence panes.

(OS-2691) Initiating an Update Status from within MediaCentral UX on a sequence created in Media Composer does not update the sequence as expected.

(OS-2717) If you send a sequence to playback (STP) and do not save the sequence, the STP button becomes disabled in the Media pane.

(OS-2718) If you drag a sequence to the Asset pane, a subclip is created.

(OS-2730) If you load a MAM asset in the Media pane, the Deliver To and Transcode menu items are enabled.

(OS-2737) If the position indicator is on the last frame of a sequence, the Trim Tail menu item is enabled. Similarly, if the position indicator is on the first frame of a sequence, the Trim Top menu item is enabled.

(OS-2767) If an Interplay Administrator changes a track label for the Audio pane, and you sign in to MediaCentral UX, the Audio pane shows the changed label. If you close the Audio pane and open it again, the default track label is displayed.

(OS-2769) If you enter a timecode earlier than the earliest frame in a clip, the position indicator does not move to the first frame of the clip.

(OS-2787) While trimming a clip in a sequence, the duration timecode shows the sequence being one frame longer than it actually is.

42

(OS-2839) If you record voice-over for a story sequence that does not contain video, the voice-over recording hangs MediaCentral UX.

(OS-2853) If you export a long sequence (for example, two hours) as MP4, a downloaded URL becomes available, but the downloaded file is incomplete and cannot be played.

Delivery

(JP-1955) Intermittently, the status of a Delivery or Deliver to Me job is not shown in the Progress pane. The status is shown in the Media Services and Transfer Status Tool.

Media Index

(CORE-6367) If you have installed a connector for Interplay Media Asset Manager (MAM) but have not correctly configured it, then federated search might not work. You should only install the MAM Connector if your configuration includes a MAM integration. This has been fixed, and federated search functions as expected.

Playback

(MPLAY-2028) Media created through Interplay Production Transcode v2.7.0.x appears as black with colored stripes in frame-based playback. This issue does not exist when working in file-based playback mode.

(MPLAY-2042) Media created by Metaglue MXFactory version 3.0.3 appears as “Media Offline” in the Media pane.

(MPLAY-1957) Some assets are only partially streamed to the iOS MediaCentral UX mobile app. Once the asset reaches the end of the file, playback will begin again from the beginning of the clip. At this time the remaining media for the asset is streamed to the device and playback of the entire asset is possible.

(MPLAY-2007) Proxy audio media captured through AirSpeed 5000 / 5500 v2.9.0, plays back in MediaCentral as static.

(MPLAY-1835) Assets created through EVS XTAccess v1.18.21 appear in MediaCentral as having the wrong aspect ratio resulting in a stretched or cropped image.

(OS-2669) The Media Asset Management (MAM) system does not pass the timecode type (drop-frame or non-drop-frame) to the player when playing a media asset. The player defaults to displaying non-drop-frame timecode for all assets.

Search

(JP-2116) In federated search, if you add the Folder criteria, then resize the Search pane as small as possible and press the Browse button, the Folder Browse dialog box is not always displayed.

43

Shortcuts

(JP-2164) When selecting a shortcut within the Launch pane on a Mac and pressing Enter, the shortcut is activated. The expected behavior is that the shortcut becomes editable.

Story

(MA-2708) On MediaCentral systems configured with the MAM Connector, the Associations pane is missing from the Story layout.

(MA-2664) When attempting to associate a sequence that is already associated with an iNEWS story to a second iNEWS story, the user is not prompted to create a duplicate sequence.

(MA-2900) After dragging and dropping a story from the Search pane into an iNEWS rundown that already contains the story, the rundown is incorrectly reordered.

Interplay | MAM

(MAM-3709) Properties of type integer prevent the Metadata pane from being opened when their size exceeds the maximal integer value.

(MAM-3580) If you enter an invalid number in a tag of type Float in the Tags column, a Server error occurs in the Logging pane.

(MAM-3547) If you select a subordinate hierarchical item in the Associations pane, an error message with misleading text is shown.

(MAM-3016) If the type of an asset was changed by the Change Class process, the icon and thumbnail of the old asset type are shown in the Search pane until you sign out and in again.

(MAM-2968) If strata are pooled in a group and no labels are provided for the group in the data model, the Strata selection list in the Logging pane does not show the strata group.

(MAM-2849) If more than one MAM system is connected to MediaCentral and you search for the asset type “EDL” using the Federated search, the search result returns the correct EDLs (basic sequences) but also other assets from connected MAM systems.

(MAM-2835) If a user is member in different user groups with conflicting read-write rights for the same metadata template, a wrong fall-back template might be shown in the Metadata pane.

(MAM-2166) An incorrect timecode for assets with drop-frame timecode is shown in the Media pane.

44

Media | Distribute

(MPD-1057) If you load a video clip in the Media pane while the Web Story pane is not active, then click the Web Story pane, the Load from Player button might be disabled and you cannot add a video clip to your story. This has been fixed.

45

Additional Documentation

This section includes information that is incorrect or not included in the v2.4 documentation.

MediaCentral | UX and Google Chrome

MOS plug-ins use a software architecture called Netscape Plugin Application Programming Interface (NPAPI). Chrome 42, launched in April 2015, depreciated support for NPAPI in favor of a newer architecture called Pepper (PPAPI). Chrome 45, launched in September 2015, eliminated support for NPAPI entirely.

MOS plug-ins can continue to function in versions of Chrome prior to v45 by manually re-enabling NPAPI using the process at the following link:

https://support.google.com/chrome/answer/6213033?hl=en

Additionally, the latest version of the Flash Player bundled with Chrome introduced an issue with audio stuttering on playback in certain situations. See the following link for more information:

http://avid.force.com/pkb/articles/en_US/troubleshooting/Audio-stutter-when-accessing-drop-down-menus-during-frame-based-playback

If your site depends on MOS plug-ins as part of the MediaCentral UX workflow, the Avid MediaCentral UX Desktop application is capable of replacing the traditional web browser as an access portal to MediaCentral UX. For more information about Avid MediaCentral UX Desktop, see the MediaCentral Platform Services Installation and Configuration Guide.

Media | Distribute Documentation

New features for Media Distribute version 2.4 are described in the PDF version of the Media | Distribute User’s Guide. The MediaCentral UX Help does not include this information.

Overriding the Default Panning for Advanced Sequences

The default audio panning for advanced sequences is odd tracks=left, even tracks=right. To override this panning, you can edit the application.properties file.

This override is global and applies to all Interplay folders.



https://support.google.com/chrome/answer/6213033?hl=en

46

To set the panning for advanced sequences:

1. Log in as the root user on the MediaCentral Platform server.

2. Use the vi text editor to open the following file for editing:

/opt/avid/etc/avid/avid-interplay-central/config/application.properties

3. Add the following line with the panning you want. For example:

system.advancedSequenceTrackPanning=A1:R;A2:C;A5:Right;

Use the following syntax:

- Key=value pairs separated by a semicolon. For example, A1:R;A2:C.

- Keys need to be in this set: A1, A2, A3, A4, A5. Not all need to be added, only keys for the tracks that you want to override. Advanced sequences have a maximum of five tracks.

- Values can be R, r, Right, right, L, l, left, Left, C, c, Center, center

4. Save and close the file.

You can use this procedure to set panning for STP stereo mixdown as it was in MediaCentral v2.0. In v2.0, single-channel tracks were mixed down to a single centered mono track. In v2.1, they are mixed left or right by default. To preserve the v2.0 behavior, edit the application.properties file with this key:

system.advancedSequenceTrackPanning=A1:C;A2:C;A3:C;A4:C;A5:C;

Media | Index Backup Locations

When you re-install the MediaCentral Platform Services software, a backup of all data is created before a complete re-installation using the USB key. However, indexes are not backed up by the system backup script. This typically does not cause an issue since users generally do not need to back up their indexes. For cluster configurations, the following notes also apply:

• In a cluster, the index should be configured with data redundancy to avoid data loss.

• In the case of a complete rebuild or of complete data loss within a cluster, Avid recommends re-indexing the data instead of using a backup. This is because the backup will no longer be in sync with what the index agents are expecting.

With the release of Elasticsearch v1.6, backups are only allowed on shared file locations, the backup in Media Index v2.4 requires manual configuration of the backup locations. Setting this up correctly requires a file server to be mounted on all machines. Customers should contact Avid Customer Care or Avid Professional Services for instructions and support from Avid Engineering in setting this up.

47

Media | Index Sort Order

(TSL-2438) When you sort search results on a column that uses a structured field, the results are sorted by the actual value of the structured field even though the results in the Search pane might display a localized label. For example, the stored index values for countries might be integer values, and these are the values used when sorting results. But the displayed values include the localized name of the countries, not the integer values, and the results might not follow the expected A-Z sort order.

Media | Index and Search Syntax

The options for Advanced Search syntax and Simple Search syntax have been removed from MediaCentral UX. All indexed searches use the advanced search syntax.

Troubleshooting Video Playback Problems on Android Devices

If you experience playback problems with the MediaCentral Android app, you can try to reload the asset. This forces the MediaCentral server to reload the full video clip and begin streaming it again. You can also try playing the asset in a browser to determine if the problem is related to the app or your connection, or if the problem exists with the MediaCentral server.

To reload an asset:

1. Tap the Action overflow button.

2. Tap Reload.

To play an asset in a browser:

1. Start the MediaCentral UX mobile app.

2. Tap the Action overflow button, and then select Settings.

The Preferences window opens.

48

3. Select Logging to enable logging.

4. Tao Logging Level and then select Verbose.

5. Click the Back button to return to MediaCentral UX.

6. Navigate to an asset in one of the directories.

7. Tap the video asset.

The asset opens in the Media viewer.

49

8. Tap the Play button to play the asset, and make a note of the time playback begins.

9. Click the Action overflow button and select Send Log to send an e-mail with the log file directly to an e-mail account.

The MediaCentral Log dialog box opens, displaying your e-mail and text options.

10. Tap the icon for the app you want to use to send the log.

The app opens on your Android device.

11. Send the log to your e-mail account.

12. Open the e-mail on your system, and then use a text editor to open the attached log file.

13. Find a link with .m3u8 suffix that is located on the line marked with the time playback started — for example:

50

07-02 16:15:29.830 [ . . . ] http://123.45.678.910/download/0e41028f99738669c581c50388e80d36/060a2b340101010101010f0013-000000-92dede5ab6034faa-b737d720c291-4093_1920x1080-fps25.00_from_0_to_7501_quality_0_video_-1_audio_-1_h264_aac_ts_.m3u8

14. Copy this link, and then paste it into the address field in a browser.

15. Edit link in address field by typing -WIFI before the .m3u8 suffix — for example:

http://123.45.678.910/download/0e41028f99738669c581c50388e80d36/060a2b340101010101010f0013-000000-92dede5ab6034faa-b737d720c291-4093_1920x1080-fps25.00_from_0_to_7501_quality_0_video_-1_audio_-1_h264_aac_ts_-WIFI.m3u8

n “WIFI” is case-sensitive.

16. Press Enter to go to the URL in the address field.

n The Safari browser supports native playback for .m3u8 files. Other browsers — for example, Chrome, Firefox, Internet Explorer, or Opera — do not. If you are not working on a computer running Mac OS X, you can use your browser to download the file to your system and play it in a media player that support .m3u8 video files.

17. Play back the asset.

If playback produces the same problem seen when you played the asset on your mobile device, the source of the problem is the MediaCentral server and not the app. If the asset plays back without issues, then the source of the problem is the mobile app, your connection, or your device.

51

Troubleshooting Video Playback Problems on iOS Devices

If you experience playback problems with the MediaCentral iOS app, you can try to reload the asset. This forces the MediaCentral server to reload the full video clip and begin streaming it again. You can also try playing the asset in a browser to determine if the problem is related to the app or your connection, or if the problem exists with the MediaCentral server.

To reload an asset:

1. Tap the Actions button.

2. Tap Reload.

To play an asset in a browser:

1. On your iOS device, tap the Settings icon.

2. Select MediaCentral UX in the list of apps.

The MediaCentral Settings screen opens.

3. Set Logging to On.

4. Select the Logging Level to Verbose.

5. Start the MediaCentral UX mobile app.

6. Navigate to an asset in one of the directories.

7. Tap the video asset.

The asset opens in the Media viewer.

52

8. Tap the Play button to play the asset, and make a note of the time playback begins.

9. Tap the Actions button, and then tap Send Log to send an e-mail with the log file directly to an e-mail account.

10. Open the e-mail on your Macintosh system, and then use a text editor to open the attached log file.

11. Find a link with .m3u8 suffix that is located on the line marked with the time playback started — for example:

07-02 16:15:29.830 [ . . . ] http://123.45.678.910/download/0e41028f99738669c581c50388e80d36/060a2b340101010101010f0013-000000-92dede5ab6034faa-b737d720c291-4093_1920x1080-fps25.00_from_0_to_7501_quality_0_video_-1_audio_-1_h264_aac_ts_.m3u8

12. Copy this link, and then paste it into the address field in a browser.

13. Edit link in address field by typing -WIFI before the .m3u8 suffix — for example:

http://123.45.678.910/download/0e41028f99738669c581c50388e80d36/060a2b340101010101010f0013-000000-92dede5ab6034faa-b737d720c291-4093_1920x1080-fps25.00_from_0_to_7501_quality_0_video_-1_audio_-1_h264_aac_ts_-WIFI.m3u8

n “WIFI” is case-sensitive.

53

14. Press Enter to go to the URL in the address field.

n The Safari browser supports native playback for .m3u8 files. Other browsers — for example, Chrome, Firefox, Internet Explorer, or Opera — do not. If you are not working on a computer running Mac OS X, you can use your browser to download the file to your system and play it in a media player that support .m3u8 video files.

15. Play back the asset.

If playback produces the same problem seen when you played the asset on your mobile device, the source of the problem is the MediaCentral server and not the app. If the asset plays back without issues, then the source of the problem is the mobile app, your connection, or your device.

Locking a Story Prevents Editing of the Associated Sequence

Starting with MediaCentral UX 2.4.1, locking an iNEWS story prevents another user from editing both the story and the associated sequence (script sequence). In previous versions of MediaCentral UX, another user could open the story and script sequence and edit the sequence if the edits did not affect the story.

n A user who opens a script sequence without opening the associated story (for example, by double-clicking in the Asset pane) can edit the sequence.

Limitations and Defects Found in Version 2.4.1

The following sections list limitations and defects for MediaCentral UX and MediaCentral Platform, except for the following:

• For the latest information and possible limitations for Media Index configuration, see the Media | Index Configuration Guide. This document is currently for Avid internal use only.

• For the latest information and possible limitations for Interplay MAM, see the Interplay MAM Release Notes.

Launch Pane

➤ Bug Number: (JP-2321). In some cases, double-clicking the Interplay Production database in the Launch pane does not open the database in the Assets pane. An error message might be displayed asking you to make sure the server connection is correctly configured.

Workaround:

1. Right-click the Interplay Production database and select Open in New Assets Tab.

2. (Administrator) Restart the ICS server at the next maintenance window.

54

Search

➤ Bug Number: JP-2176. If federated search is not accessible, the search pane might be displayed without any content for both federated search and indexed search. No error message is displayed to the user.

Workaround: The administrator should make sure all connected systems (iNEWS, Interplay Production, or Interplay MAM) are correctly configured.

Stories

➤ Bug Number: MA-3023. If you open two rundowns, select the first story in a rundown, and move it to the other rundown by dragging and dropping, MediaCentral UX might freeze. This situation might also occur if

• The story is the only one in a rundown

• The first story in a rundown is included in a group that you move.

Workaround: Do one of the following:

• Reload MediaCentral UX by reopening the application in a new browser tab. The session is cached so you should not need to sign in again.

• Reorder the rundown so that the story you want to move is not the first in the rundown. Then move the story.

User Management

➤ Bug Number: ICS-4449. (Safari only) A MediaCentral UX user password is limited to 255 characters. If an administrator enters a password of more than 255 characters in the Change Password dialog box and clicks OK, the dialog box closes without an error message. However, only the first 255 characters are saved and the user will not be able to sign in with the planned password.

Limitations and Defects Found in Version 2.4.0

Closed Captioning

➤ Bug Number: ARC-459. Occasionally, alignment of closed captions is not preserved during a Repackage/Extract or Export/Import operation.

➤ Bug Number: ARC-461. Occasionally, Out points are changed during a Repackage/Extract or Export/Import operation. Workaround: Reset the correct Out points.

55

➤ Bug Number: ARC-481. For Danish, German, and Portuguese characters, repackaging and extracting can cause the first caption to be lost. The second caption might contain part of the deleted first caption.

➤ Bug Number: SPEC-1049. If a formatted text block (for example, italics) ends with a space, the space character formatting should be automatically cleared. It is possible to add a space at the end of a caption and apply formatting that is not automatically cleared. Workaround: Manually remove the formatting.

Editing

➤ Bug Number: MPLAY-2036. MP4 files exported from MediaCentral UX will not play back in QuickTime 10.4 for Mac OSX.

Workaround: Play the MP4 file in QuickTime version 7.x. If you do not have QuickTime v7.x installed, it can be downloaded from the Apple Support site at: https://support.apple.com/downloads/quicktime

n If desired, you can set QuickTime 7 as the default player through the following process:

1. Right-click on your exported MP4 file and select Get Info.

2. Under the “Open with” section, select QuickTime 7 from the menu.

3. Click the “Change All…” button to apply that preference to all MP4 files.

4. Close the Get Info window.

➤ Bug Number: OS-2760, OS-2761. If you archive and restore a sequence in Interplay Production, the sequence is no longer editable in MediaCentral UX.

➤ Bug Number: OS-2759. In MediaCentral UX, timing blocks have a minimum size of 1 second, even if the media inside of them do not fill this area. In Instinct, timing blocks are only as long as they have to be to contain media.

If you load a sequence created in Instinct that has clips shorter than 1 second, clips are displayed next to each other in the same timing block, but programmatically belong to separate timing blocks. After you make an edit, the clips are displayed in different timing blocks.

System

➤ Bug Number: RE-1065. The reactivate-cluster script assumes the primary network adapter is named “eth0”. Dell servers use a different naming convention for their network adapters. Running the reactive-cluster script on these systems breaks the cluster. Originally listed as fixed in the v2.2.2 ReadMe (RE-960), this issue reappeared in later releases.

https://support.apple.com/downloads/quicktime

https://support.apple.com/downloads/quicktime

56

Workaround: Do not use the reactivate script when performing an upgrade to MCS v2.4.0. Instead, manually bring the cluster nodes back online in the reverse order that they were taken offline.

If you have already run the reactivate script on a Dell server, see the following article on the Avid Knowledge Base for assistance in resolving the issue: http://avid.force.com/pkb/articles/en_US/troubleshooting/Cluster-not-working-after-running-reactivate-cluster-following-a-software-update

Limitations and Defects Found in Earlier Versions

Limitations and defects in are organized in the following sections:

• “Limitations and Defects Found in Version 2.3.x” on page 56










Limitations and Defects Found in Version 2.3.x

Assets Pane

➤ Bug Number: JP-2153. Found in 2.3.0. Selecting “Create Shortcut” on a MAM folder from the context menu in the Asset pane does not create a viable shortcut. When selecting the newly created shortcut, the folder will be opened in the Asset pane without a title.

Closed Captioning

➤ Bug Number: IPAM-1386. Found in 2.3.0. If you duplicate a sequence that has closed captions created or edited in MediaCentral, the duplicated sequence does not include the closed captions. If you load the duplicated sequence, the Closed Captioning pane is empty.

http://avid.force.com/pkb/articles/en_US/troubleshooting/Cluster-not-working-after-running-reactivate-cluster-following-a-software-update



57

Editing

➤ Bug Number: OS-2769. Found in 2.3.2. If you enter a timecode earlier than the earliest frame in a clip, the position indicator does not move to the first frame of the clip.

➤ Bug Number: OS-2667. Found in 2.3.0. If the Sequence pane is closed when you load an Interplay MAM sequence, then you open the Sequence pane, you cannot edit the sequence.

Workaround: Refresh the browser page and reload the sequence. As a best practice, keep the Sequence pane open.

➤ Bug Number: OS-2676. Found in 2.3.0. If the Audio pane is in the background (does not have focus), and you load a group clip in the Media pane, and then click the Audio pane, the pop-up list of audio tracks is displayed in the incorrect location.

Workaround: Switch the Media pane to Output mode, then switch back to Asset mode.

➤ Bug Number: SPEC-443. Found in 2.3.0. The media status for STP is incorrect for partially online media. For example, if you consolidate a sequence to DV 25 (partially online), then select an STP profile, the text resolution in the Media pane output mode is still shown in red for DV 25.

Workaround: Sign out, sign in again, and send to playback again.

Interplay | MAM

➤ Bug Number: MAM-2968. Found in 2.3.0. If strata are pooled in a group and no labels are provided for the group in the data model, the Strata selection list in the Logging pane does not show the strata group.

Workaround: Provide a label for the strata group in the Interplay MAM data model.

➤ Bug Number: MAM-2779. Found in 2.3.0. When using the Federated Search to find assets in an Interplay MAM system, the MAM Connector is hard-coded to read some properties that are not mandatory properties in the MAM data model. This means that the properties can be changed or removed in a customized data model and then might impair Federated Search.

Mobile Apps

➤ Bug Number: LIZ-1292. Found in 2.3.0. (Android only) If you use the position indicator to scrub through a video in the Media viewer and then play the clip, the video might not start from where you place the position indicator. This can occur when scrubbing forward or backward and might cause playback to begin at an unexpected position.

58

➤ Bug Number: LIZ-1367. Found in 2.3.0. (iOS only) If you copy a primary production cue and then paste it somewhere else in your story, the new cue is also a primary cue even after you save the changes. You should not be able to have more than one primary production cue in any story.

Playback

➤ Bug Number: MPLAY-1928. Found in 2.3.0. When accessing certain features while playing media in frame-based playback mode within MediaCentral UX in Google Chrome, you may encounter a stutter in the audio. Features that could present this issue are: adding a marker, adding a search criteria field in the Search pane, and more. This is due to a limitation in the Flash Player that is bundled with Chrome.

Workaround: Download and install the full version of Flash Player. This will add a new Flash plug-in to Chrome.

For more information follow this link to access the Avid Knowledge Base.

System

➤ Bug Number: ICI-781. Found in 2.3.1. When switching to the System Settings layout in certain versions of the Chrome browser, the user may encounter a blank (grey) user interface or potential error messages. See the following link on the Avid Knowledge Base for further detail and methods to resolve this issue:

http://avid.force.com/pkb/articles/en_US/troubleshooting/MediaCentral-Product-Alert-Chrome-version-44

➤ Bug Number: MPLAY-1943. Found in 2.3.2. When exporting an MP4 file, the user is sent a link in the Messages pane to the file download location. Selecting the link should begin the file download process. If the address (hostname) entered in the web browser does not match the hostname entered in MediaCentral UX System Settings (Player setting), a second MediaCentral UX browser tab is opened instead.

Workaround: Verify that the hostname entered in the Player settings matches the hostname entered into the web browser address bar. Alternatively, log into the second MediaCentral UX browser tab that appears and the file download will begin.





59

Editing

➤ Bug Number: OS-2481, MA-2561. Found in 2.2.0. Rarely, closing the Story pane after creating a sequence causes MediaCentral UX to become less responsive.

Workaround: Refresh the MediaCentral UX browser page.

➤ Bug Number: MA-2491. Found in 2.2.0. The Annotation feature in the Queue/Story pane, which allowed you to use Chrome’s speech to text feature to dictate a story, is not supported Chrome version 35.0 or later.

Interplay | MAM

➤ Bug Number: MAM-2377. Found in 2.2.1. If the Thumbnails pane was closed in marker-based display mode (the Markers button is selected), then you sign in again to MediaCentral UX and load an Interplay MAM asset to the Thumbnails pane, the pane freezes instead of showing thumbnails.

Workaround: Reopen the Thumbnails pane.

Media | Distribute

➤ Bug Number: MPD-1126. Found in 2.2.1. Media Distribute might not import the backtime values from iNEWS stories in the correct format: either hh:mm:ss and seconds (from 12:00 AM) — for example, 17:00:00 and 61200 [seconds].

Workaround: If the iNEWS air date or backtime values associated with your media package are not correct, manually edit the scheduled delivery information for your story.

➤ Bug Number: MPD-1148. Found in 2.2.1. When you publish a media package including video and an image, the list of packages in the Packages pane might fail to update immediately. Usually, clicking the Refresh button after 10-20 seconds updates the list.

Workaround: If clicking the Refresh button does not update the display in the Packages pane, you might have to wait a few minutes for the Java Virtual Machine (JVM) to restart. Once the JVM restarts automatically, clicking Refresh should update the display. If the problem persists, contact your MediaCentral administrator to restart the avid-mpd service.

60

To update the avid-mpd service, do the following:

• On the MediaCentral server (for single node configurations) or on the master node (for cluster configurations), open a terminal window and type the following command: service avid-mpd clean-restart

Playback

➤ Bug Number: MPLAY-1864. Found in 2.2.2. The fix for audio playback in MPLAY-1864 introduced a limitation in MediaCentral v2.2.2. After the AirSpeed 5000 proxy media has completed the final check-in to ISIS, playback within MediaCentral UX stops. Workaround: Click Play to continuing playing the clip.

➤ Bug Number: MPLAY-1794. Found in 2.2.0. In file-based playback the beginning of a clip is skipped if you move the cursor to the start then release the mouse button outside of the scrubbing area.

➤ Bug Number: MPLAY-1708. Found in 2.2.0. In file-based playback you cannot mute a clip containing MP4 mono audio tracks.

Search

➤ Bug Number: IPAM-1183. Found in 2.2.1. You use the Production Engine Bus Connector (PEBCo) service to configure the Interplay Production properties used in the Media Index search fields. Due to differences in the properties and fields used by Interplay Production and Media Index, some duplication appears in the criteria available for indexed searches with both Interplay Production and Media Index fields appearing. If you add the wrong fields as criteria, your search might not return any usable results.

The following table lists the duplicate criteria. You should use the Media Index fields for your indexed searches.

Interplay Production Property Media Index Field

Changed By Modifier

Comments Description

Created By Creator

Creation Date Created

Duration Duration

End End

61

➤ Bug Number: IPAM-1171. Found in 2.2.0. Marker positions on subclips are not displayed correctly in the indexed search results. Clicking on a marker does not open the subclip at the correct location in the Media Pane

➤ Bug Number: JP-1936. Found in 2.2.0. You cannot change the number of assets that display in the results list for a federated search using the General group in the System Settings. The default maximum number of results displayed at one time is 1000. Changing this setting has no effect on the number of results displayed in the Search pane for federated searches.

Send to Playback

➤ Bug Number: SPEC-443. Found in 2.2.0. A sequence that includes clips with partial online status might be incorrectly evaluated, so that the STP button in the Media pane is enabled even though media is not available in the target resolution. The STP process fails with the following error message:

“Remote STP process failed: Media is offline or not compatible with playback server (in "preprocess" phase).”

Workaround: Select the correct STP profile and use the MultiRez button to play the sequence in STP review mode. “Media Offline” should be displayed for the problem clip or clips. Do one of the following:

• Transcode the problem clip or clips to the target resolution.

• Consolidate the sequence to the target resolution.

Stories

➤ Bug Number: MA-2491. Found in 2.2.1. The Annotation feature in the Queue/Story pane, which allowed you to use Chrome’s speech to text feature to dictate a story, is not supported in Chrome version 35.0 or later.

Mime Type Type

Modified Date Modified

Name Name

Start Start

Interplay Production Property Media Index Field

62


Delivery

➤ Bug Number: EA-2640. If you create a Delivery profile in Interplay that includes subjobs, and use that profile for the Deliver to Me feature, MediaCentral displays the following error message: “Batched IDs list has different size than delivered assets number.” Subjobs are not supported for MediaCentral Delivery.

Editing

➤ Bug Number: OS-2262. Under some circumstances, if you load a new sequence before the original sequence was able to obtain a lock, the two sequences could become combined, leading to unexpected behavior.

➤ Bug Number: JP-1569. If you open an Assets pane on one system, using Chrome, and log out, your layout is saved. If you then log on to the same MediaCentral server, using Safari on Mac OS X, the Asset pane might be empty.

Workaround: Close the Assets pane and open it again, or reset the layout.

➤ Bug Number: PLAD-87. Metadata Pane: Custom metadata fields that are not selected as available in the Interplay Administrator (Property Layout > Custom Metadata tab) are still visible to users signed in to MediaCentral UX.

Workaround: In the Interplay Administrator, deselect the Inspector Default column before you deselect the Available column

iNEWS

➤ Bug Number: MA-2089. You can copy multiple stories from one pane to a queue or rundown in another pane by selecting the stories and then pressing Ctrl while you drag them from one pane to the other. However, pressing Ctrl also deselects the story you position the mouse pointer over as you start to drag your stories. This results in one story not being copied during the operation.

Workaround: After you copy your stories from one pane to another, select the story that was not copied with the rest, press Ctrl, and drag it to the new pane.

63

Playback

➤ Bug Number: MPLAY-1670. In file-based playback, a problem may arise if more than one user is playing the same clip. If the first user to play the asset ends the playback session, playback will stop for the second user, near the point where the session was ended. Playback beyond that point will not be possible, though partial scrubbing may work.

Workaround: Click the Pane Menu button, then click Update Media Status, twice. The clip will play as expected.

➤ Bug Number: OS-2276. In file-based playback, if you start playback from part-way along the Media Timeline then jump to the beginning of the clip, the beginning of a clip may not play. The asset continues to load from the initial position indicator only.

Workaround: Click a few times in the Media Timeline close to the first frame. The asset will load correctly.

➤ Bug Number: MPLAY-1678. For file-based playback, the audio meter does not display an audio level.

Media | Distribute

➤ Bug Number: MPD-1059. If you attach both a video and an image to a Facebook post in the Social Message pane, a message appears: “Video profile ‘[profile_name]’ configured but not associated with any story. Are you sure you want to post this message?” This is as designed and occurs because Facebook postings allow text and either a video or an image. If your media bundle includes both a video and an image, the image prevents the video from being posted to Facebook.

Workaround: Click No to dismiss the error message, remove either the video or the image from the Social Message pane, and then publish your bundle to Facebook.

Mobile Apps

➤ Bug Number: LIZ-1407. Playing back a clip or sequence with a duration that exceeds 30 minutes results in the playback stopping unexpectedly. This occurs on both iOS and Android devices.

➤ Bug Number: LIZ-1317. Avid MediaCentral UX for Android devices does not support moving or deleting production cues while in Edit mode.

64

Search

➤ Bug Number: TSL-1645. If you conduct an indexed search using Advanced Search syntax, some special characters — “.” (period) and “-” (dash) — are not recognized if your search term also includes wildcards. For example, if you search for “C0001.new.??” the two periods in the search term prevent the search from returning an asset named “C0001.new.02.”

Workaround: Search for the asset name without using a period or a dash. You can substitute a space for the special character — for example, “C0001 new ??” returns the asset named “C0001.new.02.”

➤ Bug Number: MA-588. Asset searches that make use of a timestamp (e.g. Modified Date) fail to return all the results expected. For example, an asset with a specific, known modified date might be missed.

Workaround: For reliable time-based search results, ensure the iNEWS, Interplay Production and MediaCentral servers have the same time


Delivery

➤ Bug Number: ICI-312. If a user tries to deliver an asset using Mark In to Mark Out, and a Consolidate profile does not exist in the requested resolution, the user must be a member of the Administrators group in Interplay Production. If the user is not, the job fails with the error “java.lang.IllegalArgumentException: Service:com.avid.dms.consolidateservice does not contain a profile named:default_for_delivery_resolution.”

Workaround: Create a Consolidate profile for the requested resolution.

iNEWS Community

➤ Bug Number: MA-1574. If you search for Stories, relevant results from Search Queues on remote community servers are not displayed.

MediaCentral Help

➤ Bug Number: JP-1208. The AdBlock extension in the Chrome browser can prevent Help system buttons (Contents, Index, Search, Previous Topic, and Next Topic) from displaying. Chrome extensions are not supported in MediaCentral UX.

Workaround: Disable AdBlock for the page or the domain.

65

Media Composer

➤ Bug Number: ICI-300. In an Avid editing application, if you open a sequence created in MediaCentral that uses center pan, you cannot adjust the audio panning.

➤ Bug Number: No number. If you use the MediaCentral Messages window in Media Composer to send an attachment, you might receive an error message stating that the asset you want to attach is not checked in to Interplay Production even if it is checked in, or that you do not have the necessary permission to view the asset even if you do have the proper permissions set.

Workaround: Log in to MediaCentral UX to set your Interplay Production user credentials, and then open the MediaCentral Messages window in Media Composer and attach the asset to your message.

To sign in to MediaCentral UX:

1. Open a supported browser and type the URL of your MediaCentral server.

The URL is the computer name of the server.

2. At the sign-in screen, type your user name and password.

3. Click Sign In, or press Enter or Return (Macintosh).

To add an asset to a message in the MediaCentral Messages window in Media Composer:

t Click a clip in a bin and drag it to the asset area of the message:

Player

➤ Bug Number: MPLAY-1453. Sequences containing dissolves created and rendered in Media Composer result in a vertical shift at the transition points during playback in MediaCentral. The defect is visible in low-res sequences only.

➤ Bug Number: MPLAY-1319. Saving a frame from a sequence with a particular aspect ratio (e.g. 16:9) can result in an image with a different aspect ratio (e.g. 4:3) being saved to disk. The Save as Image feature saves in the aspect ratio of the underlying image, not in the current aspect ratio of the Player.

Restrictions

➤ Bug Number: EA-2130. If a sequence includes a restriction, and you mix down the sequence, you cannot delete the restriction on the mixed-down sequence.


All limitations and defects published in previous versions of the ReadMe have been fixed.

66


Assets Pane

➤ Bug Number: CORE-3991. When you sign out and sign back in to MediaCentral UX, the Assets tab does not retain its history. For example, if you open a folder from the root of the Interplay asset tree, you cannot use the back arrow to navigate back to the root.

Workaround: Open an new Asset tab from the Launch pane.

Playback

➤ Bug Number: SPEC-1135. Loading a Master Clip or sequence created using the Media Composer Avid Media Access (AMA) workflow and FrameFlex tool results in an “Asset not supported” message appearing in the MediaCentral UX media pane.

Workaround: In Media Composer, transcode the Master Clip or sequence with the “Apply reformatting option (compatibility mode)” and “Apply color transformation (compatibility mode)” options selected and check in the transcoded sequence. The transcoded sequence loads as expected in MediaCentral UX. Alternately, to retain FrameFlex information in the Master Clip, render the sequence for use in MediaCentral UX. You cannot render a Master Clip itself.

Sequences

➤ Bug Number: None. If the Audio - Storyline audio patching settings in the Interplay Administrator are not correctly set, you cannot save an advanced sequence. The following error message is displayed: “net.nxn.JXDK.CommandFailedException: XML returned from getMetadata is empty.”

Make sure that these settings are correct. Each track must only be used once. For example, do not set both the NAT track and the VO track to A1.

n In the Audio - Source audio patching settings, the same track can be used multiple times.

➤ Bug Number: MPLAY-1171. If you edit a clip that contains markers into a sequence, but you do not have the proper permissions set in the Interplay Administrator, the operation fails with an error message: “net.nxn.JXDK.ServerCommandFailedException: Error message from the server: “Insufficient permissions.” (0x89990301).”

Workaround: The administrator needs to grant the user the permission “Can create locators.” It is not necessary to grant the permission “Can modify locators.” In this way you can allow a user to edit clips and sequences that contain markers but not modify or delete them. These settings are in the Instinct/Assist User Settings view of the Interplay Administrator.

67

Chrome Browser

➤ Bug Number: CORE-3856, JP-6. Pressing the Alt key plus another key in the Chrome Browser causes a beep. See https://code.google.com/p/chromium/issues/detail?id=105500


All limitations and defects published in Interplay Central Services V1.6 ReadMe have been fixed.


Playback

Flash Plug-in Regression: A Flash plug-in release introduced playback regressions. Subsequent versions of the Flash plug-in have addressed the issue. If you are experiencing one or more of the following:

• Long time to load asset

• Audio/video synchronization drift

Check the Flash plug-in version (right-click to view the version number in the context menu). If the version is 11.5.31.137, upgrade to the latest version of the plug-in.

➤ Bug Number: MPLAY-1571. (MediaCentral) Some AAF timelines do not relink EVS XT media properly in MediaCentral and cannot be loaded. Workaround: None.

➤ Bug Number: MPLAY-904, EA-1956. (MediaCentral UX) Clips with created in Media Composer with a horizontal effect fail to load. Workaround: None.

➤ Bug Number: MPLAY-718. (MediaCentral UX) Repeatedly clicking the “refresh” button in the Ingest Folder during EWS results in “media offline.” Workaround: Clear the cache by opening a shell on the MediaCentral Platform server and perform a “service avid-all reconfigure” at the command line.

➤ Bug Number: MPLAY-686. (MediaCentral UX) EWC playback clip length might be incorrect, resulting in black frames at the end of the clip. Workaround: Wait for EWC to complete and trigger an update media status.

➤ Bug Number: MPLAY-572. (Interplay MAM) In some cases, audio drift on playback can occur (approx. 1 second over 3 minutes). Workaround: None.

https://code.google.com/p/chromium/issues/detail?id=105500

68

➤ Bug Number: MPLAY-571. In some cases, poor playback of partially loaded clips can occur, when seeking. Workaround: None.

Audio

➤ Bug Number: OS-372. MediaCentral UX can load clips with up to 24 tracks, but you can monitor only the first 16 audio tracks of a clip.

Workaround: Disable Dynamic Relink in the Playback Service group of the MediaCentral UX System Settings layout. Note that this affects all Dynamic Relink operations in MediaCentral UX, such as send to playback (STP).

Group Clips

➤ Bug Number: ICI-9. Playback of a 23.976p group clip in multi-angle view might stutter or stop the first time you load the clip.

Workaround: While in multi-angle view, park at the beginning of the clip and wait for a few seconds before playing back. If you encounter a stuttering during playback, pause and wait for approximately 20s before playing back again.

➤ Bug Number: SPEC-121. A Media Composer user can add markers to a group clip, but these markers do not persist in the master clips. If you open a group clip with markers checked in from a Media Composer system, MediaCentral UX adds the markers to the underlying master clips. If the group clip is then checked back in, markers are removed from the group clip and copied to the master clips.

Sequences

➤ Bug Number: EA-490. If you drag an MediaCentral UX advanced sequence from the Interplay Window to a bin, the bin displayed a custom field named “sequencejson.” This column does not include useful information.

c Do not edit this field or the sequence could be corrupted.

Searching

➤ Bug Number: EA-698. An MediaCentral UX administrator can specify the maximum number of items displayed in the Search pane at a time (System Settings, General). When the user performs a search and the search results to be displayed are more than the number specified and the user sorts the results, then the sorting might not show all assets found by the server. Especially folders might not be shown.

69

Restrictions

➤ Bug Number: EA-2829. If a sequence contains restricted material and the restricted segments are removed by trimming, the DRM column and the State column continue to show the restricted icon.

Chrome Browser

➤ Bug Number: MPLAY-917. (Chrome browser) In the Media viewer, if you right-click to open the Flash context menu and leave it open for approximately 15 seconds, a message box is displayed that the page has become unresponsive.

Workaround: Close the context menu. The warning is hidden and the player remains stable.


All limitations and defects published in previous versions of the ReadMe have been fixed.


Edit While Capture (EWC)

➤ Bug Number: PLAD-154. When editing a clip while it is still being captured (in-progress clip), you cannot create a subclip that includes material close to the ingest limit. Generally, there is a delay of 6 to 12 minutes within which this is not possible. The amount of delay depends on the ingest device and the media resolution.

Workaround: If you attempt to make a subclip that is too close to the ingest limit, a message appears indicating the timecode limit at which subclip creation should be possible. The timecode in the message is Absolute; that is, it is given as the time offset from the first frame in the asset or sequence. You have two choices. You can wait a few minutes until more media has been ingested and try again. Or, you can create a subclip shorter than the timecode presented in the message. To simplify subclip creation, use the timecode display menu button in the Media pane to set the timecode presentation to Absolute.

Playback

➤ Bug Number: MPLAY-1669. (MediaCentral UX) Sometimes when you capture clips and monitor them while capture is occurring, the final clip after recording is complete has a few extra black frames added. Workaround: Choose Update Media Status from the player drop-down options menu.

70

➤ Bug Number: MPLAY-1571. (MediaCentral UX) Media captured to Interplay by an EVS device cannot be opened by MediaCentral UX. Workaround: Open the captured asset using Media Composer and check it in again.

➤ Bug Number: MPLAY-1581. (All) The operating system reports memory usage for all Flash activity, and based on this value, the ICPS Flash player manages assets in its local cache. If you have other instances of Flash open (for example a You Tube player), ICPS asset caching will be less efficient. Workaround: Close all other instances of Flash.

➤ Bug Number: MPLAY-1313 . (MediaCentral UX) Panning audio full right in Mono mode reduces the volume of the audio. Workaround: None.

Sequences and Sequence Pane

➤ Bug Number: ICML-1934. If you open a script sequence created in Interplay Central V1.2 directly from the Asset list, the sequence opens as a read-only sequence and you cannot edit it. If you open the script sequence through an iNEWS story, you can edit the sequence.

Subclips

➤ Bug Number: ICML-1845. If you add a subclip to the sequence timeline, you cannot trim the subclip outside the borders of the subclip.

Workaround: Load the original master clip (optionally, using Match Frame) and create a new subclip that includes the material that you want.

Send to Playback

➤ Bug Number: ICTD-316, UDevC00176883. If a sequence includes a title effect, and you attempt to send it to a playback device, the job fails with an error message “Remote STP process failed.”

➤ Bug Number: WANW-2768. Send to playback of a Long GOP sequence fails if the send to playback profile specifies Direct Out and the sequence contains an odd number of audio tracks. Workaround: Use a profile with Audio Target Mixdown Mode set to Stereo. If you want to use Direct Out as the Mixdown mode, add an extra track by configuring NAT or SOT as two channels in the Interplay Administrator Application Database settings.

71

Assets Pane

➤ Bug Number: IPC-1936. If a sequence contains a video dissolve created in Interplay Central v1.3, the State column in the Assets pane does not show the supported for playback icon (green arrow). These sequences are supported for playback. If a dissolve was created by Media Composer and has not been rendered, the icon is correctly displayed.

Apps for iPad and iPhone

➤ Bug Number: ICMOB-1108. If a user account is created with the option “User must change password on next sign-in,” the user cannot sign-in to the MediaCentral UX Mobile or Tablet app. No message is displayed.

Chrome Frame and Interplay Explorer 9

➤ Bug Number: CORE-1643. If you are using Chrome Frame with Interplay Explorer 9, you cannot use an iNEWS link (deep link) more than once. The first time you open the link in the browser, the MediaCentral UX panes update correctly. If you try to open the link a second time, the MediaCentral UX panes do not update. Workaround: Close the browser and open it again.

➤ Bug Number: ICAJ-2422. If you are using Chrome Frame with Interplay Explorer 9, and you click the microphone (Annotation) button in the Queue/Story pane to enable speech-to-text, Chrome Frame crashes and Internet Explorer displays a blank page.

Updating a Sequence after Delivery

When you create a sequence with clips that have been delivered from another workgroup through Interplay Delivery, the media status of the sequence is not automatically updated in the Interplay Production database.

• If a sequence consists completely of clips delivered from another workgroup, the status is displayed as offline. In MediaCentral UX, the sequence is shown in gray in the Asset pane.

• If a sequence consists of both delivered clips and non-delivered clips, the status is displayed as nearline.

Workaround: Load the delivered clips in Media Composer, use the Relink command, and check the clips in to Interplay Production again. Then either update the Media status in Interplay Access (Update Status from Media Indexer command) or check the sequence in from Media Composer again.

n The command “Update Status from Media Indexer” updates the online media status until the next checkin.

72

OMF Support

➤ OMF workflows are no longer supported in MediaCentral UX. OMF-wrapped media has to be converted to MXF prior to using it in MediaCentral UX. This limitation applies to video playback and to the sequence timeline.

73

Legal NoticesProduct specifications are subject to change without notice and do not represent a commitment on the part of Avid Technology, Inc.

This product is subject to the terms and conditions of a software license agreement provided with the software. The product may only be used in accordance with the license agreement.

This product may be protected by one or more U.S. and non-U.S patents. Details are available at www.avid.com/patents.

Copyright © 2015 Avid Technology, Inc. and its licensors. All rights reserved.

The following disclaimer is required by Apple Computer, Inc.:APPLE COMPUTER, INC. MAKES NO WARRANTIES WHATSOEVER, EITHER EXPRESS OR IMPLIED, REGARDING THIS PRODUCT, INCLUDING WARRANTIES WITH RESPECT TO ITS MERCHANTABILITY OR ITS FITNESS FOR ANY PARTICULAR PURPOSE. THE EXCLUSION OF IMPLIED WARRANTIES IS NOT PERMITTED BY SOME STATES. THE ABOVE EXCLUSION MAY NOT APPLY TO YOU. THIS WARRANTY PROVIDES YOU WITH SPECIFIC LEGAL RIGHTS. THERE MAY BE OTHER RIGHTS THAT YOU MAY HAVE WHICH VARY FROM STATE TO STATE.

The following disclaimer is required by Sam Leffler and Silicon Graphics, Inc. for the use of their TIFF library:Copyright © 1988–1997 Sam Leffler Copyright © 1991–1997 Silicon Graphics, Inc.

Permission to use, copy, modify, distribute, and sell this software [i.e., the TIFF library] and its documentation for any purpose is hereby granted without fee, provided that (i) the above copyright notices and this permission notice appear in all copies of the software and related documentation, and (ii) the names of Sam Leffler and Silicon Graphics may not be used in any advertising or publicity relating to the software without the specific, prior written permission of Sam Leffler and Silicon Graphics.

THE SOFTWARE IS PROVIDED “AS-IS” AND WITHOUT WARRANTY OF ANY KIND, EXPRESS, IMPLIED OR OTHERWISE, INCLUDING WITHOUT LIMITATION, ANY WARRANTY OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.

IN NO EVENT SHALL SAM LEFFLER OR SILICON GRAPHICS BE LIABLE FOR ANY SPECIAL, INCIDENTAL, INDIRECT OR CONSEQUENTIAL DAMAGES OF ANY KIND, OR ANY DAMAGES WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER OR NOT ADVISED OF THE POSSIBILITY OF DAMAGE, AND ON ANY THEORY OF LIABILITY, ARISING OUT OF OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE.

The following disclaimer is required by the Independent JPEG Group:This software is based in part on the work of the Independent JPEG Group.

This Software may contain components licensed under the following conditions:Copyright (c) 1989 The Regents of the University of California. All rights reserved.

Redistribution and use in source and binary forms are permitted provided that the above copyright notice and this paragraph are duplicated in all such forms and that any documentation, advertising materials, and other materials related to such distribution and use acknowledge that the software was developed by the University of California, Berkeley. The name of the University may not be used to endorse or promote products derived from this software without specific prior written permission. THIS SOFTWARE IS PROVIDED ``AS IS'' AND WITHOUT ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, WITHOUT LIMITATION, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE.

Copyright (C) 1989, 1991 by Jef Poskanzer.

Permission to use, copy, modify, and distribute this software and its documentation for any purpose and without fee is hereby granted, provided that the above copyright notice appear in all copies and that both that copyright notice and this permission notice appear in supporting documentation. This software is provided "as is" without express or implied warranty.

Copyright 1995, Trinity College Computing Center. Written by David Chappell.

Permission to use, copy, modify, and distribute this software and its documentation for any purpose and without fee is hereby granted, provided that the above copyright notice appear in all copies and that both that copyright notice and this permission notice appear in supporting documentation. This software is provided "as is" without express or implied warranty.

Copyright 1996 Daniel Dardailler.

http://www.avid.com/US/about-avid/legal-notices/patent-marking

74

Permission to use, copy, modify, distribute, and sell this software for any purpose is hereby granted without fee, provided that the above copyright notice appear in all copies and that both that copyright notice and this permission notice appear in supporting documentation, and that the name of Daniel Dardailler not be used in advertising or publicity pertaining to distribution of the software without specific, written prior permission. Daniel Dardailler makes no representations about the suitability of this software for any purpose. It is provided "as is" without express or implied warranty.

Modifications Copyright 1999 Matt Koss, under the same license as above.

Copyright (c) 1991 by AT&T.

Permission to use, copy, modify, and distribute this software for any purpose without fee is hereby granted, provided that this entire notice is included in all copies of any software which is or includes a copy or modification of this software and in all copies of the supporting documentation for such software.

THIS SOFTWARE IS BEING PROVIDED "AS IS", WITHOUT ANY EXPRESS OR IMPLIED WARRANTY. IN PARTICULAR, NEITHER THE AUTHOR NOR AT&T MAKES ANY REPRESENTATION OR WARRANTY OF ANY KIND CONCERNING THE MERCHANTABILITY OF THIS SOFTWARE OR ITS FITNESS FOR ANY PARTICULAR PURPOSE.

This product includes software developed by the University of California, Berkeley and its contributors.

The following disclaimer is required by Paradigm Matrix:Portions of this software licensed from Paradigm Matrix.

The following disclaimer is required by Ray Sauers Associates, Inc.:“Install-It” is licensed from Ray Sauers Associates, Inc. End-User is prohibited from taking any action to derive a source code equivalent of “Install-It,” including by reverse assembly or reverse compilation, Ray Sauers Associates, Inc. shall in no event be liable for any damages resulting from reseller’s failure to perform reseller’s obligation; or any damages arising from use or operation of reseller’s products or the software; or any other damages, including but not limited to, incidental, direct, indirect, special or consequential Damages including lost profits, or damages resulting from loss of use or inability to use reseller’s products or the software for any reason including copyright or patent infringement, or lost data, even if Ray Sauers Associates has been advised, knew or should have known of the possibility of such damages.

The following disclaimer is required by Videomedia, Inc.:“Videomedia, Inc. makes no warranties whatsoever, either express or implied, regarding this product, including warranties with respect to its merchantability or its fitness for any particular purpose.”

“This software contains V-LAN ver. 3.0 Command Protocols which communicate with V-LAN ver. 3.0 products developed by Videomedia, Inc. and V-LAN ver. 3.0 compatible products developed by third parties under license from Videomedia, Inc. Use of this software will allow “frame accurate” editing control of applicable videotape recorder decks, videodisc recorders/players and the like.”

The following disclaimer is required by Altura Software, Inc. for the use of its Mac2Win software and Sample Source Code:©1993–1998 Altura Software, Inc.

The following disclaimer is required by 3Prong.com Inc.:Certain waveform and vector monitoring capabilities are provided under a license from 3Prong.com Inc.

The following disclaimer is required by Interplay Entertainment Corp.:The “Interplay” name is used with the permission of Interplay Entertainment Corp., which bears no responsibility for Avid products.

This product includes portions of the Alloy Look & Feel software from Incors GmbH.

This product includes software developed by the Apache Software Foundation (http://www.apache.org/).

© DevelopMentor

This product may include the JCifs library, for which the following notice applies:JCifs © Copyright 2004, The JCIFS Project, is licensed under LGPL (http://jcifs.samba.org/). See the LGPL.txt file in the Third Party Software directory on the installation CD.

Avid Interplay contains components licensed from LavanTech. These components may only be used as part of and in connection with Avid Interplay.

This product includes FFmpeg, which is covered by the GNU Lesser General Public License.

This product includes software that is based in part of the work of the FreeType Team.

http://www.apache.org/

http://jcifs.samba.org/

75

This software is based in part on the work of the Independent JPEG Group.

This product includes libjpeg-turbo, which is covered by the wxWindows Library License, Version 3.1.

Portions copyright 1994, 1995, 1996, 1997, 1998, 1999, 2000, 2001, 2002 by Cold Spring Harbor Laboratory. Funded under Grant

P41-RR02188 by the National Institutes of Health.

Portions copyright 1996, 1997, 1998, 1999, 2000, 2001, 2002 by Boutell.Com, Inc.

Portions relating to GD2 format copyright 1999, 2000, 2001, 2002 Philip Warner.

Portions relating to PNG copyright 1999, 2000, 2001, 2002 Greg Roelofs.

Portions relating to gdttf.c copyright 1999, 2000, 2001, 2002 John Ellson ([email protected]).

Portions relating to gdft.c copyright 2001, 2002 John Ellson ([email protected]).

Portions relating to JPEG and to color quantization copyright 2000, 2001, 2002, Doug Becker and copyright (C) 1994, 1995, 1996, 1997, 1998, 1999, 2000, 2001, 2002, Thomas G. Lane. This software is based in part on the work of the Independent JPEG Group. See the file README-JPEG.TXT for more information. Portions relating to WBMP copyright 2000, 2001, 2002 Maurice Szmurlo and Johan Van den Brande.

Permission has been granted to copy, distribute and modify gd in any context without fee, including a commercial application, provided that this notice is present in user-accessible supporting documentation.

This does not affect your ownership of the derived work itself, and the intent is to assure proper credit for the authors of gd, not to interfere with your productive use of gd. If you have questions, ask. "Derived works" includes all programs that utilize the library. Credit must be given in user-accessible documentation.

This software is provided "AS IS." The copyright holders disclaim all warranties, either express or implied, including but not limited to implied warranties of merchantability and fitness for a particular purpose, with respect to this code and accompanying documentation.

Although their code does not appear in gd, the authors wish to thank David Koblas, David Rowley, and Hutchison Avenue Software Corporation for their prior contributions.

This product includes software developed by the OpenSSL Project for use in the OpenSSL Toolkit (http://www.openssl.org/)

MediaCentral may use OpenLDAP. Copyright 1999-2003 The OpenLDAP Foundation, Redwood City, California, USA. All Rights Reserved. OpenLDAP is a registered trademark of the OpenLDAP Foundation.

Media | Distribute enables its users to access certain YouTube functionality, as a result of Avid's licensed use of YouTube's API. The charges levied by Avid for use of Media | Distribute are imposed by Avid, not YouTube. YouTube does not charge users for accessing YouTube site functionality through the YouTube APIs.

Media | Distribute uses the bitly API, but is neither developed nor endorsed by bitly.

Android is a trademark of Google Inc.

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.

Trademarks003, 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 Ignite, 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, Beat Detective, Beauty Without The Bandwidth, Beyond Reality, BF Essentials, Bomb Factory, Bruno, C|24, CaptureManager, ChromaCurve, ChromaWheel, Cineractive Engine, Cineractive Player, Cineractive Viewer, Color Conductor, Command|24, Command|8, Control|24, Cosmonaut Voice, CountDown, d2, d3, DAE, D-Command, D-Control, Deko, DekoCast, D-Fi, D-fx, Digi 002, Digi 003, DigiBase, 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, Do More, DPP-1, D-Show, DSP Manager, DS-StorageCalc, DV Toolkit, DVD Complete, D-Verb, Eleven, EM, Euphonix, EUCON, EveryPhase, Expander, ExpertRender, Fader Pack, Fairchild, FastBreak, Fast Track, Film Cutter, FilmScribe, Flexevent, FluidMotion, Frame Chase, FXDeko,

76

HD Core, HD Process, HDpack, Home-to-Hollywood, HYBRID, HyperSPACE, HyperSPACE HDCAM, iKnowledge, Image Independence, Impact, Improv, iNEWS, iNEWS Assign, iNEWS ControlAir, InGame, Instantwrite, Instinct, Intelligent Content Management, Intelligent Digital Actor Technology, IntelliRender, Intelli-Sat, Intelli-sat Broadcasting Recording Manager, InterFX, Interplay, inTONE, Intraframe, iS Expander, iS9, iS18, iS23, iS36, ISIS, IsoSync, LaunchPad, LeaderPlus, LFX, Lightning, Link & Sync, ListSync, LKT-200, Lo-Fi, MachineControl, Magic Mask, Make Anything Hollywood, make manage move | media, Marquee, MassivePack, Massive Pack Pro, Maxim, Mbox, Media Composer, MediaFlow, MediaLog, MediaMix, Media Reader, Media Recorder, MEDIArray, MediaServer, MediaShare, MetaFuze, MetaSync, MIDI I/O, Mix Rack, Moviestar, MultiShell, NaturalMatch, NewsCutter, NewsView, NewsVision, Nitris, NL3D, NLP, NSDOS, NSWIN, OMF, OMF Interchange, OMM, OnDVD, Open Media Framework, Open Media Management, Painterly Effects, Palladium, Personal Q, PET, Podcast Factory, PowerSwap, PRE, ProControl, ProEncode, Profiler, Pro Tools, Pro Tools|HD, Pro Tools LE, Pro Tools M-Powered, Pro Transfer, 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, ScriptSync, SecureProductionEnvironment, Serv|GT, Serv|LT, Shape-to-Shape, ShuttleCase, Sibelius, SimulPlay, SimulRecord, Slightly Rude Compressor, Smack!, Soft SampleCell, Soft-Clip Limiter, SoundReplacer, SPACE, SPACEShift, SpectraGraph, SpectraMatte, SteadyGlide, Streamfactory, Streamgenie, StreamRAID, SubCap, Sundance, Sundance Digital, SurroundScope, Symphony, SYNC HD, SYNC I/O, Synchronic, SynchroScope, Syntax, TDM FlexCable, TechFlix, Tel-Ray, Thunder, TimeLiner, 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, Transit, TransJammer, Trillium Lane Labs, TruTouch, UnityRAID, Vari-Fi, Video the Web Way, VideoRAID, VideoSPACE, VTEM, Work-N-Play, Xdeck, X-Form, Xmon and XPAND! are either registered trademarks or trademarks of Avid Technology, Inc. in the United States and/or other countries.

Avid MediaCentral Platform Services v2.4.1 ReadMe • Revised August 26, 2016 • This document is distributed by Avid in online (electronic) form only, and is not available for purchase in printed form.

Documents

Version 2.4.1 ReadMeresources.avid.com/SupportFiles/attach/ICS/MCS_V2... · 2/4/2016 · As of MediaCentral UX V2.3, the following browsers are no longer tested or supported: †