User Tools

Site Tools


tutorials:musicmaster:nexus-database-connection

Differences

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

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision
Previous revision
Next revisionBoth sides next revision
tutorials:musicmaster:nexus-database-connection [2018/04/24 08:43] – [Colors] twtutorials:musicmaster:nexus-database-connection [2018/10/11 14:18] – [Advanced Settings] tw
Line 86: Line 86:
 On the //Advanced// tab, specify an optional name for this database unter which is is displayed in the mAirList GUI. The default is just "Database". On the //Advanced// tab, specify an optional name for this database unter which is is displayed in the mAirList GUI. The default is just "Database".
  
 +===== 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.
 ===== Regionalization ===== ===== Regionalization =====
 +
 +[[tutorials:region-playout|Regionalization (region splitting)]] is a feature in mAirList which provides special "Region Container" playlist items that have different content for multiple regions, routed to separate audio outputs or streams.
 +
 +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 "A-Town", "B-Town" and "C-Town". We will use the following filename suffixes: ''-ATOWN'', ''-BTOWN'', ''-CTOWN''. We enter these suffixes on the //Content// tab in the database connection properties:
 +
 +{{ :tutorials:musicmaster:pasted:20180424-105812.png?400 }}
 +
 +So for example, a regionalized jingle "jingle1" must exist in three versions:
 +
 +  jingle1-ATOWN.mp3
 +  jingle1-BTOWN.mp3
 +  jingle1-CTOWN.mp3
 +
 +These should all have the same duration obviously. But most importantly, **they must all reside in the same Windows folder**.
 +
 +In the MusicMaster library, set up a new YesNo field (e.g. "Regionalized") and tick it for the above items. Don't forget to map it to "Regionalized" in the mAirList Nexus API setup.
 +
 +Then create a category+clock that will schedule **one** of the regionalized versions, e.g. ''jingle1-ATOWN.mp3'' - which one doesn't really matter.
 +
 +Now when mAirList encounters the ''jingle1-ATOWN.mp3'' file in the schedule and notices that it's a regionalized item, it will gather the matching items for the other regions (based on the filename suffixes) and create a Region Container from all of them.
  
 ===== Automation Setup ===== ===== Automation Setup =====
tutorials/musicmaster/nexus-database-connection.txt · Last modified: 2020/11/23 16:46 by tw

Donate Powered by PHP Valid HTML5 Valid CSS Driven by DokuWiki