Chapter 22. Events; Introduction - DigiDesign VENUE Profile Manual

Chapter 22: Events
This chapter introduces the Events window, and explains how
to use the Event List.

Introduction

An event consists of one or more triggers, which are configured
to cause one or more actions to occur.
Events can be very simple, such as a Footswitch input trigger-
ing a Recall Next Snapshot command. This is an example of a
single trigger (a footswitch input) causing a single action (Recall
Next Snapshot).
Events can also be quite complex and involve multiple triggers
and actions. For example, a single event can be defined so that
moving a specific fader above and/or below a certain level
sends a General Purpose output, recalls a specific snapshot and
mutes one or more channels. Multiple triggers can be consid-
ered conditionally using the available logic operators AND,
OR, and XOR.
The Event List is easy to configure, and many preconfigured
events are provided for Tap Tempo, snapshot Preview mode
and other functions.
For more information on the default events and other exam-
ples, see "Default Settings, Templates and Examples" on
page 206.
Terminology
Event A user-defined combination of one or more triggers and
one or more actions. Each event serves as a type of software
"macro" in which you establish a cause-and-effect relation-
ship between one or more console functions (triggers) and
their results (actions).
Trigger A conditional check used to fire an event.
Action A console function, mode or other response resulting
from an event being triggered.
GPI General Purpose Interface, also commonly known as a
logic interface.
Open GPI input or GPI output is floating, or at its reference
voltage.
Closed GPI input or GPI output is closed.
Footswitch Footswitch ports are functionally identical to GPI
inputs and share all of the same properties and behaviors.
Important Information about Snapshots and Events
Because Events can trigger snapshot recalls, and because snap-
shot recalls can trigger other events, it is possible to create
logic "feedback loops." For more information, see "Avoid
Feedback Loops" on page 205.
Chapter 22: Events 197