Cobalt Digital Inc 9980-CSC-3G, Руководство по эксплуатации продукта, Страница: 52 / 76

3
9980-CSC-3G Function Menu List and Descriptions
3-24
9980-CSC-3G PRODUCT MANUAL 9980CSC3G-OM (V1.4)
Presets > Event Triggers
Event Setup Controls
Provides event-based loading allowing a defined preset
to be automatically engaged upon various received
signal status or other conditions/actions. Actions can
be “canned” control commands or user-defined by
going to a user preset.
Event-based loading is particularly useful for
automated setup when transitioning from normal
processing to processing supporting an alternate
format. Up to 32 separate event can be set up.
• Event based preset loading is not passive and can result in very significant and unexpected control and signal
processing changes if not properly used. If event based presets are not to be used, make certain the Event Based
Loading button is set to Disabled.
• Because event based preset loading applies control changes by invoking presets, loading conditions cannot be
nested within a called preset (event-based loading settings performed here cannot be saved to presets).
Table 3-2 9980-CSC-3G Function Menu List — continued
Event triggers allow a variety of event screening criteria, and in turn provide an Event Action “go to” in response to the detected
event(s). For each screened criteria, categories can be set as “don’t care” or set to specific criteria to broaden or concentrate on
various areas of concern.
The Event based loading button serves as a master enable/disable for the function.
Go-to Event Actions can be user-defined presets, “canned” (hard-coded) selections (such as GPO triggers or routing changes),
or automated E-mail alert to a respondent (see Email Alerts (p. 3-26) for setting up e-mail alerts).
Note: • Screened conditions are triggered upon start of event. Any event-based setup must be done in advance of the
triggering event in order for event to be detected.
• Loss of true conditions does not disengage an event-based triggering. A new set of true conditions must be
defined and then occur to transition from one event-based trigger to another.
• Time required to engage an event-based trigger depends upon complexity of the called preset. (For example,
a preset that invokes large-scale changes may take longer to engage than a preset involving only a small
change.)
• Make certain all definable event conditions that the device might be expected to “see” are defined in any of the
Event 1 thru Event 32 rows. This makes certain that the device will always have a defined “go-to” action if a
particular event occurs. For example, if the device is expected to “see” a 720p5994 stream or as an alternate,
a 525i5994 stream, make certain both of these conditions are defined (with your desired go-to presets) in any
two of the Event 1 thru Event 32 condition definition rows.
In the example here for Event 1 and Event 2, the device is set to invoke a preset that applies custom color correction settings
nested in preset “Colorimetry 2A” whenever GPI 1 goes LO. When this GPI goes HI, corresponding action in preset “Normal”
invokes another preset to revert the device to default settings.