tutorials:musicmaster:nexus-database-connection
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revisionNext revisionBoth sides next revision | ||
tutorials:musicmaster:nexus-database-connection [2018/04/24 08:43] – [MusicMaster Nexus Database Connection] tw | tutorials:musicmaster:nexus-database-connection [2018/10/11 14:24] – [Adding Music] tw | ||
---|---|---|---|
Line 76: | Line 76: | ||
==== Colors ==== | ==== Colors ==== | ||
- | If a MusicMaster field was mapped as " | + | If a MusicMaster field was mapped as " |
A1=#FF0000 | A1=#FF0000 | ||
Line 86: | Line 86: | ||
On the // | 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. | ||
+ | |||
+ | ===== 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 ===== | ===== 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 ===== | ===== Automation Setup ===== |
tutorials/musicmaster/nexus-database-connection.txt · Last modified: 2020/11/23 16:46 by tw