User Tools

Site Tools


musicmaster:start

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
musicmaster:start [2019/07/09 16:18] – external edit 127.0.0.1musicmaster: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:musicmaster:nexus-database-connection]]
  
-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/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 Setup ===== 
- 
-mAirList for MusicMaster doesn't have an installation package of its own; instead you use the generic setup package for mAirList, found on the [[http://www.mairlist.com/en/download/|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. 
- 
-===== Nexus API Setup ===== 
- 
-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. 
- 
-==== General Setup ==== 
- 
-{{ :musicmaster:pasted:20160330-102053.png?400 }} 
- 
-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. 
- 
-==== Database and field bindings ==== 
- 
-{{ :musicmaster:pasted:20160330-102728.png?400 }} 
- 
-On the //Databases// tab, we choose which MusicMaster database this playout should be attached to, and specify the mapping of MusicMaster and mAirList fields. 
- 
-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. 
- 
-=== Library settings === 
- 
-{{ :musicmaster:pasted:20160330-103623.png?400 }} 
- 
-On the //Library// tab, specify where mAirList-specific metadata will be retrieved from and stored at. 
- 
-  * //MusicMaster (read/write):// Metadata is retrieved from the MusicMaster database. Metadata updates go back into the MusicMaster database. All mAirList-specific fields for which no field mapping exists will be stored in an XML block inside the field mapped to //XML Metadata//. 
-  * //MusicMaster (read-only):// Metadata will be retrieved from MusicMaster, but mAirList will never write back any metadata updates. 
-  * //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 === 
- 
-{{ :musicmaster:pasted:20160330-103637.png?400 }} 
- 
-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 "Traffic". Whenever this keyword appears, mAirList will look for the corresponding playlist file for that ad break and insert its contents as a container instead of the log note. If there is more than one ad break per hour, you can add a number to the log note title (e.g. "Traffic 2") which can be accessed by inserting the variable ''%b'' in the filename pattern. 
- 
-For all variables that can be used inside the filename pattern, see [[reference:logging_variables|Logging Variables]]. 
- 
-=== Advanced settings === 
- 
-{{ :musicmaster:pasted:20160330-103657.png?400 }} 
- 
-On the //Advanced// tab, you can optionally specify a text that will be used to identify this Nexus database throughout the mAirList GUI. 
- 
-==== MusicMaster Enterprise ==== 
- 
-When using Enterprise, you have two MusicMaster databases: A "parent" database that holds the metadata for all songs, and that is replicated into a "child" database, which also contains the schedule for a particular station. 
- 
-mAirList deals with Enterprise databases in the following way: 
- 
-  * Schedule and song metadata is always fetched from the "child" database. 
-  * Metadata **updates** go into the "parent" database (from where they are replicated back into the child database). 
- 
-You activate Enterprise (parent/child) database functions by filling out the information in the //Master/Parent// section of the //Databases// tab in the database configuration. For non-Enterprise databases, leave the //Database/Station ID// field empty for //Master/Parent//. 
- 
-==== Third-party libraries ===== 
- 
-If you have another database attached to your mAirList instance (e.g. a [[tutorials:mairlistdb:getting-started|mAirListDB]], or a third-party database implemented through a script), you can also use that database as metadata store; only the schedule is fetched from MusicMaster then, all song metadata is fetched from the third-party database. 
- 
-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: 
- 
-  * ''$SONGID'': The MusicMaster song ID 
-  * ''$DBID'': The value of the field defined as //Database ID// in the System Field Mapping on the //Databases// tab. 
-  * ''$VERSION'': The version tag; see Versioning below. 
- 
-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 ''$DBID''). 
- 
-==== 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. ''transition''. You can adjust that name on the //General// tab in the configuration. You can also specify the default version in case the attribute is not present for a particular schedule entry. The version string is then available as the ''$VERSION'' variable in the ID pattern. 
- 
-===== Automation Setup ===== 
- 
-(work in progress) 
- 
-Similar to mAirListDB automation setup, see here: [[tutorials:mairlistdb:music-scheduling#set_up_an_hourly_event_for_automation|Music Scheduling with mAirListDB]] 
musicmaster/start.txt · Last modified: 2021/01/05 17:41 by tw

Donate Powered by PHP Valid HTML5 Valid CSS Driven by DokuWiki