Differences

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

--- tutorials:musicmaster:nexus-database-connection [2018/04/24 08:43] – [Colors] tw
+++ tutorials:musicmaster:nexus-database-connection [2018/04/24 09:00] – [Regionalization] tw
@@ Line 87: / Line 87: @@
 ===== 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 =====