
You can automate the process of specifying an item channel with toolbar buttons or keyboard
macros. Here is an example of a toolbar button macro that changes the item channel to A:
{shift {alt c}}{home}{shift {end}}{backspace}A{enter}{ctrl s}
After you change the channel, if the show is loaded in the monitor server, the changes will be
sent to the MOS device.
Vendor-Specific Configurations
Configuring Separate Omnibus Columbus Engines
If you are configuring MOS Gateway to control an OmniBus system with multiple Columbus
engines, iNEWS allows the user to choose which Columbus system receives the rundown at load
time. You must add the names of Columbus engines as channel names in the SYSTEM.MOS-MAP
story. Thus, if Columbus engines are CBS1 and CBS2, the DeviceTable in the SYSTEM.MOS-MAP
story will contain a line that looks something like this:
MOSGATE omnimos CBS1 CBS2
Then, when the user loads a rundown to the OmniBus MOS Gateway, the following dialog box
will appear before the Monitor Queue dialog box closes:
The channels CBS1 and CBS2 are also defined in the mosconfig.xml file on the MOS Gateway
server. CBS1 will be mapped to the name of the first Columbus engine, and CBS2 will be mapped
to the second Columbus engine. That Columbus engine names are usually defined by the
Columbus system administrator, during installation
The Channel drop-down list contains CBS1 and CBS2. The user must choose a channel; the
channel cannot be left blank.
Configuring Separate Sony MAV Server Regions
The Sony MAV Server can contain multiple regions. If you want to control multiple regions, then
the site administrator must configure the iNEWS Server and MOS Gateway to treat each region
as a separate MOS device. This requires some additional names to be put in various places.
There are four main steps:
• Find the MOS ID for each region
• Create a device name for each region
• Create a host alias for each region
Kommentare zu diesen Handbüchern