This list gives an overview over the mixing consoles that are supported for faderstart, remote control etc. It also gives some configuration hints for some models.
Note that even if your console is not supported directly, it might still be possible to use some sort of generic (USB) remote device to interface between the fader start function of the console and mAirList.
Important: Interfaces listed here are not available in all mAirList editions. Please check the feature matrix to see which interfaces are actually supported by your particular mAirList license/edition.
Status: supported
TCP/IP or serial port connection via DHD External Control Protocol (ECP).
From DHD Firmware 8.x, Ember+ protocol can be used simultaneously for additional functionality, e.g. setting Global Labels from a script.
Status: supported
Compatible with Series 52 for the most part. Availability of TCP/IP depends on the core module version. For older cores use serial port instead.
Status: limited support
Serial port only. Uses a subset of the RM4200D/52 packets, with a slightly different serial protocol. Set correct console type in DHD remote control configuration.
Status: limited support, since v6.1.5
Uses an entirely different protocol than the other DHD products. Faderstart and PFL control supported.
All supported Lawo (hardware) consoles use the SAS protocol (sometimes called “RAS protocol” or “diamond protocol”) via serial port or via TCP/IP. JADE Studio uses Ember+ protocol.
Status: supported
Status: supported
Status: supported
Status: supported
Not a hardware mixing console but a software solution. Provides 8 GPIOs over Ember+.
Status: Supported from mAirList 5.1 build 2703
Note: libember_slim.dll is packaged with mAirList but requires Visual C++ 2013 runtimes: http://www.microsoft.com/de-de/download/details.aspx?id=40784
Status: supported, since v6.1
Status: supported, since v5.0
Status: supported
Status: supported
Status: remote control not supported
USB connection is only for audio; separate USB interface required for fader start.
Status: remote control not supported
Does not support SAS protocol.
Status: supported
Uses SAS over serial port.
Status: supported (tbc)
Uses SAS over TCP/IP or serial port.
Status: supported
Uses SAS over serial port.
Status: supported (tbc)
Uses SAS over TCP/IP or serial port.
Status: supported (tbc)
Uses SAS over TCP/IP or serial port.
Status: not supported
Has no remote control over TCP or serial or USB at all. Only physical GPIO and Web.
Status: supported
Uses the Axia TCP/IP Direct Interface on localhost port 93.
Status: supported, since v5.1