tutorials:musicmaster:nexus-database-connection
Differences
This shows you the differences between two versions of the page.
Next revision | Previous revision | ||
tutorials:musicmaster:nexus-database-connection [2017/08/21 15:26] – created tw | tutorials:musicmaster:nexus-database-connection [2020/11/23 16:46] (current) – [Editing Music] tw | ||
---|---|---|---|
Line 1: | Line 1: | ||
====== MusicMaster Nexus Database Connection ====== | ====== MusicMaster Nexus Database Connection ====== | ||
+ | In this tutorial, you will learn how to set up the MusicMaster Nexus Database connection in mAirList. | ||
+ | |||
+ | Using this method, the mAirList playout application can be attached directly to the [[http:// | ||
+ | |||
+ | {{ : | ||
+ | |||
+ | The Nexus Database Connection is not part of the regular buyout licenses of mAirList. Please contact sales for licensing options and pricing. | ||
+ | |||
+ | ===== Prerequisites ===== | ||
+ | |||
+ | We assume that the following is available: | ||
+ | |||
+ | * A MusicMaster database. | ||
+ | * A Nexus server, or a MusicMaster Client/ | ||
+ | * 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. | ||
+ | |||
+ | ===== Nexus API Configuration ===== | ||
+ | |||
+ | Before you can configure the database connection, you must set up the Nexus API in the mAirList configuration. In particular, the following fields must be mapped correctly between MusicMaster and mAirList: | ||
+ | |||
+ | * Artist, Title and their Keywords | ||
+ | * Filename | ||
+ | * XML Metadata (mAirList will store additional technical metadata here) | ||
+ | |||
+ | Please follow the instructions found here: [[tutorials: | ||
+ | |||
+ | ===== Database Connection Setup ===== | ||
+ | |||
+ | Once the Nexus API has been set up, go to the // | ||
+ | |||
+ | ==== General settings ==== | ||
+ | |||
+ | On the first page, select the Nexus API (host, port and database name) to be used; we assume that it has been [[tutorials: | ||
+ | |||
+ | {{ : | ||
+ | |||
+ | You can also enable reconciliation here. If turned on, mAirList will report all song start/stop events to MusicMaster in realtime. | ||
+ | |||
+ | ==== Library settings ==== | ||
+ | |||
+ | On the //Library// tab, specify where mAirList-specific metadata will be retrieved from and stored at. | ||
+ | |||
+ | * // | ||
+ | * // | ||
+ | * //Other database (by Internal ID)// and //Other database (by External ID)//: Allows you to use another database connection as metadata source; see section on third-party libraries below. | ||
+ | |||
+ | {{ : | ||
+ | |||
+ | "Other database" | ||
+ | |||
+ | In the //Other databases// box, you can define the pattern to use for the ID, using the following variables: | ||
+ | |||
+ | * '' | ||
+ | * '' | ||
+ | * '' | ||
+ | |||
+ | In case the ID must be extracted from the //Database ID// field, you can specify a regular expression to do so (Perl format, first match will be the '' | ||
+ | |||
+ | Versioning is a feature used with third-party databases where multiple versions of a particular song exist; the version to play is included as an XML attribute in the schedule returned from Nexus, e.g. '' | ||
+ | |||
+ | |||
+ | ==== Content settings ==== | ||
+ | |||
+ | When loading schedules from MusicMaster, | ||
+ | |||
+ | {{ : | ||
+ | |||
+ | For advertising import, specify an " | ||
+ | |||
+ | For other external content, specify a prefix (e.g. " | ||
+ | |||
+ | For the configuration of region suffixes, see section on Regionalization below. | ||
+ | |||
+ | ==== Colors ==== | ||
+ | |||
+ | If a MusicMaster field was mapped as " | ||
+ | |||
+ | A1=#FF0000 | ||
+ | A2=#00FF00 | ||
+ | B1=#FFFF00 | ||
+ | | ||
+ | ==== Advanced Settings ==== | ||
+ | |||
+ | On the // | ||
+ | |||
+ | ===== Adding Music ===== | ||
+ | |||
+ | New audio files can be added to the MusicMaster library in two ways: | ||
+ | |||
+ | - Manually, by creating the song in MM and entering all details by hand. Make sure that the exact file name is entered into the corresponding field. | ||
+ | - Automatically using the //Nexus Importer// tool found in the mAirList Start Menu group. This tool will fetch a list of all files contained in the MusicMaster library, then scan the audio folder for new files, and add the files to the MusicMaster library. Any existing file tags (ID3 etc.) will be parsed and translated to the respective MusicMaster fields. | ||
+ | |||
+ | Beginning with mAirList 6.3.8, the Nexus Importer can also be integrated into the MusicMaster GUI by the means of a [[https:// | ||
+ | |||
+ | < | ||
+ | [UserButton1] | ||
+ | Tooltip=Look for New Files in mAirList | ||
+ | Image=C: | ||
+ | App=C: | ||
+ | CommandScript=" | ||
+ | </ | ||
+ | |||
+ | If you are working with more than one MusicMaster database, you must additionally pass the name of the database on the command line: | ||
+ | |||
+ | < | ||
+ | CommandScript=" | ||
+ | </ | ||
+ | |||
+ | In that case, all databases must be registered in the Nexus API configuration of mAirList. In order to identify the database, mAirList will first compare the value to the Nexus ID, then to the alias set in the Nexus API configuration. | ||
+ | ===== Editing Music ===== | ||
+ | |||
+ | Generally, all library maintenance should be performed from inside MusicMaster. | ||
+ | |||
+ | There are a few things however that cannot be edited easily from MusicMaster. In particular the cue markers, as MusicMaster does not have any built-in editing tool. | ||
+ | |||
+ | If you need to edit any fields that are not easily accessible from MusicMaster, | ||
+ | |||
+ | In the browser part, click //Add// and add a new // | ||
+ | |||
+ | Starting with mAirList 6.3.8, another way to edit items has been established: | ||
+ | |||
+ | < | ||
+ | [UserButton2] | ||
+ | Tooltip=Edit song in mAirList | ||
+ | Image=C: | ||
+ | App=C: | ||
+ | CommandScript=" | ||
+ | </ | ||
+ | |||
+ | When working with more than one database, you must pass the database name on the commandline, | ||
+ | |||
+ | < | ||
+ | CommandScript=" | ||
+ | </ | ||
+ | ===== Regionalization ===== | ||
+ | |||
+ | [[tutorials: | ||
+ | |||
+ | mAirList can create region containers from items found in a Nexus Schedule. This requires a little bit of preparation: | ||
+ | |||
+ | First, we need to define a filename suffix for each region to be used. Imagine you are broadcasting to three regions " | ||
+ | |||
+ | {{ : | ||
+ | |||
+ | So for example, a regionalized jingle " | ||
+ | |||
+ | jingle1-ATOWN.mp3 | ||
+ | jingle1-BTOWN.mp3 | ||
+ | jingle1-CTOWN.mp3 | ||
+ | |||
+ | These should all have the same duration obviously. But most importantly, | ||
+ | |||
+ | In the MusicMaster library, set up a new YesNo field (e.g. " | ||
+ | |||
+ | Then create a category+clock that will schedule **one** of the regionalized versions, e.g. '' | ||
+ | |||
+ | Now when mAirList encounters the '' | ||
+ | |||
+ | ===== Automation Setup ===== | ||
+ | |||
+ | (work in progress) | ||
+ | |||
+ | Similar to mAirListDB automation setup, see here: [[tutorials: |
tutorials/musicmaster/nexus-database-connection.txt · Last modified: 2020/11/23 16:46 by tw