Avid Technology iNEWS, Руководство по установке и эксплуатации

Страница: 84 / 152

Chapter 5
84
The <names> Group
<names>
<mos>MOS_ID_GOES_HERE</mos>
<amcp>iNEWS_DEVICE_GOES_HERE</amcp>
<network>NETWORK_NAME_GOES_HERE</network>
</names>
The MOS_ID_GOES_HERE should be changed to the MOS ID reported
by the MOS device. This ID identifies the MOS device to the MOS
Gateway and is used in MOS items placed in an iNEWS rundown to
indicate which MOS device receives the items.
n
Refer to the manufacturer’s documentation provided with the device for
more configuration details, such as the MOS ID.
The
iNEWS_DEVICE_GOES_HERE
should be changed to the iNEWS
device name for the MOS device. It is the same name that appears in the
SYSTEM.MOS-MAP
story located in the iNEWS database. See “Edit the
SYSTEM.MOS-MAP Story” on page 51 and “Adding MOS Devices to the
SYSTEM.MOS-MAP Story” on page95 for more information.
The
NETWORK_NAME_GOES_HERE
should be changed to the network
(host) name of the MOS device. Contact your network administrator for
this information.
The <roSlugMaps> Group
The <iNewsRunning
OrderName> tags
should be on the same
line in the actual file,
not wrapped as appears
here.
<roSlugMaps>
<roSlugMap>
<iNewsRunningOrderName>INEWS_RO_NAME</iNewsRunni
ngOrderName>
<MOSroSlug>MOS_RO_NAME</MOSroSlug>
</roSlugMap>
</roSlugMaps>
The group allows the name of a running order sent to a particular MOS
device to be different than the running order’s name in the iNEWS Server.
This is useful in cases where the MOS device provides a small space for
the running order name, such as the text on a button. If the entire group is
missing or a particular name for a rundown is missing, MOS Gateway will