3.0
Table Of Contents
- Avid iNEWS Command Installation and Configuration Guide
- Contents
- Using This Guide
- Installing and Configuring the Command Server
- System Architecture
- Checklist: Before you Begin
- Checklist: Command Server Installation
- Copying Install CD to Local Directory
- Installing Avid Service Framework
- Installing the License Service
- Installing Avid iNEWS Command on the Server
- Configuring the iNEWS Command Server
- Configuring a Second Command System
- Installing and Configuring the AirSpeed Video Servers
- Checklist: Installing the AirSpeed Video Server
- Installing Avid Service Framework
- Installing AirSpeed Multi Stream Device Services
- Checklist: Configuring the AirSpeed Video Server
- Configuring Properties for Interplay Workgroup
- Configuring the AirSpeed Multi Stream Device Service
- Configuring Properties for Command Workgroup
- Working with Play While Record
- AirSpeed Multi Stream Los-Res Proxy Viewer
- Installing and Configuring the Deko
- System Architecture
- Checklist: Installing the Deko
- Installing Avid Service Framework
- Installing Avid Deko Device Service
- Installing the DekoMOS Gateway
- Installing the DekoMOS Macro Server
- Checklist: Configuring the Deko
- Configuring the DekoMOS Gateway
- Configuring the DekoMOS Macro Server
- Configuring Avid Workgroup Properties
- Configuring the Deko Device Service
- Configuring the Avid Deko Renderer Service
- Creating Graphic Styles in Command
- Installing and Configuring the Graphic Device Service
- Installing Avid Service Framework
- Installing Avid Graphic Device Service
- Installing Third-Party Plug-ins for the Graphic Device Service
- CII Integration
- Installing and Configuring the Thunder
- Installing the Command Workstation
- Installing and Configuring the Tablet Application
- Configuring Playout Control
- Controling Playout via the Keyboard
- Disabling a Command Workstation’s Keyboard
- Checklist: Setting up an X-keys USB Keypad
- Installing an X-keys USB Keypad
- Mapping Indices to Channel Names
- Programming the X-keys
- Setting up the Playout Panel for Touch Screens
- Checklist: Setting up the GPI Panel
- Configuring the GPI Card
- Restarting the GPI Device Service
- Confirming Successful Setup of a GPI Panel
- Mapping Events to Actions for a GPI Panel
- Enabling the GPI Panel
- Configuring GPI Out
- Integrating with Avid iNEWS
- Integrating with ENPS
- Configuring the Perle IOLAN Server
- Confirming Functionality
- Index
Setting up the Plug-ins in iNEWS
241
n
You must enter a new line with MOS ID and channel group for each Deko channel group you
configured in Avid iNEWS Command.
The fifth line contains the following device information:
• The MOS ID of an Avid Thunder production server, such as
MOSIDTHDR_A
. This must
match the MOS ID configured in the
ThunderMOS.cfg
file. See “Creating the
ThunderMOS.cfg File” on page 174.
• The channel group for the Thunder, such as
Thunder
.
To ensure that the Avid Deko Select and Avid Thunder Select plug-ins use the correct device
designation, you must set the MOS ID and channel groups in the MOS-Map story.
The MOS-Map story can be edited like any other story in the newsroom computer system;
however, access to it is typically limited to system administrators who already have access to
SYSTEM.MOS-MAP
directory in iNEWS.
To edit the
SYSTEM.MOS-MAP
story:
1. Log in to an iNEWS Workstation as a system administrator.
2. Navigate to the
SYSTEM.MOS-MAP
queue.
3. Double-click on the first story in the queue.
4. Modify the story as needed.
5. Click Save.
Setting up the Plug-ins in iNEWS
Using plug-ins, such as Deko Select or Thunder Select, with Avid iNEWS and iNEWS
Command is optional. The plug-ins are installed on iNEWS Workstations and are accessed
through the iNEWS client software. The appearance of the plug-in(s) in Avid iNEWS
depends on whether one or more were installed. For instance, when both Deko Select and
Thunder Select are installed, the title of the workspace—shown on the title bar—is Avid
Graphics Select, and the plug-in workspace will appear in the iNEWS window with each
plug-in on its own tab, as shown: