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

Return to the regular view of this page.

Generic

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

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.

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.

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.

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.