Version 3.0.2 ReadMe
6
items in the loaded rundown's story form and story body.
The mosItemReplace command is defined in the MOS Protocol.
Known Limitations
This section provides information on known limitations that were not addressed in this release. Any
available workaround procedures are also documented, when possible.
Note: For limitations related to compatibility of this release with previous versions/other products,
see the section of this document entitled,
“Compatibility Issues”.
iNEWS
iNEWS does not get "Download Complete" message from MOS Gateway
This is caused by the MOS device not including a roID with its roAck to the Avid MOS Gateway after a
show has been loaded. If the roID is not included in the message, the MOS Gateway does not know
where to send the "Download Complete" message.
iNEWS installer overwrites inewscom.dll registration used by MOS Gateway
The registration of the inewscom.dll installed with MOS Gateway 2.6.1 and 2.6.2 will be overwritten
by the iNEWS client install program. When this occurs, an incorrect version of the inewscom.dll is
used by MOS Gateway. This can cause parts of the MOS Gateway functionality to fail, specifically
roStorySend.
Workaround: Do not install iNEWS client software on the MOS Gateway computer. Or install MOS
Gateway after the iNEWS client software.
MOS Gateway
Unused MOS devices will generate reqMachineInfo errors in the log file
If a MOS device is specified in the mosconfig.xml file and it is not present on the network, there will
be errors indicating that the device is not reachable during start up of the MOS Gateway. This is normal
behavior.
Workaround: Remove any unused MOS device configurations from the mosconfig.xml file.
MOS devices on the network but not specified in the mosconfig.xml file generates errors
in the log file
If a MOS device is present on the network and is configure to communicate with the MOS Gateway
computer it will cause error messages to be logged in the MOS Gateway logging if it is not also specified in
the mosconfig.xml file. This is normal behavior.
Workaround: Remove from the network or reconfigure any unused MOS devices that are configured to
talk to the MOS Gateway but are not going to be used.
Additional download time overhead when using handlesRoStorySend option
Because of the amount of data being processed and sent with this option enabled, the amount of time to
load MOS devices will be significant.
Workaround: Unless required by the MOS device, Avid recommend that this option be set to NO.
(8 paginas)
Manymanuals.com
Manymanuals.de
Manymanuals.fr
Manymanuals.it
Manymanuals.pl
Manymanuals.cz
Manymanuals.es
Manymanuals-pt.com
Comentarios a estos manuales