mAirList for MusicMaster is a special edition of the mAirList Radio Automation that can attach directly to a MusicMaster database via the Nexus API, using the MusicMaster database as its audio library and scheduling backend.

This page gives detailed setup instructions to build an automated playout system attached to a MusicMaster database.

We assume that the following is available:

• A MusicMaster database.
• A Nexus server, or a MusicMaster Client/Server database implementing the Nexus API; the HTTP port must be reachable from the playout computer, optionally through a reverse proxy.
• A folder with audio files, accessible through a Windows share or HTTP server; the file names (without folder) of the individual must be entered into a MusicMaster field.

Please check with MusicMaster support if you are unsure whether your MusicMaster installation provides the above requirements.

mAirList for MusicMaster doesn't have an installation package of its own; instead you use the generic setup package for mAirList, found on the download page. The MusicMaster/Nexus functionality is unlocked through your license file.

mAirList for MusicMaster requires mAirList 5.3 or newer.

Having completed the setup, open the License Manager (found in the Windows Start Menu), and download/activate your license.

Note about Windows Server: If you use a Windows Server operating system, you will need to add the “Desktop Experience” feature in Windows Server Manager in order to install the required audio codecs.

Once mAirList is installed and activated, open the standalone configuration software, found in the Windows Start Menu. Then go to Databases and click Add to add a new MusicMaster Nexus Server database.

On the General tab, make the required settings for accessing the Nexus API:

• Nexus Server URL: Enter URL of the Nexus server, including the port number. Protocol is usually http but can be https if the server is accessed through a secure reverse proxy. In a typical setup, no username or password is required; when using a reverse proxy with authentication, you can include the user name and password into the url: http://user:password@host:port/
• Audio folder: Specify the folder where the MusicMaster audio files are stored. This can be an HTTP URL if the files are to be accessed via HTTP. In this case, don't forget the trailing slash character.
• Cache folder: If you maintain a synchronized copy of the audio folder on the local hard drive, specify the location here.
• Versioning: See section on versioning below.
• Options: Typically you will want to enable reconciliation, so mAirList will report the actual start and stop times back to MusicMaster.

On the Databases tab

For MusicMaster Enterprise, there are separate settings for the Parent and Child database – see section on MusicMaster Enterprise below. For non-Enterprise databases, we only use the Default/Child settings.

• Database/Station ID: Use the dropdown to select database/station ID on the Nexus to use for this connection; this will also serve as a simple test to check if the HTTP connection to the Nexus server is working.
• System Field Mapping: Specify the names of the MusicMaster fields to use for Artist, Title, Duration and Filename in mAirList. The XML Metadata field must be a Memo field that you defined in MusicMaster – this is where mAirList stores additional metadata that does not fit into any other field, e.g. cue markers. Database ID is only used when integrating another database as metadata source – see section on third-party libraries below.
• Attribute Field Mapping: You may add additional fields here that are mapped between MusicMaster and mAirList attributes, e.g. for use in logging. Use the cursor-down key to add more rows to the table.