musicmaster:start
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revision | |||
musicmaster:start [2019/07/09 16:18] – external edit 127.0.0.1 | musicmaster:start [2021/01/05 17:41] (current) – tw | ||
---|---|---|---|
Line 1: | Line 1: | ||
====== mAirList for MusicMaster ====== | ====== mAirList for MusicMaster ====== | ||
- | ===== Introduction ===== | + | This page was moved to: [[tutorials: |
- | 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. | ||
- | |||
- | ===== 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. | ||
- | |||
- | |||
- | ===== mAirList Setup ===== | ||
- | |||
- | mAirList for MusicMaster doesn' | ||
- | |||
- | 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/ | ||
- | |||
- | **Note about Windows Server:** If you use a Windows Server operating system, you will need to add the " | ||
- | |||
- | ===== Nexus API Setup ===== | ||
- | |||
- | Once mAirList is installed and activated, open the standalone configuration software, found in the Windows Start Menu. Then go to // | ||
- | |||
- | ==== General Setup ==== | ||
- | |||
- | {{ : | ||
- | |||
- | 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, | ||
- | * //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. | ||
- | * // | ||
- | * // | ||
- | |||
- | ==== Database and field bindings ==== | ||
- | |||
- | {{ : | ||
- | |||
- | On the // | ||
- | |||
- | 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 // | ||
- | |||
- | * // | ||
- | * //System Field Mapping:// Specify the names of the MusicMaster fields to use for //Artist//, //Title//, // | ||
- | * //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. | ||
- | |||
- | === 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. | ||
- | |||
- | === Advertising settings === | ||
- | |||
- | {{ : | ||
- | |||
- | mAirList can inject advertising breaks from other sources, e.g. M3U files. Advertising breaks must be present inside the schedule as log notes with a particular keyword -- default is " | ||
- | |||
- | For all variables that can be used inside the filename pattern, see [[reference: | ||
- | |||
- | === Advanced settings === | ||
- | |||
- | {{ : | ||
- | |||
- | On the // | ||
- | |||
- | ==== MusicMaster Enterprise ==== | ||
- | |||
- | When using Enterprise, you have two MusicMaster databases: A " | ||
- | |||
- | mAirList deals with Enterprise databases in the following way: | ||
- | |||
- | * Schedule and song metadata is always fetched from the " | ||
- | * Metadata **updates** go into the " | ||
- | |||
- | You activate Enterprise (parent/ | ||
- | |||
- | ==== Third-party libraries ===== | ||
- | |||
- | If you have another database attached to your mAirList instance (e.g. a [[tutorials: | ||
- | |||
- | In order to use this feature, go to the //Library// tab and select either //Other database (by Internal ID)// or //Other database (by External ID)//, whichever is the ID system you use in the third-party database. (Only mAirListDB supports External IDs.) | ||
- | |||
- | 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 ==== | ||
- | |||
- | 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. '' | ||
- | |||
- | ===== Automation Setup ===== | ||
- | |||
- | (work in progress) | ||
- | |||
- | Similar to mAirListDB automation setup, see here: [[tutorials: |
musicmaster/start.txt · Last modified: 2021/01/05 17:41 by tw