Event Setup Controls - Cobalt Digital Inc 9903-UDX-ADDA Product Manual

Operating Instructions
Table 3-2 9903-UDX-ADDA Function Menu List — continued

Event Setup Controls

• 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).
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-55) for setting up e-mail alerts).
In the example here for Event 1, Acquired Video Format is used to screen for an SD input (rather than the normal 720p5994
format). When detected, this status can be used here to invoke a user preset (among numerous other actions). In this example,
the detected SD input condition invokes user preset "upconvert to 720p", which would be a scaler up-convert setting.
Conversely, to go back to the original processing (no scaling), an event could be set up here looking for normal 720p input
status, and in turn invoke an event action returning normal no-scaling operation (in this example, user preset "no scaling").
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 a scaler format change will take longer to engage than a preset involving only an audio
routing 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.
9903UDXADDA-OM (V1.5)
9903-UDX-ADDA Function Menu List and Descriptions
Provides event-based loading allowing a defined preset
to be automatically engaged upon various received
signal status. Actions can be "canned" control
commands or user-defined by going to a user preset.
Event-based loading is particularly useful for
automated card setup when transitioning from normal
processing to processing supporting an alternate
format.
9903-UDX-ADDA PRODUCT MANUAL
3-53