Key concepts – Grass Valley Kaleido-X v.7.80 User Manual
Page 330
322
Creating Actions
Key Concepts
Key Concepts
Term
Description
Layout
A group of monitors (or composite monitors) arranged for display on a
monitor wall.
XAdmin
The application used to perform administrative functions (e.g., configure
network settings) on a Kaleido-X monitoring system.
XEdit
The application used to create and modify rooms, layouts and other
components of a Kaleido-X monitoring system.
Composite monitor A group of primary monitors.
Monitor
A graphical component used in the creation of a layout. Typical monitors
include UMDs, time code monitors, audio monitors, video monitors, and
clocks.
Action item
Action elements that are associated with a specific action (e.g., Load
Layout, Set GPI Out, etc.).
System list
Refers to the hierarchical list visible under XEdit’s System tab, which
gives a virtual representation of the system hardware (i.e., multiviewers
and peripheral devices).
Trigger
Refers to the event that causes an action to be invoked. For a monitor
wall action, a trigger could be a double click on a monitor. Background
actions are triggered by alarms or by a Gateway command. When
defining an action for a monitor, you could specify, for instance, that a
specific full screen layout be displayed on the monitor wall in response
to the trigger.
On Change: background action is triggered by any change in alarms
status
On Disabled: background action is triggered when an alarm is disabled
On Normal/OK: background action is triggered when an alarm reverts to
normal
On Minor/Warning: supported for Gateway alarms only
On Major: supported for Gateway alarms only
On Critical/Error: background action is triggered by a critical alarm
Triggering of
actions
Any multiviewer alarm can be used as a trigger to invoke a background
action.
The end event of any countdown timer can be used as a trigger to invoke
a background action.
Any GPI input from the multiviewer can trigger a background action.
Gateway commands sent by an external device can be used to trigger
actions created in XEdit.
Note:
A background action triggered by an alarm is always executed,
regardless of the alarm’s operational mode (see