Table of Contents
Advertisement
7.
Troubleshooting the 9625LG Series Keyer
If an error occurs while using the 9625LG Series Keyer, consult the following table for more
information.
provides a complete list of error messages with corresponding error descriptions.
Displayed Error Message
"Not a logo"
"No window avail"
"Bad position"
"Bad logo"
"2 clocks already"
"Too many objects"
"Bad logo file"
"Crawl is running"
"No logo or audio"
"Bad audio
"Stream active"
"MAL read failed"
"Play cache full"
"Timeout"
TROUBLESHOOTING
9625LG Series Logo Inserters and Media Keyers Manual
Error Description
While loading the logo, the firmware found was unable to support
the load action. The file is probably corrupt.
All windows are in use. There is a limit of sixteen active logos, each
of which has a window on the display. This error occurs when there
is an attempt to load a seventeenth logo. Note that the EAS crawl,
whether active or not, takes up a window.
Indicates that an attempt was made to insert a logo that would
overlap with another logo(s).
Not a logo. There has been an attempt to load a file that is not a
logo file.
Too many time & temperature or CG logos have been requested. In
the case of time, the 9625LG Keyer Series only supports two clocks
at one time.
Clock file is corrupt. Error occurs if media is removed.
Too many crawls have been requested. The 9625LG Keyer Series
only supports one crawl running at any one time. Similar to "2
clocks already" error, with respect to crawls.
A logo and an audio clip are tied together and one of the elements
cannot be loaded.
Not an audio file. There has been an attempt to load a file that is
not an audio file.
An attempt to insert an audio clip while another audio clip is in play
mode.
Unable to read the media action list. Occurs while reading a media
action list file.
Attempting to load a file into the playout cache when there is
insufficient space available.
Connection timed out. A
connected party did not properly respond after a period of time
(timeout period varies, depending on the communication protocol).
Revision 4.2
request failed because the
connect()
Page 7-1
Advertisement
Table of Contents
