Grass Valley LGK-3901 - Manual (Page 33)

GUIDE TO INSTALLATION AND OPERATION
LGK-3901/DSK-3901 | 27
EASNoneHD1080.oxa None 1080i / 59.94, 1080i / 50, 1080p / 59.94, 1080p / 50,
EASNoneHD720.oxa None 720p / 59.94, 720p / 50
Each default EAS template file can be copied (from /etc/eas/ into /home/images/) and then modified to suit
requirements via the TextBuilder application (available from the Media Conversion Suite (MCS) CD that ships with
LGK-3901/DSK-3901). Background color, crawl speed, font, size, shadow, and positioning are all customizable.
Additional elements may also be added to the crawl such as another text field or logo/graphical element.
Note the following considerations relating to EAS template files:
• The EAS template filename should not be changed. If it is then the EAS option will not find the template.
• Always use TextBuilder or IMM to transfer modified files to the LGK-3901 so that all fonts associated with the
template are also transferred.
• The datasource name “EAS_TEXT” is associated with the text crawl element in an EAS template. Ensure that
its datasource value is not inadvertently adjusted via automation since it may affect the EAS message on-air.
• If no text has been received from the EAS receiver blank text will be seen in the EAS template. Either leave
this blank, or pre-set the data-source to something harmless such as “Stand by for an important EAS alert”
4.8.3.3 EAS Triggering
Note: EAS messages are displayed on-air following appropriate GPI triggers or automation commands. To set the
relevant GPI refer to section 4.10. For automation commands refer to the Oxtel Series Automation Protocol manual.
When an EAS alert on LGK-3901 is triggered ‘on’ by GPI or automation, the following internal events occur:
• The EAS option determines the ‘EAS Layer’ (DSK3, DSK4 or DSK5) which is the most downstream keyer that
has an associated store – (this is configured via SETUP > STORES > STORES CONFIG)
• The ‘EAS Layer’ is cut down. Its prior keyer state plus the image loaded (if any) are recorded for later use.
• Any layers downstream of the ‘EAS Layer’ are also cut down and their previous keyer state recorded for later.
• The appropriate EAS crawl template is loaded into the ‘EAS Layer’. The selected crawl file is determined by
the alert level in the crawl data and the video standard. The crawl data must be received before the EAS alert
is initiated, otherwise stale data will be displayed.
• The ‘EAS Layer’ is cut up to reveal the EAS alert (in the video foreground).
When an EAS alert is triggered ‘off’ by GPI or automation, the following internal events occur:
• The current EAS crawl will complete after which the ‘EAS Layer’ cuts down.
• The previous image (if any) is reloaded into the ‘EAS Layer’.
• The ‘EAS Layer’ plus any layers downstream of it are restored back to their prior cut states.
• Any remaining events in the EAS alert ‘off’ GPI macro will be processed. These macro events are suspended
until the above events complete.
Additional commands can be added to the GPI macros to provide other EAS actions. At a minimum, these events
must include a ‘Voiceover On’ and ‘Voiceover Off’ command and appropriate delays to ensure that the data for the
crawl is received. Such GPI macros are outside the scope of this manual, but can be discussed with Miranda Support.
As the LGK-3901 retains the last EAS text message received, the EASNone.oxa crawl will only be seen when the
EAS mode is activated with no alert level.