1. No category

Avid MediaCentral Platform Services
®
ReadMe Version 2.2.1
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
Date Revised
Changes Made
April 30, 2015
MediaCentral 2.2.1 Update
March 26, 2015
MediaCentral 2.2.0 First Publication
Contents
About MediaCentral Platform Services Version 2.2.1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2
Compatibility Notes and Issues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
Security Updates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
Installing MediaCentral Platform Services Version 2.2.0 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
Installing MediaCentral Platform Services Version 2.2.1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
Installing the Media | Distribute Update . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
New Features in MediaCentral | UX Version 2.2.0 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
About MediaCentral Platform Services Version 2.2.1
Fixed in Version 2.2.1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38
Fixed in Version 2.2.0 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42
Additional Documentation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45
Limitations and Defects Found in Version 2.2.1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48
Limitations and Defects Found in Version 2.2.0 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50
Limitations and Defects Found in Earlier Versions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52
Legal Notices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63
About MediaCentral Platform Services Version 2.2.1
MediaCentral Platform Services (MCS) v2.2.1 is a patch release that provides bug fixes. It
requires prior installation of MCS v2.2.0. This ReadMe contains all information contained in the
previously published MCS v2.2.0 ReadMe.
For more information, see the following topics:
•
“Installing MediaCentral Platform Services Version 2.2.1” on page 21
•
“Fixed in Version 2.2.1” on page 38
•
“Limitations and Defects Found in Version 2.2.1” on page 48
Documentation
For the latest information on MediaCentral, see the documentation available from the
MediaCentral documentation page of the Avid Knowledge Base:
http://avid.force.com/pkb/articles/en_US/readme/Avid-MediaCentral-Version-2-2-x-Documenta
tion
Localized User Interface and Documentation
The MediaCentral UX user interface and Help are available in the following languages:
•
English
•
French
•
German
•
Italian
•
Japanese
2
Compatibility Notes and Issues
•
Korean
•
Simplified Chinese
•
Spanish
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-2-Documentati
on-Translated
Compatibility Notes and Issues
This section contains compatibility information for MediaCentral Platform Services and its
related products.
MediaCentral Platform Services 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.2.1.
To determine the version and build numbers:
1. Connect to the MediaCentral Platform server console as the root user.
2. Type the following command:
ics_version
3. Press Enter.
Version and build numbers are returned as follows:
UMS Version: 2.2.1.0-1.noarch
ICPS Version: 2.2.1.0-9677989AVID.x86_64
ICPS manager Version: 2.2.104-1.noarch
ACS Version: 2.2.0-20150313.1709.x86_64
System ID: xxxxxxxxxxx
ICS installer: 2.2.1(Build 66)
n
The System ID is an 11-digit number used in support calls, entered during system configuration.
3
Compatibility Notes and Issues
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.0.23 for
MediaCentral v2.2.1.
Compatibility: MediaCentral Platform
This section contains compatibility information related to MediaCentral Platform v2.2.1.
For information about 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
Qualified Products
MediaCentral Platform v2.2.1 is qualified with the following products.
Product
Version
MediaCentral UX
v2.2.1
Media Distribute
v2.2.1
Media Composer Cloud
Latest plug-in for:
•
Media Composer v8.0.1, 8.1, 8.2.x (includes
NewsCutter option)
•
Media Composer v6.5.x, 7.0.x
•
NewsCutter v10.5.x, 11.0.x
Interplay MAM Connector (plug-in)
v1.1.0
Interplay MAM
v5.0, v5.1
4
Compatibility Notes and Issues
Operating Systems for Servers
The following table lists minimum supported versions for MediaCentral Platform servers.
Server
Version
MediaCentral Platform
Red Hat Enterprise Linux (RHEL) 6.5 (64-bit) plus approved
security patches. See “Security Updates” on page 16.
Platform requires that you set the
c MediaCentral
language for RHEL to English. English is set
automatically by the MediaCentral Platform
installation scripts. Do not change the input language
afterwards.
GlusterFS 3.4.0 (Required if file caching is used and you set up
a cluster). See “Obtaining Gluster” on page 18.
MediaCentral Distribution Service
Microsoft Windows 7
Systems and Storage
The following table lists minimum supported versions for Interplay and ISIS components.
Product
Version
Interplay Production Engine
•
V2.5 and later
•
V2.6 and later for
•
-
DNxHD 85/100
-
Sphere 2 Mbps proxy
-
Multi-ISIS
V3.1 and later for
-
MediaCentral Distribution Service
•
Media Index
V3.2, V3.2.1
V3.2 and V3.2.1are qualified with the following
components:
5
•
Interplay Central v2.2.1
•
Interplay Engine v3.2
•
Production Services Engine v3.2
•
Interplay Transcode v3.2
•
Interplay STP Encode v3.2
Compatibility Notes and Issues
Product
Version
Interplay Transcode
•
V2.7.0 plus V2.7.0.1 patch and later
•
V2.7.5 and later
Supported by Interplay Engine v2.5 and later.
Interplay STP Encode
•
V2.7.0 plus V2.7.0.1 patch and later
•
V2.7.5 and later
Supported by Interplay Engine v2.5 and later.
Interplay Production Services Automation
•
V3.2 and later.
Supported by Interplay Engine v2.5 and later.
Interplay Consolidate
•
V3.2 and later.
Supported by Interplay Engine v2.5 and later.
Avid iNEWS
•
V3.4.3 and later
ISIS client (Linux version)
•
V4.7.4
•
V4.0.3, V4.0.4 System Director
•
V4.5 System Director
•
V4.6 System Director
•
V4.7, V4.7.3, 4.7.4 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 client is automatically installed
c The
with the MCS software. Do not update the
ISIS client on the MediaCentral Platform
server unless otherwise documented and
approved by Avid.
ISIS | 7500, ISIS | 7000
6
Compatibility Notes and Issues
Product
Version
ISIS | 5500, ISIS | 5000
•
V4.0.3 System Director
•
V4.5 System Director
•
V4.6, V4.6.1 System Director
•
V4.7, V4.7.3, 4.7.4 System Director
•
GigE and 10GigE support
•
V4.1 System Director
•
V4.2 System Director
•
V4.5 System Director
•
V4.6, V4.6.1 System Director
•
V4.7, V4.7.3, 4.7.4 System Director
•
GigE and 10GigE support
•
Only supports real-time playback of proxy
material that is 3Mb/s or less.
ISIS | 2500, ISIS | 2000
For playback of group clips, a 10 GigE connection between the MediaCentral Platform 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.
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.
The following table lists the supported browsers for MediaCentral UX. This table also lists the
tested versions of the browsers. Other versions might work but have not been tested.
Browsers for MediaCentral UX
Browser
Operating System
Tested
Version
Google Chrome
Microsoft Windows 7, Windows 8.1
41.0.2272.76 m
Safari 6.0.3 and
later versions of
Safari 6
Mac OS X 10.7 (Lion), Mac OS X 10.8 (Mountain
Lion)
7
Compatibility Notes and Issues
Browsers for MediaCentral UX
Tested
Version
Browser
Operating System
Safari 7
Mac OS X 10.9 (Mavericks)
Safari 8
Mac OS X 10.10 (Yosemite)
8.0.3 (10600.3.18)
Internet Explorer 9 Microsoft Windows 7, Windows 8.1
32-bit with Chrome
Frame plug-in
The minimum size for a browser window is 1024 x 768 pixels. If the browser window is smaller,
some UI elements might not be displayed.
Tablets for MediaCentral | UX
The MediaCentral UX tablet app is available for the following tablets and operating systems.
Device
Version
iPad®
iOS 7, iOS 8
Android tablets
Android 4.4 through 4.4.4; 4.4W through 4.4W2; 5.0 through 5.1
Phones for MediaCentral | UX
The MediaCentral UX mobile app is available for the following phones and operating systems.
Phone
Version
iPhone®
iOS 7, iOS 8
Android smart phones
Android 4.4 through 4.4.4; 4.4W through 4.4W2; 5.0 through 5.1
You can install the MediaCentral UX mobile app on Android devices with the qualified
operating system versions listed in this section. Note that Avid has tested and supports the
MediaCentral UX mobile app only on the following smart phones:
•
Nexus 5
•
Samsung Galaxy S4 mini
8
Compatibility Notes and Issues
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 Central and MediaCentral | UX Device Compatibility
The following table lists which devices (tablets and phones) and operating systems are
compatible with which versions of the MediaCentral UX app. Gen A refers to devices that
cannot install iOS 7 (iPad 1, iPod 4, iPhone 3GS).
Device
Avid Central 1.8 MediaCentral UX 2.0
MediaCentral UX 2.1 MediaCentral UX 2.2
Gen A, iOS 6 Not Supported
Not Supported
Not Supported
Not Supported
Gen B, iOS 6 Not Supported
Not Supported
Not Supported
Not Supported
Gen B, IOS 7 Supported
Supported
Supported
Supported
Gen B, IOS 8 Supported
Supported
Supported
Supported
Android OS
Supported
Supported
Supported
Supported
The following table lists which MediaCentral servers are compatible with which versions of the
MediaCentral UX app.
Server
Avid Central 1.8 MediaCentral UX 2.0 MediaCentral UX 2.1
MediaCentral UX 2.2
ICS v1.3
Not Supported
Not Supported
Not Supported
Not Supported
ICS v1.4
Not Supported
Not Supported
Not Supported
Not Supported
ICS v1.5
Supported
Not Supported
Not Supported
Not Supported
ICS v1.6
Supported
Not Supported
Not Supported
Not Supported
ICS v1.7
Supported
Supported
Supported
Supported
ICS v1.8
Supported
Supported
Supported
Supported
MCS v2.0
Not Supported
Supported
Supported
Supported
MCS v2.1
Not Supported
Not Supported
Supported
Supported
MCS v2.2
Not Supported
Not Supported
Supported
Supported
9
Compatibility Notes and Issues
Compatibility: Interplay | MAM and MAM Connector
The following table presents Interplay | MAM compatibility with MCS.
Interplay | MAM Version
MCS Version
Interplay MAM 5.1/5.0
MediaCentral Services 2.2.0 / 2.2.1
Interplay MAM 5.0.1
MediaCentral Services 2.1.1/2.1.3
Interplay MAM 5.0
MediaCentral Services 2.1
Interplay MAM 4.3.6
Interplay Central Services 1.8.0.2/1.8.1
Interplay MAM 4.3.5
Interplay Central Services 1.8.0
Interplay MAM 4.3.4
Interplay Central Services 1.7.1
Interplay MAM 4.3.3
Interplay Central Services 1.7
Interplay MAM 4.3.2
Interplay Central Services 1.6
Interplay MAM 4.3.1
Interplay Central Services 1.4.1/1.5.0
Interplay MAM 4.3
Interplay Central Services 1.4.1
Interplay MAM 4.2.2.1
Interplay Central Services 1.4
n
ICS 1.3, MCS 2.0 and MCS 2.0.1 are not supported by any version of Interplay | MAM.
The MAM connector enables all Interplay | MAM workflows in MediaCentral UX. The
following installed components are necessary for the current version of the MAM connector:
•
MCS v2.2.x
•
Interplay MAM v5.1/v5.0
•
ISIS client (Linux version) v4.7.4
•
RHEL v6.5
10
Compatibility Notes and Issues
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
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.
11
Compatibility Notes and Issues
Media Formats Supported for Playback
The following table lists 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.
Media Format
Support for Playback
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
Avid JFIF 2:1, 3:1, 10:1, 20:1
25, 29.97 only
DNxHD 1080 36-40-45
All frame rates
DNxHD 1080 115-120-145
All frame rates
DNxHD 1080 175-185-220
All frame rates
DNxHD 1080 175X-185X-220X
All frame rates
Media Composer Cloud only
DNxHD 720 75-145
50, 59.94 only
DNxHD 720 110-220
50, 59.94 only
220 Media Composer Cloud only
DNxHD 720 110X-220X
50, 59.94 only
220X Media Composer Cloud only
12
Compatibility Notes and Issues
Media Format
Support for Playback
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
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
13
Compatibility Notes and Issues
Media Formats Supported for MediaCentral STP
The following table lists media formats supported for send to playback (STP) operations for
MediaCentral.
Media Format
Frame Rate
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
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
14
Notes
Compatibility Notes and Issues
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
348 px
400 px
480 px
560 px
640 px
720 px
960 px
Quality
Value
Peak
Valley
Typical
Good
40
5.400Mbps
2.520Mbps
3.440Mbps
Better
60
6.600Mbps
2.840Mbps
4.380Mbps
Best
80
9.000Mbps
3.480Mbps
5.690Mbps
Good
40
6.400Mbps
2.840Mbps
4.690Mbps
Better
60
8.200Mbps
3.320Mbps
5.000Mbps
Best
80
11.650Mbps
4.200Mbps
6.780Mbps
Good
40
8.400Mbps
3.320Mbps
4.985Mbps
Better
60
11.400Mbps
3.880Mbps
6.300Mbps
Best
80
15.400Mbps
5.080Mbps
9.480Mbps
Good
40
11.295Mbps
4.179Mbps
6.529Mbps
Better
60
14.868Mbps
5.023Mbps
8.547Mbps
Best
80
21.009Mbps
6.694Mbps
12.284Mbps
Good
40
14.324Mbps
5.029Mbps
8.098Mbps
Better
60
18.991Mbps
6.131Mbps
10.735Mbps
Best
80
27.011Mbps
8.315Mbps
15.616Mbps
Good
40
17.757Mbps
5.993Mbps
9.878Mbps
Better
60
23.664Mbps
7.338Mbps
13.215Mbps
Best
80
33.814Mbps
10.152Mbps
19.392Mbps
Good
40
30.480Mbps
9.566Mbps
16.472Mbps
Better
60
40.980Mbps
12.046Mbps
22.405Mbps
Best
80
59.028Mbps
16.959Mbps
33.385Mbps
The next table explains the contents in detail.
15
Security Updates
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
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
RHEL v6.5 is required for MediaCentral v1.8.1, MediaCentral v2.0.x, MediaCentral v2.1.x, and
MediaCentral v2.2.x.
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-a
s-Heartbleed
16
Installing MediaCentral Platform Services Version 2.2.0
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-716
9
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-pr
oducts
Installing MediaCentral Platform Services Version
2.2.0
The MediaCentral Platform Services (MCS) v2.2.0 installation package is available as a full
installation package, for upgrading or new installations.
•
For systems running MediaCentral Services 2.1.x (or earlier), see the MediaCentral
Platform Services v2.2 Upgrading Guide.
•
For new systems, see the MediaCentral Platform Services v2.2 Installation and
Configuration Guide.
Be sure to download the latest version of these documents from the MediaCentral page on the
Avid Knowledge Base:
http://avid.force.com/pkb/articles/en_US/readme/Avid-MediaCentral-Version-2-2-x-Documenta
tion
c
You must install MCS v2.2.0 before you install the MCS v2.2.1 update.
For information about setting up multi-zone configurations see the MediaCentral Platform
Services v2.2 Installation and Configuration Guide.
For information about setting up Media Index, see the Media Index Configuration Guide,
available internally.
17
Installing MediaCentral Platform Services Version 2.2.0
n
(RE-894) A problem with configuration of the mongo database that affected new MCS v2.1
installations has been fixed in MCS v2.2.0.
Obtaining the MCS Installation Package
MediaCentral Platform Services installation packages are available from the Avid Download
Center.
MediaCentral installation packages:
•
MediaCentral_Services_2.2.0_Linux.zip
MAM Connector installation package (if applicable):
•
n
MediaCentral_MAM_Connector_1.1.0_Linux.zip
MediaCentral 2.2.1 does not include an update for the MAM Connector. See the MediaCentral
Platform Services 2.2 Installation and Configuration Guide for details.
Obtaining Gluster
If you are installing Gluster, note that as of MediaCentral Platform Services v2.0 a new version
of Gluster is required, including additional Gluster packages. Navigate to the download directory
at gluster.org containing the GlusterFS version supported by MediaCentral Platform Services
v2.2.x:
http://download.gluster.org/pub/gluster/glusterfs/3.4/3.4.0/RHEL/epel-6Server/x86_64
Download the following six packages:
•
glusterfs-3.4.0-8.el6.x86_64.rpm
•
glusterfs-cli-3.4.0-8.el6.x86_64.rpm
•
glusterfs-fuse-3.4.0-8.el6.x86_64.rpm
•
glusterfs-geo-replication-3.4.0-8.el6.x86_64.rpm
•
glusterfs-libs-3.4.0-8.el6.x86_64.rpm
•
glusterfs-server-3.4.0-8.el6.x86_64.rpm
18
Installing MediaCentral Platform Services Version 2.2.0
Migrating User Settings from UMS to USS During an Upgrade
Backing up and restoring system settings and the MCS database is a regular part of some
upgrading paths. To recap, for upgrades involving an OS change (e.g. from RHEL 6.3 to RHEL
6.5), you back up the system settings and database, upgrade the system, then restore the settings
and data using the system-backup script (located on the MCS Installation USB drive).
During an upgrade from an MCS system compatible with RHEL 6.3 to MCS 2.2.x (requires
RHEL 6.5), an additional step is required. Once you have restored the MCS database, and before
logging in via the MediaCentral | UX user interface, you must migrate user settings from the
UMS database to the USS database (new in MCS 2.0). This is done using the avid-uss-import
script, which must be run once only on the master node.
Instructions are provided in the MediaCentral Platform Services 2.2 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.2.x:
•
Markers pane: redesigned as Logging pane.
•
Search pane in Users Layout: replaced by Filter field.
After Media Central UX is upgraded to v2.2.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 to MCS v2.2.x.
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.2.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.
19
Installing MediaCentral Platform Services Version 2.2.0
Installing Media Services
If you install any of the following Media Services providers, you must also install Interplay
Access on the same system:
•
Interplay Transcode
•
STP Encode
•
Interplay Consolidate (MediaCentral workflows only)
If you do not install Interplay Access, a job will fail with the error message “Fail to check out
moniker.”
Installing SSL Certificates
For instructions on eliminating the “your connection is not private” (Chrome) or “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-connec
tions
Upgrading Media | Index and Multi-Zone Deployments
If your deployment is configured for Media Index and 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.
•
Delete the MediaIndex System Data Index: The system data index contains information on
registered systems and localization strings for display fields. In initialized systems it also
contains production data. If Media Index is configured, you must delete the system data
index in the master zone before the upgrade. Deleting the system data index restores a clean
index state. For instructions, see the Avid Media | Index Configuration Guide.
20
Installing MediaCentral Platform Services Version 2.2.1
Installing MediaCentral Platform Services Version
2.2.1
The following topics describe how to install the MCS v2.2.1 patch release:
c
•
“Obtaining the MCS Installation Package” on page 21
•
“Copying Software to the MCS Server” on page 21
•
“Updating a Single-Server System from MCS v2.2 to MCS v2.2.1” on page 24
•
“Updating a Cluster System from MCS v2.2 to MCS v2.2.1” on page 25
You must install MCS v2.2.0 before you install the MCS v2.2.1 update.
Obtaining the MCS Installation Package
MediaCentral Platform Services (MCS) 2.2.1 is a cumulative patch release that provides bug
fixes. It requires prior installation of MCS v2.2.0. MediaCentral Platform Services installation
packages are available from the Avid Download Center.
MediaCentral installation packages:
•
MediaCentral_Services_2.2.1_Linux.zip
MAM Connector installation package (if applicable):
•
MediaCentral_MAM_Connector_1.1.0_Linux.zip
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 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.
21
Installing MediaCentral Platform Services Version 2.2.1
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.
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. 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.
9. After all desired files or folders have been copied, close WinSCP.
22
Installing MediaCentral Platform Services Version 2.2.1
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.
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
/dev/sdc1
Size Used Avail Use% Mounted on
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. Copy files to the MCS server:
cp filename /media/installers
cp -R foldername /media/installers
9. Once you have finished coping all necessary files, unmount the USB drive.
cd
23
Installing MediaCentral Platform Services Version 2.2.1
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 /sysinstall
umount /media/usb
Remove the USB drive from the server.
Updating a Single-Server System from MCS v2.2 to MCS v2.2.1
Installing MCS v2.2.1 on a server already running MCS v2.2 is a simple automated update of the
affected packages. All MCS v2.2 system settings are preserved. There is no need to manually
backup and restore any MCS system settings.
Expected downtime: 30 minutes.
Although the patch is non-destructive, it is a good idea to back up the MCS database. Log in as
root and dump the current database:
avid-db dumpall
To install MCS v2.2.1:
1. Copy the installation package to the MCS server.
See “Copying Software to the MCS Server” on page 21.
2. Navigate to the directory containing the installer:
cd /media/installers
3. Unzip the installation package:
tar -zxovf MediaCentral_Services_Update_2.2.1_Linux.tar.gz
4. Change to the patch directory:
cd MediaCentral_Services_Update_2.2.1_Build_XX_Linux
5. Start the installation script:
./update-ics.sh
24
Installing MediaCentral Platform Services Version 2.2.1
n
Be sure to use the dot-slash (“./”) notation, which tells Linux to look for the update-ics script
in the current directory. Otherwise you will receive the following error message:
-bash: update-ics.sh: command not found
For security, Linux does not include the “current” directory (“.”) in its PATH variable. You must
specify the path, even when you are in the directory where the script or command is located.
During the installation process, progress is displayed (details have been omitted, for clarity):
Cleaning repos:
Cleaning up Everything
If you are familiar with the Linux yum update process, you will recognize the pattern of the
update.
The update completes with an indication of success:
Complete!
6. Check that the installation was successful using the ics_version script:
ics_version
For the correct version numbers, see “MediaCentral Platform Services Version Numbers” on
page 3.
7. Restart the MediaCentral core service (“the middleware”) so it incorporates module updates
(for example, an updated STP module):
service avid-interplay-central restart
8. 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.2 to MCS v2.2.1
Installing MCS v2.2.1 on a cluster already running MCS v2.2 is a simple automated update of
the affected packages. All MCS v2.2 system settings are preserved. There is no need 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.
25
Installing MediaCentral Platform Services Version 2.2.1
The cluster update involves the following steps:
•
“Backing Up the MCS Database” on page 26
•
“Identifying the Master, Slave and Load-Balancing Nodes” on page 27
•
“Bringing the Cluster into Standby Mode” on page 27
•
“Updating the Cluster” on page 28
Backing Up the MCS Database
The MCS database contains ACS (Avid Common Services, “the bus”), UMS (User Management
Services) and MCPS (MediaCentral Playback Services) data. In a cluster, the MCS database is
replicated across the master and slave node, but it is only mounted on the master. Therefore, the
MCS database is only available for dumping and backup on the master node.
n
The backup command (avid-db dumpall) must be run on the active (non-standby) master node of
the cluster, or the backup will fail. That is, it must be run on the master node, and the master
node must not be in standby mode.
To back up the database:
1. Log in as root.
2. Create the backup:
avid-db dumpall
The MCS database is dumped to the following directory:
/var/lib/avid/db/dumps
The backup file has a name of the following form:
ALL-YYYYMMDD_HHMMSSZ.sql.gz.cr
The time stamp appended to the file name uses the Universal Time Code (UTC), not the
local time.
26
Installing MediaCentral Platform Services Version 2.2.1
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 extra 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. Log in to any machine in the cluster as root and type:
crm_mon
2. In the output of that command, look for the line containing “AvidClusterIP.” This service
runs on the master server.
For example, if the crm_mon command output contains the line:
AvidClusterIP (ocf::heartbeat:IPaddr2):
Started mcs-1
the master server is mcs-1.
3. To identify the slave, look for the line containing “Master/Slave Set.”
For example, if the crm_mon command output contains the lines:
Master/Slave Set: ms_drbd_postgres [drbd_postgres]
Masters: [ mcs-1 ]
Slaves: [ mcs-2 ]
the slave server is mcs-2.
4. To identify the load-balancing nodes, look for the line containing “Clone Set.”
For example, if the crm_mon command output contains the lines:
Clone Set: AvidAllEverywhere [AvidAll]
Started: [ mcs-1 mcs-2 mcs-3 ]
The extra server in this case is mcs-3.
Bringing the Cluster into Standby Mode
Before updating the cluster, bring all its nodes into standby mode.
To bring the cluster into standby mode:
1. Begin by putting the load-balancing nodes into standby mode:
crm node standby <node name>
2. Next, put the slave node into standby mode:
crm node standby <node name>
3. Finally, put the master node into standby mode:
crm node standby <node name>
27
Installing MediaCentral Platform Services Version 2.2.1
Updating the Cluster
To update the cluster:
1. Copy the installation package to all nodes.
See “Copying Software to the MCS Server” on page 21.
2. Navigate to the directory containing the installer:
cd /media/installers
3. Unzip the installation package:
tar -zxovf MediaCentral_Services_Update_2.2.1_Linux.tar.gz
4. Change to the patch directory:
cd MediaCentral_Services_Update_2.2.1_Build_xx_Linux
5. Start the installation script:
./update-ics.sh
n
Be sure to use the dot-slash (“./”) notation, which tells Linux to look for the update-ics script
in the current directory. Otherwise you will receive the following error message:
-bash: update-ics.sh: command not found
For security, Linux does not include the “current” directory (“.”) in its PATH variable. You must
specify the path, even when you are in the directory where the script or command is located.
During the installation process, progress is displayed (details have been omitted, for clarity):
Cleaning repos:
Cleaning up Everything
If you are familiar with the Linux yum update process, you will recognize the pattern of the
update.
The update completes with an indication of success:
Complete!
6. Check the installation was successful using the ics_version script.
ics_version
For the correct version numbers, see “MediaCentral Platform Services Version Numbers” on
page 3.
28
Installing MediaCentral Platform Services Version 2.2.1
7. Proceed to the next node, and follow the same steps (1 through 6):
a.
Copy and unzip the installer package.
b.
Run the update script.
c.
Verify the installation using the ics_version script.
8. When all the nodes have been updated, bring the cluster back online using the
reactivate-cluster script, on the master node:
/opt/avid/cluster/bin/reactivate-cluster
The script updates the cluster and brings all its nodes back online.
When the script pauses and asks if you wish to apply configuration settings (e.g cluster IP
address, pingable IP address), answer in the affirmative (“y”).
n
Warnings may be issued during cluster reactivation. These can be ignored.
9. For a cluster of three or more nodes, verify the DRBD configuration by querying the crm
data:
crm configure show | grep ^location
The system finds the match(es) indicating cluster nodes are present. For example, the
following sample output indicates a four-node cluster consisting of mcs-1, mcs-2, mcs-3 and
mcs-4:
location
location
location
location
location
location AvidClusterIP_on_ConnectedNode AvidClusterIP \
cluster_on_node1 ms_drbd_postgres -inf: mcs3
cluster_on_node2 ms_drbd_postgres -inf: mcs4
pgsqlDB_prefered_node1 pgsqlDB 20: mcs1
pgsqlDB_prefered_node2 pgsqlDB 20: mcs2
Note that each load-balancing node should have an entry similar to the following, indicating
it has been excluded from DRBD:
location cluster_on_node1 ms_drbd_postgres -inf: mcs3
location cluster_on_node2 ms_drbd_postgres -inf: mcs4
The master and slave nodes will have entries similar to the following, indicating they are
included in DRBD:
location pgsqlDB_prefered_node1 pgsqlDB 20: mcs1
location pgsqlDB_prefered_node2 pgsqlDB 20: mcs2
29
Installing the Media | Distribute Update
10. 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.
11. 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.
Installing the Media | Distribute Update
Media Distribute v2.2.1 is a full plug-in installer. For installation instructions, see the
Media | Distribute V2.2 Installation and Configuration Guide.
30
New Features in MediaCentral | UX Version 2.2.0
New Features in MediaCentral | UX Version 2.2.0
This topic provides an overview of the major new features in MediaCentral UX v2.2.0.
Stories and Sequences
For complete information on these features, see the MediaCentral | UX User’s Guide or the
MediaCentral | UX Help.
Feature
Description
Associate a sequence with a story
You can associate a sequence created in Media Composer or
MediaCentral UX with a story. You can also set some asset
metadata fields to update with information from the story or
sequence.
Story grouping
You can create a story group from contiguous stories in a
queue. This allows you to reorder grouped stories without
having to reorder each story separately. You can also float all
stories as a group.
Editing
For complete information on these features, see the MediaCentral | UX User’s Guide or the
MediaCentral | UX Help.
Feature
Description
Controlling zoom level with the mouse
wheel
Position the mouse pointer below the Media viewer and rotate
the mouse wheel forward one click to zoom in by 50 percent,
or back one click to zoom out by 50 percent.
Using keyboard shortcut S to create a
subclip
After setting In and Out points, and with focus in the Media
pane, you can press the S key to open the Select Folder for
Subclip dialog box. You can continue to use keyboard
shortcuts to create the subclip:
1. Select the location.
2. Press Tab.
3. Type the subclip name.
4. Press Tab twice, so that the focus is on the Create Subclip
button.
5. Press Enter (Windows) or Return (Macintosh)
31
New Features in MediaCentral | UX Version 2.2.0
Feature
Description
Creating a text-only story segment
For some news stories, you might need to create a story
segment that is not associated with video in the story. For
example, a story might include presenter text before the video
starts. MediaCentral UX lets you create a story segment that
does not display a corresponding timing block in the
sequence.
Detecting black gaps in video sent to
playback
A user might unintentionally include gaps in the video track
that result in black gaps in the video output. This could cause
a problem when the sequence is sent to playback. An
administrator can create an option to check a sequence for
black gaps when the sequence is sent to playback. If the
system detects black gaps, one of the following occurs,
depending on how this option is configured:
•
NONE: No message is displayed and the sequence is sent
to the playback device.
•
WARNING: A warning message is displayed and the user
can either continue the operation or cancel it.
•
ERROR: An error message is displayed and the process is
canceled.
For more information, see the MediaCentral | UX
Administration Guide.
Keyboard shortcut to delete segment
You can now use the Delete key for Windows, in addition to
the Delete key for Macintosh and the Backspace key for
Windows.
32
New Features in MediaCentral | UX Version 2.2.0
Interplay MAM
For complete information on these features, see the MediaCentral | UX User’s Guide or the
MediaCentral | UX Help.
Feature
Description
Viewing thumbnails
The Thumbnails pane lets you display a series of small
images of an asset. Viewing and double-clicking thumbnails
can help you navigate through video assets more quickly.
Locking metadata
If you are editing an Interplay MAM asset in the Metadata
pane, metadata is locked to prevent other users from editing
the metadata at the same time. The lock is automatically set
when you begin editing a metadata field or can be manually
applied by clicking the Lock button. The Lock is released
when you end editing or click the Lock button again.
Using Actions sub-menus during process You can create processes from the Assets, Search, and Media
creation
panes by using the Actions menu. If the process is configured
in Interplay MAM accordingly, the Actions menu can provide
sub-menu items that let you select additional options; for
example, you can select an export target for a MAM Export
process.
Search
For complete information on these features, see the MediaCentral | UX User’s Guide or the
MediaCentral | UX Help.
Feature
Description
Display markers in the search results for
an indexed search
Search results can display any markers and time-based
metadata included in the assets listed in the search pane.
Markers include a link that opens the asset in the Media Pane
and takes the user to the marker location.
Limit the number of active languages in
an index
You can specify which languages you want to use in an
indexed search. You can limit the number of languages per
zone so that all indexes in that zone search the same
languages. Limiting the number of languages searched can
improve the performance of indexed searches.
Check the status of a re-index operation.
You can use the Media Index Cluster State pane to monitor
the status and progress of systems when you perform a
re-index operation.
33
New Features in MediaCentral | UX Version 2.2.0
Assets
Feature
Description
Create duplicates of Interplay Production Duplicating an asset in the Interplay Production database
assets
creates a new asset, with new metadata (MobID). You can
duplicate master clips, subclips, audio-only clips, and
sequences.
Right-click the asset you want to duplicate and select
Duplicate. A new asset is created in the same folder as the
original asset, with the extension .duplicate. The name is
highlighted in edit mode so that you can easily rename it.
Layouts
Feature
Description
Visual indication of which pane has focus The pane that has focus (selected for keyboard or mouse
(active pane)
input) is outlined in orange.
This feature helps you to know which keyboard shortcuts are
available, because some shortcuts are available only if a pane
has focus.
Markers
For complete information on these features, see the MediaCentral | UX User’s Guide or the
MediaCentral | UX Help.
Feature
Description
Filter markers by color and user
Click the Filter Criteria list and select your criteria in one of
two groups: Colors and Users.
34
New Features in MediaCentral | UX Version 2.2.0
Feature
Description
Create a marker by pressing Ctrl +number Set the icon color as follows:
(top-row or numeric keypad)
• Ctrl+0: Last color picked. If no previous color was
selected in a session, the color is white.
•
Ctrl+1: White
•
Ctrl+2: Black
•
Ctrl+3: Red
•
Ctrl+4: Green
•
Ctrl+5: Blue
•
Ctrl+6: Cyan
•
Ctrl+7: Magenta
•
Ctrl+8: Yellow
If you use the numeric keypad, the NumLock state must be
enabled to use these commands.
Messaging
For complete information on these features, see the MediaCentral | UX User’s Guide or the
MediaCentral | UX Help.
Feature
Description
Support for including links to MAM assets In addition to providing links to Interplay Production assets
in the Message pane.
in the text of a message, you can now include links to
Interplay MAM assets.
Mobile Applications
For complete information on these features, see the MediaCentral | UX User’s Guide or the
MediaCentral | UX Help.
Feature
Description
New story editing features for the Android You can cut, copy and paste text and production cues in the
mobile app
iNEWS story text.
Support for the latest Android OS version This release adds the ability to run the MediaCentral mobile
app for Android devices on the latest release of Android OS
(Android 5.0 “Lollipop”)
35
New Features in MediaCentral | UX Version 2.2.0
System Settings
For complete information on these features, see the MediaCentral | UX Administration Guide or
the MediaCentral | UX Help.
Feature
Description
General
In an organization with multi-zone setups and remote users,
timezone and locale can vary from one site to another. To
properly display date values to the user, especially when data
is coming from different places, an administrator can set
default values. Individual users can then override these
defaults in the User Settings.
•
Time Zone
•
Date Format
These settings are used by the indexed search in
MediaCentral UX to display dates and other formatted data
correctly.
•
Time Zone: The default time zone for users signed in to
the MediaCentral UX server. Click the down arrow for a
list of time zones and select the most appropriate one.
•
Date Format: The default date and time format for users
signed in to the MediaCentral server. Click the down
arrow key for a list of formats and select the most
appropriate one.
iNEWS
Two new options allow you to specify how metadata from
associated sequences update story form fields for iNEWS
stories.
Interplay MAM
The MediaCentral administrator must specify Interplay MAM
configuration information before you can use
MediaCentral UX with Interplay MAM. The layout of the
Settings pane for Interplay MAM was redesigned and aligned
to other settings groups in the Settings pane.
User Settings
For complete information on user settings, see the MediaCentral | UX User’s Guide or the
MediaCentral | UX Help.
36
New Features in MediaCentral | UX Version 2.2.0
Feature
Description
General
An administrator sets the default values for both time zone
and date format in the System Settings. Individual users can
override the defaults in these user settings.
•
Time Zone
•
Date Format
These settings are used by the indexed search in
MediaCentral UX to display dates and other formatted data
correctly.
Administration
For complete information on password settings, see the MediaCentral | UX Administration
Guide or the MediaCentral UX Help.
Feature
Description
Insecure (weak) password settings
Starting with MediaCentral UX v2.2.0, an administrator has
the option of turning off the password complexity
requirement in UMS. This is primarily for facilities that use
Interplay Production, iNEWS, or Interplay MAM for user
authentication, and users have passwords that do not conform
to the MediaCentral UX v2.1 password strength requirement.
In the Users layout, select the top level folder (Users). In the
right-hand column of the Details pane, select Allow Weak
Passwords, then click Apply.
this option allows insecure passwords that
c Enabling
will put system security at risk.
37
Fixed in Version 2.2.1
Fixed in Version 2.2.1
The following bugs are fixed in version 2.2.1.
Audio
(MPLAY-1818) The final two seconds of audio media created by SAT AI AutoIngest™ is
truncated during playback. Customers using SAT AI AutoIngest should contact NL Technology
(http://www.nltek.com) for a related patch to the AutoIngest software.
(MPLAY-1781) The metadata (audio_length property) for an audio-only sequence incorrectly
reports the length of the asset.
Editing
(OS-2496) If you drag media from the Media viewer, then drop it back in the Media viewer, the
media reloads.
(OS-2513) With a group clip loaded in a multiple-angle view, and the second or third bank of
angles displayed, if you update the media status, the Media viewer displays the first bank of
angles.
(OS-2528) If you load a sequence that has a start timecode different from 00:00:00:00, then use
Save As to save a copy, the start timecode of the copy begins at 00:00:00:00.
(OS-2537) If the Interplay Administrator setting for Audio Storyline patching has the NAT
Sound track set to A4, setting the audio level for A4 in the Audio pane does not work correctly.
For example, Audio set to -100 can still be heard.
(OS-2536) Restrictions might disappear from the Media pane after sequence edits or undo
operations.
(OS-2510) If you create a restriction, every time you change text for the restriction, the red color
of the restriction in the Media timeline changes.
(MA-2609) In the Thumbnails pane, if a long clip is loaded (for example, 6 hours) or a clip with
a large number of markers (2,000 or more), clicking the Time and Marker buttons can cause the
browser to freeze and crash, and then prevent playback in the Media viewer.
Installation and Upgrade
(RE-947) Running the reactivate-cluster script in a Media Index configuration causes the
PamAgent cluster resource to be lost.
38
Fixed in Version 2.2.1
Mobile Apps
(LIZ-1594) Android app only: The MediaCentral UX mobile app becomes unresponsive when
running in the background for a long period of time. This has been fixed. If the app runs in the
background, opening it again either brings you to the last screen viewed (if you selected the
option to keep you logged in and if the device has sufficient memory to run the app) or to the log
in screen (if the device has sufficient memory to run the app).
(LIZ-1596) Android app only: If you select the MC button for typing machine control
instructions in a production cue, and then select the N button and continued to enter text, the new
text is formatted as normal text even though it is included in a machine control instruction. This
has been fixed so that selecting the N button automatically moves the cursor to a new line for the
normal text.
(LIZ-1610) Android app only: If you copy and paste text that includes segments or page breaks
from one story to a second, empty story, only the text is pasted into the second story. This has
been fixed so that segments and page breaks as well as text are now copied and pasted correctly.
(LIZ-1616) Android app only: For stories including a page break, you cannot copy and paste a
page break before a segment division. This has been fixed so that you can now copy page breaks
and paste them anywhere in a story, including before segments.
Media | Index
(TSL-1930) Indexed searches return a maximum of five markers for each asset in the search
results list. This has been fixed. You can now use the following procedure to set the maximum
number of markers returned by an indexed search.
To change the default number of markers returned by an indexed search:
1. Open the avid-acs-search configuration file for editing by typing the following command:
vi /etc/sysconfig/avid-acs-search
2. Using the text editor, locate the following line:
export HIGHLIGHT_NUMBER_OF_FRAGMENTS=5
3. Delete the value at the end of the line and type the value you want to use.
4. Press the Escape key to return to command mode, then type :wq and press Return to write
and quit the text editor.
5. Restart the search service on each node where you changed the configuration information:
service avid-acs-search restart
39
Fixed in Version 2.2.1
(JP-1980) In an indexed search using Grid view, if you open the Sort By dialog, Relevance is
selected and the Sort Ascending/Sort Descending buttons are disabled by default. If you switch
to another field, such as Name, the Sort Ascending/Sort Descending buttons are still disabled. If
you close the dialog and perform a search, the search fails with the message “Search failed due to
internal problem.” This has been fixed.
(JP-1945) In a list of search results, clicking on the link for a restriction jumps to the wrong
location in the Markers and Media panes. This has been fixed.
(JP-1857) In an indexed search view, with focus on a criterion, pressing Return should start the
search process. This has been fixed.
Playback
(MPLAY-1479) The last few frames of audio might not be heard.
(MPLAY-1678) For file-based playback, the audio meter does not display an audio level.
(MPLAY-1688) After encountering a network lag, the player remains at a reduced frame rate
resulting in stuttered playback. The player will now adjust to higher rates as network latency
issues are resolved.
(MPLAY-1831) The aspect ratio of some MP4 media is not detected correctly. As a result, the
beginning and end of the file are truncated during frame-based playback.
(MPLAY-1689) Originally documented as fixed in MCS 2.1.1, additional enhancements were
made to player code to strengthen system security during a clip information request.
Search
(JP-1936) 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. This has been fixed so the setting now
functions correctly and specifies the number of results displayed in the Search pane for federated
searches.
40
Fixed in Version 2.2.1
Stories
(MA-2606) Under some circumstances, a sequence associated with an iNEWS story in
MediaCentral UX is not associated with the story in the iNEWS client.
(MA-2567) You cannot open a queue to view iNEWS stories in MediaCentral UX when there is
a colon in the queue name.
(MA-2610) If you select a story in a rundown, select Copy Link, then paste the link into a story
from another rundown, the link fails with the message that the asset no longer exists.
(MA-2618) If you open an iNEWS project, you cannot open ALL queue, QUERY queue, or a
facet.
System Settings
(JP-1843) In the System Settings layout, if you enter an incorrect value in one tab (for example,
General), an error message is displayed. If you then switch to another tab, the “Save Changes”
dialog is not displayed.
(JP-2041) If you sign in as Administrator and change the date/time format in the User Settings,
log out, and another user signs in, the User Settings do not show the default date/time format as
set in the System Settings.
Media | Distribute
(MPD-1131) The Status column in the Packages pane now displays the status of a Web story
publication with video and image items separated by semicolons. This makes it clearer which
items have been published and which remain pending.
(MPD-1133) If you published a media package using a Generic OVP profile with
Media Distribute v2.2, the final step of delivering an MP4 files to the FTP location fails to
complete. This has been fixed and you can now successfully publish videos using a Generic
CMS profile.
(MPD-1139) When you publish a media package using a Generic CMS profile, an XML file is
created with metadata information used by the video stored in your Interplay database. Now, the
Generic CMS output XML file includes all metadata fields for your video that have been set in
the Property Layout view in the Interplay Administrator tool, including all properties marked as
Available even if those properties are empty.
41
Fixed in Version 2.2.0
Fixed in Version 2.2.0
The following bugs are fixed in version 2.2.0.
Audio
(OS-2435) If both a clip and a sequence are loaded, and you change the master volume in Output
mode, the slider changes but the master volume does not change.
(OS-2438) If custom audio panning is set, performing an undo after editing a sequence causes
the default panning to be applied.
Editing
(OS-2303) If you open a sequence after a crash, click the Recovered button, then click the Last
Saved button, any markers in the sequence are removed.
(OS-2273) If you are editing with a group clip in which one of the angles includes padding, you
can replace a segment in the sequence with padding. If you then move the position indicator into
the replaced segment, the “Media Offline” slide is displayed.
(PLAD-104) If you attempt to create subclips from an in-progress (EWC or chained ingest) clip
created in a remote Interplay workgroup, and copied to a local workgroup, an error message
might be displayed. This message states that subclipping is available only after timecode
00:01:00. This message might be displayed even if one minute of media has been ingested.
To fix this bug, install Interplay Copy v3.2 or Interplay Copy patch v3.0.6 on the remote Copy
provider. These versions of Interplay Copy include the DMSCopyMedia.vmoptions file, which is
configured for check-ins at three-minute intervals. You can edit this interval. For details, see the
Interplay Production v3.2 ReadMe. Also note that there is a delay of 6 to 15 minutes before you
can create subclips from an EWC clip. See “Edit While Capture” on page 60.
(OS-2232) If you add text to a story segment, press tab, and continue to add text (creating more
than one timing block in the associated sequence), the operation cannot be properly undone.
(OS-2250) If you close the Media pane without saving the sequence, a message is displayed
asking if you want to save the sequence. There is no Cancel button to cancel the operation and
keep the Media pane open.
(OS-2263) For advanced sequences, playback might not reflect some changes in audio until an
edit is made to the sequence that triggers the player to reload the sequence.
(OS-2265) In some MAM sequences, the Match Frame feature displays the wrong frame.
42
Fixed in Version 2.2.0
(OS-2267) In some cases, the Sequence pane does not retain focus when you click on a clip in a
different timing block in a story sequence.
(OS-2304) If you open a story sequence, load another story but do not load the sequence, click in
Asset mode in the Media pane, then change to Output mode, a frame from a previously loaded
sequence is displayed.
(OS-2306) If In and Out points are set to a padded area of a group clip, when you overwrite the
clip into an advanced sequence, a single-frame clip is added to the sequence.
(OS-2315) If you open a sequence in recovery mode, the headframe is shown as a waveform
graphic.
(OS-2319) After browser crash, the Auto-Recovered Assets menu item is disabled.
(OS-2478) If your session is automatically timed out, unsaved changes in a sequence are lost.
Markers
(SPEC-119) Markers created in MediaCentral UX are not saved with track information (V1) in
Interplay Production. Marker metadata cannot be exported to Interplay MAM.
Playback
(MA-2271, OS-2361) For file-based playback, the master volume slider is unresponsive.
(MPLAY-1686) Changing the master volume level in a clip with both Natural Sound (NAT) and
Sound on Tape (SOT) channels, then muting, unmuting, and replaying the clips can produce
exaggerated volume changes. In addition, volume levels for soloed NAT tracks do not accurately
reflect changes made to master volume.
Server
(RE-893) On a system with more than two nodes, a failover puts the cluster in an unusable state.
Media | Distribute
(MPD-1090) If you included a Summary Text with standard HTML tags in a standalone video
package with a WorldNow CMS account, you received an error if you selected the Use Summary
Text as SEO Description. This has been fixed.
(MPD-1091) You were unable to use more than 200 characters in a Summary Text for a
standalone video with a WorldNow CMS account if you selected the Use Summary Text as SEO
Description. This has been fixed so that the maximum number of characters you can use in a
Summary Text is now 500.
43
Fixed in Version 2.2.0
(MPD-1092) You can publish video files greater than 2 GB using the Web Story pane.
Previously, you might have received an error when publishing large video files.
(MPD-1093) When you click Load iNEWS Story in the Web Story pane, the Story Headline
field respects the account setting for either transforming iNEWS stories to lowercase or keeping
the case of the story and the slug text the same as the story in iNEWS.
(MPD-1096) When you attach an image in the Web Story pane, the Description field is
automatically filled with the asset name or the file name by default. The Image Caption fields
now are optional.
(MPD-1098, MPD-1099) If you removed a Summary graphic or an Abstract graphic, you could
not attach another graphic without removing all attached graphics from your Web Story.
Intermittently, you also could also attach more than one Summary or Abstract graphic with a
WorldNow account, even though WorldNow allows only one of each. These issues have been
fixed.
(MPD-1100) If you cleared all graphics from the Attached Images list, and then added new Story
Body graphics, the Story Body graphic in the Attached Images list could list a negative number.
If you used a WorldNow account, this could allow you to add more than the maximum five
allowed graphics. This has been fixed.
(MPD-1105) If you create a standalone video package using a WorldNow account, you can now
select both summary text options: Use Summary Text as Abridged Text and Use Summary Text
as SEO Description.
Media | Index
(TSL-1872) Permissions for indexed searches were not being applied correctly in some
multi-zone configurations. This has been fixed, and now indexed searches find assets from
systems with permissions set within multi-zone environments.
44
Additional Documentation
Additional Documentation
This section includes information that is incorrect or not included in the v2.1 documentation.
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.
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;
Indexes Displayed in MediaCentral | UX System Settings
In the MediaCentral UX System Settings for Media Index, the Indexes Details pane displays
only the indexes in the local zone. To display indexes of other zones, connect directly to the
MediaCentral UX of that zone.
45
Additional Documentation
Media | Distribute System Settings
The settings for Media Distribute available in the MediaCentral UX System Settings now are
organized in two separate panes:
•
General — This pane now provides the option to change all iNEWS story text to lowercase
characters. This setting applies to all packages that include iNEWS stories.
•
Profiles — This pane allows you to create and configure system accounts and user profiles
used for publishing media packages to platforms such as Facebook and Twitter.
46
Additional Documentation
Information Not Included in Translated Documentation
Media | Index and Indexed Search
Indexed search maps Interplay Production properties to Media Index criterion fields. The
following table describes how Media Index categorizes some common Interplay Production
properties:
Interplay Production Property
Media Index Field
Name
Name
MobID
GlobalAssetID
Created By
Creator
Creation Date
Created
Modified Date
Modified
Changed By
Modifier
Start
Start
End
End
Duration
Duration
Comments
Description
Mime Type
Type
The Search Results List
The topics covering the indexed search and the search results list have been revised. Included in
the updated topics are the following:
•
You can search for time-based metadata, such as text within markers.
•
You can view your results in Card view or in Grid view. Card view provides a summary of
the metadata information in your search results, and Grid view displays your results in a grid
with columns for each selected metadata category.
For more information, see the English version of the User's Guide or Help.
47
Limitations and Defects Found in Version 2.2.1
Date and Time Formats
The Language user setting also affects the date and time format that is displayed in most
components of MediaCentral UX:
•
English:
month/date/year hours:minutes:seconds AM/PM
•
French and Spanish:
date/month/year hours:minutes:seconds
•
German:
date.month.year hours:minutes:seconds
•
Chinese:
year-month-date hours:minutes:seconds
•
Japanese:
year/month/date hours:minutes:seconds
•
Korean:
year. month. date AM/PM hours:minutes:seconds
The Time Zone and Date settings affect how dates and times are displayed in indexed search
results
Limitations and Defects Found in Version 2.2.1
The following sections list limitations and defects for MediaCentral UX, MediaCentral Platform,
and Media Distribute.
Editing
➤
Bug Number: 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. Workaround: Save the sequence and reload it. The extra restrictions are no
longer displayed.
Search
➤
Bug Number: IPAM-1183. 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.
48
Limitations and Defects Found in Version 2.2.1
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
Mime Type
Type
Modified Date
Modified
Name
Name
Start
Start
Stories
➤
Bug Number: MA-2491. 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.
Media | Distribute
➤
Bug Number: MPD-1126. 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. 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.
49
Limitations and Defects Found in Version 2.2.0
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.
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
Interplay | MAM
➤
Bug Number: MAM-2377. 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.
Limitations and Defects Found in Version 2.2.0
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.
Delivery
➤
Bug Number: 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.
Editing
➤
Bug Number: OS-2481, MA-2561. Rarely, closing the Story pane after creating a sequence
causes MediaCentral UX to become less responsive. Workaround: Refresh the
MediaCentral UX browser page.
50
Limitations and Defects Found in Version 2.2.0
➤
Bug Number: 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. Workaround: Switch to Output mode, then
switch back to Asset mode.
➤
Bug Number: MA-2491. 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.
Playback
➤
Bug Number: MPLAY-1794. 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. In file-based playback you cannot mute a clip containing MP4
mono audio tracks.
Search
➤
Bug Number: IPAM-1171. 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. 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. 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).”
51
Limitations and Defects Found in Earlier Versions
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.
Then try the STP job again.
Limitations and Defects Found in Earlier Versions
Limitations and defects in are organized in the following sections:
•
“Limitations and Defects Found in Version 2.1” on page 52
•
“Limitations and Defects Found in Version 2.0” on page 55
•
“Limitations and Defects Found in Version 1.8” on page 56
•
“Limitations and Defects Found in Version 1.7” on page 56
•
“Limitations and Defects Found in Version 1.6” on page 57
•
“Limitations and Defects Found in Version 1.5” on page 58
•
“Limitations and Defects Found in Version 1.4” on page 60
•
“Limitations and Defects Found in Version 1.3” on page 60
Limitations and Defects Found in Version 2.1
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, Media Central 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: MPLAY-. If you add two in-progress (EWC or chained ingest) clips to a
sequence, you might not be able to add a dissolve. An error message is displayed. Workaround:
Wait until 10 minutes of the clips has been recorded.
➤
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.
52
Limitations and Defects Found in Earlier Versions
➤
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: OS-2364. If you add two in-progress (EWC or chained ingest) clips to a
sequence, you might not be able to add a dissolve. An error message is displayed. Workaround:
Wait until 10 minutes of the clips has been recorded.
➤
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.
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.
53
Limitations and Defects Found in Earlier Versions
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.
➤
Bug Number: 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.
Workaround: Open the Web Story pane, and then load the video clip in the Media pane.
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.
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.
54
Limitations and Defects Found in Earlier Versions
Limitations and Defects Found in Version 2.0
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.
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.
55
Limitations and Defects Found in Earlier Versions
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.
Limitations and Defects Found in Version 1.8
All limitations and defects published in previous versions of the ReadMe have been fixed.
Limitations and Defects Found in Version 1.7
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: MPLAY-1171. 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.
56
Limitations and Defects Found in Earlier Versions
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.
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
Limitations and Defects Found in Version 1.6
All limitations and defects published in Interplay Central Services V1.6 ReadMe have been
fixed.
57
Limitations and Defects Found in Earlier Versions
Limitations and Defects Found in Version 1.5
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.
➤
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).
58
Limitations and Defects Found in Earlier Versions
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
➤
c
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.
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.
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.
59
Limitations and Defects Found in Earlier Versions
Limitations and Defects Found in Version 1.4
All limitations and defects published in previous versions of the ReadMe have been fixed.
Limitations and Defects Found in Version 1.3
Edit While Capture
➤
Bug Number: ICI-592, ICML-2236. When editing a clip while it is still being captured, 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.
➤
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.
60
Limitations and Defects Found in Earlier Versions
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.
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.
61
Limitations and Defects Found in Earlier Versions
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.
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.
62
Legal Notices
Legal Notices
Product 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.
At this point, a couple of non-conreffed items usually appear. They cannot be conreffed because they need to be edited to include
the specific product name or the year of publication.The first is the general copyright law disclaimer; the second is the copyright line
that includes the publication year and (sometimes) the place of printing. Both of these items are present in title_template.fm.
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.
63
Legal Notices
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.
64
Legal Notices
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 (ellson@lucent.com).
Portions relating to gdft.c copyright 2001, 2002 John Ellson (ellson@lucent.com).
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 Legend
U.S. GOVERNMENT RESTRICTED RIGHTS. This Software and its documentation are “commercial computer software” or
“commercial computer software documentation.” In the event that such Software or documentation is acquired by or on behalf of a
unit or agency of the U.S. Government, all rights with respect to this Software and documentation are subject to the terms of the
License Agreement, pursuant to FAR §12.212(a) and/or DFARS §227.7202-1(a), as applicable.
65
Legal Notices
Trademarks
003, 192 Digital I/O, 192 I/O, 96 I/O, 96i I/O, Adrenaline, AirSpeed, ALEX, Alienbrain, AME, AniMatte, Archive, Archive II, Assistant
Station, AudioPages, AudioStation, AutoLoop, AutoSync, Avid, Avid Active, Avid Advanced Response, Avid DNA, Avid DNxcel, Avid
DNxHD, Avid DS Assist Station, Avid 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,
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.2.1 ReadMe • April 30, 2015 • This document is distributed by Avid in
online (electronic) form only, and is not available for purchase in printed form.
66