MOS Gateway Configuration File
87
The iNEWS Server expects one of ten event status codes to be returned as
the status of a MOS item. Since the MOS Protocol specifies a string as the
status of a MOS item in the
roItemStat
MOS command, MOS
Gateway must map these strings to the iNEWS event status codes.
Furthermore, different MOS devices use different strings to mean the same
concept. The
<statusTranslations>
group specifies which string to
map to each event status code.
n
There can be multiple strings that map to the same event status code, in
which case, the relevant line of the
<statusTranslations>
group is
duplicated and each string recorded.
For instance:
<statusCued>READY</statusCued>
and
<statusCued>ON LINE</statusCued>
may both appear in the
<statusTranslations>
group for a particular MOS device. Status
codes vary with each MOS device, so refer to the manufacturer’s
documentation provided with the device for more configuration details.
The
UNKNOWN_STR
should be changed to the string the MOS device
reports if it is unable to determine the presence or absence of the MOS
item media.
The
UNAVL_STR
should be changed to the string the MOS device reports
if the MOS item media is absent.
The
AVAIL_STR
should be changed to the string the MOS device reports
if the MOS item media is present and ready to play.
The
INCOMP_STR
should be changed to the string the MOS device
reports if the MOS item media is partially present. An example is media is
being transferred from another machine and the transfer is not complete.
The
CUEING_STR
should be changed to the string the MOS device
reports when a request to cue a MOS item has been received.
The
CUED_STR
should be changed to the string the MOS device reports
when the MOS item media has been cued.
The
P_STR
should be changed to the string the MOS device reports when
a request to play a MOS item has been received.
Summary of Contents for iNEWS
Page 1: ...Avid Technology Inc MOS Gateway Installation Operations Manual Version 2 0 ...
Page 6: ...6 ...
Page 12: ...12 ...
Page 76: ...Chapter 4 76 ...
Page 98: ...Chapter 5 98 ...
Page 104: ...Chapter 6 104 ...
Page 116: ...Appendix A 116 ...
Page 130: ...Appendix B 130 ...
Page 150: ...Index 150 ...
Page 152: ... 152 Reader s Comments ...