This is the multi-page printable view of this section. Click here to print.

Return to the regular view of this page.

Remote Control

mAirList can be controlled by a wide range of external hardware and software: keyboards, MIDI controllers, USB devices, mixing consoles, network clients, and more. Each of these is set up as a remote control interface on this configuration page.

Most remote control interfaces translate incoming events (a key press, a MIDI message, a GPIO input, a fader being opened) into remote control commands, e.g. PLAYER 1-1 START. Interfaces for mixing consoles usually also work the other way round, and send the state of mAirList (e.g. “player is playing”) back to the console, e.g. to light up buttons.

This page is also available in the live configuration (mAirList Control Panel).

Managing Remote Control Interfaces

The list shows all configured remote control interfaces. The following functions are available from the toolbar:

  • Add…: Add a new remote control interface. A menu will pop up, with the available interface types grouped by category (manufacturer), and the configuration dialog of the new interface will be opened.
  • Configure: Open the configuration dialog of the selected interface. You can also double-click the entry in the list.
  • Remove: Remove the selected interface from the configuration.
  • Export: Save the selected interface(s) to an .ini file.
  • Import: Add the interface(s) from a previously exported .ini file to the list.

You can set up any number of interfaces, also more than one of the same type, e.g. when you have two MIDI controllers connected.

Players Tab

Interfaces for mixing consoles and similar devices often have a Players tab in their configuration dialog. It contains a row of tabs for each playlist, and a row of tabs for each player of the selected playlist. On these tabs, you can assign console channels, faders or GPIOs to each player (e.g. for fader start or ON AIR lamps), without having to enter raw commands. The Players tab is only displayed when at least one playlist is configured.

The interface types are described in detail on the following pages.

1 - Generic

This section covers the generic remote control interfaces that are not tied to a particular manufacturer: keyboard hotkeys, MIDI, and serial ports.

1.1 - Hotkey Remote Control

This article covers the configuration of hotkeys for the remote control of mAirList.

Local and Global (System-Wide) Hotkeys

mAirList supports two kinds of hotkeys, represented by two distinct remote control interfaces:

  • Local: Hotkeys only work when mAirList application is in the foreground and focused.
  • System-wide: Hotkeys work regardless of whether the mAirList application is in the foreground or background. System-wide hotkeys are always routed to mAirList, so they cannot be used by any other application anymore.

As a thumb rule, use system-wide hotkeys only for very special shortcuts (e.g. Alt+Ctrl+F1) that are not used in any other software. System-wide hotkeys are often used with programmable POS keyboards.

Configuration

In the configuration app or Control Panel, go to Remote Control and add an interface of the desired type (local or system-wide hotkeys).

To add a new shortcut, click the Shortcut field first, then press the desired key or key combination. It will appear in the Shortcut field. Click Add to add it to the list of hotkeys in the upper part of the dialog.

To assign a remote control command to the shortcut, select it from the drop down menu, or type it manually in the table cell next to the shortcut.

1.2 - MIDI

The MIDI remote control lets you control mAirList with any MIDI device, e.g. a MIDI keyboard or a DJ controller. Incoming MIDI messages are mapped to remote control commands.

Configuration

In the configuration app or Control Panel, go to Remote Control and add an interface of type MIDI (Generic category).

General

On the General tab, select the MIDI input Device that mAirList should listen to.

The Monitor helps you to find out which messages your MIDI device sends. Check Enable Monitor, then press a button or move a fader on your device. The received messages will be displayed in the list, with their status/channel byte, Data1 and Data2 values (decimal and hexadecimal). Double-click a message to add it to the command list.

Commands

The Commands tab contains the list of MIDI messages that mAirList will react to, along with the command to execute. Use the toolbar to add, edit, or remove entries.

Each entry consists of the following settings:

  • Status/Channel: The MIDI status byte, which contains both the message type and the MIDI channel, e.g. 144 (90 hex) for a Note On message on channel 1.
  • Data1: The first data byte, e.g. the note or controller number.
  • Data2 Condition and Data2 Value: A condition for the second data byte (e.g. the velocity or controller value). Choose one of =, !=, <, <=, >=, > to compare the received value against the Data2 Value, or * to match any value.
  • Command: The remote control command to execute when a matching message is received.

The variable $DATA2 in the command will be replaced by the actual Data2 value of the received message (0 to 127). This way, a single entry with the * condition can pass the position of a fader or rotary control on to a command.

SYSEX messages are not supported for commands.

Scripting

MIDI messages can also be processed by background scripts, using the OnMidiMessage and OnMidiSysex event handlers. Scripts can also send MIDI messages, e.g. to control the LEDs of a MIDI controller: Open the output device with MidiOutOpen, then use MidiOut and MidiOutSysEx to send messages. MidiOutListDevices writes the list of available output devices to the System Log.

1.3 - Serial Port

The serial port remote control allows you to receive raw remote control commands over a serial port.

Configuration

Before you can set up this remote control, you must first configure the serial port parameters (baud rate etc.) in the Miscellaneous section of the configuration.

Thereafter you can add the Serial Port remote control interface, and select the appropriate serial port from the list.

Usage

Commands - e.g. PLAYER 1-1 START - must be sent as plain ASCII text, terminated with a CR character (ASCII 13) each.

1.4 - Art-Net DMX

The Art-Net DMX interface lets mAirList control lighting equipment (e.g. ON AIR lights, studio lighting, or LED effects) via Art-Net, the protocol for transmitting DMX over the network. Unlike most other remote control interfaces, it does not receive commands from an external device, but sends DMX values, triggered by remote control commands.

Configuration

In the configuration app or Control Panel, go to Remote Control and add an interface of type Art-Net DMX (Generic category).

  • Broadcast Address and Port: The IP or broadcast address that the Art-Net packets are sent to, e.g. the address of the Art-Net node, or the broadcast address of the network. The default is the standard Art-Net broadcast address 2.255.255.255, port 6454.
  • Bind IP: The local IP address to send from, i.e. the network interface to use. Leave empty to let Windows choose.
  • Remote Control ID: The prefix of the commands that are handled by this interface. The default is ARTNET. Use different IDs if you set up more than one Art-Net interface.

Commands

The following commands are available (assuming the default ID ARTNET):

  • ARTNET SET <universe> <channel> <value>: Sets a DMX channel (1 to 512) of the specified universe to a value (0 to 255).
  • ARTNET FADE <universe> <channel> <from> <to> <duration>: Fades a DMX channel from one value to another, over the specified duration in milliseconds.

Example: ARTNET FADE 0 1 0 255 2000 fades channel 1 of universe 0 from 0 to full brightness within two seconds.

The commands can be used anywhere commands are accepted, e.g. in actions, event scheduler entries, or the commands of other remote control interfaces.

2 - USB

This section covers remote control interfaces for USB devices: game controllers (joysticks/gamepads), and the IO-Warrior and Velleman K8055 I/O boards, which provide digital inputs and outputs, e.g. for GPIO connections to a mixing console.

2.1 - Joystick

The Joystick/Gamepad remote control lets you trigger remote control commands with the buttons of any game controller recognized by Windows.

This is not limited to actual joysticks: Many USB button boxes and encoder interfaces (often sold for arcade machines or flight simulators) register as game controllers, and are an inexpensive way to build custom button panels.

Configuration

In the configuration app or Control Panel, go to Remote Control and add an interface of type Joystick/Gamepad (USB category).

On the General tab, select the Device from the list of game controllers, or (First available device) to use the first one found.

In the table below, you can enter a command for each button, separately for when the button is Pressed and when it is Released. Click a cell to edit the command. Leave the cell empty if no command should be executed.

2.2 - IO-Warrior

The IO-Warrior is a family of USB I/O boards by Code Mercenaries, which provide a number of digital I/O pins. mAirList supports the IO-Warrior 24, 28, 28L, 40, 56 and 100.

Each pin can be used as an input, to trigger remote control commands, or as an output, controlled by a script.

Configuration

In the configuration app or Control Panel, go to Remote Control and add an interface of type IO-Warrior (USB category).

Device

On the Device tab, click Select Device… and choose your IO-Warrior from the list of connected devices. This will fill in the Vendor/Product ID, Serial Number and Path fields.

When a Path is set, mAirList will open exactly this device (i.e. the device connected to this particular USB port). Clear the Path field to identify the device by its vendor/product ID and serial number instead, so it is still found when plugged into a different USB port.

Commands

The Commands tab lists all pins of the device. The pins are named P<port>.<bit>, e.g. P0.3 for bit 3 of port 0, followed by a consecutive number in parentheses.

For each pin, enter the command to execute when the input goes On and Off, respectively. Click a cell to edit the command.

The inputs are active-low: A pin is considered On when it is connected to ground (e.g. through a switch or relay contact), and Off otherwise.

Outputs

The pins can also be used as outputs, e.g. to drive an LED or a relay, from a background script:

IOWarriorRemote(0).SetPin(3, true);

The first parameter of IOWarriorRemote is the index of the IO-Warrior interface (0 for the first one, if you have more than one configured). The first parameter of SetPin is the pin number, counted from 0 (P0.0 = 0, P1.0 = 8, etc.); the second parameter switches the output on (pulled to ground) or off. While a pin is switched on as an output, it will not trigger any input commands.

2.3 - Velleman K8055

The Velleman K8055 (and its successor, the K8055N) is a USB experiment board with five digital inputs, eight digital outputs, and two analog inputs and outputs. mAirList can use the digital inputs to trigger remote control commands, and set the outputs from a script.

The required driver library (K8055D.dll) is included with mAirList.

Configuration

In the configuration app or Control Panel, go to Remote Control and add an interface of type Velleman K8055/K8055N (USB category).

Device

  • Device address: The address of the board (0 to 3), as set with the jumpers on the board. This allows you to use up to four boards on the same computer.
  • Update interval: How often (in milliseconds) mAirList polls the board for changes of the inputs. The default is 50 ms.

Commands

On the Commands tab, enter the command to execute for each of the five digital inputs when it goes ON, and when it goes OFF.

Outputs

The outputs can be controlled from a background script through the following methods:

K8055Remote(0).SetDigitalChannel(1);       // switch on digital output 1
K8055Remote(0).ClearDigitalChannel(1);     // switch off digital output 1
K8055Remote(0).ClearAllDigital;            // switch off all digital outputs
K8055Remote(0).OutputAnalogChannel(1, 255); // set analog output 1 (0..255)

The parameter of K8055Remote is the index of the K8055 interface (0 for the first one, if you have more than one configured). The current state of the inputs can be read with ReadDigitalChannel and ReadAllDigital.

2.4 - Elgato Stream Deck

mAirList can be controlled with an Elgato Stream Deck. The buttons can execute remote control commands, or trigger cart players, with the button color indicating the state of the cart player.

The integration consists of two parts: a remote control interface in mAirList, and a plugin for the Stream Deck software, which connects to mAirList.

Configuration

In the configuration app or Control Panel, go to Remote Control and add an interface of type Elgato Stream Deck (USB category).

Install the Stream Deck software from Elgato, then click Click here to install the plugin in the configuration dialog to install the mAirList plugin.

Advanced Settings:

  • HTTP Port: The port that the plugin connects to. The default is 10810.
  • Allow connections from other computers: By default, only the Stream Deck software on the same computer can connect. Check this option to allow connections over the network, e.g. when the Stream Deck is connected to a different computer.

Stream Deck Actions

In the Stream Deck software, the plugin provides the following actions:

  • Cart Player: Triggers a cart player (enter the Cart Number). The button shows the number of the cart player, colored green when an item is loaded and red while it is playing. By default, the button is only active when the cartwall is ON AIR (or in PFL or voice tracking mode); check Enable button when OFF AIR to change this.
  • Execute Command: Executes the entered Command when the button is pressed.

If mAirList runs on a different computer, or uses a different port, enter the Host/IP and Port in the plugin settings.

3 - Lawo/Studer

This section covers the integration with Lawo and Studer mixing consoles through the SAS protocol. For Lawo consoles with Ember+ support, see also the Ember+ section.

3.1 - SAS

The SAS remote connects mAirList to Lawo and Studer consoles (e.g. Lawo Zirkon, Crystal, and Studer OnAir series) through the SAS automation protocol.

mAirList identifies the console channels by their source names: When a source is selected on a fader, the console reports the source name, and mAirList knows which player is on which fader. Fader start, PFL, and GPIs of the console can then be used to control mAirList.

Configuration

In the configuration app or Control Panel, go to Remote Control and add an interface of the desired type (Lawo/Studer category):

  • SAS (TCP/IP): Connection via network. Enter the Host name or IP of the console/SAS interface, and the Port (default 18512).
  • SAS (serial port): Connection via a serial port. Select the COM Port. The port parameters (baud rate etc.) must be set up in the Serial Ports section of the configuration first.

The connection settings are found on the Communication tab.

Players

On the Players tab, select the playlist and player, and enter the Source name of the console source that the player is connected to. Leave empty to disable the assignment for that player.

When the fader of that source is opened (fader start), the player is started; when it is closed, the player is stopped.

Options:

  • Automatic PFL switch: The PFL button of the fader switches the PFL of the player on and off.
  • Use PAUSE/STOP: When the fader is closed, the player is paused rather than stopped (PAUSE/STOP command, i.e. the player is stopped if it is already paused).

Cartwall

Enter the Source name of the cartwall source. When its fader is opened, the cartwall is switched to ON AIR mode, and back to OFF AIR mode when the fader is closed. PFL on that fader switches the cartwall to PFL mode.

The options determine what mAirList does on the console when the cartwall mode changes in mAirList:

  • Open fader when cartwall goes ON
  • Turn channel on when cartwall goes ON (Studer)
  • Close fader when cartwall goes OFF
  • Turn channel off when cartwall goes OFF (Studer)

Voice Tracking

Enter the source names used for voice tracking: Player A, Player B, and Microphone. Opening the fader of the player sources starts the respective voice tracking player; opening the microphone fader starts the voice track recording. The fader levels of the player sources are applied to the volume of the voice tracking players.

Other Sources

Enter the names of further console sources (one per line) that are not bound to a player, but which you want to control with SAS actions or from scripts.

GPI

The GPI tab lists the GPIs of the console. For each GPI, you can enter the remote control command to execute when it goes On and Off.

Monitor

The Monitor tab displays the communication with the console, which is helpful for troubleshooting.

Actions

The following actions (SAS category) are available, e.g. for use in event scheduler or cartwall actions: Set fader level, Set fader input gain, Turn on/off fader start button light, Turn on/off PFL, and Turn on/off GPI.

4 - Barth

This section covers the integration with mixing consoles by Barth.

4.1 - D.MAX

The D.MAX remote connects mAirList to a Barth D.MAX mixing console via a serial port. mAirList receives the state of the fader start (GO), PFL, NEXT and OPT keys, as well as the fader levels, and executes the configured remote control commands.

Configuration

In the configuration app or Control Panel, go to Remote Control and add an interface of type D.MAX (Barth category).

Select the COM Port that the console is connected to. The port parameters (baud rate etc.) must be set up in the Serial Ports section of the configuration first.

Commands

The commands are assigned to the console inputs (1 to 32), not to the fader numbers. mAirList keeps track of which input is currently routed to which fader, so the commands follow the source when it is assigned to a different fader.

There is a separate tab for each key type: Fader (fader start), PFL, Next, and OPT. For each input, enter the command to execute when the key goes ON and OFF.

A fader start only triggers the Fader command when the GO key is active and the fader is open; closing the fader or releasing the GO key triggers the OFF command.

Volume

On the Volume tab, you can enter a command for each input that is executed whenever its fader level changes. The following variables can be used:

  • $VALUE – the raw fader value as sent by the console,
  • $DB – the fader level in dB.

Example: PLAYER 1-1 VOLUME $DB

5 - DHD

mAirList supports DHD mixing consoles and audio cores through three interface types:

  • DHD ECP for Series 52 cores and the RM4200D/RM3200D, using the External Control Protocol via TCP/IP or serial port.
  • DHD Control API for DHD cores with firmware 10.3 or newer, using the JSON/WebSocket-based Control API.
  • DHD RM2200D for the older RM2200D console.

5.1 - DHD ECP (Series 52, RM4200D, RM3200D)

This interface connects mAirList to DHD Series 52, RM4200D and RM3200D consoles through the DHD External Control Protocol (ECP). It supports fader start, PFL, channel on/off switching, motorized faders, and the exchange of logic states in both directions.

Configuration

In the configuration app or Control Panel, go to Remote Control and add an interface of type DHD ECP (Series 52, RM4200D, RM3200D) (DHD category).

General

  • Communication: Select either TCP/IP, and enter the Hostname or IP and Port (default 2008) of the DHD core, or select the Serial Port that the core is connected to.
  • Console/Core Type and Firmware Version: Select Firmware 7.x or newer, Firmware 6.x, Firmware 5.x, or RM3200D.
  • Fader Level Notifications: Determines whether the core should report fader level changes to mAirList, either Channel-based or Fader-based, or Off.

Toolbox Import

For easier configuration, export the Audio IDs, Logic IDs and Fader Channels from DHD Toolbox to an “Ext. DHD AudioID/LogicID Export” (*.dpx) or XML Export (*.xp5) file, and click Import Toolbox Data to import that file.

The imported data is displayed on the Logic IDs, Audio IDs and Fader Channels tabs. It allows you to select logics and fader channels by name in the rest of the dialog (the … and Select Fader Channel… buttons), rather than entering numeric IDs.

Players

On the Players tab, select the playlist and player, and set up the assignment:

  • Automatic Setup: Click Select Fader Channel… to choose the fader channel the player is connected to from the imported Toolbox data. This will fill in the fields below.
  • FaderStart logic or fader number: The logic ID of the fader start, or alternatively, a fixed fader number.
  • Fader channel number: The fader channel (used for channel on/off switching, motorized faders, and channel labels).
  • PFL logic: The logic ID for the PFL of the channel.

In the State Indication Logics table, you can enter logic IDs that are set by mAirList to indicate the state of the player (e.g. to light up buttons on the console).

Options:

  • Automatic PFL switch: The PFL of the channel switches the PFL of the player on and off.
  • Use PAUSE/STOP: When the fader is closed, the player is paused rather than stopped.
  • Keep channel on when player is paused
  • Disable channel on/off switching: By default, mAirList switches the console channel on and off along with the player. Check this option to disable this.
  • Enable motorized fader control: Moves the motorized fader along with the player state.
  • Set channel label to item title: Displays the title of the loaded item in the channel display of the console.

Cartwall

The Cartwall Fader settings work the same as for the players (see above). When the cartwall fader is opened, the cartwall goes ON AIR.

In the Player Logic IDs table, you can assign logic IDs to the individual cartwall players, to start them from the console, and to indicate their state.

The options Disable channel on/off switching and Enable motorized fader control are also available for the cartwall.

Voice Tracking

Set up the fader assignment (fader start logic or fixed fader number, or fader channel number with firmware 6.x and up) for the voice tracking Player A, Player B, and Mic channels.

Logic

On the States tab, you can link global mAirList states to DHD logics. For each of the states ON AIR, PFL active, ExtPFL active, AUTOMATION 1 active, and VT active:

  • Logic: The logic that is updated when the state changes in mAirList, and/or changes the state in mAirList when it changes on the console.
  • Outgoing Logic: An optional separate logic that is only set by mAirList.
  • Console is master (request current state at startup): When mAirList connects, the current state of the logic is retrieved from the console and applied to mAirList, rather than the other way round.
  • Invert: Inverts the logic state.

On the Commands tab, you can enter remote control commands to execute when a logic (identified by its address) goes On and Off.

Monitor

The Monitor tab displays the communication with the core, which is helpful for troubleshooting.

Actions

The following actions (DHD category) are available: Set Logic, Set PFL, Set all PFL off, and Set Fader On/Off.

5.2 - DHD RM2200D

This interface connects mAirList to a DHD RM2200D console via TCP/IP. It supports fader start and PFL for players, the cartwall, and voice tracking, as well as commands for the console buttons.

Configuration

In the configuration app or Control Panel, go to Remote Control and add an interface of type DHD RM2200D (DHD category).

On the Connection tab, enter the Host name or IP and the Port (default 2200) of the console.

Players

On the Players tab, select the playlist and player, and enter either the Fixed fader number or the Audio Source ID that the player is connected to. When an audio source ID is used, mAirList follows the source when it is assigned to a different fader.

Options:

  • Automatic PFL switch: The PFL of the channel switches the PFL of the player on and off.
  • Use PAUSE/STOP: When the fader is closed, the player is paused rather than stopped.

Cartwall

Enter the Fixed fader number or Audio Source ID of the cartwall fader. In the Player Logic IDs table, you can assign logic IDs to the individual cartwall players.

Voice Tracking

Enter the Fixed fader number or Audio Source ID for the voice tracking Player A, Player B, and Mic channels.

Buttons

On the Buttons tab, you can enter remote control commands to execute when a button of the console is pressed (On) and released (Off).

Monitor

The Monitor tab displays the communication with the console, which is helpful for troubleshooting.

5.3 - DHD Control API

This interface connects mAirList to DHD audio cores through the DHD Control API, a JSON-based protocol over WebSocket, which is available from DHD firmware 10.3 onwards. It offers the same functions as the ECP interface (fader start, PFL, channel on/off, motorized faders, logic exchange), and additionally supports external button lists for the cartwall.

Configuration

In the configuration app or Control Panel, go to Remote Control and add an interface of type DHD Control API (DHD category).

General

  • Core Communication: Enter the URL of the core, e.g. http://192.168.1.100, and the API Token configured on the core. mAirList connects to the WebSocket endpoint (/api/ws) of the core automatically; an https:// URL results in an encrypted connection.
  • Number of Faders of Virtual Mixers: Click Retrieve to read the virtual mixers and their number of faders from the core. This information is required to select fader channels in the rest of the dialog.

Players

On the Players tab, select the playlist and player, and set up the assignment:

  • Automatic Setup: Click Select Fader Channel… to choose the fader channel the player is connected to.
  • Mixer and Fader channel number, or fader number: The virtual mixer and the fader channel (or alternatively, a fixed fader number) that the player is assigned to.

The State Indication Logics and the Options are the same as for the ECP interface.

Cartwall

The Cartwall Fader settings, Player Logic IDs and Options work the same as for the ECP interface.

External Button List for Cart Players: Enter the List ID of an external button list configured on the core. mAirList will fill the list with one entry per cart player, showing its number and title, colored green when an item is loaded and red while it is playing. Pressing an entry on the console triggers the cart player. Set to 0 to disable this feature.

Voice Tracking

Set up the fader assignment (mixer and fader channel number, or a fixed fader number) for the voice tracking Player A, Player B, and Mic channels.

Logic

On the States tab, you can link the global mAirList states (ON AIR, PFL active, ExtPFL active, AUTOMATION 1 active, VT active) to DHD logics, with the options Console is master and Invert, the same as for the ECP interface.

On the Commands tab, you can enter remote control commands to execute when a logic (identified by its address) goes On and Off.

6 - Network

This section covers the remote control interfaces that work over the network (TCP/IP or UDP). They allow other software, scripts, or devices to send remote control commands to mAirList, or to query its status.

  • The REST interface is an HTTP(S) server with user authentication, and the recommended choice for new integrations.
  • The TCP Server, TCP Client and UDP Server interfaces receive plain text commands, one per line or packet.
  • The JSON Server and JSON Client interfaces exchange JSON data, which is processed by background scripts.

6.1 - REST

The REST remote (REST Remote Access) is a built-in HTTP/HTTPS server, through which other software can execute remote control commands and query the status of mAirList. All requests require authentication with a username and password, or a token.

Configuration

In the configuration app or Control Panel, go to Remote Control and add an interface of type REST Remote Access (Network category).

General

  • Server Settings: Select the Mode (HTTP only, HTTPS only, or HTTP and HTTPS), and the HTTP Port (default 9300) and HTTPS Port (default 9301).
  • SSL Certificate Files: For HTTPS, select the Certificate and Key files (PEM format), and an optional Root Certificate.
  • User Management: Select where the user accounts are stored: either in the local configuration (Local configuration (auth.db file)), or in one of the configured mAirListDB databases. Click Manage Users… to add or edit users. When a database is selected, you must first sign in with a database user with administrator level.

In the user management dialog, you can set up users and groups, and set their passwords. For each user or group, the permissions determine which functions of the REST interface they may access, e.g. Command execution, General status (read-only), Playlist read access, Encoder status, or File Server.

File Server

The REST server can also serve static files, e.g. a custom web interface that uses the REST API.

  • Enable File Server: Turns on the file server.
  • URL Prefix: The path under which the files are available, e.g. www.
  • Document Root: The local folder that contains the files.
  • Allow unauthenticated access: If checked, the files can be retrieved without signing in.

Authentication

Clients authenticate using HTTP Basic authentication (username and password), or with a token (Authorization: Bearer ... header). Tokens can be obtained through the /auth endpoint.

Endpoints

The following endpoints are available. Numbers in the path (e.g. the playlist number) are counted from 0.

MethodPathDescription
GET, POST/executeExecute a remote control command, passed as parameter command.
POST/actionsExecute an action list, passed as request body. Optional parameters: playlist, timeoffset.
GET/status/onairReturns the current ON AIR status (true or false).
GET/runtimedata/<name>Returns the value of a runtime data variable.
GET/logic/<name>Returns the value of an internal logic state.
GET/playlist/<n>/contentReturns the content of playlist n as JSON.
GET/playlist/<n>/content.xmlReturns the content of playlist n as XML.
POST/log/startLog the start of an item, passed as JSON body (item, id, optional region).
POST/log/stopLog the stop of an item, passed as JSON body (item, id, optional region and duration).
GET/encoder/summaryReturns the status of the encoder and all connections.
GET/encoder/connectedReturns the connection state of the encoder.
GET/encoder/listenersReturns the total number of current listeners.
GET/encoder/silenceReturns the number of seconds the audio level has been below the silence threshold.
POST/encoder/streamtitleUpdates the stream title on all encoder connections, passed as parameter title.
GET/encoder/connection/<n>/summaryReturns the status of an encoder connection.
GET/encoder/connection/<n>/nameReturns the name of an encoder connection.
GET/encoder/connection/<n>/enabledReturns whether an encoder connection is enabled.
GET/encoder/connection/<n>/connectedReturns whether an encoder connection is established.
GET/encoder/connection/<n>/listenersReturns the number of listeners on an encoder connection.
GET/streammonitor/summaryReturns the status of the StreamMonitor and all streams.

Example, using curl:

curl -u user:password -d "command=PLAYER 1-1 START" http://localhost:9300/execute

Further endpoints can be implemented in a background script with the OnRESTRequest event handler.

6.2 - TCP Server

The TCP Server remote opens a TCP port that other software can connect to and send remote control commands, e.g. from a telnet client, a script, or a home automation system.

Configuration

In the configuration app or Control Panel, go to Remote Control and add an interface of type TCP Server (Network category).

  • Bind IP: The local IP address(es) to listen on, separated by commas. Leave empty to listen on all network interfaces.
  • Port: The TCP port to listen on. The default is 9302.
  • Password: If set, clients must authenticate before they can send commands (see below).
  • Command prefix: If set, only lines starting with this prefix (followed by a space) are executed, and the prefix is removed before execution. All other lines are ignored.

Usage

Send one command per line, terminated by CR/LF, e.g.:

PLAYER 1-1 START

If a password is set, the first line must be AUTH <password>. mAirList replies with AUTH OK if the password is correct, or AUTH REQUIRED otherwise. Until the client is authenticated, all other lines are rejected with AUTH REQUIRED.

Multiple clients can be connected at the same time. Connections and disconnections are recorded in the System Log.

A script can send data to all connected clients using the SendString and WriteLine methods of the interface, available through TCPServerRemote(<index>).

6.3 - TCP Client

The TCP Client remote is the counterpart of the TCP Server: mAirList connects to a TCP server, and executes each line received from that server as a remote control command.

This is useful when the device or software sending the commands can only act as a server, or to connect two mAirList instances (with a TCP Server remote on the other instance).

Configuration

In the configuration app or Control Panel, go to Remote Control and add an interface of type TCP Client (Network category).

  • Host name or IP and Port: The address of the TCP server to connect to. The default port is 9303.
  • Password: If set, mAirList sends AUTH <password> to the server after connecting. Use this when connecting to the TCP Server remote of another mAirList instance.
  • Command prefix: If set, only lines starting with this prefix (followed by a space) are executed, and the prefix is removed before execution. All other lines are ignored.
  • Dummy mode: If checked, all incoming data is discarded and no commands are executed. Use this option when the connection is only used to send data from a script.

mAirList connects automatically when the interface is started, and tries to reconnect every few seconds if the connection is lost or cannot be established.

Scripting

A script can send data to the server using the SendString and WriteLine methods of the interface, available through TCPClientRemote(<index>).

For sending a one-off string to a TCP server without setting up a remote control interface, scripts can use the TCPSendString(Server, Port, Text) procedure.

6.4 - UDP Server

The UDP Server remote receives remote control commands as UDP packets. Unlike TCP, no connection needs to be established, which makes UDP a good choice for devices that send short, single messages, e.g. GPIO-to-network converters or broadcast consoles with “UDP trigger” functions.

Configuration

In the configuration app or Control Panel, go to Remote Control and add an interface of type UDP Server (Network category).

  • Bind IP: The local IP address(es) to listen on, separated by commas. Leave empty to listen on all network interfaces.
  • Port: The UDP port to listen on. The default is 9303.

Usage

Each UDP packet must contain exactly one command, as UTF-8 encoded text, e.g. PLAYER 1-1 START. There is no authentication, and no reply is sent.

Scripts can send UDP packets with the UDPSendString(Server, Port, Text) procedure, e.g. to control another mAirList instance.

6.5 - JSON Server

The JSON Server remote opens a TCP port through which clients can exchange JSON messages with mAirList. Unlike the TCP Server, the received data is not executed as commands. Instead, it is passed to background scripts, which can process it and send replies. This makes it possible to implement custom protocols.

Configuration

In the configuration app or Control Panel, go to Remote Control and add an interface of type JSON Server (Network category).

  • Bind IP: The local IP address(es) to listen on, separated by commas. Leave empty to listen on all network interfaces.
  • Port: The TCP port to listen on. The default is 9303.

Protocol

Each message is a JSON document, encoded as UTF-8 and terminated by a null byte (ASCII 0). Messages that are not valid JSON are ignored.

Scripting

The following event handlers are available in background scripts:

procedure OnJSONServerRemoteClientConnect(Remote: IJSONServerRemote; ClientID: cardinal);
procedure OnJSONServerRemoteClientDisconnect(Remote: IJSONServerRemote; ClientID: cardinal);
procedure OnJSONServerRemoteClientData(Remote: IJSONServerRemote; ClientID: cardinal; Data: IPersistentStorage);
procedure OnJSONServerRemoteClientDataObject(Remote: IJSONServerRemote; ClientID: cardinal; Data: IPersistentObject);

OnJSONServerRemoteClientDataObject is only called when the received document is a JSON object (rather than an array or a single value).

To send data, use the following methods of the Remote object (or JSONServerRemote(<index>)):

  • SendTo(ClientID, Data) – send to a single client,
  • Broadcast(Data) – send to all connected clients,
  • BroadcastExcept(ClientID, Data) – send to all clients except the specified one.

6.6 - JSON Client

The JSON Client remote is the counterpart of the JSON Server: mAirList connects to a TCP server, and exchanges JSON messages with it. The received data is passed to background scripts for processing.

Configuration

In the configuration app or Control Panel, go to Remote Control and add an interface of type JSON Client (Network category).

Enter the Host name or IP and Port of the server to connect to. The default port is 9303.

mAirList connects automatically when the interface is started, and tries to reconnect every few seconds if the connection is lost or cannot be established.

Protocol

Each message is a JSON document, encoded as UTF-8 and terminated by a null byte (ASCII 0), the same as for the JSON Server.

Scripting

The following event handlers are available in background scripts:

procedure OnJSONClientRemoteConnect(Remote: IJSONClientRemote; ClientID: cardinal);
procedure OnJSONClientRemoteDisconnect(Remote: IJSONClientRemote; ClientID: cardinal);
procedure OnJSONClientRemoteData(Remote: IJSONClientRemote; Data: IPersistentStorage);
procedure OnJSONClientRemoteDataObject(Remote: IJSONClientRemote; Data: IPersistentObject);

OnJSONClientRemoteConnect and OnJSONClientRemoteDisconnect are called whenever the connection to the server is (re-)established or lost. Their ClientID parameter is always 0; it only exists for compatibility with the JSON Server event handlers.

OnJSONClientRemoteDataObject is only called when the received document is a JSON object.

To send data to the server, call Remote.Send(Data) (or JSONClientRemote(<index>).Send(Data)).

For sending a single JSON document to a server without setting up a remote control interface, scripts can use the JSONSendString(Server, Port, Data) procedure.

7 - Livewire

This section covers the integration with Livewire/Axia devices by Telos Alliance:

  • LWRP – GPIO control of Axia consoles and xNodes via the Livewire Routing Protocol.
  • Telos VX – control of Telos VX phone systems via the Livewire Control Protocol (LWCP).

7.1 - LWRP

The Axia GPIO TCP/IP Direct Interface (LWRP) connects mAirList to an Axia console or xNode via the Livewire Routing Protocol. It uses the virtual GPIO ports of the device, so no physical GPIO wiring is required.

Configuration

In the configuration app or Control Panel, go to Remote Control and add an interface of type Axia GPIO TCP/IP Direct Interface (LWRP) (Livewire category).

On the Connection tab, enter the Host name or IP of the device. The default port is 93 (LWRP).

Players

On the Players tab, select the playlist and player, and enter the GPIO Number (port 1 to 24) that is assigned to the console channel of that player.

mAirList uses the standard Axia GPIO pin assignment for console channels:

  • Pin 4 (channel ON) starts the player.
  • Pin 5 (channel OFF) stops the player.
  • Pin 3 (PFL) switches the PFL of the player, if Automatic PFL switch is enabled.

Options:

  • Automatic PFL switch: Pin 3 switches the PFL of the player on and off.
  • Use PAUSE/STOP: When the channel is switched off, the player is paused rather than stopped.

GPO Events

The GPO Events tab lists all GPIO ports and pins. For each pin, you can enter a remote control command to execute when the pin goes High and Low.

Actions

The Set GPI action (Livewire category) sets the state of the pins of a GPIO port. For each of the five pins, select H (high), L (low), or x (no change).

7.2 - Telos VX (LWCP)

This interface connects mAirList to a Telos VX broadcast phone system via the Livewire Control Protocol (LWCP). It allows scripts to monitor the state of the phone lines and to control calls, e.g. to build a custom call screener interface.

Configuration

In the configuration app or Control Panel, go to Remote Control and add an interface of type Telos VX LWCP (Livewire category).

  • Host name or IP and Port: The address of the VX engine. The default port is 20518.
  • Authentication: The User and Password for the VX engine.
  • Studio ID or name: The studio to select after logging in, either by its numeric ID or its name.

The Monitor tab displays the communication with the VX engine, which is helpful for troubleshooting.

Scripting

This interface does not execute any commands by itself. It is controlled by background scripts.

To control the phone lines, use the following methods of VXLWCPRemote(<index>):

  • CallNumber(Line, Number) – dial a number on a line,
  • TakeCall(Line) – take a call,
  • HoldCall(Line, Ready) – put a call on hold,
  • DropCall(Line) – drop a call,
  • SelectStudio(Value) – select a different studio.

Changes of the line states are reported through the following event handler:

procedure OnVXLineEvent(Remote: IVXLWCPRemote; Line, Hybrid: integer;
  Comment, State, CallState: string; Time, Cause: integer;
  Busy: boolean; RemoteNumber, CallerID, Direction: string);

In addition, all LWCP messages received from the VX engine (including line events) are passed to the OnLWCPCommand(Remote, Command, ObjectName, Data) event handler.

8 - Wheatstone

This section covers the integration with Wheatstone WheatNet-IP systems:

8.1 - WheatNet-IP Mixer

This interface connects mAirList to a WheatNet-IP mixing console (e.g. an LXE, Strata or GSX surface) via TCP/IP, and executes remote control commands when an input channel is switched on or off, or when its CUE is switched on or off.

Configuration

In the configuration app or Control Panel, go to Remote Control and add an interface of type WheatNet-IP Mixer (Wheatstone category).

On the Connection tab, enter the Host name or IP of the mixer engine, and the Port (default 55777).

On the Input Commands tab, enter the commands for each input (1 to 64) and function:

  • Channel On / Channel Off
  • CUE On / CUE Off

mAirList only subscribes to the events of those inputs and functions for which a command is configured.

8.2 - WheatNet-IP BLADE

This interface connects mAirList to a WheatNet-IP BLADE via TCP/IP, and uses the software logic I/Os (SLIOs) of the BLADE to exchange logic signals with the WheatNet-IP network.

Configuration

In the configuration app or Control Panel, go to Remote Control and add an interface of type WheatNet-IP BLADE (Wheatstone category).

On the Connection tab, enter the Host name or IP of the BLADE, and the Port (default 55776).

On the SLIO tab, enter the remote control commands to execute when an SLIO (1 to 192) goes ON and OFF.

Scripting

SLIOs can also be read and set from background scripts through WheatNetBladeRemote(<index>), using the methods SetSLIO(Index, State), GetSLIOState(Index), QuerySLIO(Index) and SubscribeSLIO(Index).

9 - AEQ

This section covers the integration with mixing consoles by AEQ.

9.1 - AEQ Virtual GPIO (Capitol IP, Forum IP)

AEQ Capitol IP and Forum IP consoles can send the state of their virtual GPIOs as UDP packets over the network. This interface receives these packets and executes remote control commands when a virtual GPI changes its state.

Configuration

In the configuration app or Control Panel, go to Remote Control and add an interface of type AEQ Virtual GPIO (Capitol IP, Forum IP) (AEQ category).

On the Connection tab, enter the Bind IP (leave empty to listen on all network interfaces) and the UDP Port (default 2001). Configure the console to send its virtual GPIO messages to the IP address of the mAirList computer and this port.

On the GPI tab, enter the command to execute when a virtual GPI (0 to 255) goes ON and OFF.

10 - D&R

This section covers the integration with mixing consoles by D&R:

  • AIRENCE – USB console with built-in control switches.
  • AIRLAB – connected via serial port.
  • AIRLITE and WEBSTATION – USB consoles, controlled through the AIRLITE Control/WEBSTATION Control software by D&R.
  • AURON – connected via TCP/IP.
  • AXITE/AXUM – connected via the MambaNet protocol.

Most of these interfaces support fader start and PFL for the players, using the cartwall with the control switches of the console (including colored button LEDs), and assigning remote control commands to buttons and switches.

10.1 - D&R AIRENCE

The D&R AIRENCE is a USB broadcast mixer with built-in control switches. mAirList communicates with it via USB, using the airence.dll driver library that is included with mAirList.

Configuration

In the configuration app or Control Panel, go to Remote Control and add an interface of type D&R AIRENCE (D&R category).

Players

On the Players tab, select the playlist and player, and choose the USB channel used by this player (USB 1 to USB 4, or none). Opening and closing the fader of that USB channel starts and stops the player.

Options:

  • Automatic PFL switch: The PFL (CUE) button of the channel switches the PFL of the player on and off.
  • Use PAUSE/STOP: When the fader is closed, the player is paused rather than stopped.

Cartwall

Check Use control switches for cartwall to control the cart players with the control switches of the AIRENCE, and select the Buttons to use for Cartwall: the “A” Buttons, the “B” Buttons, or both (numbered either top to bottom or left to right).

The Color Settings determine how the button LEDs indicate the state of each cart player: For each player state, select a Color (off, Red, Green, or Yellow), and optionally enable Blink with a second Blink Color and a Speed.

Switches

On the Switches tab, you can assign a command to each switch (1 to 39) for when it is switched On and Off. Switches used for the cartwall are not available here.

Advanced

  • Read timeout (ms): How long mAirList waits for data from the device in each read cycle.
  • Enable debug log file: Writes a log file of the communication, for troubleshooting.

10.2 - D&R AIRLAB

This interface connects mAirList to a D&R AIRLAB mixing console via a serial port. It executes remote control commands when channels are switched on or off, and when the ON AIR signals of the console change.

Configuration

In the configuration app or Control Panel, go to Remote Control and add an interface of type D&R AIRLAB (D&R category).

On the Communication tab, select the COM Port that the console is connected to. The port parameters (baud rate etc.) must be set up in the Serial Ports section of the configuration first.

On the Channels tab, enter the commands to execute when a channel is switched On and Off, e.g. PLAYER 1-1 START and PLAYER 1-1 STOP for fader start.

On the On Air tab, enter the commands to execute when one of the console’s ON AIR signals goes On and Off.

10.3 - D&R AIRLITE

The D&R AIRLITE is a USB broadcast mixer. mAirList does not communicate with the console directly, but through the AIRLITE Control software by D&R, using its UDP API.

The D&R WEBSTATION is configured in exactly the same way.

Configuration

In the configuration app or Control Panel, go to Remote Control and add an interface of type D&R AIRLITE (D&R category).

Players

On the Players tab, select the playlist and player, and choose the USB channel used by this player, i.e. the console module that the player’s audio is connected to (or none). Opening and closing the fader of that module starts and stops the player.

Options:

  • Automatic PFL switch: The CUE button of the module switches the PFL of the player on and off.
  • Use PAUSE/STOP: When the fader is closed, the player is paused rather than stopped.
  • Send track state: Sends the state of the player to the console, e.g. to light up the module buttons.
  • Disable remote control during voice tracking: The fader does not start or stop the player while voice tracking is active.
  • Disable remote control when channel is set to Line: The fader only controls the player when the module is switched to its USB input.

Cartwall

Check Use control switches for cartwall to control the cart players with the control switches of the console, and select the Buttons to use for Cartwall (“A” Buttons, “B” Buttons, or both, numbered top to bottom or left to right).

The Color Settings determine how the button LEDs indicate the state of each cart player: For each player state, select a Color (off, Red, or Green), and optionally enable Blink with a second Blink Color and a Speed.

Additionally, you can select the USB channel used by cartwall, so that the fader of that module controls the cartwall.

Modules

On the Modules tab, you can assign commands to the functions of each module (Cue, On, Fader, Start, VT), for when the function goes On and Off.

Switches

On the Switches tab, you can assign commands to the control switches (Button 1A to Button 8B) and the Non-Stop, Mic On and Silence Detection functions, for when they go On and Off.

Advanced

The Host, UDP send port (default 19551) and UDP receive port (default 19550) for the communication with the AIRLITE Control software. The default host (127.0.0.1) assumes that the software runs on the same computer as mAirList. The ports should not be changed unless instructed by D&R support.

10.4 - D&R WEBSTATION

The D&R WEBSTATION is a USB broadcast mixer. Its integration works exactly the same as for the D&R AIRLITE, through the UDP API of the WEBSTATION Control software by D&R, which must be installed and running. Please refer to the D&R documentation for its installation and setup.

In the configuration app or Control Panel, go to Remote Control and add an interface of type D&R WEBSTATION (D&R category). Please see the AIRLITE page for a description of the settings.

10.5 - D&R AXITE/AXUM (MambaNet)

D&R AXITE and AXUM consoles use the MambaNet protocol for communication between their components. mAirList joins the MambaNet network as a node, and executes remote control commands when its actuators are switched by the console. The required mbn.dll library is included with mAirList.

Configuration

In the configuration app or Control Panel, go to Remote Control and add an interface of type D&R AXITE/AXUM (MambaNet) (D&R category).

General

  • Communication: Select how mAirList connects to the MambaNet network:
    • TCP or UDP: Enter the IP and Port (default 34848) of the console.
    • Ethernet: Communicate directly on the Ethernet layer, through the selected network Device.
  • Address and Unique ID: The MambaNet address and unique ID of the mAirList node. Each node in the network must have a unique ID; only change these values if there is more than one mAirList node.

Commands

On the Commands tab, enter the commands to execute when an actuator of the mAirList node is switched On and Off. The actuators can be assigned to console functions (e.g. buttons or fader start) in the console configuration.

10.6 - D&R AURON

This interface connects mAirList to a D&R AURON mixing console via TCP/IP. It supports fader start and PFL for the players, cartwall control through the console buttons (including colored LEDs), and commands for all buttons of the console.

Configuration

In the configuration app or Control Panel, go to Remote Control and add an interface of type D&R AURON (D&R category).

On the Connection tab, enter the Host name or IP of the console, and the Port (default 9000).

Players

On the Players tab, select the playlist and player, and choose the Channel used by this player (or none). Opening and closing the fader of that channel starts and stops the player.

Options:

  • Automatic PFL switch: The PFL button of the channel switches the PFL of the player on and off.
  • Use PAUSE/STOP: When the fader is closed, the player is paused rather than stopped.

Cartwall

  • Channel used by cartwall: The console channel that the cartwall is connected to.
  • Buttons to use for Cartwall: None, the “A” Buttons, the “B” Buttons, or both (numbered top to bottom or left to right).
  • Color Settings: For each cart player state, select a Color (off, Red, Green, or Yellow), and optionally enable Blink with a second Blink Color and a Speed.

Buttons

On the Buttons tab, you can assign commands to the buttons of the console, for when they are Pressed and Released. The buttons are grouped into the channel buttons, the control buttons, and the buttons of the CRM and Studio monitoring sections.

11 - Sonifex

This section covers the integration with mixing consoles by Sonifex.

11.1 - Sonifex S0

This interface connects mAirList to a Sonifex S0 mixer via a serial port, and executes remote control commands for fader, PFL and start button events of the mixer channels.

Configuration

In the configuration app or Control Panel, go to Remote Control and add an interface of type Sonifex S0 (Sonifex category).

Select the COM Port that the mixer is connected to. The port parameters (baud rate etc.) must be set up in the Serial Ports section of the configuration first.

On the Commands tab, enter the commands for each channel (1 to 9) and event:

  • Fader open / Fader close: Executed whenever the fader is opened or closed.
  • PFL on / PFL off
  • Start button: Executed when the start button of the channel is pressed.
  • Fader+Start on / Fader+Start off: Fader start, i.e. the combination of start button and fader. The start button arms the channel (pressing it again disarms it); Fader+Start on is executed when the fader of an armed channel is opened (or when the start button is pressed while the fader is already open), and Fader+Start off when it is closed again.

For a typical fader start setup, use Fader+Start on and Fader+Start off to start and stop the player, e.g. PLAYER 1-1 START and PLAYER 1-1 STOP.

12 - Ember+

Ember+ is an open control protocol used by many broadcast devices, e.g. mixing consoles by Lawo and others. A device that offers its parameters is called a provider, a device that connects to it and reads or changes those parameters is called a consumer.

mAirList can act as both:

  • Ember+ Consumer – connects to an Ember+ provider (e.g. a mixing console) and executes commands when parameters change.
  • Ember+ Consumer (Lawo) – the same, with additional fader start support for Lawo consoles.
  • Ember+ Provider – offers the internal logic states of mAirList as Ember+ parameters, so they can be read and changed by other devices.

12.1 - Ember+ Consumer

The Ember+ Consumer remote connects to an Ember+ provider (e.g. a mixing console) via TCP/IP, and executes remote control commands when the value of a parameter changes.

Configuration

In the configuration app or Control Panel, go to Remote Control and add an interface of type Ember+ Consumer (Ember+ category).

Connection

  • Host name or IP and Port: The address of the Ember+ provider. The default port is 9000.
  • Keepalive Interval: If set, mAirList sends keepalive requests in this interval, so that a broken connection is detected and re-established.

The Monitor helps you to find the parameters you are interested in. Check Enable Monitor, then operate the device: Each parameter change is displayed in the list. Double-click a parameter to add it to the command list.

Parameter Tree

The Parameter Tree tab displays the complete parameter tree of the provider, along with the current values. Double-click a parameter to add it to the command list.

Commands

The Commands tab contains the list of parameter changes that mAirList reacts to. Each entry consists of:

  • Parameter: The path of the parameter in the Ember+ tree.
  • Value Condition and Value: A condition for the new value of the parameter: =, !=, <, <=, >=, > compare it to the specified Value, * matches any value.
  • Command: The command to execute when the parameter changes and the condition is met. The variable $VALUE is replaced by the new value of the parameter.

12.2 - Ember+ Consumer (Lawo)

This interface is a variant of the Ember+ Consumer for Lawo mixing consoles. In addition to the generic parameter commands, it supports fader start and PFL for the players, based on the console’s source names.

Configuration

In the configuration app or Control Panel, go to Remote Control and add an interface of type Ember+ Consumer (Lawo) (Ember+ category).

The connection settings, monitor, parameter tree, and commands are the same as for the Ember+ Consumer. Additionally, select the console’s Product ID, i.e. the root node of its Ember+ tree.

Players

On the Players tab, select the playlist and player, and enter the Source name of the console source that the player is connected to (leave empty to disable). mAirList monitors the Fader Result Start, Channel On and PFL1 active parameters of that source, and starts and stops the player accordingly.

Options:

  • Automatic PFL switch: The PFL of the source switches the PFL of the player on and off.
  • Use PAUSE/STOP: When the fader is closed, the player is paused rather than stopped.

12.3 - Ember+ Provider

The Ember+ Provider remote turns mAirList into an Ember+ provider: Ember+ consumers (e.g. a mixing console, a broadcast controller, or a monitoring system) can connect to mAirList and read the internal logic states of mAirList, such as the ON AIR state or the states of the players, and receive updates when they change.

Configuration

In the configuration app or Control Panel, go to Remote Control and add an interface of type Ember+ Provider (Ember+ category).

  • Bind IP: The local IP address(es) to listen on, separated by commas. Leave empty to listen on all network interfaces.
  • Port: The TCP port to listen on. The default is 9000.
  • Read-only access: If checked, consumers can only read the parameters. Otherwise, they can also change them, e.g. to trigger functions in mAirList.

Connections and disconnections of consumers are recorded in the System Log.

13 - RODE

This section covers the integration with podcast/broadcast mixers by RØDE.

13.1 - RØDECaster Pro, Pro II and Duo

The RØDECaster Pro, RØDECaster Pro II and RØDECaster Duo send MIDI messages over USB when faders are moved or buttons are pressed. mAirList uses these messages for fader start and PFL of the players, and to trigger the cart players with the SMART pads.

Configuration

In the configuration app or Control Panel, go to Remote Control and add an interface of the type matching your device: RODECaster Pro, RODECaster Pro II, or RODECaster Duo (RODE category).

On the MIDI tab, select the Input Device of the RØDECaster.

Players

On the Players tab, select the playlist and player, and choose the Fader used for this player (or none). The player is started when the fader is opened (and not muted), and stopped when it is closed or muted. The PFL button of the fader switches the PFL of the player.

Option:

  • Use PAUSE/STOP: When the fader is closed, the player is paused rather than stopped.

Cartwall

The SMART Pads of the device can be used to start and stop the cart players. To do so, configure the pads as MIDI triggers in the RØDE Central software, set them to Custom, and adjust their configuration as follows:

  • Mode: Latching
  • Type: CC
  • Channel: 16
  • Control: the cart player number minus 1 (i.e. 0 for cart player 1)
  • On/Off values: 127 / 0

Fader State

The device only reports that the MUTE or PFL button of a channel has been pressed, but not whether the function is currently on or off. mAirList tries to reconstruct the state by tracking all messages. If the tracked state gets out of sync, you can adjust it on the Fader State tab to match the actual state of the faders. Click Save as Default to store the current state as the default state when mAirList starts.

14 - Axel Tech

This section covers the integration with mixing consoles by Axel Tech.

14.1 - Axel Tech Oxygen

This interface connects mAirList to an Axel Tech Oxygen 1000, 2000 or 3000 mixing console via TCP/IP. It supports fader start and PFL for the players and the cartwall, and commands for the channel events.

Configuration

In the configuration app or Control Panel, go to Remote Control and add an interface of type Axel Tech Oxygen 1000/2000/3000 (Axel Tech category).

On the Connection tab, enter the Host name or IP of the console, and the Port (default 93).

Players

On the Players tab, select the playlist and player, and choose the console Channel (1 to 16, or none) that the player is connected to. The fader start of that channel starts and stops the player.

Options:

  • Automatic PFL switch: The PFL of the channel switches the PFL of the player on and off.
  • Use PAUSE/STOP: When the fader is closed, the player is paused rather than stopped.

Cartwall

Choose the console Channel that the cartwall is connected to. The fader start of that channel switches the cartwall ON AIR and OFF AIR, and PFL switches the cartwall to PFL mode.

Commands

On the Commands tab, you can assign remote control commands to the events of each channel: Channel on/off, Faderstart on/off, and PFL on/off.