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
9 Integrating with Avid iNEWS
250
c. Add the monitor server’s device number to the servers line in the host definition for
the iNEWS Server that will run the monitor server program. For instance:
servers 261 263 265 267
The device number 267 is added to the servers line in this example.
n
Divide your server programs evenly among your iNEWS Servers to distribute the load they
put on your system. For instance, put odd numbered programs on server A and even
numbered ones on server B. Additionally, ensure that you also add the configuration line for
the monitor server to alternate host definitions for your iNEWS Servers. This ensures it can
run on the surviving computer should one of your iNEWS Servers stop functioning.
Do not confuse the configuration line, which starts with server, and the servers line
mentioned in 3c on page 249, which lists device numbers.
d. Add a configuration line for the monitor server in the host definition belonging to
the iNEWS Server that will run the server program. This line begins with the word
server and contains the mailbox number assigned to the monitor server.
The format for server programs’ configuration lines are:
server <device#> <type> <mailbox> <device name>
Comments appearing after the semicolons (;) are optional.
The following are sample configuration lines for monitor server programs:
Parameter Description
device #
The device number assigned to the server program. This 3-digit
number must also be listed in the servers line in a host definition.
type
The type of server program is monitor.
mailbox
The mailbox the server program uses. Valid standard mailbox
numbers are 1 through 4096. This number typically matches the
server program’s device number.
device name
Monitor servers do not use a device name; enter a hyphen (-).
server 264 monitor 264 - ;monitor server
server 265 monitor 265 - ;monitor server
server 266 monitor 266 - ;monitor server
server 267 monitor 267 - ;monitor server