Pinnacle Systems MediaCentral - 2.1 Administrator’s Guide

Avid MediaCentral | UX
Administration Guide
Version 2.1
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 document is protected under copyright law. An authorized licensee of MediaCentral may reproduce this publication for the licensee’s own use in learning how to use the software. This document may not be reproduced or distributed, in whole or in part, for commercial purposes, such as selling copies of this document or providing support or educational services to others. This document is supplied as a guide for MediaCentral. Reasonable care has been taken in preparing the information it contains. However, this document may contain omissions, technical inaccuracies, or typographical errors. Avid Technology, Inc. does not accept responsibility of any kind for customers’ losses due to the use of this document. Product specifications are subject to change without notice.
Copyright © 2014 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.
.
2
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.
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.
3
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.
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.
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,
4
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.
Adobe and Photoshop are either registered trademarks or trademarks of Adobe Systems Incorporated in the United States and/or other countries. Apple and Macintosh are trademarks of Apple Computer, Inc., registered in the U.S. and other countries. Windows is either a registered trademark or trademark of Microsoft Corporation in the United States and/or other countries. All other trademarks contained herein are the property of their respective owners.
Avid MediaCentral Administration Guide • 9329-065181-00 Rev A • December 2014 • Created 12/19/14 • This document is distributed by Avid in online (electronic) form only, and is not available for purchase in printed form.
5

Contents

Using This Guide. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
Symbols and Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
If You Need Help. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
Avid Training Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
Chapter 1 Administration and System Settings. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
The Administrator Account . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
Signing In to MediaCentral | UX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
Configuring System Settings. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
MediaCentral System Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
Configuring Image Quality. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
Configuring File-Based Playback . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
Configuring a Session Timeout . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
Configuring Interplay | Production for Sharing Messages. . . . . . . . . . . . . . . . . . . . . . . . 22
Configuring Message Archiving . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
Configuring E-Mail Forwarding . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
Configuring for Send to Playback . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
Understanding the Send-to-Playback Components and Process . . . . . . . . . . . . . . 27
Creating or Editing a Send-to-Playback Profile . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
Send-to-Playback Profile Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38
Monitoring STP Processes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45
Configuring Settings in the Interplay | Production Administrator. . . . . . . . . . . . . . . . . . . 45
Configuring Interplay | MAM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50
Configuring Settings in Interplay | MAM User Manager . . . . . . . . . . . . . . . . . . . . . . 50
Configuring Interplay | MAM in the System Settings Pane. . . . . . . . . . . . . . . . . . . . 52
Configuring Central Index for Interplay | MAM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54
Creating Interplay | MAM Users in MediaCentral . . . . . . . . . . . . . . . . . . . . . . . . . . . 55
6
Chapter 2 User Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56
Opening the Users Layout . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56
The Users Layout . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57
Understanding Users and Groups. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60
Available Layouts: Administrators and Users . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62
Working with MediaCentral Zones . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63
Configuring a Multi-Zone Environment. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63
Managing Multi-Zone Environments. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63
Configuring MediaCentral Zones . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65
Managing Users and Groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66
Importing Users . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67
Creating a New User or Editing User Details . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75
Creating a New Group or Editing Group Details . . . . . . . . . . . . . . . . . . . . . . . . . . . 77
Adding a User to a Group. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79
Removing a User from a Group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79
Removing Groups from Groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81
Understanding the Unassigned Group. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82
Deleting Users and Groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82
Changing Passwords . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83
Creating, Deleting, and Assigning Roles. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84
Default Roles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85
MediaCentral | UX Client Licensing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85
Creating and Deleting Roles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88
Assigning Roles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89
Displaying Information in the Details Pane . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92
Viewing and Ending Active Sessions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93
Chapter 3 Monitoring and Troubleshooting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95
Log Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95
Troubleshooting Send to Playback Problems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99
Troubleshooting Mixdown Problems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105
Appendix A User Management Utility Tools . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106
MediaCentral Glossary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 108
Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 123
7

Using This Guide

This guide is intended for all Avid MediaCentral | UX administrators who are responsible for configuring and maintaining a MediaCentral UX system (formerly Interplay Central). This guide describes product features and administrative procedures, such as MediaCentral UX system settings and user management.
For initial installation and configuration, see the Avid MediaCentral Platform Services
Installation and Configuration Guide. For user information, see the Avid MediaCentral | UX User’s Guide.

Symbols and Conventions

Avid documentation uses the following symbols and conventions:
Symbol or Convention Meaning or Action
n
c
w
> This symbol indicates menu commands (and subcommands) in the
(Windows), (Windows only), (Macintosh), or (Macintosh only)
Italic font Italic font is used to emphasize certain words and to indicate variables.
A note provides important related information, reminders, recommendations, and strong suggestions.
A caution means that a specific action you take could cause harm to your computer or cause you to lose data.
A warning describes an action that could cause you physical harm. Follow the guidelines in this document or on the unit itself when handling electrical equipment.
order you select them. For example, File > Import means to open the File menu and then select the Import command.
This symbol indicates a single-step procedure. Multiple arrows in a list indicate that you perform one of the actions listed.
This text indicates that the information applies only to the specified operating system, either Windows or Macintosh OS X.
Symbol or Convention Meaning or Action

If You Need Help

Monospace font
Ctrl+key or mouse action Press and hold the first key while you press the last key or perform the
| (pipe character) The pipe character is used in some Avid product names, such as
If You Need Help
If you are having trouble using your Avid product:
1. Retry the action, carefully following the instructions given for that task in this guide. It is especially important to check each step of your workflow.
2. Check the latest information that might have become available after the documentation was published. You should always check online for the most up-to-date release notes or ReadMe because the online version is updated whenever new information becomes available. To view these online versions, select ReadMe from the Help menu, or visit the Knowledge Base at
www.avid.com/support.
3. Check the documentation that came with your Avid application or your hardware for maintenance or hardware-related issues.
Monospace font identifies text that you view and type from the operating system command line.
mouse action. For example, Command+Option+C or Ctrl+drag.
Interplay | Production. In this document, the pipe is used in product names when they are in headings or at their first use in text.
4. Visit the online Knowledge Base at hours per day, 7 days per week. Search this online Knowledge Base to find answers, to view error messages, to access troubleshooting tips, to download updates, and to read or join online message-board discussions.

Avid Training Services

Avid makes lifelong learning, career advancement, and personal development easy and convenient. Avid understands that the knowledge you need to differentiate yourself is always changing, and Avid continually updates course content and offers new training delivery methods that accommodate your pressured and competitive work environment.
For information on courses/schedules, training centers, certifications, courseware, and books, please visit 800-949-AVID (800-949-2843).
www.avid.com/support and follow the Training links, or call Avid Sales at
www.avid.com/support. Online services are available 24
9

1 Administration and System Settings

The following topics provide information about configuration of MediaCentral UX components:

The Administrator Account

Signing In to MediaCentral | UX
Configuring System Settings
MediaCentral System Settings
Configuring Image Quality
Configuring File-Based Playback
Configuring a Session Timeout
Configuring Interplay | Production for Sharing Messages
Configuring Message Archiving
Configuring E-Mail Forwarding
Configuring for Send to Playback
Configuring Settings in the Interplay | Production Administrator
Configuring Interplay | MAM
The Administrator Account
During MediaCentral UX installation, a user named Administrator is created. This user is a member of the Administrator group by default, and as a result has administrator privileges.
During installation, the default Administrator password signs in with the user name Administrator, the user must supply this password. Note that this password is context-sensitive. For security, the user must then change the password. For more information, see
on page 106
After the first sign-in, the administrator must configure system settings such as information about the Avid iNEWS, Interplay Production, and Interplay MAM systems. For more information, see
Settings” on page 12
.
“Changing Passwords” on page 83 and “User Management Utility Tools”
“Signing In to MediaCentral | UX” on page 11 and “Configuring System
.
Avid123
is set. The first time a user
Additional Administrator Accounts
An administrator can add other users to the Administrators group. All members of the Administrators group have the same administrator privileges. For more information, see
“Creating a New Group or Editing Group Details” on page 77.
Layouts Available Only to an Administrator
Administrator tasks are performed in MediaCentral UX layouts. The following layouts are available only to a MediaCentral UX administrator:
System Settings
•Users

Signing In to MediaCentral | UX

Use a supported browser to connect to and sign in to your MediaCentral UX server. See the Avid MediaCentral ReadMe for a list of supported browsers.
MediaCentral UX lets you use a single user name and password to access all Avid systems for which your account is configured. A journalist might have access to both an Avid iNEWS database and an Interplay Production database, while a logger might have access only to an Interplay Production database. MediaCentral UX credentials (user name and password) are created by a MediaCentral UX administrator in the Users layout. Access is determined by the user’s role. For more information, see
“Default Roles” on page 85.
Signing In to MediaCentral | UX
Interplay MAM users must sign in with MediaCentral UX credentials that match credentials set in the Interplay MAM system.
iNEWS and Interplay Production users have the option of using MediaCentral UX credentials that are different from their iNEWS and Interplay Production credentials.
The first time you sign in to MediaCentral UX, you must use MediaCentral UX credentials. You are then given the option of using your MediaCentral UX credentials to sign in to iNEWS and Interplay Production or to use different credentials. The credentials you use depend on the user name and password that you can use to sign in directly to iNEWS or Interplay Production. Supplying these credentials enable you to use only the MediaCentral UX user name and password at future sign-ins.
Your iNEWS and Interplay Production credentials are set in the iNEWS or Interplay Production sections of the User Settings dialog box, which you access from the Home menu. You can change these credentials at any time.
11

Configuring System Settings

To sign in to MediaCentral UX:
1. Open a supported browser and type the URL of your MediaCentral Services server.
The URL is the computer name of the server.
2. At the sign-in screen, type your user name and password.
3. Click Sign In, or press Enter (Windows) or Return (Macintosh).
After a few moments, the MediaCentral UX application opens and displays the last layout that you used.
When you sign in to MediaCentral UX, you are automatically signed in to your iNEWS
n
newsroom computer system, your Interplay MAM system, your Interplay Production system, or all three. If, however, the security settings for one of these integrated systems is inaccurate, you might see a warning message that states that the application is unable to authorize the sign-in name or password. If you receive this message, click the link provided and verify your security settings.
4. (Optional) If the layout you want is not displayed, select the one you want from the Layout selector.
Left: Sign Out button. Right: Layout selector.
To sign out:
t Click Sign Out in the menu bar.
Configuring System Settings
The MediaCentral UX administrator needs to specify configuration information before users can use MediaCentral UX. You specify these settings in the System Settings layout, which is only available to administrators. The System Settings layout includes a Settings pane, in which you select the group of settings, and the Details pane, in which you specify the settings.
For information about these settings, see
To configure MediaCentral UX system settings:
1. Sign in to MediaCentral UX as an administrator.
2. Select System Settings from the Layout selector.
The System Settings layout opens.
“MediaCentral System Settings” on page 13.
12
3. In the Settings pane select a settings group, for example, General.
The Details pane displays the settings in that group.
4. In the Details pane, specify one or more settings, as described in the table at the end of this procedure.
5. Click Apply to save your new settings or click Revert to replace changed information with the previously saved settings.

MediaCentral System Settings

This topic describes settings in the System Settings layout. For information about how to access and save these settings, see
Load Balancer
Provides a view of server nodes and connections. See “Monitoring Load Balancing” in the Avid MediaCentral Platform Services Installation and Configuration Guide.
Playback Service
Settings and user credentials for the MediaCentral Playback Service. This is the service responsible for the compression and playback of media. See “Configuring MCPS for Interplay” in the Avid MediaCentral Platform Services Installation and Configuration Guide.
“Configuring System Settings” on page 12.
MediaCentral System Settings
Player
Setting Description
Server The computer name of the MediaCentral Platform server. The
MediaCentral Player uses this setting to communicate with the MediaCentral Platform server.
Media Composer | Cloud User The credentials that Media Composer Cloud uses to
communicate with the Media Central player. This user is automatically assigned a special Media Composer Cloud user role named “Playback-Only Client.” The user and role are listed in the Users layout.
You need to configure Media Composer Cloud to use this user name and password. For more information, see the Media
Composer | Cloud Installation and Configuration Guide.
13
MediaCentral System Settings
Setting Description
Variable Speed Playback Control the speed of the L key (forward) and J key (backward)
for variable speed playback (J-K-L). The default settings are:
Press 2 times: 2x normal speed
Press 3 times: 3x normal speed
Press 4 times: 4x normal speed
To change a value, type a number directly in a field. You can also use the Up Arrow and Down Arrow keys on the keyboard, or the up and down arrows next to the field, to increase or decrease the value by .10.You can include values with a decimal point. If you type more than two decimal places, the application rounds the value to two decimal places. The maximum value allowed is
9.99.
To save the new settings, click Apply. These settings apply to all users.
Image Quality Settings Define the image quality, which you set for a user group. For
more information, see
“Configuring Image Quality” on page 18.
Media | Index
An administrator uses these settings to configure Media Index. For more information, see the Avid MediaCentral Platform Services Installation and Configuration Guide.
General
Setting Description
System ID The identification number for your MediaCentral system, which
is required by Avid support. An administrator needs to enter this number, which is supplied as part of the MediaCentral installation. After the System ID is entered, it is displayed in the Home > About box.
Search Pane: Maximum Number The maximum number of items listed in a pane. To view more
items, click the Show More Results button. The range is 5 to 1000 items.
Session Timeout If you select Enabled, the number of minutes of inactivity before
a user’s session is disconnected. Session Timeout is enabled by default, and the default value is 30 minutes. You can set a time between 10 minutes and 1440 minutes (24 hours). For more information, see
“Configuring a Session Timeout” on page 21.
14
MediaCentral System Settings
iNEWS
Setting Description
iNEWS Server: System ID The system ID for an iNEWS cluster, which is set in the iNEWS
/site/system file. Using this ID ensures load balancing and failover if necessary. Do not include a suffix such as -a or -b. Ensure that all MediaCentral servers can resolve the IP addresses of systemID-a, systemID-b, and if present, systemID-c. Address resolution can be through DNS or hosts file.
Pagination: Maximum Number The maximum number of items listed in the Queue/Story pane or
the Project/Story pane. To view more items beyond the number displayed, click the Show More Results button. The range is 5 to 255 items.
Interplay MAM
Setting Description
Interplay MAM System The version stack of the Interplay MAM system enabled in
MediaCentral UX. For more information about this and other settings, see
Settings Pane” on page 52
“Configuring Interplay | MAM in the System
.
Registry Servers Specifies the following:
The computer name of the server where the Interplay MAM Configuration Service WS is running
The URL of Configuration Service WS
Information about the version of Configuration Service WS
Information about the run-time status of Configuration Service WS
Credentials The user name and password to connect to the Interplay MAM
server. The user name must match the ID of the MediaCentral system user that is created in Interplay MAM User Management. For additional information, see
Interplay | MAM User Manager” on page 50
15
“Configuring Settings in
.
MediaCentral System Settings
Setting Description
Search Specifies the search behavior. If you check Auto-Append
Wildcards, each search term is appended with an asterisk before submission. This allows a search behavior more similar to Interplay Production and iNEWS. Auto-Append Wildcards is unselected by default.
If you set Limit Result Set, Interplay MAM never returns more than this number of hits in a search. The number must be greater than zero; the default value is 1000. This is a technical limit for the result to avoid that the MediaCentral server runs out of memory if a user searches the archive for “*”.
Interplay Production
Setting Description
Interplay Production Server: Hostname The computer name or the IP address of the server that hosts the
Interplay Production database.
MediaCentral Distribution Service: Service URL
A secure URL for the server that hosts the MediaCentral Distribution Service (MCDS), which is used for send-to-playback operations. Provide the URL in the following format, including the port number: https://hostname:port. For example, https://localhost:8443. You can use an IP address instead of a hostname.
If your Interplay Production workgroup is configured for multiple MCDS servers, specify the multiple URLs separated by a comma and a space. The first server listed is the active MCDS server. Multiple MCDS servers provide a failover capability. See
“Failover for Multiple MCDS Servers” on page 31.
Location for Script Sequences: Path A path for a folder in the Interplay Production database to store
the sequences created as part of an iNEWS script. Select whether you want sub-folders created by Queue name, Date, or Story name.
Assets Pane: Maximum Number The maximum number of items listed in a pane. To view more
items, click the Show More Results button. The range is 5 to 1000 items.
16
MediaCentral System Settings
Messages & Sharing
Setting Description
Message Archiving The interval (in days) before messages are moved to an
archive location, the most recent archive date, and the number of messages archived. The default interval is 7 days.
“Configuring Message Archiving” on page 23.
See
Email Forwarding Enables and configures e-mail forwarding. You can
configure MediaCentral UX to forward messages to e-mail accounts so users can receive messages when they are not logged on to MediaCentral UX. See
Forwarding” on page 25
.
“Configuring E-Mail
Also see “Configuring Interplay | Production for Sharing Messages” on page 22.
Modules
Modules used in MediaCentral UX showing name, version, location, state, fragment. For reference only.
Send to Playback
See “Creating or Editing a Send-to-Playback Profile” on page 33.
Zones
An administrator uses these settings to configure two or more single-zone systems into a multi-zone environment. For more information, see
page 63
and the Avid MediaCentral Platform Services Installation and Configuration Guide.
“Working with MediaCentral Zones” on
17

Configuring Image Quality

The Player system settings include options to improve the image quality that is displayed in the Media viewer:
Maximum size of the proxy video. You can select the pixel dimensions of the image displayed by selecting the pixel width. This is especially useful if a user wants to work with a large Media viewer. The default pixel width is 480. As you enlarge the Media viewer, the pixel size of the image enlarges up to the maximum size.
Option to display high-resolution video (for a multi-resolution asset). You can enable a button in the Media pane that lets the user view the highest resolution video that is available for an asset. If video is available only in one resolution, the video is displayed in that resolution.
This button also allows the user to view the asset in the STP Target Resolution. If the asset is not available in the target resolution (as specified in the selected STP profile), a Media Offline screen is displayed.
This option is available for both frame-based playback and file-based playback of Interplay Production assets. It is not available for Interplay MAM assets. See
Playback” on page 20
.
Configuring Image Quality
“Configuring File-Based
You set these options for a user group that is defined in the Users layout.
18
Configuring Image Quality
Note the following:
If a user is a member of more than one group, and different pixel sizes are associated with the groups, the user is assigned the largest pixel size.
This setting does not apply to remote assets.
c
n
If workstations in a facility will regularly use enlarged images for proxy video or high-resolution video, Avid recommends changes to the MediaCentral infrastructure. For more information, see How to Buy Hardware for MediaCentral Services.
You can also set the compression of the proxy video. Select Playback Quality in the Media pane menu. For more information, see “Selecting the Playback Quality” in the Avi d MediaCentral | UX User’s Guide.
To enable settings for image quality:
1. Sign in to MediaCentral UX as an administrator.
2. Select System Settings from the Layout selector.
The System Settings layout opens.
3. In the Settings pane, select Player.
4. In the Image Quality Settings section of the Details pane, do one of the following:
t To add a new group, click the plus button, then select the user group from the User
Group menu.
t To edit settings for an existing group, click the user group name.
5. To set the image size, select the width in pixels from the Maximum Size menu.
6. To enable a button for viewing high-resolution video, select MultiRez.
After applying this setting, a user who is a member of the selected group can select STP Target Resolution or Highest Resolution from the MultiRez button, which is displayed in Asset mode and in Output mode in the Media pane.
7. Click Apply.
19

Configuring File-Based Playback

Earlier versions of MediaCentral UX used only frame-based playback. Starting with v2.1, MediaCentral UX includes an option to use file-based playback. If you select file-based playback, the media is downloaded to your workstation and played back from the downloaded media. File-based playback provides good quality in low-bandwidth situations.
A user can select file-based playback for assets loaded in Asset mode or for basic sequences loaded in Output mode. For more information, see the Video Media chapter of the Avid
MediaCentral | UX User’s Guide.
File-based playback is the default mode for Interplay MAM assets. The user’s ability to select
n
frame-based playback depends on Interplay MAM rules. The credentials used to sign in to the Interplay MAM database determine if the user is allowed to use frame-based playback.
A MediaCentral administrator has the option of configuring the bit rate for file-based playback. There are two profiles available:
Low-bandwidth: The default setting for file-based playback. This option is available for file-based playback of both Interplay Production and Interplay MAM assets. The default settings are 512 Kb/sec for video and 96 Kb/sec for audio.
Configuring File-Based Playback
High-bandwidth: This setting applies to the MultiRez option for playback of high-quality media. This option is available only for playback of Interplay Production assets. See
“Configuring Image Quality” on page 18. The default settings are 5 Mb/sec for video and
128 Kb/sec for audio.
To change the default bit rate for these profiles, you must edit a configuration file on the MediaCentral Platform server.
To configure the bit rate for file-based playback:
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:
/usr/maxt/maxedit/etc/fl_xmd.cfg
3. Locate the following lines:
<render_profile_low>video_bitrate=512000,audio_bitrate=96000,max_width= 480</render_profile_low>
<render_profile_high>video_bitrate=5000000,audio_bitrate=128000,max_wid th=960</render_profile_high>
The above examples use the default bit rates, written as bits per second.
4. Edit the video bit rate and the audio bit rate as desired, then save and close the file.
20

Configuring a Session Timeout

The following are valid values. Enter the full bit rate.
Video Bit Rate Value for File Audio Bit Rate Value for File
256 Kb 256000 64 Kb 64000
512 Kb (low profile default) 512000 96 Kb (low profile default) 96000
1 Mb 1000000 128 Kb (high profile default) 128000
3 Mb 3000000 156 Kb 156000
5 Mb (high profile default) 5000000 512 Kb 512000
10 Mb 10000000
Use the following table to estimate the amount of media that can be transferred at different bit rates. This information was based on media transferred with the following specifications:
DNxHD 36 HD_1920x1080@25p@16:9, transferred with a maximum width of 960 pixels.
Video Bit Rate/ Audio Bit Rate
256 Kb/128 Kb 2.72 MB
512 Kb/128 Kb 5.6 MB
1 Mb/128 Kb 8.8 MB
3 Mb/128 Kb 22.8 MB
5 Mb/128 Kb 32 MB
10 Mb/128 Kb 32.4 MB
Approximate Media Transfer Per Minute
Configuring a Session Timeout
By default, MediaCentral UX is configured for a session timeout. After 30 minutes of inactivity, a user’s session is disconnected. An administrator can change the time or disable the option.
This setting applies to all users. If you change and apply the setting, the new setting takes effect the next time a user loads a layout.
21

Configuring Interplay | Production for Sharing Messages

Timeout is a good way of ensuring that a system license is released when a user leaves for the day without signing out of MediaCentral UX. With the implementation of auto-save for stories and sequences, any unsaved changes are saved in a recovery file. For more information, see the Avid MediaCentral | UX User’s Guide.
To configure a session timeout:
1. Sign in to MediaCentral UX as an administrator.
2. Select System Settings from the Layout selector.
The System Settings layout opens.
3. In the Settings pane, select General.
4. In the Session Timeout section of the Details pane, make sure Enable is selected and specify the number of minutes of inactivity before a user’s session is disconnected.
You can set a time between 10 minutes and 1440 minutes (24 hours).
Configuring Interplay | Production for Sharing Messages
Before you can send messages from MediaCentral UX to Media Composer or NewsCutter, you need to configure your Interplay Production database so it uses the correct MediaCentral UX server for the messaging service.
To configure Interplay Production for sharing messages with Avid editing applications:
1. Start the Interplay | Administrator application and log in to the server for the appropriate Interplay Production workgroup.
2. In the Application Settings section of the Interplay Administrator window, click the Application Database Settings icon.
3. Click the Editing Settings tab.
4. In the database tree on the left, select the server used for your Interplay Production database (in most cases, the top-level database AvidWG).
5. In the MCS Settings section, type the URL for the server that hosts your MediaCentral Messaging Pane:
6. Click Apply.
https://[MediaCentral server hostname]
.
22

Configuring Message Archiving

You can archive MediaCentral UX messages sent using the Messages pane. Messages are archived and stored on a server, and you can view archived messages using the Messenger Archive tool.
You can specify the interval for MediaCentral UX message archiving using the following increments: 1 day, 3 days, 7 days, 14 days, or 30 days. After this time, MediaCentral UX deletes messages from the users’ view.
Message archiving applies only to messages sent using the Messages pane.
n
You can use the Messenger Archive tool to retrieve the following information about the message archive:
Number of messages in the archive
Size of the archive
The oldest message in the archive, including the date of the message
The most recent message in the archive, including the date of the message
You can also use the Messenger Archive tool to export the archive to a comma-separated values (CSV) file, with the options of compressing the file and of deleting the exported message archive from your server.
Configuring Message Archiving
The Messenger Archive tool is located in the following folder:
root
the archive utility program as Linux nodes in your cluster setup.
To configure message archiving:
1. Sign in to MediaCentral UX as an administrator.
2. Select System Settings from the Layout selector.
The System Settings layout opens.
from a command line. You can run the tool on any of the
23
/opt/avid/bin
. You must run
3. In the Settings pane select Messages & Sharing.
The Details pane displays the settings in that group.
4. Type a number in the Archiving Interval (days) text box.
Configuring Message Archiving
The default period for archiving messages is 7 days. Any message older than the interval specified are moved from the Message list to the archive location.
5. Click Apply.
To use the Message Archive tool:
1. On one of the nodes in your cluster setup, use the standard Linux command to navigate to the directory containing the Messenger Archive tool:
cd opt/avid/bin
24

Configuring E-Mail Forwarding

2. Type
acs-messenger-archive-tool
from the following table:
Option Description
-c
-o
-p
Adds a command. You can use the following values:
info
and last messages)
export
Specifies the output folder for the exported CSV file. The default folder is
/opt/avid/share/message_archives
Specifies a time period for the exported messages. You can use the following values:
•day
•week
month
half_year
•year
•all
The default value is
to run the utility, selecting the appropriate options
(lists the number of messages and the size of the archive, as well as the first
(creates a CSV file with all messages in the archive)
.
all
.
-z
-d
If you do not specify any options, the command displays the help text for the Messenger Archive
n
tool.
Creates a compressed file (.zip) for the CSV output file.
Deletes the exported data from the message archive.
Configuring E-Mail Forwarding
You can configure MediaCentral UX to forward messages to e-mail accounts so users can receive messages when they are not logged on to MediaCentral UX. You can also specify the protocols used to encrypt e-mails, using a Secure Sockets Layer (SSL), and by using or ignoring a Transport Layer Security (TLS) protocol.
E-mail forwarding requires a MediaCentral UX administrator to enable e-mail forwarding and to assign a valid SMTP server. When your administrator enables e-mail forwarding in the System Settings, MediaCentral UX users can then use the User settings to enable e-mail forwarding for their accounts and specify the e-mail address to which they want their messages sent when not logged in to MediaCentral UX.
25
To enable and configure e-mail forwarding:
1. Sign in to MediaCentral UX as an administrator.
2. Select System Settings from the Layout selector.
The System Settings layout opens.
3. In the Settings pane select Messages & Sharing.
The Details pane displays the settings in that group.
Configuring E-Mail Forwarding
4. Select Email forwarding.
5. Type a valid SMTP server name for the hosting e-mail application, and then type the appropriate port number.
6. (Option) If you want to use Secure Sockets Layer protocol, select Use SSL, and then type a user name and password for your administrator e-mail account.
7. (Option) If you do not want to use Transport Layer Security, select Ignore TLS.
8. In the Recipient’s e-mail field, type a a valid e-mail address to send a test -email message.
9. Select Validate to ensure that your SMTP configuration is correct.
A test e-mail is sent to the address specified in the settings.
An error message informs you if the validation process fails. If you receive an error message, try entering your configuration information again.
10. Click Apply.
26

Configuring for Send to Playback

Configuring for Send to Playback
You can transfer a sequence to a playback device or playout server for viewing or broadcast. This process is called send to playback, or STP. Users can also send to playback a sequence stored in an Interplay Production database.
The following topics describe administrator tasks for sending a sequence to a playback device:
“Understanding the Send-to-Playback Components and Process” on page 27
“Creating or Editing a Send-to-Playback Profile” on page 33
“Send-to-Playback Profile Examples” on page 38
“Monitoring STP Processes” on page 45
The following topic provides troubleshooting information:
“Troubleshooting Send to Playback Problems” on page 99
For information about how users send to playback, see the “Sending to Playback” chapter in the Avid MediaCentral | UX User’s Guide.

Understanding the Send-to-Playback Components and Process

A MediaCentral UX system and an Interplay Production system are required for the send-to-playback process.
Required Components
Make sure the following components are correctly installed and configured:
•MediaCentral
- MediaCentral Middleware Service
- MediaCentral Common Playback Service
- MediaCentral Distribution Service. The Distribution Service coordinates and monitors
send-to-playback and mixdown operations. It determines if there is any preprocessing required. If it determines an audio mixdown is required, it submits a Transcode Mixdown request. If Long GOP media is required, it submits an STP Encode request. You can configure your workgroup for more than one MCDS.
The MediaCentral Distribution Service communicates with other Interplay Production Services,
n
but it is not an Interplay Production Service itself.
For information about installing and configuring these components, see the MediaCentral Services Installation and Configuration Guide.
27
Configuring for Send to Playback
Interplay | Production
- Interplay | Production Services Engine. This component serves as a broker for all
Production Services. The Interplay | Transcode service and the Interplay | STP Encode service are used for MediaCentral UX send-to-playback operations.
For installation and configuration information for the Production Services Engine and Production Services, see the Interplay | Production Services Setup and User’s Guide.
- Interplay | Transcode service. This service mixes down audio for script sequences and
checks the sequence in to the Interplay | Engine. No video mixdown is required when sending a script sequence to a playback device.
- Interplay | STP Encode service. This service exports and encodes Long GOP media,
then passes the media to the Transfer Engine for a send-to-playback operation. The STP Encode service supports various XDCAM media formats.
- Interplay | Engine. This component manages the Interplay Production database.
Sequences that are sent to playback are checked into the Send to Playback folder in the Interplay Production database.
- Media Indexer. This component is used to store information of all available resolutions
for an Interplay Production asset. It enables relinking of a clip to a particular resolution (Dynamic Relink).
- Avid System Framework (ASF). This component is used for various Interplay
Production interactions. For send-to-playback, it identifies the high-availability group (HAG) that includes the Media Indexer used for relinking.
- Interplay | Transfer Engine. This component sends the sequence to the playout device. If
you are sending to an Avid AirSpeed, Avid AirSpeed Multi Stream, or Avid AirSpeed 5000 server, you do not need a separate Transfer Engine, because it is included as a component of the AirSpeed Multi Stream server. For installation and configuration information, see the Interplay | Transfer Setup and User’s Guide.
Playback Servers
- AirSpeed 5000, AirSpeed Multi Stream. A playback server that can handle different
formats, including HD media. It includes a Transfer Manager as an installable component.
- AirSpeed (Classic). A playback server that can handle different formats but only one at
a time.
- Third-party playback servers
For more information, see the following topics:
“Send-To-Playback Workflow: I-Frame Sequences” on page 29
“Send-To-Playback Workflow: Long GOP Sequences” on page 30
28
“Sending a Mixed-Resolution Long GOP Sequence to a Playback Device” on page 31
MediaCentral Client (Browser)
ww
qq ee
ISIS Shared Storage
Media Indexer
MediaCentral Middleware Service
y
Production Services Engine
Playback Server
i
Interplay Transcode
t
MediaCentral Distribution Service
wru
Interplay Transfer
“Failover for Multiple MCDS Servers” on page 31
Send-To-Playback Workflow: I-Frame Sequences
The following illustration shows a typical send-to-playback workflow for I-frame (non-Long GOP) sequences.
1. The user starts an STP process in MediaCentral UX.
Configuring for Send to Playback
2. The MediaCentral Middleware Service checks media status through Media Indexer.
3. The MediaCentral Middleware Service creates an STP job and sends it to the MediaCentral Distribution Service (MCDS). MCDS performs an analysis of the sequence to determine if it needs an audio mixdown, a video mixdown, or both.
4. The MCDS uses MI to dynamically relink the sequence to media in the target resolution.
5. The MCDS sends a request for any required mixdowns to the Production Services Engine, which then sends the jobs to the Interplay | Transcode provider.
6. Interplay | Transcode performs the mixdowns and saves the media on the Avid ISIS system.
7. MCDS initiates a transfer to the playback server, through Interplay | Transfer.
8. Interplay | Transfer transfers the sequence to the playback server.
29
Send-To-Playback Workflow: Long GOP Sequences
MediaCentral Client (Browser)
ww
qq ee
ISIS Shared Storage
Media Indexer
y
Production Services Engine
Playback Server
i
Interplay Transcode
t
MediaCentral Distribution Service
wr
u
Interplay Transfer
STP Encode
o
1)
MediaCentral Middleware Service
The following illustration shows a typical send-to-playback workflow for a Long GOP sequence.
1. The user starts an STP process in MediaCentral UX.
2. The MediaCentral Middleware Service checks media status with through Media Indexer.
3. The MediaCentral Middleware Service creates an STP job and sends it to the MediaCentral Distribution Service (MCDS). MCDS performs an analysis of the sequence to determine if it needs mixdown or Long GOP encoding.
Configuring for Send to Playback
- If an audio mixdown or video mixdown is needed, the MCDS will send a Transcode
mixdown job to the Production Services Engine, which sends the job to the Interplay | Transcode provider.
- If no transcoding is required, the MCDS will send an STP Encode job to the Production
Services Engine, which sends the job to the STP Encode provider.
4. The MCDS uses ASF and MI to dynamically relink the sequence to media in the target resolution.
5. The MCDS sends a request for any required mixdowns to the Production Services Engine, which then sends the jobs to the Interplay | Transcode provider.
After sending the Transcode jobs, the MCDS periodically checks the Production Services Engine to determine when to send the encoding job to the STP Encode provider.
6. Interplay | Transcode performs the required jobs and saves the media on the Avid ISIS system.
7. When the transcode jobs are complete, MCDS sends an encoding job to the STP Encode provider.
30
Configuring for Send to Playback
8. STP Encode creates Long GOP OP1a media, stores it on the ISIS system, and initiates a transfer to the playout server, through Interplay | Transfer.
9. Interplay | Transfer transfers the sequence to the playback server.
Sending a Mixed-Resolution Long GOP Sequence to a Playback Device
In most cases, all media used in the sequence must be available in the target resolution to start an STP operation.
However, when you select a Long GOP resolution as a target resolution, you can mix media of different resolutions if the frame rates match. For example, if the target resolution is XDCAM-HD 1080i, you can include both XDCAM 1080i clips and DV25 411 NTSC clips in the same sequence. Both use an actual frame rate of 29.97 fps.
The DV25 clips do not need to be transcoded to XDCAM 1080i before the STP operation begins. For Long GOP sequences, any necessary transcoding takes place during the STP operation.
For more information, see “Sending a Mixed-Resolution Long GOP Sequence to a Playback Device” in the Avid MediaCentral | UX User’s Guide.
Failover for Multiple MCDS Servers
You can configure your Interplay Production workgroup for multiple MediaCentral Distribution Service (MCDS) servers. Multiple MCDS servers provide a high-availability configuration and failover capability. For installation and configuration information, see the MediaCentral Services Installation and Configuration Guide and
“Configuring System Settings” on page 12.
The MediaCentral Middleware Service (MCMS) keeps an ordered list of the available MCDS servers to be used for send to playback (STP). The active server is determined by the order in which it is listed in the Interplay Production settings (see
page 12
). Initially, the first server listed is the active server. Each time you send an STP job, the
“Configuring System Settings” on
ICMS checks if the currently active server is available. If not, the next available server in the list is made the active server. If none of the listed servers are available, the job will fail.
31
Example
qq
qw
qe
qr
qt
qy
The following example shows servers MCDS Server A, MCDS Server B, and MCDS Server C configured for MCDS high availability.
1. Server A is listed first, so it is initially the active server.
2. Server A stops responding, so all new jobs go to Server B.
3. Server A comes back up, but jobs continue to go to Server B.
4. Server B stops responding, so all new jobs go to Server C.
5. Server C stops responding, so all new jobs go to Server A.
6. Server A stops responding, Server B is not responding, so all new jobs go to Server C
Configuring for Send to Playback
Configuration Changes
If you change the servers listed in the System Settings, and the currently active MCDS server is in the new list, the order in which availability is checked on failover begins with the currently active server, no matter where it is located on the list.
Example 1:
1. Servers A, B and C were initially configured for MCDS high availability.
2. Server B is the currently the active MCDS.
3. You reconfigure the settings list to use servers D, B and E.
a. Server B remains the active server (not D).
b. The sequence for testing on failover is B > E > D.
32
Example 2:
1. Servers A, B and C were initially configured for MCDS high availability.
2. Server B is the currently the active MCDS.
3. You reconfigure the settings list to use servers D, E, and F.
a. Server B will no longer be active because it is not on the list.
b. The sequence for testing on failover is now D> E > F.

Creating or Editing a Send-to-Playback Profile

A send-to-playback operation requires a profile, which a MediaCentral UX administrator creates in the Send to Playback settings Details pane.
The values displayed in some fields are retrieved from the Interplay Production system. Make sure the send-to-playback configuration in Interplay Production is done correctly before creating profiles in MediaCentral UX.
The following procedure provides general steps in creating or editing a send-to-playback profile. For more information, see
“Send-to-Playback Profile Examples” on page 38.
Configuring for Send to Playback
The first time you sign in, information might not be available to create a profile. In this case, sign
n
out and sign in again to MediaCentral UX. MediaCentral UX can then get the send-to-playback information from the Interplay Production engine, and you can create a send-to-playback profile.
To create or edit a send-to-playback profile:
1. Sign in to MediaCentral UX as an Administrator.
2. Select System Settings from the Layouts list.
The Settings pane and Details pane open.
3. In the Settings tab, select Send to Playback.
The top part of the Details pane lists the send-to-playback profiles, and the bottom part lists the profile details.
33
Configuring for Send to Playback
c
If the menus do not display any values, the connection to Interplay Production might not be working. Try signing out and signing back in, or check the configuration between MediaCentral UX and Interplay Production. For more information, see the MediaCentral Services Installation and Configuration Guide.
4. Do one of the following:
t To create a new profile, click the + (plus) button in the Send to Playback Profiles
section.
A profile named “New Profile” is created in the Send to Playback Profiles section.
t To edit an existing profile, select the profile in the Send to Playback Profiles section.
5. In the Details tab, specify the required settings, as described in the table at the end of this procedure.
6. Click Apply to save the profile. If you are editing a file, click Revert to return to the original settings.
34
Configuring for Send to Playback
The following table describes the settings in each group.
Send to Playback Setting Description
Name A name for the profile. Choose a meaningful, descriptive name because
this name is displayed to users.
Individual Device or Studio Specifies if the profile applies to a single playout server or to an
AirSpeed Studio.
If you select Individual Device, the following fields are displayed:
Servers. Select the Transfer Engine server for the profile. This list includes all Interplay | Transfer Engines, AirSpeed Transfer Engines, and AirSpeed Multi Stream Transfer Engines in the Interplay Production workgroup. See “Selecting a Transfer Server”
on page 38
Playback Device. Select the playback device for the profile. This list includes device profiles created on an Interplay | Transfer Engine as well as individually named AirSpeed and AirSpeed Multi Stream servers. This list can also include individual devices in an AirSpeed Studio if the following option is selected in the Interplay | Transfer Settings view in the Interplay | Administrator: “Show individual studio hosts in Send to Playback choices.”
If you select an AirSpeed Multi Stream server, you have a choice of a playback device with the name of the server and a playback device with the name of the server followed by -HD. Use the HD device for XDCAM-HD Long GOP media only. See
Device” on page 39
If you select Studio, the following fields are displayed:
Studio. Select the AirSpeed Studio group for the profile. This list displays the AirSpeed Studio groups in the Interplay Production workgroup.
Playback Device. Select the playback device for the profile. You have a choice of a playback device with the name of the server and a playback device with the name of the server followed by -HD. Use the HD device for XDCAM-HD Long GOP media only.
.
“Selecting a Playback
.
35
Configuring for Send to Playback
Send to Playback Setting Description
Video Options Long GOP: Select Long GOP if this profile will be used to transfer
Long GOP media (for example, XDCAM HD). Long GOP media is transferred through the STP Encode service.
AirSpeed: Select AirSpeed if this profile will be used to transfer to an Avid AirSpeed or AirSpeed Multi Stream server.
Accelerated STP: If you select both Long GOP and AirSpeed, the Accelerated STP option is activated. Select this option if this profile will be used with an AirSpeed Multi Stream server version 1.7 or later. This feature allows an AirSpeed Multi Stream user to play media while it is being transferred.
Dalet: Select Dalet if this profile will be used to transfer the audio part of story sequences or other sequences for further reuse in a Dalet audio system. To completely enable this feature, you also need to install a dll file that was developed by Dalet especially for this workflow. You need to contact Dalet to obtain this dll file.
Selecting this option enables transfer of audio only. There is
n
currently no support for transferring video.
Video Target Resolution Select the resolution for the sequence that you want to send to the
playback device. This list includes video resolutions that are supported in the Interplay Production workgroup.
If you select Long GOP as a video option and a Long GOP (XD CAM) resolution, the MediaCentral Distribution Service uses the Interplay Production Dynamic Relink technology to link to media in a similar resolution (closest match) if media is not available in the target resolution.
If you do not select Long GOP as a video option, and media is not available in a target resolution, the send-to-playback operation fails with an error message.
In both cases, audio is linked to a similar resolution (closest match).
Video Frame Rate Select a frame rate that matches the selected video target resolution.
Some resolutions specify a frame rate and others do not. The frame rate is also a more exact value. For example, for XDCAM-HD 50 mbps 1080i 60, select 29.97.
Audio Target Sample Rate 48 kHz (this is the only choice)
The audio target format is always PCM
Audio Target Bit Depth Select 16 bit or 24 bit.
36
Configuring for Send to Playback
Send to Playback Setting Description
Audio Target Mixdown Mode Select Stereo or Direct Out. The maximum number of audio tracks
supported for send to playback is 16.
Stereo: Maps to a left/right alternating pan (odd tracks on one channel, even tracks on the other channel), creates a stereo mixdown of all audio tracks, and outputs the resulting two tracks to two channels when sent to playback. This results in two channels of audio.
Direct Out: Does not combine audio in any way; all audio tracks remain as they are in the source media, which creates separate output channels for each audio track in the source media when it is sent to playback. Select this option to retain the greatest flexibility to do further audio manipulation after the source media is sent to the playback device.
Interplay ISIS Workspace Select a workspace for storing media that results from an audio
mixdown or an STP Encode operation.
To delete a profile, select the profile you want to delete and click the minus (-) button in the Send to Playback Profiles section.
For information about performing a send-to-playback operation, see the Avid MediaCentral | UX User’s Guide.
37

Send-to-Playback Profile Examples

The following examples of send-to-playback profiles show settings for different resolutions and different playback servers.
Selecting a Transfer Server
When you select a server in an STP profile, the Servers list includes all Interplay | Transfer Engines, AirSpeed Transfer Engines, and AirSpeed Multi Stream Transfer Engines that are specified in the Interplay Production workgroup. The following illustration shows the Servers list and the corresponding Interplay | Transfer Settings in the Interplay | Administrator.
Configuring for Send to Playback
Individual AirSpeed Multi Stream servers in a studio are listed because the option “Show individual studio hosts in Send to Playback choices” is selected in the Interplay Transfer Settings in the Interplay | Administrator.
38
Configuring for Send to Playback
Selecting a Playback Device
When you select a playback device in an STP profile, the Playback Device list includes the playback devices that are associated with the Interplay | Transfer server you selected.
For AirSpeed servers, there is only one selection that matches the server name.
For AirSpeed Multi Stream servers, there might be two types of selections:
- One selection that matches the server name. Select this playback device for all resolutions except for XDCAM-HD Long GOP media.
- One selection that adds -HD to the server name. The -HD suffix indicates that the AirSpeed Multi Stream server is equipped with an HD board. Select this playback device for XDCAM-HD Long GOP media.
For Transfer Engine servers, the list includes all devices that have been configured for the selected Transfer Engine server. The following illustration shows the Playback Device list for a Transfer Engines server and the corresponding list in the Transfer Engine Configuration window.
39
Configuring for Send to Playback
40
Configuring for Send to Playback
XDCAM-HD on AirSpeed Multi Stream
This profile, named AMS1-XDCAM1080i60_50mb, specifies settings for an AirSpeed Multi Stream server that supports XDCAM-HD media.
Note the following:
Servers: Airspeed Multi Stream includes a Transfer Engine, so A51-WG1-AMS1 is the computer name for the AMS server.
Playback Device: Because this profile supports XDCAM-HD Long GOP media, the playback device name includes the -HD suffix.
41
Configuring for Send to Playback
Long GOP and AirSpeed must be selected for this profile. With these options selected Accelerated STP (Send to Playback) becomes available, and can be used in this case because the AirSpeed MultiStream server is version 1.7 or later.
The remaining media options specifically describe the target video and audio resolutions. The Mixdown Mode is set for Stereo, and the specified ISIS workspace will hold the mixed-down media.
XDCAM-HD on AirSpeed Multi Stream Studio
The following profile, named AMS_studio, is similar to the previous profile but is configured for an AirSpeed Multi Stream Studio.
42
Configuring for Send to Playback
Note the following:
Studio: The Studio option is selected and the Servers list is replaced by the Studio list. A51-WG1-AMS[3] is the computer name for the AirSpeed Multi Stream Studio group.
Playback Device: Because this profile supports XDCAM-HD Long GOP media, the playback device name includes the -HD suffix.
Long GOP and AirSpeed must be selected for this profile. With these options selected Accelerated STP (Send to Playback) becomes available, and can be used in this case because the AirSpeed MultiStream server is version 1.7 or later.
The remaining media options specifically describe the target video and audio resolutions. The Mixdown Mode is set for Direct Out, and the specified ISIS workspace will hold the mixed-down media.
SD on AirSpeed Multi Stream
The following profile, named AMS2, specifies settings for an AirSpeed Multi Stream server that supports DV 25 SD media.
43
Configuring for Send to Playback
Note the following:
Servers: A51-WG1-AMS2 is the computer name for this AirSpeed Multi Stream server.
Playback Device: Because this profile supports SD media, the playback device name matches the server name and does not include the -HD suffix.
AirSpeed must be selected for this profile.
The remaining media options specifically describe the target video and audio resolutions. The Mixdown Mode is set for Stereo, and the specified ISIS workspace will hold the mixed-down media.
Generic FTP Profile
The following profile, named Omneon, specifies settings for a third-party server configured for Generic FTP settings through a Transfer Engine server.
44
Note the following:
Servers: A51-WG1-TM2 is the computer name for the Transfer Engine server.
Playback Device: a51-wg1-tm2:6534/OMN_SD is the third-party server configured through the Transfer Engine.
The remaining media options specifically describe the target video and audio resolutions. The Mixdown Mode is set for Stereo, and the specified ISIS workspace will hold the mixed-down media.

Monitoring STP Processes

The Progress pane is used to monitor sequence mixdowns and send to playback processes as they happen. For more information, see the Progress Pane topic in the Avid MediaCentral | UX User’s Guide.
An STP job might use Interplay Transcode and STP Encode to prepare the STP job for transfer. When this occurs, the Transcode and STP Encode jobs are listed in the Media Services and Transfer Status Tool while processing, but are removed from the jobs list after processing is complete. This behavior is different from typical job status reporting, in which jobs persist after processing is complete.

Configuring Settings in the Interplay | Production Administrator

A similar situation occurs for a Delivery job that uses Mark In to Mark Out. These jobs use
n
Interplay Consolidate and Interplay Production Services Automation to prepare the files for delivery. An Interplay Consolidate job is deleted after processing is complete. An Interplay Production Services Automation job persists.
Configuring Settings in the Interplay | Production Administrator
The Interplay Production Administrator application includes settings that apply to MediaCentral UX. The initial configuration of these settings is described in the MediaCentral Services Installation and Configuration Guide. After the initial configuration, you might want to modify these settings.
Settings that apply to MediaCentral UX are in the following views:
Application Database Settings: audio settings and others
Instinct/Assist User Options: markers (locators) and restrictions settings
In Media Composer v6.0, Avid Symphony v6.0, and NewsCutter v10.0, the term “locators” was
n
changed to “markers” in both the user interface and the documentation. MediaCentral UX uses the term “markers.” Interplay Production currently uses the term “locators.”
45
Configuring Settings in the Interplay | Production Administrator
To check or modify Application Database settings in the Interplay | Administrator:
1. Start the Interplay | Administrator application and log in to the server for the appropriate Interplay Production workgroup.
2. In the Application Settings section of the Interplay Administrator window, click the Application Database Settings icon.
3. Click the Editing Settings tab.
4. In the database tree on the left, select the folder to which you want to apply the settings (in most cases, the top-level database AvidWG.
5. Select the desired settings and click Apply.
The following table describes settings that are applicable to MediaCentral UX.
Section Setting Description
Format Video Format This setting determines the default video format for Interplay
Production sequences. Select a format or select Any. If you select Any, MediaCentral UX determines the video format by using the format of the first clip that the user adds to the sequence.
Audio Patching Natural Sound What you choose in the Audio Patching section determines how
many channels are shown (for NAT or SOT) in the context menu options for audio when a user right-clicks on a clip in the Sequence Timeline.
This setting is the channel count for natural sound. Options include: 1-Channel or 2-Channel.
Audio - Track labels
Sound on Tape This setting is the channel count for sound on tape. Options
include: 1-Channel or 2-Channel.
Natural Sound label
Sound on Tape label
Voice Over label This setting determines the wording or character(s) used as a
This setting determines the wording or character(s) used as a label for the natural sound track control in the Audio pane as well as the header for the natural sound column in the Script Editor’s Sequence Timeline. By default, NAT is used.
This setting determines the wording or character(s) used as a label for the sound on tape track control in the Audio pane as well as the header for the sound on tape column in the Script Editor’s Sequence Timeline. By default, SOT is used.
label for the voice-over track control in the Audio pane as well as the header for the voice-over column in the Script Editor’s Sequence Timeline. By default, VO is used.
46
Configuring Settings in the Interplay | Production Administrator
Section Setting Description
Audio - Source audio patching
Audio - Storyline audio patching
Audio - General settings
Natural Sound tracks 1 & 2
Sound on Tape tracks 1 & 2
These settings determine which two tracks are used for natural sound from the source media.
These settings determine which two tracks are used for sound on tape from the source media.
Voice Over track This setting determines which track is used for voice-over audio
from the source media.
Natural Sound tracks 1 & 2
These settings determine which two tracks are used for natural sound on the output sequence. Each track for natural sound and sound on tape must be unique. For instance, do not set the first track for natural sound to A1 if the first track for sound on tape is already set to A1.
Sound on Tape tracks 1 & 2
These settings determine which two tracks are used for sound on tape on the output sequence. Each track for natural sound and sound on tape must be unique. For instance, do not set the first track for sound on tape to A1 if the first track for natural sound is already set to A1.
Voice Over track This settings determines which track is used for voice-over audio
on the output sequence.
Media Creation workspace
This is the name of the location on ISIS where MediaCentral UX creates voice-over files.
Sample bit depth Set this to 16 for MediaCentral UX.
Ducking [-db] When audio must be ducked because of overlapping tracks, this
Dynamic Relink Dynamic Relink
Enabled
Audio Effects Dissolve Duration
[frames]
Center-Panned Sound on Tape and Voice Over
setting (in decibels) is what determines the reduction in audio level.
This setting is not configured for MediaCentral UX in this location in the Interplay | Administrator application. Instead, this setting is configured in the Playback Service group of the MediaCentral UX System Settings layout.
Brief dissolves between audio tracks are used to make audio edits sound smooth. Set this to the number of frames you want dissolves between audio edits to last.
If enabled, maps the VO track as center-panned (played on both channels). This setting applies to both Mono and Stereo Mixdown modes. For MediaCentral UX, this setting applies only to the VO track. If the setting is not enabled, VO is mapped odd tracks=left, even tracks=right
47
Configuring Settings in the Interplay | Production Administrator
Section Setting Description
MediaCentral Playback Service
MCS Settings Messaging URL Type the URL for the server that hosts your MediaCentral
To check or modify settings for markers and restrictions in the Interplay | Administrator:
Hostname Username Password
These settings are used for Media Composer Cloud, not MediaCentral UX.
Messaging Pane, using the following syntax: https://MediaCentral server hostname
1. Start the Interplay | Administrator application and log in to the server for the appropriate Interplay Production workgroup.
2. In the Application Settings section of the Interplay Administrator window, click the Instinct/Assist User Settings icon.
3. In the Users tree on the left, select an individual user or a group of users.
The settings for the selected user or user group area are displayed in the pane on the right.
4. Select the desired settings and click Apply.
The following table describes settings that are applicable to MediaCentral UX.
Section Setting Description
Permission Settings
Can create locators
If yes, allows the selected user or group to create markers. If no, a user of an Avid editing application can still create markers for an asset, but can check in only the asset, not the marker metadata (an error message is displayed).
In most cases, if you want a user to create markers, select “yes” for both “Can create locators” and “Can modify locators.” Both settings are needed because adding text is one aspect of modifying a marker.
Administrators and owners have the ability to create markers by default. Other users must have “Can create locators” set to “yes” and must also have a read/write or read/write/delete role for at least one folder that contains the asset.
48
Configuring Settings in the Interplay | Production Administrator
Section Setting Description
Permission Settings
Permission Settings
Permission Settings
Can modify locators
Can create restrictions
Can modify restrictions
If yes, allows the selected user or group to modify or delete markers. If no, a user of an Avid editing application can still modify markers on an asset, but can check in only the asset, not the marker metadata (an error message is displayed).
Administrators and owners have the ability to modify markers by default. Other users must have “Can modify locators” set to “yes” and must also have a read/write or read/write/delete role for at least one folder that contains the asset.
If yes, allows the selected user or group to mark a section of a clip with a restriction marker. In most cases, if you want a user to create restrictions, select “yes” for both “Can create restrictions” and “Can modify restrictions.” Adding text is considered modifying a restriction.
Administrators and owners have this right set by default. Other users who have this right must also have a read/write or read/write/delete role for at least one folder that contains the asset.
If yes, allows the selected user or group to modify a restriction.
Administrators and owners have this right set by default. Other users who have this right must also have a read/write or read/write/delete role for at least one folder that contains the asset.
49

Configuring Interplay | MAM

To use MediaCentral UX with Interplay MAM, an administrator has to check and adapt some configuration settings in Interplay MAM and MediaCentral configuration applications.
Prerequisites: Before configuring and using Interplay MAM in MediaCentral, the following must be performed:
Install the MAM.Core.MediaCentralConnection package in the MAM system. This package contains components and settings that are required to connect Interplay MAM to MediaCentral (BPMController and SyncCentralIndex Service).
Install the MAM connector on the MediaCentral Platform server. See the Avid MediaCentral Platform Services Installation and Configuration Guide.
Mount the filesystem containing the Interplay MAM proxies on the MCS servers. See the Avid MediaCentral Platform Services Installation and Configuration Guide.
After installing the MAM.Core.MediaCentralConnection package and MAM connector, and mounting the file system, perform the following:
1. Check if the MediaCentral system user is available in Interplay MAM User Management.
“Configuring Settings in Interplay | MAM User Manager” on page 50.
See
Configuring Interplay | MAM
2. Provide Interplay MAM configuration settings in MediaCentral UX System Settings pane.
“Configuring Interplay | MAM in the System Settings Pane” on page 52.
See
3. Check if Central Index is configured properly to be used with Interplay MAM. See
“Configuring Central Index for Interplay | MAM” on page 54.
4. Create or import Interplay MAM users in MediaCentral. See
Users in MediaCentral” on page 55
.
“Creating Interplay | MAM

Configuring Settings in Interplay | MAM User Manager

To ensure that users who sign in to MediaCentral UX can automatically sign in to Interplay MAM, do the following:
1. Check if the MediaCentral system user is available in Interplay MAM User Management
(default ID: system user, as described in the procedure in this section. For more information, see the Interplay | MAM User Manager User’s Guide.
2. Use the MediaCentral system user ID and password as the credentials in the Credentials area
of the Interplay MAM settings in the System Settings layout. See
Interplay | MAM in the System Settings Pane” on page 52
Configure the MediaCentral user settings in Interplay MAM before specifying the Interplay MAM credentials in MediaCentral UX.
Service-Ics
, default password:
Avid123
). If not, create the MediaCentral
.
“Configuring
50
Configuring Interplay | MAM
To create the MediaCentral system user:
1. Sign in to Interplay MAM Control Center as an administrator.
2. Open the User Manager from within Interplay MAM Control Center.
3. Open the Users view.
4. Click the Add New User button in the Users pane.
The Add User dialog box opens.
5. Provide data for the mandatory fields:
a. Id: ID of the user account. The ID must be unique and cannot be changed. Avid
recommends using Service-Ics.
b. Password: Password of the user account.
c. Confirm: Confirmation of the password for the user account.
6. Click OK.
The new user account is added to the database and the User ID is shown in the Users pane.
7. Click the Edit User Rights button.
The Edit User Rights dialog box opens.
8. Click the right UserManagement/LoginAsMandate in the Available Rights box.
The right UserManagement/LoginAsMandate is moved to the Granted Rights box.
9. Click OK.
The rights assignment is applied. The assigned right is shown in the User Rights pane.
10. Click the Change Group Membership button.
The Edit User Groups dialog opens.
11. Click the MediaCentral group in the Available Groups box to assign the user to the MediaCentral group.
12. Click OK.
The group assignment is applied. The assigned group is shown in the Member of Groups pane.
13. Quit User Manager.
51
Configuring Interplay | MAM

Configuring Interplay | MAM in the System Settings Pane

The MediaCentral administrator must specify Interplay MAM configuration information before you can use MediaCentral UX with Interplay MAM.
To configure Interplay MAM settings:
1. Sign in to MediaCentral UX as an administrator.
2. Select System Settings from the Layouts list.
The Settings pane and Details pane open.
3. Do one of the following:
t To add and configure a new Interplay MAM system, click the Settings pane menu button
and select Add Interplay | MAM. An entry “New Interplay | MAM” is added to the Settings pane. You can rename the entry by double-clicking and overwriting it.
Note that you can configure more than one MAM system in a MediaCentral server if those MAM systems are connected to the bus of this MediaCentral instance. Also note that for each MAM system a unique Default Realm must be configured in Interplay MAM System Administrator.
t To edit the settings of an existing MAM system, select its name in the Settings pane. In
the following illustration it is named Interplay | MAM.
The Details pane displays the Interplay MAM settings.
52
Configuring Interplay | MAM
4. Configure the MAM System settings:
a. Select Enabled to make the MAM system available in MediaCentral UX. Deselect
Enabled to make the MAM system temporarily unavailable for user access.
b. Click Version Stack and select the version number of the MAM system to be connected.
5. Configure the Registry Servers settings:
a. Do one of the following:
t To create a new registry server entry, click the + (plus) button in the Registry
Servers section.
t To edit an existing registry server entry, select it in the Registry Servers section.
b. Type the host name or IP address of the server where the Configuration Service WS is
running. The name is automatically inserted as <servername> in the URL when you leave the Name field.
c. (Option) Change the server name of the automatically generated URL
http://<servername>:9910/ControlCenter/ConfigurationService/Naming.asmx.
If you change the server name the Name field is updated when you leave the URL field. The Version, System Id, Bus Realm, and Status fields are automatically filled in and updated when you leave the Name or URL field.
n
c
6. Configure the credentials that are required to connect MediaCentral UX automatically to the Interplay MAM server:
User name and password must match the credentials of the MediaCentral system user that is created in Interplay MAM User Manager. For more information, see “Configuring Settings in
Interplay | MAM User Manager” on page 50.
a. Type the user name (default:
b. Type a password (default:
7. Configure the behavior of MAM Searches in MediaCentral UX:
Changing the default settings might result in slow performance or an out of memory error. Avid does not recommend changing these settings.
a. Select Auto-Append Wildcards if you want to append each search term by an asterisk
before submission. This allows a search behavior more similar to Interplay Production and iNEWS. However, selecting Auto-Append Wildcards significantly slows down your searches for MAM assets.
b. Deselect Limit Result Set if you want MAM to return all hits in a search. However, if
you search for “*” the Interplay Central server might run out of memory. The default result limit is 1000.
Service-Ics
Avid123
).
).
53
8. Click Apply.

Configuring Central Index for Interplay | MAM

To use Central Index for Interplay MAM in MediaCentral UX, check and adapt the following settings. Note that these settings have been configured during the installation of the MAM.Core.MediaCentralConnection package and should already show correct values.
To configure Central Index for Interplay MAM:
1. Check that Media | Index services are installed and configured properly in MediaCentral and that the system data index is created. For additional information, see the Avid Media | Index Configuration Guide.
2. Sign in to Interplay MAM Control Center as an administrator and open the System Administrator.
3. In the Configuration tab, select the profile Global > section Bus and check the following settings:
t HostNames: must show the name of the ICS host.
t DefaultRealm: must show the name of the system realm.
4. Select the section SystemInfo and check if the key SystemId shows a valid value. Note that this ID must not be changed once it was set up.
Configuring Interplay | MAM
5. Select the profile SyncCentralIndex > section Settings and set the value of the key EnableDataPropagation to true, if necessary.
6. Select the profile DataManagerWS > section CentralIndex and set the value of the key MarkDirtyEnabled to true, if necessary.
7. In Interplay MAM Control Center, open the Sync Service Administrator.
8. On the Monitor tab, select the option Synchronize all objects and click the Synchronize button.
All Interplay MAM objects are synchronized to Central Index. Note that this can take a long time. This step is only needed once after enabling synchronization. As long as synchronization is enabled all changes are propagated automatically to Central Index. For more information, see the Interplay | MAM Sync Service Administrator User’s Guide.
54

Creating Interplay | MAM Users in MediaCentral

To work with MediaCentral UX, all Interplay MAM users must also be available in MediaCentral. To avoid entering every user twice in MediaCentral and Interplay MAM, connect the User Managements of both systems to the same Active Directory. This allows importing the Interplay MAM users to MediaCentral. Note that there is no runtime authentication against the Active Directory on MediaCentral side.
Once created in MediaCentral, Interplay MAM users can log in to MediaCentral UX using their Interplay MAM credentials. The MediaCentral User Management then uses the system user “Service-Ics” to do a mandate login for the user in Interplay MAM User Management.
To create Interplay MAM users in MediaCentral:
1. Import the Interplay MAM user as described in “Importing Users” on page 67.
Configuring Interplay | MAM
2. (Option) Create new users as described in
page 75
3. Assign roles to users as described in
.
“Assigning Roles” on page 89.
“Creating a New User or Editing User Details” on
55

2 User Management

The following topics provide information about managing MediaCentral UX users and groups:

Opening the Users Layout

The Users Layout
Understanding Users and Groups
Available Layouts: Administrators and Users
Working with MediaCentral Zones
Managing Users and Groups
Creating, Deleting, and Assigning Roles
Displaying Information in the Details Pane
Viewing and Ending Active Sessions
Opening the Users Layout
The Users layout is a layout that a MediaCentral UX administrator uses to import, create, and manage users and groups.
To open the Users layout:
1. Sign in to MediaCentral UX as an administrator and select Users from the Layout selector.
The Layout selector shows the name of the current layout. The list shows the role for the signed-in user, along with the layouts that role can access. In the following illustration, the signed-in user is assigned the Administrator role and has seven layouts available.

The Users Layout

w
q
r
t
e
The Users layout consists of seven panes: Active Sessions, Details, Help, Layouts, MediaCentral Zones, Roles, and User Tree. The following illustration shows the default layout with several panes displayed. In this illustration, the group Journalists is selected and the Details pane shows information about the group.
The Users Layout
57
The Users Layout
Display or Control Description
1 Menu bar Includes the same items as the Menu bar in other MediaCentral UX layouts. The
contents of the Panes menu is specific to the Users layout.
2 User Tree pane Displays the contents of the user database. For more information, see
Pane” on page 58
Media Central Zones pane Lists the registered MediaCentral zones. Configuring MediaCentral servers as
MediaCentral zones allows the servers to share a central User Management Service (UMS). It also allows users to search for assets across multiple zones and to have remote assets delivered to the local zone. For more information, see
“Working with MediaCentral Zones” on page 63.
3 Roles pane Lists the default roles and any roles you created. For more information, see
“Creating, Deleting, and Assigning Roles” on page 84.
Layouts pane Lists the default layouts and lets you assign access to users or groups. For more
information, see
4 Layout selector Includes the same options as other MediaCentral UX layouts, but only
administrators have access to the Systems Settings and Users layouts. For more information, see
5 Details pane The Details pane displays information about the group or user you double-click in
the user tree. If you double-click the top-level group (Users), the pane lets you specify information about the selected Authentication Provider. The Details pane also displays information about a selected role or zone.
Active Sessions pane The Active Sessions pane displays a list of users who are currently signed in to the
MediaCentral UX Web application. For more information, see
Ending Active Sessions” on page 93
.
“Creating and Deleting Roles” on page 88.
“Available Layouts: Administrators and Users” on page 62.
.
“User Tree
“Viewing and
You can adjust the size and location of the panes in the same way as you do in other MediaCentral UX layouts. For more information, see the Avid MediaCentral | UX User’s Guide or the Avid MediaCentral | UX Help.
User Tree Pane
The User Tree pane displays the contents of the user database in a hierarchical arrangement of groups and users. Each entry in the hierarchy is represented by an icon, as shown in the following illustration.
58
The Users Layout
w
r t
y
q
e
Display or Control Description
1 User Tree toolbar Includes the following buttons: Refresh, Expand All, Collapse All, Add User, Add
Group, Delete. The same commands are included in the Pane Menu.
2 Filter field Lets you enter text to filter the list of users and groups. The list filters as you type.
This field is available in several panes in addition to the user tree: Roles, Layouts, and Active Sessions. Press Ctrl-F to activate the field for typing. You can use the Up and Down Arrow keys to move from the filter field to the pane entries and back to the filter field.
3 Top-level group (Users) A folder that functions as a top-level group for users and groups.
4 User The sign-in name for a MediaCentral account. The illustration shows the default
Administrator user. For more information, see “Understanding Users and Groups”
on page 60
5 Group A name that represents a group of users. For more information, see
Users and Groups” on page 66
6 Pane Menu button Displays a list of options. See the following list.
and “Managing Users and Groups” on page 66.
“Managing
.
The active Pane Menu items depend on the selected entry in the user tree, as listed in the following table.
Selected Entry in the User Tree:
Top-Level Group Group User
Refresh Refresh Refresh
Create User Create User Create User
Create Group Create Group Create Group
Remove from Group (child groups only) Remove from Group
59

Understanding Users and Groups

Selected Entry in the User Tree:
Top-Level Group Group User
Expand All Expand All
Collapse All Collapse All
Delete (except for Administrators, Import, and Unassigned)
Import Users Import Users Import Users
Help Help Help
Understanding Users and Groups
Users and groups are the basic entities that you manage in MediaCentral UX. The following are concepts about users and groups that you should understand:
MediaCentral User Management is a service that provides the ability to do the following:
- Create users and groups
- Manage users and groups
- Authenticate users across iNEWS and Interplay Production
- Manage which MediaCentral UX licenses a user has access to
MediaCentral User Management is one of the MediaCentral Services that runs on the MediaCentral Services server.
•A user is an entity that represents a real-world user. Users are authenticated through the MediaCentral User Management Service.
Delete
•A group is an entity that represents a collection of users. For example, the group named Administrators is a collection of users that have administrator privileges. The Administrators group, the Administrator user, and the Auto Import group are created by default. For more information, see
“Creating a New Group or Editing Group Details” on page 77.
A user is a member of a group. The group to which the user belongs is referred to as the parent group. A new user is created as a member of the top-level group (Users) and can be assigned to one or more groups. For more information, see
User Details” on page 75
.
“Creating a New User or Editing
A group can be a member of another group. The group to which the group belongs is referred to as the parent group.
60
Understanding Users and Groups
A
B
C
X
qq
ww
A
B
C
X
qq
A user can be a member of more than one group, and a group can be a member of more than one group. Users and groups are considered members only of their immediate parent groups.
The following illustration shows the relationships that are allowed.
1 User X is a member of Groups A and B. 2 Group C is a member of Groups A and B.
A user or a group can be a member of more than one group in a single subtree. In the following illustration, user X can be a member of both group B and group C.
1 User X can be a member of both Group C and Group B.
Relationships are hierarchical. Cyclical relationships, as in the following illustration, are not permitted.
61

Available Layouts: Administrators and Users

qq
ww
ee
A
B
C
1 Group C is a member of Group A. 2 Group A is a member of Group B. 3 Group B cannot be a member of Group C.
If a user or a group is removed from all parent groups, the user or group is moved to the Unassigned group. For more information, see “Understanding the Unassigned Group” on
page 82
Users and groups have properties. Properties are defined fields that describe a user or a group. Only the values of properties can be changed. Examples of properties are group name, user first name and last name, and description.
.
Available Layouts: Administrators and Users
Which layouts are available in MediaCentral UX depends on the group to which a user belongs.
Administrators group: A user in the Administrators group can access the System Settings and Users layouts and perform administrative actions that are available in the layouts. An Administrator can also access any other layout.
Other groups: A user in a group other than the Administrators group can access only the Cut, Log, Media | Distribute, Research, Rundown, and Story layouts.
The following tables lists the available layouts:
Layout Available To...
Cut All users based on configuration
Log All users based on configuration
Research All users based on configuration
Rundown All users based on configuration
Story All users based on configuration
Media | Distribute (if installed)
All users based on configuration
62
Layout Available To...
System Settings Administrators only
Users Administrators only
An administrator assigns layouts and license types to a role. For more information, see
“Creating, Deleting, and Assigning Roles” on page 84
.

Working with MediaCentral Zones

A MediaCentral zone consists of the following configuration:
One MediaCentral server or MediaCentral cluster server
One Interplay | Production engine, one iNEWS database, or both
One or more ISIS storage systems
By default, a MediaCentral system is configured as a single zone. Large organizations can combine two or more single-zone systems into a multi-zone environment. For more information, see the following topics:
Working with MediaCentral Zones
“Managing Multi-Zone Environments” on page 63
“Configuring MediaCentral Zones” on page 65
MediaCentral v2.1 does not support multi-zone environments for Interplay MAM.
n

Configuring a Multi-Zone Environment

An administrator configures a multi-zone environment through the Zone settings in the System Settings layout. For information about configuring a multi-zone environment, see the Avid Media | Index Configuration Guide.

Managing Multi-Zone Environments

Some large organizations have multiple MediaCentral zones, which can be located in a single facility or geographically distributed over several facilities. Prior to MediaCentral v2.0, each zone functioned as an individual workgroup. Users had credentials for only a single zone, and there was no way for a user signed into one zone to search for assets in other zones.
63
Working with MediaCentral Zones
Starting with MediaCentral v2.0, administrators can configure two or more MediaCentral zones to work together in the following workflows:
Multi-zone user management
Multi-zone central index search
Multi-zone media asset delivery
Multiple zones are connected (or federated) through the MediaCentral Platform bus. For information about configuring multiple zones, see the Avid Media | Index Configuration Guide.
Multi-Zone User Management
Multi-zone user management is a workflow in which a single user authentication database is used to manage users across multiple MediaCentral zones. An administrator signed into one zone can manage users and roles for all other zones. Although users are centrally managed in a multi-zone environment, a user’s roles can vary from zone to zone. Multi-zone user management makes the administrator role easier when faced with a complex multi-zone environment.
A user needs to have at least one role in a zone before the user can sign into that zone. For more information, see
“Creating and Deleting Roles” on page 88.
The User Management Service is configured with a master zone and slave zones. If the master zone becomes unavailable for some reason, users can continue to sign in and work, using a slave zone. Note, however, that in this situation, databases in the slave zones are automatically switched to read-only mode. Thus, there is no way to work with the database (for example, adding new users or changing roles until the master zone is available again. When this happens, databases are automatically switched to Read/Write mode.
Multi-Zone Search
A user signed into one zone can search for assets across a multi-zone environment. Although users work and create sequences in their local zone, they can find media assets in remote zones, then obtain them and include them in their local work. There are two types of search available:
Federated search: Searches each zone in a multi-zone environment.
Indexed search: Searches a central index, which receives its data from the original data sources and then pushes the data to the service that does the indexing.
Multi-zone search gives storytellers broader and faster access to media assets across the network, to tell better stories faster. For more information, see “Searching for Assets” in the Avid MediaCentral | UX User’s Guide.
64
Multi-Zone Media Asset Delivery
Multi-zone media asset delivery lets you trigger the transfer of a remote media asset to a local zone. You can search Interplay Production databases across all zones, view remote assets, and deliver them to your local Interplay Production workgroup.
Multi-zone media asset delivery makes all media assets on the network no more than one step away from being assets that can be used in local projects. For more information, see “Delivering Assets and Media” in the Avid MediaCentral | UX User’s Guide.
Each of these workflows can be configured and used independently (multi-zone central index
n
search and multi-zone media asset delivery are licensed and enabled separately).

Configuring MediaCentral Zones

An administrator configures a multi-zone environment through the Zone settings in the System Settings layout. For information about configuring a multi-zone environment, see the Avid MediaCentral Platform Services Installation and Configuration Guide.
After configuration on the server, the MediaCentral zones are listed in the MediaCentral Zones pane. These are the zones that make up your multi-zone environment. Information about each zone is displayed in the Details tab.
Working with MediaCentral Zones
If there are no zones configured on the server, the MediaCentral Zones tab lists the default zone. No further configuration is needed.
If multiple zones are configured, they are listed in the MediaCentral Zones pane.
65
The following fields are displayed in the Details tab:
ID: The UUID of the selected zone, which is assigned when the zone is created on the MediaCentral server. This field is not editable. This ID can be useful for troubleshooting, for example, to understood data in logs.
Name: The name of the zone as it was configured in the Zones settings in the System Settings layout. This name is stored in the UMS and is an easy way to identify the zone. An administrator can edit the name of zone, and the changed name will be used in the Users layout and will also be changed in the Zones settings.
To edit the name of a MediaCentral zone
t Click the Name field, edit the name, and click Apply.

Managing Users and Groups

MediaCentral UX requires its own database of users. You can import users from a Windows domain, individually create users, or both.
The MediaCentral UX user database is independent of the Interplay Production user database, Interplay MAM user database, and the Avid iNEWS user database. However, the MediaCentral UX database, through the MediaCentral User Management Service, serves as a password manager that authenticates the MediaCentral UX user against the Interplay Production, Interplay MAM, and iNEWS user databases.
Managing Users and Groups
When a user first signs in to MediaCentral UX, the user needs to accept or change the displayed credentials to access the iNEWS database or the Interplay Production database or both. Interplay MAM users must sign in with MediaCentral UX credentials that match credentials set in the Interplay MAM system. For more information, see
page 11
The following topics describe tasks for managing users and groups:
“Creating a New User or Editing User Details” on page 75
“Creating a New Group or Editing Group Details” on page 77
“Adding a User to a Group” on page 79
“Removing a User from a Group” on page 79
“Removing Groups from Groups” on page 81
“Understanding the Unassigned Group” on page 82
.
“Importing Groups of Users” on page 67
66
“Signing In to MediaCentral | UX” on
“Deleting Users and Groups” on page 82
“Changing Passwords” on page 83

Importing Users

If you enable Windows Domain authentication, you can import groups and individual users from a Windows domain. This authentication uses the LDAP protocol. Users imported from a Windows domain can use their Windows domain user names and passwords to sign in to MediaCentral UX. After initially importing users, additional users can be automatically imported. For more information, see the following topics.
“Importing Groups of Users” on page 67
“Importing an Individual User” on page 74
MediaCentral UX users must also have accounts on the system they will be using in their
n
workflows: Interplay Production, Interplay MAM, or iNEWS. For information on how these accounts work with MediaCentral UX, see “Signing In to MediaCentral | UX” on page 11.
Importing Groups of Users
Importing a group of users is a two part process:
Managing Users and Groups
c
Supply information about the authentication provider.
Perform the actual import.
During the import process authentication requests cannot be handled. Currently signed-in users might not be able to complete their work. Other users will not be able to sign in. You should inform active users that the system will not be available.
New users added to the Windows domain are not continually imported to the MediaCentral UX user database. To add new users, you need to perform another import or have individual users sign in, as described in
Users deleted from the Windows domain are not automatically deleted from the MediaCentral UX user database and they are not deleted if you perform another import. A user deleted from the Windows domain cannot be authenticated and thus will not be able to sign in. If you want to delete that user’s account, you need to delete the account manually.
An organization might have an Active Directory that includes several domains. MediaCentral UX allows user authentication from multiple sub-domains. In this case, set the common root of the domain instead of the Base DN of a specific domain. MediaCentral User Management will then authenticate against the overall directory, allowing users from all imported domains to log in.
“Importing an Individual User” on page 74.
67
Managing Users and Groups
To supply information about an authentication provider:
1. Sign in to MediaCentral UX as an administrator and select Users from the Layout selector.
2. In the user tree, double-click the top-level group Users.
3. In the Authentication Providers section of the Details pane, select the option Windows Domain Authentication.
68
Managing Users and Groups
4. In the Server section, supply the following information:
- (Optional) If the Active Directory uses Secure Sockets Layer (SSL) technology, select
Use SSL Connection.
- Type the hostname of the Windows domain server on which the user database is stored.
- Type the port for the domain server. The default port is 389. For an SSL connection, the
default port is 636.
- Type the Base DN (root location) where the import of the user tree should be started.
When you begin the import procedure, the user tree is displayed and you can select the subgroups you want to import.
How you type the Base DN depends on how your Active Directory is configured and which domains you want to authenticate from. If you want to authenticate from multiple sub-domains, set the common root of the sub-domains instead of the Base DN of a specific domain.
For example, the common root of an Active Directory with multiple domains could be named “company.com” and could be divided into the domain components DC=company and DC=com. Type these entries separated by a comma, but no space:
DC=company,DC=com
For a specific sub-domain, you might type:
DC=company,DC=division,DC=com
5. In the Sign-In Credentials section, do one of the following:
- Select Use Anonymous Access. If you select this option, the User Name and Password
fields in this section are inactive and not required.
- Type the user name and password of a domain user who has access to the domain server.
How you type the user name depends on how your Active Directory is configured. For example, you can specify the user “Administrator” in the group “Users” by typing the following, separated by a comma, but no space:
CN=administrator,CN=Users
Your Active Directory can also be configured to use only a user name, for example:
administrator
The password is represented by asterisks.
To test if your user name and password are correct, click Test Connection.
6. (Optional) If your facility uses SAM Account Names instead of the newer Active Directory Principal Names, select “Import users by SAM Account Name instead of Principal Name.” This configuration is specifically for those users who are used to logging into Interplay Production with the older Windows Domain style login.
69
Managing Users and Groups
If you later decide to change to Principal Name, you need to reimport users and the current settings will be lost.
7. If you do not want to display the name of the Windows domain controller or controllers, select “Hide domain controllers in the user tree.”
If you select this option, domain controllers are hidden and merged. If you then try to delete a folder of users, the correct domain controller is unknown and an error message is displayed. To delete the folder, you need to deselect the option.
8. If you want to automatically import new users from this Windows domain, select “Use Auto Import.” For more information, see “Importing an Individual User” on page 74
.
9. Click Apply.
Clicking Apply saves the settings but does not import users.
To import users from a Windows domain:
1. Click the User Tree Pane Menu button and select Import Users.
The Import Users dialog box opens.
70
Managing Users and Groups
If you did not specify an authentication provider, the following message appears: “You have no authentication providers configured.” Click the Go to Authentication Providers button to display the Details pane and then complete the previous procedure.
2. Select whether you want to overwrite existing users that have the same user names.
In most cases, especially when reimporting, select “Do not overwrite existing users that have the same names.” This option preserves any existing user settings.
3. Click the Load User Tree button.
A bar displays the progress while the user tree is loading. When the loading is complete, the root of the user tree appears.
71
Managing Users and Groups
4. If necessary, click the triangle to expand a group and display subgroups. You can also use the maximize icon to expand the pane. Select the groups that you want to import, and click Import.
A message box displays the progress of the import. If the import process fails for any reason, such as a failure to connect to the Active Directory server, a message box describes the problem and gives you an option to retry.
If the import process is successful, the User Import Results dialog box opens.
72
Managing Users and Groups
There are four tabs:
- All: Lists all users and groups and their status
- Failed: Lists the users and groups that could not be imported and their status
- Skipped: If you selected “Do not overwrite existing users that have the same names,”
lists the users and groups that were not imported because they already exist in the user database.
- Successful: Lists the users and groups that were successfully imported.
The following table explains some messages that can prevent a successful import. Check with the Active Directory administrator to resolve these problems.
Message Cause
Mandatory attribute ‘userPrincipalName’ not set.
Insufficient access rights The user account provided for the import does not have
The required userPrincipalName attribute of the user is empty. This can be caused by migrating pre-Windows 2000 users or by creating users without providing this attribute.
sufficient privileges to read the user information.
73
5. Click OK.
The selected group is imported in the user tree, in the folder named Users/Import/Microsoft/full_qualified_name. You can then assign imported users to other groups.
Importing an Individual User
After an administrator successfully imports a group of users through Windows domain authentication, an additional user can be automatically imported through the MediaCentral UX sign-in screen without the need to import the entire group again. After the process is complete, the user is added to the “Auto-Import users” group. The following illustration shows this group with a user named TU11.
Managing Users and Groups
You can assign any role to this group. A user added to the group inherits any role and other permissions assigned to the group.
To import an individual user:
1. Make sure the Use Auto Import option is selected in the Users Details page. See “Importing
Groups of Users” on page 67
.
2. At the sign-in screen, a user whose user name is not in the MediaCentral user database signs in to MediaCentral, using the appropriate Windows domain user name and password. Another sign-in screen is displayed, as shown in the following illustration.
74
Managing Users and Groups
3. Click the Import and Sign-In button.
A message is displayed, the user is imported to the “Auto-Import users” folder, and the user is signed in with the role inherited from the “Auto-Import users” folder.
If the user name exists in Windows domain, but the user provides the wrong Windows password, the user is imported but the sign-in fails. The user can sign in again with the correct password. If the user provides a user name that does not exist in either the Windows domain or the MediaCentral user database, the user is not imported and the sign-in fails.

Creating a New User or Editing User Details

You can create individual users instead of importing a group of users. You can assign a user to one or more groups, including the Administrators group.
To create a new user:
1. Sign in to MediaCentral UX as an administrator and select Users from the Layout selector.
2. Do one of the following:
t In the user tree, select a group to which you want to add a new user, right-click, and
select Create User.
The new user will be added to the selected group.
t Click the Create User button.
t Click the Pane Menu button and select Create User.
3. In the Details pane, type the properties for the new user.
75
Managing Users and Groups
User Name, Password, and Confirm Password are required fields and are marked by small white stars. Other fields and settings are optional.
Note the following restrictions:
- Minimum length of user names: 1 character
- Minimum length of passwords: 6 characters
- Maximum length of user names and passwords: 255 characters
- Passwords are case-sensitive.
- Passwords cannot contain all or part of the user’s account name.
- Passwords cannot consist of spaces only.
- Passwords must contain characters from three of the following four categories:
- English uppercase characters (A through Z)
- English lowercase characters (a through z)
- Base 10 digits (0 through 9)
- Nonalphanumeric characters (e.g., !, $, #, %)
76
Managing Users and Groups
4. Select the options you want, such as “User must change password at next sign-in.”
5. (Optional) Add the new user to a group.
If you selected a group and then selected Create User, the group you selected is listed in the Groups section. To add the user to another group, drag the group icon from the user tree to the Groups section.
If you do not assign a user to a group, the user is added to the top-level group (Users).
6. (Optional) Assign one or more roles to a user.
By default, a user inherits the role of the assigned group. This default role is not displayed until you save the new user. If you are working in a multi-zone environment, assign the appropriate role for each zone.
For more information, see “Creating, Deleting, and Assigning Roles” on page 84
.
7. If you do not want to create the user, click Cancel.
This action clears the Details pane.
8. When you are satisfied with the information, click Save or press Ctrl+S.
The user is added to the groups that you specified.
If you navigate away from the Details pane without clicking Cancel or Save, a message box asks if you want to apply your changes. Click Yes to apply changes, click No to ignore the changes, or click Cancel to go back to the Details pane and make additional changes.
To edit user details:
1. In the user tree, double-click a user or select the user and press Enter.
You can use the filter field (Ctrl-F) to locate the user. Use the Up and Down Arrow keys to move from the filter field to the user tree and back again.
2. Change the properties, options, membership, or roles.
For additional information about changing passwords, see
page 83
.
“Changing Passwords” on
3. If you want to cancel your changes and return to the last set of saved information, click Revert.
4. When you are satisfied with the information, click Apply or press Ctrl+S.

Creating a New Group or Editing Group Details

To create a new group:
1. Sign in to MediaCentral UX as an administrator and select Users from the Layout selector.
2. Do one of the following:
77
Managing Users and Groups
t In the user tree, select the top-level group (Users) or another group to which you want to
add a new group, right-click, and select Create Group.
The new group will be added to the selected group.
t Click the Create Group button.
t Click the Pane Menu button and select Create Group.
3. In the Details pane, type the properties for the new group.
Group Name is a required field (marked by a white star). Other fields are optional.
4. Add members to the new group by dragging users from the user tree to the Members section.
Use Ctrl+click (Windows) or Command+click (Macintosh) to select multiple users, or Shift+click to select contiguous users.
To remove a user from the group, do one of the following:
- Click the x next to the user’s name
- Select one or more users, right-click, and select Remove from Group.
- Select one or more users, right-click, and press the Backspace key or the Delete key.
78
Managing Users and Groups
Removing a user through these actions does not delete the user from the database. You can delete
n
a user or group from the database only through the user tree. See “Deleting Users and Groups”
on page 82.
5. Assign one or more roles to the group.
By default, the group inherits the roles assigned to the parent group, unless the parent group is the top-level Users group. The top-level group cannot be assigned a role.
By default, members of the group inherit the roles assigned to the group. If you are working in a multi-zone environment, assign the appropriate role for each zone. For more information, see
6. (Optional) If you want to make the group a member of another group, drag the new parent group from the user tree to the Groups section. To remove the parent group, click the x next to the group’s name.
7. If you want to clear and close the Details pane before creating the group, click Cancel.
8. When you are satisfied with the information, click Save or press Ctrl+S.
To edit group details:
1. In the user tree, double-click a group.
2. Change the properties, membership, or roles.
“Creating, Deleting, and Assigning Roles” on page 84.
3. If you want to cancel your changes and return to the last set of saved information, click Revert.
4. When you are satisfied with the information, click Apply or press Ctrl+S.

Adding a User to a Group

To add an existing user to a group, do one of the following:
t In the user tree, double-click a user, drag the group to the Groups section of the Details pane,
and click Apply or press Ctrl+S.
t In the user tree, double-click a group, drag the user to the Members section of the Details
pane, and click Apply or press Ctrl+S.
Use Ctrl+click (Windows) or Command+click (Macintosh) to select multiple users, or Shift+click to select contiguous users.

Removing a User from a Group

If you remove a user from a group, and the user is not a member of any other groups, the user is moved to the Unassigned group. You can reassign a user from the Unassigned group to another group or to the top-level group (Users). For more information, see
Unassigned Group” on page 82
.
“Understanding the
79
Managing Users and Groups
Removing a user through these actions does not delete the user from the database. You can delete
n
a user or group from the database only through the user tree. See “Deleting Users and Groups”
on page 82.
To remove a user from a group by using a menu command:
1. In the user tree, click the turn-down arrow to open the group from which you want to remove the user.
2. Select the user you want to remove.
Use Ctrl+click (Windows) or Command+click (Macintosh) to select multiple users, or Shift+click to select contiguous users.
3. Do one of the following:
t Right-click and select Remove from Group.
t Click the Pane Menu button and select Remove from Group.
To remove a user from a group by using the user’s details:
1. In the user tree, click the turn-down arrow to open the group from which you want to remove the user.
2. Double-click the user you want to remove.
3. In the Groups section of the Details pane, select the group from which you want to remove the user.
4. Do one of the following:
t Click the x next to the group’s name.
t Right-click and select Remove from Group.
t Press the Backspace key or the Delete key.
5. Click Apply or press Ctrl+S.
To remove a user from a group by using the group’s details:
1. In the user tree, double-click the group from which you want to remove the user.
2. In the Members section of the Details pane, select the user you want to remove from the group.
3. Do one of the following:
t Click the x next to the group’s name.
t Right-click and select Remove from Group.
t Press the Backspace key or the Delete key.
4. Click Apply or press Ctrl+S.
80

Removing Groups from Groups

If you remove a group from a group, and the group is not a member of any other groups, the group is moved to the Unassigned group. You can reassign a group from the Unassigned group to another group or to the top-level group (Users). For more information, see
Unassigned Group” on page 82
Removing a group through these actions does not delete the group from the database. You can
n
delete a user or group from the database only through the user tree. See “Deleting Users and
Groups” on page 82.
To remove a group from a group by using a menu command:
1. In the user tree, click the turn-down arrow to open the group from which you want to remove the group.
2. Select the group you want to remove.
Use Ctrl+click (Windows) or Command+click (Macintosh) to select multiple groups, or Shift+click to select contiguous groups.
3. Do one of the following:
t Right-click and select Remove from Group.
.
Managing Users and Groups
“Understanding the
t Click the Pane Menu button and select Remove from Group.
To remove a group from a group by using the group’s details:
1. In the user tree, double-click the group you want to remove.
2. In the Groups section of the Details pane, select the group from which you want to remove the group.
3. Do one of the following:
t Click the x next to the group’s name.
t Right-click and select Remove from Group.
t Select the group and press the Backspace key or the Delete key.
4. Click Apply or press Ctrl+S.
To remove a group from a group by using the parent group’s details:
1. In the user tree, double-click the group from which you want to remove the group.
2. In the Members section of the Details pane, select the group you want to remove from the group.
81
3. Do one of the following:
t Click the x next to the group’s name.
t Right-click and select Remove from Group.
t Press the Backspace key or the Delete key.
4. Click Apply or press Ctrl+S.

Understanding the Unassigned Group

A group labeled Unassigned is included by default as a member of the top-level group (Users). The Unassigned group holds users and groups that have been removed from all other groups.
The Unassigned group is a system group and thus you cannot rename it, move it, delete it, or make it a member of another group. You cannot manually add or remove users or groups. You can reassign the users or groups in the same way that you assign users and groups to other groups. (For more information, see
“Creating a New Group or Editing Group Details” on page 77.) After you reassign the users
and or groups, they are removed from the Unassigned group.
If a group is moved to the Unassigned group, the group and its members are moved to the Unassigned group. Members of this group can be members of other groups. In other words, only the group is unassigned.
“Creating a New User or Editing User Details” on page 75
Managing Users and Groups

Deleting Users and Groups

When you delete a user or a group, the user or group is permanently deleted from all groups of which it is a member. If you delete a user that was imported, the user can be reimported during the next import sync operation.
If you delete a group, members of the group are not deleted. Members that belong to other groups remain as members of the other groups. Members that are not members of other groups are moved to the Unassigned group.
If you delete a group that contains one or more subgroups, the subgroups remain in the user tree. A subgroup might remain as a member of a different group or, if the subgroup is not part of a different group, it is moved to the Unassigned group.
If you imported users from a Windows domain, users deleted from the Windows domain are not automatically deleted from the MediaCentral UX user database and they are not deleted if you perform another import. You need to disable or delete the accounts manually.
82
Managing Users and Groups
To delete a user:
1. In the user tree, select a user. You can use the filter field (Ctrl-F) to locate the user. Use the Up and Down Arrow keys to move from the filter field to the user tree and back again.
Use Ctrl+click (Windows) or Command+click (Macintosh) to select multiple users, or Shift+click to select contiguous users.
2. Do one of the following:
t Click the Delete button.
t Right-click and select Delete.
t Click the Pane Menu button and select Delete.
t Press Ctrl+Delete.
If one user is selected in the user tree, and a different user is displayed in the Details pane, the
n
user selected in the user tree is deleted.
To delete a group:
1. In the user tree, select a group. You can use the filter field (Ctrl-F) to locate the group. Use the Up and Down Arrow keys to move from the filter field to the user tree and back again.
Use Ctrl+click (Windows) or Command+click (Macintosh) to select multiple groups, or Shift+click to select contiguous groups.
2. Do one of the following:
t Click the Delete button.
t Right-click and select Delete.
t Click the Pane Menu button and select Delete.
t Press Ctrl+Delete.
If one group is selected in the user tree, and a different group is displayed in the Details pane, the
n
group selected in the user tree is deleted.

Changing Passwords

Stronger password requirements were introduced in MediaCentral UX v2.1. These requirements do not affect passwords for MediaCentral users whose accounts were created in MediaCentral UX v2.0.x or earlier. The new requirements are enforced when user passwords are changed or created in MediaCentral UX v2.1.
These requirements do not apply to passwords for users imported from Active Directory. These users use their Active Directory credentials.
83

Creating, Deleting, and Assigning Roles

To change a user’s password:
1. In the user tree, double-click the user whose password you want to change or select the user and press Enter.
You can use the filter field (Ctrl-F) to locate the user. Use the Up and Down Arrow keys to move from the filter field to the user tree and back again.
2. In the Details pane, click Change Password.
3. In the Change Password dialog box, type the new password, and then type it again in the Confirm Password text box.
Note the following restrictions:
- Minimum length of user names: 1 character
- Minimum length of passwords: 6 characters
- Maximum length of user names and passwords: 255 characters
- Passwords are case-sensitive.
- Passwords cannot contain all or part of the user’s account name.
- Passwords cannot consist of spaces only.
- Passwords must contain characters from three of the following four categories:
- English uppercase characters (A through Z)
- English lowercase characters (a through z)
- Base 10 digits (0 through 9)
- Nonalphanumeric characters (e.g., !, $, #, %)
4. Click OK or press Enter.
Creating, Deleting, and Assigning Roles
The Users layout includes a pane labeled Roles.
In MediaCentral UX, a role is a set of features, privileges, and layouts that are assigned to a user by a MediaCentral UX administrator. An administrator can create MediaCentral UX roles based on roles within an organization.The following topics describe how to manage roles:
“Default Roles” on page 85
“MediaCentral | UX Client Licensing” on page 85
“Creating and Deleting Roles” on page 88
“Assigning Roles” on page 89
84

Default Roles

MediaCentral UX includes the following default roles.
Role Default Layouts
Administrator Cut, Media | Distribute (if installed), Log, Research, Rundown, Story,
Journalist Research, Rundown, Story
Media Logger Log
The Media | Distribute installation and configuration process creates additional roles. For more information, see the Media | Distribute Installation and Configuration Guide.
Creating, Deleting, and Assigning Roles
System Settings, Users
An administrator can change the layouts for a role. See
page 88
.

MediaCentral | UX Client Licensing

MediaCentral UX requires a user to be assigned one of the following licenses:
Base License: Can connect to only one system during a session: iNEWS, Interplay MAM, or Interplay Production.
Advance License: Can connect to any or all systems during a session: iNEWS, Interplay MAM, and Interplay Production.
Beginning with MediaCentral UX v2.1, there is no restriction on the features and functionality of the product as a result of the type of license. This situation applies to both the Web application and the mobile applications. Note, however, that if a user has access to only one system, layouts and panes specific to another system might be available but will not be functional.
Earlier versions of MediaCentral UX used a different way of assigning licenses. Beginning with
n
Interplay Central v1.5, you need to reassign licenses based on roles.
Running MediaCentral | UX and Interplay Production Concurrently
A client workstation can use a single license to run MediaCentral UX and Interplay Production client applications concurrently. For example, a user can run both MediaCentral UX and Interplay | Access while using a single MediaCentral UX license. For more information, see the Interplay | Engine and Interplay | Archive Engine Configuration Guide.
“Creating and Deleting Roles” on
85
Creating, Deleting, and Assigning Roles
To run applications concurrently with a single license, the client workstation must be connected
n
to the same LAN as the MediaCentral server. The client workstation must have a correct DNS entry and the MediaCentral server must be configured to resolve the client workstation’s host name.
Installation
Licenses are installed on an iNEWS server or an Interplay Production server, or both. No licenses are installed on the MediaCentral Services server. For Interplay Production, the license types are Key-J (base license) and Key-G (advance license).
See the MediaCentral Services Installation and Configuration Guide for information on installing licenses.
Assigning Licenses
After licenses are installed, a MediaCentral UX administrator assigns a license to a role. The two license types are displayed in the Details pane of the Users layout:
Advance License
Base License. The Base License includes a drop-down menu that lets you select either Interplay Production, Interplay MAM, or iNEWS.
An administrator can assign multiple roles to a user. Multiple-role assignments can help license management by letting the user consume either a Base or an Advance license, depending on the work that needs to be done and the licenses that are available.
The following illustration shows an example of a multiple-role assignment. By default, the Journalist role is associated with an Advance license, and the Media Logger role is associated with a Base license. An administrator can assign both Journalist and Media Logger roles to a user, as shown in the following illustration.
86
Creating, Deleting, and Assigning Roles
Which license the user consumes is determined by the role the user selects after signing in. This selection depends on the MediaCentral UX application you are using:
For the MediaCentral UX Web application, the user selects a different role by choosing a layout assigned to that role in the Layout selector.
For the MediaCentral UX iOS applications, the user selects a different role by choosing the role in the role switcher.
The following illustration shows the Layout selector for the MediaCentral UX Web application. The Layout selector shows two roles, Journalist and Media Logger, with different layouts assigned to each role.
If the user selects the Story layout, the user is working as a Journalist and is consuming an Advance license. If the user switches to the Log layout, the user is then working as a Media Logger and is consuming a Base license.
You can open only those panes that are available through the license you are currently using. If a pane that is not available is open, such as through the Reset Layout command, a message is displayed in the center of the pane that reads “The pane_name is not available for your license type.”
87
An administrator can assign the same layout to roles that use different licenses. Changing from one license type to another can also cause some panes to be unavailable.
This behavior also applies if you receive an Interplay Production link through the MediaCentral UX Messenger and you do not have a license that allows access to the Interplay Production database. A message is displayed that reads “You do not have permission to view this asset.”

Creating and Deleting Roles

The three default roles are Administrator, Media Logger, and Journalist. You can create additional roles and name them as you like. You cannot rename or delete the Administrator role.
In Interplay Central v1.2.x and earlier, the names of roles were case-sensitive. As a result, the
n
roles Journalist and JOURNALIST were treated as separate roles. In Interplay Central v1.3 and later, names of roles are no longer case-sensitive and cannot be duplicated. If you upgraded from a version earlier than Interplay Central v1.3, any duplicate roles were renamed, for example, JOURNALIST DUPLICATE_d8abb. You can rename this role to something more meaningful.
To create a role:
1. Select Users from the Layout selector.
Creating, Deleting, and Assigning Roles
2. Click the Roles pane.
3. Do one of the following:
t Click the Pane Menu button and select Create Role.
t Click the New Role button.
4. In the Details pane, type a name for the role.
This field is required.
5. (Optional) Type a description of the new role.
6. Select one of the following license types for the role:
-Advance
-Base
For more information on license types, see
page 85
7. Click the Layouts pane, select the layout or layouts you want to assign to the role, and drag them to the Layouts section.
The layout is added to the Layouts list.
.
88
“MediaCentral | UX Client Licensing” on
8. Click Save or press Ctrl+S.
The role is added to the list in the Roles pane.
To delete a role:
1. Select Users from the Layout selector.
2. Click the Roles pane.
3. Select the role you want to delete.
4. Do one of the following:
t Click the Pane Menu button and select Delete Role.
t Right-click and select Delete Role.
t Press the Backspace key or the Delete key.
A confirmation box asks if you want to delete the selected role.
5. Click Yes or press Enter.
The role is deleted.

Assigning Roles

Creating, Deleting, and Assigning Roles
You can assign roles in two ways:
In the Role Details pane
In the User or Group Details pane.
You can assign roles by dragging and dropping.
If you are working in a multi-zone environment, a user needs at least one role in a zone to sign in to the server for that zone. The same user can have different roles in different zones.
To assign a role in the Role Details pane:
1. Select Users from the Layout selector.
2. In the Roles pane, do one of the following:
t Double-click the role that you want to assign to a user or group.
t Use the arrow keys to select the role, then press Enter.
Information about the role is displayed in the Details pane.
3. Click the User Tree pane.
89
Creating, Deleting, and Assigning Roles
4. Select the user or group to which you which you want to assign the role and drag it to the Users and Groups section of the Details pane.
The following illustration shows the Journalists group assigned the role Journalist.
The following illustration shows the Journalists group assigned the role Journalist in two zones: news-ipc1 and news-ipc4.
5. Click Apply or press Ctrl+S to save your changes, or click Revert to cancel your changes.
90
Creating, Deleting, and Assigning Roles
To assign a role in the User or Group Details pane:
1. Select Users from the Layout selector.
2. In the user tree, double-click a user or select the user and press Enter.
You can use the filter field (Ctrl-F) to locate the user. Use the Up and Down Arrow keys to move from the filter field to the user tree and back again.
3. Click the Roles tab.
4. Select the role you want to assign to the user or group and drag it to the Role section of the Details pane.
The following illustration shows the Journalists group assigned the role Journalist.
The following illustration shows the Journalists group assigned the role Journalist in both zones of a multi-zone configuration.
5. Click Apply or press Ctrl+S to save your changes or click Revert to cancel your changes.
The From Group column shows if the role is assigned directly (“Assigned to group directly”) or inherited from a parent group. If a role is inherited, the parent group is listed in the From Group column.
To remove a role, select the role and do one of the following:
t Click the x to the right of the role.
t Right-click and select Revoke Role.
91

Displaying Information in the Details Pane

The Revoke Role option works with multiple selections. This option skips roles that cannot be deleted, for example the default Administrator role for the Administrators group or any other role inherited from a group.
The only way to remove roles inherited from a group is to remove the user or group from that
n
group.
t Press the Backspace key or the Delete key.
Displaying Information in the Details Pane
You can double-click users, groups, or roles in the Details pane to select the item in the User Tree pane, and display information about the item in the Details pane. For example, in the following illustration, if you double-click Journalist 2, information about the user Journalist 2 is displayed in the Details pane.
92

Viewing and Ending Active Sessions

Viewing and Ending Active Sessions
A MediaCentral UX administrator can view a list of users who are currently signed in to the MediaCentral UX Web application, along with information such as their IP address, when they logged in, and when they were last active. If a user has more than one session open in a browser, all sessions are shown. The following illustration shows an example, sorted by user name in the Session ID column. The user named osprey-user has more than one session open.
The administrator has the option to end one or more sessions. If more than one session is open for a user, the administrator can choose to end individual sessions or all sessions.
A user can have multiple roles assigned, of which only one is active at any time. A user can select
n
a different role by choosing a layout assigned to that role in the Layout selector. When the user switches the role, the old session stays active until it automatically times out after five minutes. This might cause multiple sessions for that user to appear in the Active Sessions view.
93
Viewing and Ending Active Sessions
c
Ending a user session can cause data loss if the user has not saved all changes. For example, the auto-save feature does not work for stories and sequences.
To view active sessions:
1. Open the Users layout.
2. Click the Active Sessions pane. If the pane is not open, select Panes > Active Sessions.
3. Click the Refresh button to display the most recent information.
You can use the filter field (Ctrl-F) to filter sessions by user login or name, logged in date, or last active date. You can sort each column by clicking on the column heading.
To view details about a user, do one of the following:
t Right-click a session and select Show User Details.
t Select a session, click the Pane Menu button, and select Show User Details.
To end one or more sessions:
1. Select one or more sessions.
Click the user name to select all sessions. Use Ctrl+click (Windows) or Command+click (Macintosh) to select multiple sessions, or Shift+click to select contiguous sessions.
2. Do one of the following:
t Click the End Session(s) button.
t Right-click and select End Session(s).
t Click the Pane Menu button and select End Session(s).
t Press Ctrl+Delete.
A confirmation box is displayed.
3. Click the End session(s) button or press Enter.
The session is ended on the server. The operation skips sessions that cannot be ended (such as your own session).
After a short delay (up to a minute), a message box is displayed on the selected clients that reads “Your session has been terminated. You will be redirected to the Sign-in screen.”
4. The user must click the Sign Out button.
94

3 Monitoring and Troubleshooting

The following topics include information that you can use for monitoring and troubleshooting:

Log Files

Troubleshooting Send to Playback Problems
Troubleshooting Mixdown Problems
Log Files
The following sections list some useful log files. Not all log files are listed.
For information about log files related to a server cluster, see the Avid MediaCentral Server Clustering Guide.
MediaCentral Middleware Service
Log files for the MediaCentral Middleware Service are located in the following folder on the MediaCentral Services server:
/var/log/avid/avid-interplay-central
There are several sets of log files, which are described in the following table.
Log File Description
interplay_central_n.log Contains the main log messages. The folder contains a
maximum of ten files, numbered from 0 (most recent) to
10.
Log File Description
client/client-yyyy_mm_dd.n.log Contains log messages pertaining to the client
application. The folder contains a maximum of ten files, numbered from 0 (most recent) to 10.
Prior to Interplay Central v1.5, this information was in the interplay_central_n.log file
If necessary, you can disable client logging by adding a property to the application.properties file:
/opt/avid/etc/avid/avid-interplay-central/co nfig/application.properties
Add the following line:
system.clientLoggingEnabled=false
If the application.properties file does not exist, you need to create it. For more information, see the MediaCentral
Services Installation and Configuration Guide.
jetty-yyyy_mm_dd.request.log Contains logs of all HTTP requests to Jetty.
Log Files
performance/performance.yyyy-MM-dd.csv.log performance/performance.yyyy-MM-dd.csv.tree.log
Contains HTTP performance statistics when enabled. Logging is disabled by default; contact Avid for instructions for enabling. The folder contains log files for the last 7 days.
MediaCentral User Management Service
Log files for the MediaCentral User Management Service are located in the following folder on the MediaCentral Services server:
/var/log/avid/avid-ums
These logs are described in the following table.
Log File Description
importer.log Contains information about import issues
service.log General log output and issues for the User Management Service
session.log User session related information.
96
Log Files
MediaCentral Distribution Service
Log files for the MediaCentral Distribution Service are located in the following folder on the server where you installed the MediaCentral Distribution Service:
C:\ProgramData\Avid\Interplay Central Distribution Service
These logs are described in the following table:
Log File Description
STPService_nn.log Contains log messages from the MediaCentral Distribution Service
STPTimerTask_nn.log Contains log messages from the MediaCentral Distribution Service’s automatic clean-up of
job status.
MediaCentral Playback Service
Log files for the MediaCentral Playback Service are located in the following folder on the MediaCentral Services server:
/var/log/avid
The most useful logs are described in the following table:
Log File Description
edit.log Contains information about the streaming service.
isis.log Contains information about access to ISIS shared storage.
jips.log Contains information about the Interplay gateway.
spooler.log Contains information about the dynamic resolver service.
Also, log files for the Avid AAF service are created in the following subfolder:
/var/log/avid/avid-aaf-gen
Log files are created in the following subfolder for each instance of the service:
Log File Description
/log_n/avid_aaf_gen_n.log Contains information about the Avid AAF service, created in a subfolder.
97
MediaCentral Common Services
Log files for common services used in MediaCentral (messaging and e-mail forwarding) are located in the following folder on the MediaCentral Services server:
/var/log/avid/acs
These logs are described in the following table:
Log File Description
avid.acs-messenger.log Contains log messages from the MediaCentral messaging service.
avid.acs-mail.log Contains log messages from the e-mail forwarding service.
MCPS Manager Service
Log files for the MCPS Manager Service are located in the following folder on the MediaCentral Services server:
/var/log/avid/avid-icps-manager
These logs are described in the following table:
Log Files
Log File Description
avid-icps-manager.log Contains log messages from the MCPS Manager service.
avid-icps-manager-err.log Contains service startup errors.
MediaCentral | UX iPad and iPhone Applications
You can create a log file for the MediaCentral UX iPad or iPhone application and send it to Avid support by opening the Settings for MediaCentral UX and turning on the Logging setting.
If set to On, MediaCentral UX keeps logs on session activities, which you can use to troubleshoot issues. Use the Logging Level setting to determine how much information is logged.
If you tap the Actions button, a Send Log option appears that lets you e-mail the logs directly to Avid.
If set to Off (default), logging and the Send Log option are disabled.
98

Troubleshooting Send to Playback Problems

If the log file is more than 15 MB, you cannot send it directly. Use the iTunes File Sharing feature:
1. Connect your device to a Macintosh computer.
2. Open iTunes and navigate to Device > Apps.
3. Open iTunes and navigate to Device > Apps.
4. In the Avid Central Documents list, select the Logs folder.
5. Click “Save to” or drag the folder to a location on your computer.
6. Zip the folder and send it to Avid as an e-mail attachment.
Troubleshooting Send to Playback Problems
The following information will help you solve Send to Playback problems. See the following sections:
“Problems and Error Messages” on page 99
“MediaCentral Send to Playback Configuration Check List” on page 103
“Information to Provide to Support” on page 103
First check the table of problems and error messages for a possible solution. Then check the configuration check list. Finally, if necessary, gather the information needed for Avid support.
Problems and Error Messages
Problem or Error Message Probable Cause Solution
The STP progress seems to hang and there is no error message
“Remote STP process failed” messages
Message: Remote STP process failed: CM_INCOMPAT_TRACK_TYPES (in "wait render" phase) for sequence with D-track and dissolve.
No specific cause. Check the status of the related
Production Services job. Connect to your Production Services Engine, using the Production Services and Transfer Status tool, and check the jobs list.
Wrong version of Interplay | Transcode.
99
Install Interplay | Transcode v2.7.0.1 or later.
Troubleshooting Send to Playback Problems
Problem or Error Message Probable Cause Solution
Message: Remote STP process failed: Exception:ameBaseStream::GettotalKno wnMediaDurationForEWC() - unable to get EWC known media duration value. (in “wait render” phase)
Message: Remote STP process failed: Exception: FatalProc() Assertion failed:iNumOfInputs = = iNumExpectedInputs, fileName=...(in “wait audiomixdown” phase).
Message: Remote STP process failed: Exporter failed with error code:4 (in “wait long GOP export” phase)
Message: Remote STP process failed: java.lang. RuntimeException: Relink process time out after 60000 ms (in “preprocess” phase)
Message: Remote STP process failed: java.lang.RuntimeException: Relink process return error: DynamicRelinker::Relink failed error code:80000008 (in "preprocess" phase).
Send to playback failed because the
Wait until the capture is complete. clip is in the process of being captured (EWC=edit while capture).
Audio transcode failed because audio track assignment is wrong in the Interplay Administrator. There could be some other problem with Interplay Transcode.
Clip is in the process of being
Check the Interplay Administrator.
Open the Application Database
Settings view, click the Editing
Settings tab, and make sure the audio
patching is correct.
Wait until the capture is complete. captured
No specific cause. On the server running the
MediaCentral Distribution Service
check if the Windows process
“STPDR” is running. If not, check if
it is possible to start it by
double-clicking the exe file.
Sequence contains a title. (Error from CDS v2.7.0.1).
MediaCentral UX does not support
STP of sequences containing titles.
(Avid MediaCentral ReadMe,
UDevC00176883, ICTD-316)
Message: Remote STP process failed: net.nxn.JXDK.MonikerNotFoundExcepti on: ID/Moniker:nnnn
The sequence you want to send to playback cannot be found in the Interplay Production database.
100
1. Check if the sequence exists in the Interplay Production database. You can run a search for the sequence or browse to the location of the sequence. When you save a story, the related sequence is saved in the Interplay Production database location for script sequences, for example, projects/iNEWSsequences. This location is defined in the iNEWS System Settings.
2. Check the STP profile settings (especially the frame rate).
Loading...