This page describes the new features and other notable changes in mAirList 5.3.

Note that not all features are available in all licenses/editions.

The complete changelog can be found http://download.mairlist.com/mAirList/v5.3/Changelog.txt here.

mAirList can now use a MusicMaster Nexus server as a database backend. That means you can use mAirList as a playout system using MusicMaster as the sole scheduling backend, without any synchronization (library import, schedule export). mAirList-specific metadata (e.g. cue markers) can be stored in a Memo text field inside MusicMaster. You can also map any mAirList attribute to any field in MusicMaster. The interface supports MusicMaster Enterprise (master/client) databases, as well as versioning through XML attributes in the schedule output.

This version introduces support for the MambaNet protocol, mainly used to remote control mAirList from a D&R Axum mixing console.

The DHD 52/4200/3200 remote control interface can now report certain internal states of mAirList (automation on, PFL active, …) as logic states to the console, for example for display on a TFT view, or as a base for logic and output functions (e.g. switch PFL input to monitor when PFL is active).

For users of all current Series 52 models (firmware 7.x.x.x or 8.x.x.x), it's now possible to export the Toolbox project as an XML file and import that file into mAirList – this will make the configuration much easier, because you can simply select the desired fader channel for a player from a list, and mAirList will set up all logics automatically.

The cartwall supports Hook Mode (again), so you can easily play hooks through a cart player.