Differences

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

--- config:remotecontrol:dhd [2019/10/04 13:02] – tw
+++ config:remotecontrol:dhd [2024/10/14 09:27] (current) – [Set Logic] Typo tondose
@@ Line 116: / 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 150: / 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 224: / Line 229: @@
 ==== Set Logic ====
-Using this action, you can set logic addresses to on our off.
+Using this action, you can set logic addresses to on or off.
 ===== 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);