Known Problems & Limitations
iNEWS Workstation
• 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.
• It is not possible to copy a MOS item from the Story Form panel and paste it into
another story’s body or story form. This is a limitation of MOS replication.
Workaround: If the MOS information appears in the story body, you can copy the MOS
item’s production cue marker—also known as a grommet—and then paste it into another
story’s body. If the MOS information appears only in the Story Form panel, the entire
story must be copied from the device-specific (replication) queue to the rundown queue,
and then edited.
MOS Gateway
• Sometimes cannot stop router service
Under certain conditions that we have not yet learned to consistently reproduce, the
MOS Gateway Router service cannot be stopped by the Services control panel.
• Occasionally see ‘ghost’ rundowns on vizrt Content Pilot
Content Pilot will occasionally have ‘ghost’ rundowns shown even after turning off
monitor. The ‘ghost’ rundown cannot be updated or unloaded. This seems to happen
infrequently; the steps to reproduce it are not known.
Workaround: Try loading then unloading the show, restarting the MOS Gateway
services or rebooting the MOS Gateway machine.
• AMCP name must match MOS Gateway hostname channel assignments to work
A device needs its amcp name to be the same as the hostname of the MOS Gateway
machine in order to allow channel assignments in system.mos-map.
• If one device uses channels, all devices are prompted for channels
All devices on the gateway will be prompted for a channel assignment if any of the
devices on the gateway are configured to use channels.
• Cannot get item duration when using replication
There is currently no way to display the MOS duration in the MOS items created by the
replication process.
Comentarios a estos manuales