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

D*AP4
6
Control Concept
The communication between external applications or the X*AP RM
1 remote panel, is based on
TCP/IP over Ethernet.
The setup GUI utilizes web technology. At the time of editing this manual the functionality of the web GUI is
optimized for Firefox 30.x and higher.
The setup GUI can be complemented by other application programs running on MS Windows® XP, W7, W8
like the Junger Application Manager J*AM. Operator access will also be available for mobile devices running
an appropriate browser on iOS or Android.
An SNMP agent may be activated to incorporate the device into a station monitoring system.
For 3
rd
party remote applications, Junger highly recommends using the l-s-b Ember+ protocol which is widely
distributed in the European broadcast industry. The user community is also increasing rapidly world wide.
By default, the X*AP RM
1 remote panel and the D*AP4 "talk" Ember natively.
Operating Concept
Further below you will see that the setup GUI for the device is grouped into several parameter areas.
One can reach the parameters via a 3 tier navigation by tabs which may have sub tabs, and the sub tabs may
have pages embedded or extra soft buttons for groups of parameters.
Each function block (parameter area) has dedicated presets. The presets can be recalled at any time during
operation, either by manual intervention via the embedded web server (browser based GUI), automatically
by the internal event manager or by external applications.
For all relevant settings an ON AIR and a PRESET part exists. I.e. you may either edit the parameters
ON AIR or offline for the respective part of the D*AP4.
The presets of the D*AP4 are persistent by nature. You are working directly on the preset memory.
I.e. you need not to worry about storing such presets, the D*AP4 does it for you.
Event Concept
The D*AP4 incorporates a sophisticated event management system.
Events may be combined to perform actions. The D*AP4 offers these event types:
* Preset Events for System set up, Interfaces, Routing, Audio Processing etc.
* I/O Events to control GPOs
* Bypass Events for pre-configured bypass scenarios
* Measurement Events to control loudness measurements per program
These events may be combined to form Actions which are fired by Triggers.
Triggers are defined by a logical combination (AND, OR, XOR) of two random trigger sources.
Trigger source may be GPIs, hotkeys of the X*AP RM
1 remote panel, network commands, parameters, other
active events, other active triggers (nested trigger), or device status information (e.g. sync lost).