config:remotecontrol:airlite
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
config:remotecontrol:airlite [2016/08/31 13:55] – [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 |
- | This article describes the remote control interface for the [[http:// | + | This article describes the remote control interface for the [[http:// |
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 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 ===== | ===== Audio Setup ===== | ||
Line 9: | Line 13: | ||
The audio setup is not exactly part of the remote control configuration, | The audio setup is not exactly part of the remote control configuration, | ||
- | The AIRLITE has four USB channels/ | + | The AIRLITE has four USB channels/ |
- | + | ||
- | 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 | + | 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", |
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! | 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 (" | 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 (" | ||
- | 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 " | + | 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/ |
It is recommended that you use WASAPI instead of DirectSound, | It is recommended that you use WASAPI instead of DirectSound, | ||
Line 27: | Line 29: | ||
===== Configuration ===== | ===== Configuration ===== | ||
- | The AIRLITE software must be installed on your computer before you can start with the remote control configuration. | + | The AIRLITE/ |
- | 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 ==== | ==== Players ==== | ||
Line 45: | Line 48: | ||
==== Cartwall ==== | ==== Cartwall ==== | ||
- | The AIRLITE has 16 buttons, in two rows (labeled " | + | The AIRLITE has 16 buttons |
{{ : | {{ : | ||
Line 61: | Line 64: | ||
==== Advanced ==== | ==== Advanced ==== | ||
- | On the // | + | On the // |
===== Scripting ===== | ===== 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/ |
function AirliteRemote(iIndex: | function AirliteRemote(iIndex: | ||
+ | |||
+ | Note: Name of the function is always '' | ||
| | ||
- | Remotes are 0-based, so '' | + | Remotes are 0-based, so '' |
| | ||
- | At the time b | + | Up to mAirList 6.2, the '' |
procedure SetLED(iNumber: | procedure SetLED(iNumber: | ||
procedure SetLEDBlink(iNumber: | procedure SetLEDBlink(iNumber: | ||
+ | |||
+ | 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: | ||
+ | |||
+ | * " | ||
+ | * " | ||
+ | * 255 (hex '' | ||
+ | |||
+ | And for WEBSTATION, given the lower number of butttons: | ||
+ | |||
+ | * " | ||
+ | * " | ||
+ | * 255 (hex '' | ||
+ | |||
+ | The available color values are: | ||
+ | |||
+ | * '' | ||
+ | * '' | ||
+ | * '' | ||
+ | |||
+ | The available blink speed values are: | ||
+ | |||
+ | * '' | ||
+ | * '' | ||
+ | * '' | ||
+ | |||
+ | Starting with mAirList 6.3, access to the following low level remote functions is possible through the '' | ||
+ | |||
+ | function RemoteOn(iModule: | ||
+ | function RemoteCue(iCueType: | ||
+ | function RemoteCueReset: | ||
+ | function RemoteAutoCueAnnouncer(iAction: | ||
+ | function RemoteAutoCueCRM(iAction: | ||
+ | function RemoteNonStop(iAction: | ||
+ | function RemoteComm(iModule: | ||
+ | function RemoteCough(iModule: | ||
+ | function RemoteVT(iModule: | ||
+ | |||
+ | Possible values for '' | ||
+ | |||
+ | * '' | ||
+ | * '' | ||
+ | * '' | ||
+ | * '' | ||
+ | * '' | ||
+ | * '' | ||
+ | * '' | ||
+ | * '' | ||
+ | * '' | ||
+ | |||
+ | Possible values for '' | ||
+ | |||
+ | * '' | ||
+ | * '' | ||
+ | * '' | ||
+ | * '' | ||
+ | * '' | ||
+ | * '' | ||
+ | * '' | ||
+ | * '' | ||
+ | * '' | ||
+ | * '' | ||
+ | * '' | ||
+ | * '' | ||
+ | |||
+ | Possible values for '' | ||
+ | |||
+ | * '' | ||
+ | * '' | ||
+ | * '' | ||
+ | |||
+ | ==== Example ==== | ||
+ | |||
+ | Switch on //Cue// over AIR input when Extra-PFL is launched: | ||
+ | |||
+ | procedure OnExtPFLOn(Item: | ||
+ | begin | ||
+ | if ExtPFLCount <> 0 then | ||
+ | AirliteRemote(0).RemoteCue(actAir, | ||
+ | end; | ||
+ | |||
+ | … and turn off when Extra-PFL is closed: | ||
+ | |||
+ | procedure OnExtPFLOff(Item: | ||
+ | begin | ||
+ | if ExtPFLCount = 0 then | ||
+ | AirliteRemote(0).RemoteCue(actAir, | ||
+ | end; | ||
+ | |||
+ | |||
+ | |||
config/remotecontrol/airlite.1472651701.txt.gz · Last modified: 2019/07/09 16:18 (external edit)