Audio Processing Blocks; Control, Operating & Event Concept - junger D*AP4 FLX User Manual

Audio Processing Blocks

Above you see the various function blocks of the audio processor rendered by the DSP engine.
Each function block has its representation in the GUI by individual tab sheets. You may simply click on the
respective graphical area as an alternative way to navigate through the GUI.
It is important to understand that the physical input interfaces of the device (SDI DE-EMBEDDER, AES IN)
must be routed to the DSP inputs in order to process it. Similarly the DSP outputs must be routed to output
interfaces (SDI EMBEDDER, AES OUT). You will find those settings by clicking on the ROUTING tab.
Control Concept
The communication between external applications or the X*AP RM
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.
rd
For 3 party remote applications, Junger Audio highly recommends using the 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
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.
remote panel and the D*AP4 "talk" Ember natively.
1
6
remote panel, is based on
1
D*AP4