tutorials:region-playout
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
tutorials:region-playout [2015/10/12 11:55] – [Set up the region names] tw | tutorials:region-playout [2019/07/09 16:18] (current) – external edit 127.0.0.1 | ||
---|---|---|---|
Line 35: | Line 35: | ||
To understand how the audio routing works, it is important to note that **only the Region Container output will be routed to these region devices**; non-region items will continue to play on the ordinary playback devices. So you must use some external device (matrix mixer) to generate the appropriate submixes for each region, usually by combining one region output with the main output of your mixing console. A notable exception is mAirList' | To understand how the audio routing works, it is important to note that **only the Region Container output will be routed to these region devices**; non-region items will continue to play on the ordinary playback devices. So you must use some external device (matrix mixer) to generate the appropriate submixes for each region, usually by combining one region output with the main output of your mixing console. A notable exception is mAirList' | ||
- | ===== How it works ===== | + | ===== Create Region Containers |
- | For other audio routings (e.g. when you are using a mixing console), you need an extra soundcard output for each region, | + | Once the audio routing is set up, you can save your config |
- | mAirList' | ||
+ | ==== In the playout window ==== | ||
+ | To create a Region Container from the mAirList main window, click the arrow next to //Insert// in the main toolbar, then select //Region Container// | ||
+ | |||
+ | {{ : | ||
+ | {{ : | ||
+ | {{ : | ||
+ | |||
+ | (Note: If you wish to add content by drag& | ||
+ | |||
+ | You can add as many items as you like. Ideally, the content should have the exact same duration for each region. Otherwise you can use one of the available //Auto fill// settings: | ||
+ | |||
+ | * **None:** No auto-fill will take place. A region will play silence if it is shorter than the other regions. | ||
+ | * **Silence: | ||
+ | * **Use filler (fade out at end)**: If a region is too short, the filler item will be added to the playlist for that region; the fade out marker for the filler will be set so that the total duration matches the maximum duration of all region content playlists. | ||
+ | * **Use filler (fade in and play until end)**: The filler item will be used, however it will fade **in** and then play util the end. For example, when the filler has a duration of 2:00 minutes, and we need to fill 10 seconds, mAirList will play the filler from 1:50 of 2:00. | ||
+ | |||
+ | Once you have set up the Region Container, you can drag it into any player and check if the audio is routed to the correct sound card. | ||
+ | |||
+ | ==== In the mAirListDB library ==== | ||
+ | |||
+ | Region Containers can also be added manually to any mAirListDB library, using the //Add// menu in the library toolbar. | ||
+ | |||
+ | Again, you must first save and the reopen the container in order to add other items by drag& | ||
+ | ==== In the built-in advertising scheduler ==== | ||
+ | |||
+ | When scheduling ads through the mAirListDB build-in advertising scheduler, you will see a new tab named //Regions// in the campaign settings: | ||
+ | |||
+ | {{ : | ||
+ | |||
+ | By default, all regions are checked -- you can modify this settings in order to schedule a spot only for some but not all regions. | ||
+ | |||
+ | 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 // | ||
+ | |||
+ | {{ : | ||
+ | |||
+ | 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' | ||
+ | |||
+ | {{ : | ||
+ | |||
+ | The topmost two bars are for the " | ||
+ | |||
+ | ==== Audio devices ==== | ||
+ | |||
+ | When setting up the player devices to play directly into the encoder, only select " | ||
+ | |||
+ | {{ : | ||
+ | |||
+ | In the rare case that you need a particular player to play directly into a specific region, there are devices " | ||
+ | |||
+ | ==== Connection submixes ==== | ||
+ | |||
+ | When adding a new Shoutcast/ | ||
+ | |||
+ | {{ : | ||
+ | |||
+ | 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 " |
tutorials/region-playout.1444650933.txt.gz · Last modified: 2019/07/09 16:19 (external edit)