Differences

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

--- config:remotecontrol:airlite [2016/08/31 14:05] – [Scripting] tw
+++ config:remotecontrol:airlite [2022/04/15 15:03] (current) – Beispiel aktualisiert tondose
@@ Line 1: / Line 1: @@
-====== D&R AIRLITE Remote Control ======
+====== D&R AIRLITE and WEBSTATION Remote Control ======
-This article describes the remote control interface for the [[http://www.d-r.nl/airlite-usb.html|D&R AIRLITE-USB]] mixing console.
+This article describes the remote control interface for the [[http://www.d-r.nl/airlite-usb.html|D&R AIRLITE-USB]] and [[https://www.d-r.nl/webstation.html|D&R WEBSTATION]] mixing consoles.
 The AIRLITE is an 8-channel 19" mixer which includes four stereo USB audio interfaces, and a USB control module for fader start etc., all through a single USB connection.
+The WEBSTATION is the little brother of the AIRLITE, featuring 6 channels and three USB audio interfaces.
+Configuration steps are similar for both models.
 ===== Audio Setup =====
@@ Line 9: / Line 13: @@
 The audio setup is not exactly part of the remote control configuration, actually it's entirely separate, but you will find the following remarks useful.
-The AIRLITE has four USB channels/faders, labelled "USB 1" through "USB 4" on the mixer surface.
+The AIRLITE has four USB channels/faders, labeled "USB 1" through "USB 4" (WEBSTATION: three USB channels) on the mixer surface. These USB channels all have their own USB (stereo) audio interface, all of which are connected to a common USB hub inside the console.
-The USB channels all have their own USB (stereo) audio interface, all of which are connected to a common USB hub inside the console.
-Also connected to that USB hub is the USB control module used for remote control (see below). So there is a total of **five** USB devices inside the console.
+Also connected to that USB hub is the USB control module used for remote control (see below). So there is a total of five USB devices inside the console.
-When you plug the USB cable into your computer, Windows will detect the devices one by one, and give the soundcards names like "USB Audio", "2-USB Audio", "3-USB Audio" and "4-USB Audio" (names may vary).
+When you plug the USB cable into your computer, Windows will detect the devices one by one, and give the sound cards names like "USB Audio", "2-USB Audio", "3-USB Audio" and "4-USB Audio" (names may vary).
 It is important to know that the order of these devices is somewhat random, and it does not coincide with the order of the USB channels on the mixer surface most of the time!
@@ Line 21: / Line 23: @@
 So we recommend that you first go to the Windows audio settings, playback devices, identify each USB channel, then edit each device and change it's name ("Speaker") to something more useful (e.g. "AIRLITE USB 1"). These names will appear in the mAirList audio setup, so you can easily identify the correct USB audio channel.
-Each audio device also has a stereo return signal, represented by a record device in the Windows audio settings. The exact signal mapping can be looked up in the AIRLITE manual. The return signal for USB 1 will usually carry the "main" (program) output; use this as the line-in device for streaming.
+Each audio device also has a stereo return signal, represented by a record device in the Windows audio settings. The exact signal mapping can be looked up in the AIRLITE/WEBSTATION manual. The return signal for USB 1 will usually carry the "main" (program) output; use this as the line-in device for streaming.
 It is recommended that you use WASAPI instead of DirectSound, as this will avoid mixing up of the several audio devices. Also make sure that you have the console plugged into the same USB port at all times; otherwise Windows may detect all devices as new, breaking your audio setup.
@@ Line 27: / Line 29: @@
 ===== Configuration =====
-The AIRLITE software must be installed on your computer before you can start with the remote control configuration.
+The AIRLITE/WEBSTATION software must be installed on your computer before you can start with the remote control configuration.
-Then open the standalone configuration app, or the Control Panel, go to the //Remote Control// page, and add a new //D&R AIRLITE// remote.
+Then open the standalone configuration app, or the Control Panel, go to the //Remote Control// page, and add a new //D&R AIRLITE// or //D&R WEBSTATION// remote.
+We will demonstrate the configuration of the AIRLITE in the remainder of this article; WEBSTATION is similar.
 ==== Players ====
@@ Line 45: / Line 48: @@
 ==== Cartwall ====
-The AIRLITE has 16 buttons, in two rows (labeled "A" and "B"), that can be used to control the cartwall players. If you are going to use these buttons, select the row(s) to use on the //Cartwall// tab:
+The AIRLITE has 16 buttons (WEBSTATION: 12 buttons), in two rows (labeled "A" and "B"), that can be used to control the cartwall players. If you are going to use these buttons, select the row(s) to use on the //Cartwall// tab:
 {{ :config:remotecontrol:pasted:20160831-153751.png?400 }}
@@ Line 61: / Line 64: @@
 ==== Advanced ====
-On the //Advanced// tab, you can adjust the IP and ports that the AIRLITE interface software is running on. It is not required to make any changes here unless you are running the AIRLITE software on a different computer.
+On the //Advanced// tab, you can adjust the IP and ports that the AIRLITE/WEBSTATION interface software is running on. It is not required to make any changes here unless you are running the AIRLITE/WEBSTATION software on a different computer.
 ===== Scripting =====
-The AIRLITE remote offers an interface which can be used to communicate with the console from a script. To access the interface, use the following function:
+The AIRLITE/WEBSTATION remote offers an interface which can be used to communicate with the console from a script. To access the interface, use the following function:
   function AirliteRemote(iIndex: integer): IAirliteRemote;
+Note: Name of the function is always ''AirliteRemote'', and name of the interface is always ''IAirliteRemote'', also for WEBSTATION. (The same class is used used internally for both models.)
 Remotes are 0-based, so ''AirliteRemote(0)'' will return a reference to the first remote in the system.
-At the time being, the ''IAirliteRemote'' interface offers two useful functions:
+Up to mAirList 6.2, the ''IAirliteRemote'' interface offers two useful functions:
   procedure SetLED(iNumber: integer; iColor: TAirliteColor);
   procedure SetLEDBlink(iNumber: integer; iOnColor, iOffColor: TAirliteColor; iSpeed: TAirliteBlinkSpeed);
-The first one sets an LED of one of the push buttons to a particular color, the second one does the same, but with flashing. The available button IDs are:
+The first one sets an LED of one of the push buttons to a particular color, the second one does the same, but with flashing. The available button IDs for AIRLITE are:
   * "A" buttons: 0 (Button 1A) to 7 (Button 8A)
   * "B" buttons: 8 (Button 1B) to 15 (Button 8B)
-  * 255 (hex $FF): All buttons at the same time
+  * 255 (hex ''$FF''): All buttons at the same time
+And for WEBSTATION, given the lower number of butttons:
+  * "A" buttons: 0 (Button 1A) to 5 (Button 6A)
+  * "B" buttons: 6 (Button 1B) to 11 (Button 6B)
+  * 255 (hex ''$FF''): All buttons at the same time
+The available color values are:
+  * ''alcNone'' (no color, LED off)
+  * ''alcRed''
+  * ''alcGreen''
+The available blink speed values are:
+  * ''albsSlow''
+  * ''albsNormal''
+  * ''albsFast''
+Starting with mAirList 6.3, access to the following low level remote functions is possible through the ''IAirliteRemote'' interface:
+  function RemoteOn(iModule: TAirliteModuleType; iAction: TAirliteAction): integer;
+  function RemoteCue(iCueType: TAirliteCueType; iAction: TAirliteAction): integer;
+  function RemoteCueReset: integer;
+  function RemoteAutoCueAnnouncer(iAction: TAirliteAction): integer;
+  function RemoteAutoCueCRM(iAction: TAirliteAction): integer;
+  function RemoteNonStop(iAction: TAirliteAction): integer;
+  function RemoteComm(iModule: TAirliteModuleType; iAction: TAirliteAction): integer;
+  function RemoteCough(iModule: TAirliteModuleType; iAction: TAirliteAction): integer;
+  function RemoteVT(iModule: TAirliteModuleType; iAction: TAirliteAction): integer;
+Possible values for ''TAirliteModuleTypes'' are:
+  * ''almModule1''
+  * ''almModule2''
+  * ''almModule3''
+  * ''almModule4''
+  * ''almModule5''
+  * ''almModule6''
+  * ''almModule7''
+  * ''almModule8''
+  * ''almModuleAll''
+Possible values for ''TAirliteCueType'' are:
+  * ''actModule1''
+  * ''actModule2''
+  * ''actModule3''
+  * ''actModule4''
+  * ''actModule5''
+  * ''actModule6''
+  * ''actModule7''
+  * ''actModule8''
+  * ''actAux''
+  * ''actNonStop''
+  * ''actAir''
+  * ''actAll''
+Possible values for ''TAirliteAction'' are:
+  * ''alaDeactivate''
+  * ''alaActivate''
+  * ''alaToggle''
+==== Example ====
+Switch on //Cue// over AIR input when Extra-PFL is launched:
+  procedure OnExtPFLOn(Item: IPlaylistItem; ExtPFLCount: integer);
+  begin
+    if ExtPFLCount <> 0 then
+      AirliteRemote(0).RemoteCue(actAir, alaActivate);
+  end;
+… and turn off when Extra-PFL is closed:
+  procedure OnExtPFLOff(Item: IPlaylistItem; ExtPFLCount: integer);
+  begin
+    if ExtPFLCount = 0 then
+      AirliteRemote(0).RemoteCue(actAir, alaDeactivate);
+  end;
-The first button (1A) ha