Differences

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

--- tutorials:region-playout [2015/10/12 12:30] – [In the built-in advertising scheduler] tw
+++ tutorials:region-playout [2019/07/09 16:18] (current) – external edit 127.0.0.1
@@ Line 74: / Line 74: @@
 When the Mini Scheduler notices that there are any spots which are to be left out in at least one region, it will automatically use a Region Container instead of an ordinary Container item for that ad block.
 ==== Imported from third-party ad schedulers ====
+For ad blocks imported from external sources, check the option //Regionalized content// in the import source configuration:
+{{ :tutorials:pasted:20151012-143439.png?400 }}
+The Mini Scheduler will now look for a separate import log file for each region; use %N in the filename format as a placeholder for the region number (starting with 1 for the first region), or %2N or %3N for the region number padded with zeroes to two or three digits.
+===== Regions and Streaming =====
+When you use mAirList's built-in encoder, and have the Encoder Status screen object active, you will notice that there are now eight peakmeter bars visible where there used to be only two:
+{{ :tutorials:pasted:20151012-145908.png }}
+The topmost two bars are for the "common" signal, and then there are two bars for each region.
+==== Audio devices ====
+When setting up the player devices to play directly into the encoder, only select "Encoder - all regions" for the playback device of each particular player. Do **not** set any playback devices for the individual regions. The encoder can handle regions automatically, so it is not necessary to do this (and would break a few things):
+{{ :tutorials:pasted:20151019-134409.png?400 }}
+In the rare case that you need a particular player to play directly into a specific region, there are devices "Encoder - Region 1" etc. available in the drop-down list:
+==== Connection submixes ====
+When adding a new Shoutcast/Icecast connection, go to the //Regions// tab and check the regions that should be audible on this connection - typically the common signal plus exactly one region:
+{{ :tutorials:pasted:20151012-150038.png?400 }}
+mAirList will now automatically create a proper submix and route it to this connection.
+==== A note on sound processing ====
+When using soundprocessing and regionalized stream content, it is obvious that you cannot use the "master signal" DSP chain, as you need a separate processing for each downmixed stereo stream. Use the per-connection DSP chain instead.