D*AP8
87
The
D*AP8
has two different
action types:
Event Actions
executes the predefined events
Bypass Actions
executes pre-defined bypass scenarios, independent of
the bypass events
An action runs like a flip-book inside the
D*AP8
. This powerful technology spans from simply
recalling a certain system parameter over speaker or Dolby specific parameter combinations
(household name: "Preset") to the complete reconfiguration of the
D*AP8
including all signal routing,
processing parameters and so forth. It allows you to create your own
snap shots
where you decide
what is part of it and what is not! But it also enables several
fail over
scenarios where the
D*AP8
will
automatically react to the system and/or parameter status.
The steps to set up the
EVENTS
system are as follows:
1.
Define
- trigger sources
2.
Configure
- triggers by logical combination of the pre-defined trigger sources
3.
Set up events
- by selecting presets for function blocks
4.
Create actions
- what will happen - which trigger will launch which event? Or what will happen
in case someone presses the
<BYPASS>
button at the
X*AP RM
1
or
engages the
<Force Trigger Active>
check box
(see EVENTS
> Actions > Bypass Action).
Setup GUI – EVENTS – Triggers – Sources
–
Remote Hotkeys
Hotkeys are the eight buttons of an
X*AP RM
1
remote panel. You may give them names and enable them
to become active on the
X*AP RM
1
remote panels main operating menu:
<add trigger>
You can add lines here.
#
The number of the Hotkey on the
X*AP RM
1
remote panel, counting
from left to right.
Label
Each Hotkey may have a label that
appears in the display of the
X*AP RM
1
remote panel above that
button.
X*AP Remote
[ON / OFF]
If you un-check, the respective
Hotkey on the
X*AP RM
1
remote
panel becomes inactive - no label is
displayed and the button
background light turns off.
Mobile Options
The buttons of the
Mobile UI
can be assigned an individual color.
You will see the bright color if the button is active and the dark color
if it is inactive. [OFF/Divider] acts as a place holder for a button that
is temporarily set to OFF.
<remove>
will remove a line from the list. This will automatically disable the
respective front panel button.
The number of hotkey triggers is not limited. You may also add virtual hotkeys which can be used by a
graphical UI for example that may have more than 8 compared to the
X*AP RM
1
.