Junger Audio D*AP4 FLX / D*AP4 LM Edition - Manual (Page 64)

D*AP4
59
Setup GUI – EVENTS – Overview
As mentioned previously, D*AP4 includes a sophisticated event management system.
The event system performs Actions. These actions are built from Events.
Actions may be triggered manually (via the X*AP RM
1 remote panel Hotkeys), semi-automatically
(triggered by network commands or GPIs) and automatically (triggered by changes of parameters and/or
the internal status) or as a combination of all three.
The overview shows the building blocks of the action management of the D*AP4:
A trigger is subdivided into a trigger type and a trigger source. E.g. a GPI is a trigger type while its
number (the physical input) represents the trigger source. Other trigger types have sources which must be
configured, like the names of X*AP Hotkeys or network triggers.
Hotkey Sources You may assign hotkeys of the X*AP remote and / or the mobile UI
to become a trigger source.
Network Sources Received via the l-s-b EmBER+ protocol.
Parameter Sources Device parameters / status information grouped into
system and Interfaces.
The triggers will be defined by its trigger equation that may be the logical combination of 2 trigger sources.
The D*AP4 knows five different event types:
Preset Events System / Interfaces / Routing / Audio Processor / Program / Delay
Parameter Events Measurment
Measurement Events Pause / Continue / Reset / Reset Max / Start / Pause / Stop
I/O Events GPOs / Loudness Measurement
Bypass Events Program 1 / Program 2
The D*AP4 has two different action types:
Event Actions executes the predefined events
Bypass Actions executes pre-defined bypass scenarios, independent on
the bypass events
An action runs like a flip-book inside the D*AP4. This powerful technology spans from simply recalling a
certain parameter over specific parameter combinations (household name: "Preset") to the complete
reconfiguration of the D*AP4 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 fail over scenarios where the D*AP4 will automatically react to the system
and/or parameter status.