1 - DHD External Control Protocol (ECP)
This connection type implements the DHD External Control Protocol (ECP) for mixing consoles and routers from DHD.audio GmbH.
Supported Devices and Prerequisites
The following devices are supported:
- All series 52 cores and consoles
- RM4200D
- Fully supported if running on Firmware 5.x
- Partial support for Firmware 4.x (routing not implemented at this time)
Only TCP/IP connections are supported, no serial port connections.
Configuration
General Tab
Connection-specific settings:
- Network connection: Enter IP/host and port number (usually 2008) of the core.
- Fader Level Notification (only supported for Firmware 7.x): Choose either Channel-based or Fader-based to enable instant notification of fader level, either based on fader channels or by physical faders.
Elements Tab
Click the Load Toolbox Data to import information about your core
from an Extended DHD AudioID/LogicID Export (*.dpx
) file.
This file can be created from the DHD Toolbox application (Project -> Export -> Export AudioIDs/LogicIDs).
Important
Make sure that you set the file type to Extended (Ext.) output in the Save dialog in Toolbox.After importing the file into BTConnect, the various tabs (Logics, Channels, Routings) will be filled with the IDs and descriptions from the Toolbox file. (If there is more than one device in your Toolbox project, and thus in the export file, you will be first asked which device should be imported for this connection.)
Additional information can be entered manually on the tabs:
- Logics: Enter an optional description that will be used in the GUI rather than the default string imported from Toolbox. Optionally, check a logic for which the current state should be queries when BTConnect starts. (All other logics remain in “unknown” state until the first update is received from the core.)
- Channels: Enter an optional description for each fader channel.
- Faders: Enter an optional description for each fader of each virtual mixer.
- Routing: Check the Req box in order to request the state of a particular routing on startup. Check Enable routing crosspoint notifications in order to receive instant updates when routing changes.
Parameters
The following parameters are provided by ECP connections:
Logics
logic/<id>
(boolean, read/write) - the state of the logic with the number<id>
(1-4095)
Fader Channels
<number>
refers to channel number as given in Toolbox.
channel/<number>/start
(boolean, write-only) - switch channel on or off. Note: This parameter is write-only, the current state can only be retrieved via logics.channel/<number>/pfl
(boolean, write-only) - turn PFL on or off. Note: write-only, use logics to retrieve status.channel/<number>/level
(float, write-only or read/write) - set fader of the channel to the specified level (in dB, range -32.768..+10). If Level Notification is set to “Channel-based” in the configuration, this parameter is read/write, and indicates current fader level, e.g. when operated manually on the console.channel/<number>/timedlevel
(string, write-only) - set fader of the channel to the specified level (in dB, range -32.768..+10), within the specified time (in milliseconds) and with a curve of either level linear (0) or fader linear (1). The value must be encoded as a string in the form<level>,<time>,<curve>
, or just<level>,<time>
; in the latter case, linear fade (0) is used.
Faders
<mixer>
refers to virtual mixer (1..4).
<fader>
refers to fader (1..48) of that virtual mixer.
mixer/<mixer>/fader/<number>/start
(boolean, write-only) - switch fader on or off. Note: This parameter is write-only, the current state can only be retrieved via logics.mixer/<mixer>/fader/<number>/pfl
(boolean, write-only) - turn PFL for this fader on or off. Note: write-only, use logics to retrieve status.mixer/<mixer>/fader/<number>/level
(float, write-only or read/write) - set fader to the specified level (in dB, range -32.768..+10). If Level Notification is set to “Fader-based” in the configuration, this parameter is read/write, and indicates current fader level, e.g. when operated manually on the console.mixer/<mixer>/fader/<number>/timedlevel
(string, write-only) - set fader to the specified level (in dB, range -32.768..+10), within the specified time (in milliseconds) and with a curve of either level linear (0) or fader linear (1). The value must be encoded as a string in the form<level>,<time>,<curve>
, or just<level>,<time>
; in the latter case, linear fade (0) is used.
Potentiometer (Monitor Level)
potentiometer/<id>
(float, write-only) - Level of the potentiometer/monitor channel (in dB)
Routing
routing/<output ID>
(string, read/write) - the input audio ID of the signal currently routed to the specified output audio ID. Audio IDs are specified as a 4-digit (Toolbox 4) or 8-digit (Toolbox 5-9) hex number.
Routing is generally based on mono channels in a DHD system, so all outputs are mono, and all inputs are mono as well; thus, a stereo output (input) is represented by two mono outputs (inputs), and in order to route a stereo input to a stereo output, two mono routes must be set.
In order to facilitate the routing of stereo signals, BTConnect will create three parameters for all stereo outputs: one for the left channel, one for the right channel, and one “virtual” stereo parameter (with the stereo bit set in the audio ID). Assigning a mono input ID to this virtual stereo parameter will route that mono signal to both outputs; setting it to a stereo audio ID (with the stereo bit) will send two routing commands for the left and the right channel.
Note
In order to change the output of a stereo Selector with routing parameters, “Source list accepts external routings” must be checked in the Selector configuration in Toolbox. This is because two separate ECP packets are sent in order to change the stereo routing, and the system must be in an “allowed state” in between these to packets.2 - DHD REST API
This protocol implements the DHD REST API.
Supported Devices and Prerequisites
All DHD Series 52 cores, running on Firmware 9.1+ and having the REST API license enabled, are supported.
Configuration
On the General Tab, enter IP and port of the core, and the WebApps API token defined in Toolbox.
For picture upload, you can specify an optional Picture folder which is used
as the base for relative filenames supplied to the picture/<id>
parameter.
Parameters
Channels
channel/<id>/label
(string, write-only) - Update the label of the fader channel with the specified iD.channel/<id>/snapshot
(integer, write-only) - Load a channel snapshot. The value is the snapshot number.
Global Labels
globallabel/<id>
(string, write-only) - Update a global label.
Picture Upload
picture/<id>
(string, write-only) - Upload and replace the picture with the specified resource ID (see Toolbox). The value must be the valid filename of a PNG file, either an absolute filename, or a relative filename in the picture folder set in the configuration.
Snapshots
mixer/<id>/snapshot
(integer, write-only) - Load a mixer snapshot.ID
is the number of the virtual mixer in the range1..4
. The value is the snapshot number.
3 - DHD RM2200D
This connection type implements the remote control protocol for the DHD RM2200D.
Supported Devices and Prerequisites
This protocol supports the DHD RM2200D. Communication is through TCP, so the DSP core must be connected with the network.
Configuration
On the General tab, enter the IP address and the TCP port for the remote control protocol (usually 2200).
Parameters
This connection type provides the following parameters:
Main Control Unit
main/button/<button>
(boolean, read-only) - the press state of the respective button on the main control unitmain/lcd/1
andmain/lcd/2
(string, read-only) - the texts currently displayed in the two-line LCD of the main control unit
Faders
Fader numbers are 1
through 16
.
fader/<number>/source
(integer, read/write) - the ID of the audio source currently assigned to this faderfader/<number>/on
(boolean, read/write) - the status of the fader ON functionfader/<number>/cue
(boolean, read/write) - the status of the fader CUE functionfader/<number>/button/<button>
(boolean, read-only) - the press state of the respective button on this fader stripfader/<number>/led/<led>
(boolean, read-only) - the state of the respective LED on this fader stripfader/<number>/status/<status>
(boolean, read-only) - theinputstate
,timer
,faderstart
andloadsetup
state of this fader strip