tutorials:musicmaster:nexus-database-connection
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revisionLast revisionBoth sides next revision | ||
tutorials:musicmaster:nexus-database-connection [2018/04/24 08:41] – [Content settings] tw | tutorials:musicmaster:nexus-database-connection [2020/11/23 16:44] – [Adding Music] tw | ||
---|---|---|---|
Line 1: | Line 1: | ||
====== MusicMaster Nexus Database Connection ====== | ====== MusicMaster Nexus Database Connection ====== | ||
- | |||
- | Tutorial is work in progress, please see previous version of documentation here: [[musicmaster: | ||
In this tutorial, you will learn how to set up the MusicMaster Nexus Database connection in mAirList. | In this tutorial, you will learn how to set up the MusicMaster Nexus Database connection in mAirList. | ||
Line 20: | Line 18: | ||
Please check with MusicMaster support if you are unsure whether your MusicMaster installation provides the above requirements. | 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: | 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: | ||
Line 78: | Line 78: | ||
==== Colors ==== | ==== Colors ==== | ||
- | If a MusicMaster field was mapped as " | + | If a MusicMaster field was mapped as " |
A1=#FF0000 | A1=#FF0000 | ||
Line 84: | Line 84: | ||
B1=#FFFF00 | 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 // | ||
+ | ===== 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