Differences

This shows you the differences between two versions of the page.

--- config:remotecontrol:dhd [2019/09/03 10:12] – Beispiel hinzugefügt tondose
+++ config:remotecontrol:dhd [2019/10/28 06:22] (current) – [Scripting] Typo tondose
@@ Line 48: / Line 48: @@
 Note: The XP5 XML format is not documented and not officially supported by DHD. We did our best to parse the file and extract all relevant information. But future Toolbox versions may change the format of the XP5 files without notice. If your XP5 file fails to load, in particular after an update of the DHD Toolbox application, please contact mAirList support so we can adjust our code to the new format.
+<WRAP center round tip 60%>
+The XP5 export function is only available in Toolbox 7 and 8.
+Starting with mAirList 6.2.3, the XP5 file is only used for the //DHD Console// window. Automatic configuration of fader channels and logics is done using the Extended Audio and Logic ID export from Toolbox (see next paragraph). From that version, mAirList configuration is compatible with Toolbox 9.
+</WRAP>
+==== Toolbox Import (mAirList 6.2.3 and up) ====
+mAirList can import Audio ID, Logic ID and Fader Channel information from Toolbox 7.x, 8.x or 9.x. This will allow a more convenient setup of the player etc. configuration, as you don't have to type the fader channel numbers and logic IDs manually anymore, but you can just select them from the list.
+In order to use this function, you just first export the IDs as an "Ext. DHD AudioID/LogicID Export (*.dpx)" file from DHD Toolbox (//Project -> Export -> Export AudioIDs/LogicIDs//). **Make sure that you select the correct file type with the "Ext." in it**, as the ordinary export will be missing the fader channel numbers:
+{{ :config:remotecontrol:pasted:20191004-125218.png?400 }}
+The resulting ''*.dpx'' file can then be imported into the mAirList configuration. If you have more than one device in your Toolbox project, or more than one virtual mixer in your core, you will be prompted to select the device/mixer from the list.
+The IDs are copied into the mAirList configuration. It is not necessary to keep the ''*.dpx'' file after import.
 ==== Players ====
@@ Line 60: / Line 78: @@
   * Fader channel number or fixed fader number (for faderstart mAirList -> console)
-If you linked an XP5 file on the //General// tab, click the //Select Fader Channel// button and select the channel that is associated with this player.
+If imported Toolbox data on the //Toolbox Import// tab (or linked an XP5 file in the case of a mAirList ersion older than 6.2.3), click the //Select Fader Channel// button and select the channel that is associated with this player.
-Without an XP5 file, you must look up the Fader Channel and Logic values manually:
+Without Toolbox import data, you must look up the Fader Channel and Logic values manually:
 The **FaderStart logic** and **PFL logic** addresses are used to control the mAirList player from the console, i.e., to start the player when the channel is opened on the console, and to start PFL playback when you press the PFL/CUE button on the channel strip.
@@ Line 98: / Line 116: @@
   * **Keep channel on when player is paused**: When enabled, the channel switch will remain in ON position when you pause the player, e.g. by pulling the fader down to the bottom. Otherwise, the channel will immediately go to OFF.
   * **Disable channel on/off switching**: Normally mAirList will switch on/off the channel when the player is started or stopped; this behavior can be disabled here.
+  * **Enable motorized fader control**: Check this if you are using a DHD model with motorized faders (e.g. SX2 or RX2) and the "Channel Start ON/OFF" function in Toolbox (rather than "Channel ON/OFF"). mAirList will move the faders to 0 dB or off, respectively, as you start or stop a player from the GUI. You should also check //Disable channel on/off switching// (see above) as motorized channels do not use the on/off function.
   * **Set channel label to item title**: When enabled, the title of the item loaded into the player will be sent to the console, where it will be displayed on the channel strip OLED.
 ==== Cartwall ====
@@ Line 109: / Line 128: @@
 Usually, all cart players will use the same audio output (and thus input channel on your mixer). The cartwall state (ON AIR, OFF AIR, PFL) can be linked to the state of the associated fader on your console, so the cartwall follows the fader start, and vice versa.
-Specify the FaderStart logic, PFL logic, and Fader Channel or fixed fader number; or use the Automatic Setup function if you linked an XP5 file. Please refer to the Players section above for an explanation of these parameters.
+Specify the FaderStart logic, PFL logic, and Fader Channel or fixed fader number; or use the Automatic Setup function if you imported Toolbox data. Please refer to the Players section above for an explanation of these parameters.
 === Player Logic IDs ===
@@ Line 132: / Line 151: @@
 Then enter these addresses into the //Ready// and //Idle// columns of the associated cart player.
+=== Options ===
+The options //Disable channel on/off switching// and //Enable motorized fader control// have the same meaning as with the players (see above).
 ==== Voice Tracking ====
@@ Line 209: / Line 232: @@
 ===== Scripting =====
-The DHD interface can be accessed via ''DHDRemote(0)'' (or ''DHDRemote(1)'' etc.) if you have more than one DHD remote controls registered). The function will return a ''IDHDRemote'' interface, which has, amongst others, the following methods:
+The DHD interface can be accessed via ''DHDRemote(0)'' (or ''DHDRemote(1)'' etc. if you have more than one DHD remote controls registered). The function will return a ''IDHDRemote'' interface, which has, amongst others, the following methods:
     procedure SetMonitorChannel(iNumber: byte; iLeft, iRight: word);