Differences

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

--- tutorials:mairlistdb:music-scheduling [2015/10/02 13:00] – [Step 8: Access Playlist in Live Assist] tw
+++ tutorials:mairlistdb:music-scheduling [2021/05/19 13:47] (current) – [Available template items] Duration of music block or fill with music ulinobbe
@@ Line 2: / Line 2: @@
-<WRAP info round>This article applies to mAirList 5.x. For mAirList 4, see the [[tutorials:mairlistdb:music-scheduling-mairlist4|old version of this tutorial]].</WRAP>
+<WRAP info round>This article applies to mAirList 5.x and 6.x. For mAirList 4, see the [[tutorials:mairlistdb:music-scheduling-mairlist4|old version of this tutorial]].</WRAP>
-In this article, we will show you how to import your audio files into mAirListDB and set up music scheduling for 24/7 automated operation (or live assist, or mixed).
+In this article, we will show you how to import your audio files into mAirListDB and set up the "Mini Scheduler" music scheduling for 24/7 automated operation (or live assist, or mixed).
 We assume that the mAirListDB connection has already been set up as described here:
@@ Line 102: / Line 102: @@
 === Music block ===
-Insert the entire music block (or the remaining items from that block if you have used "one song" before).
+Insert __the entire music block__ (or the remaining items from that block if you have used "one song" before).\\
+Please note: If you try to give the music block a specific duration in the settings, it will be ignored.
 === Fill with music ===
-Insert songs from the specified music block to fill up the time until the following fixed-time item.
+Insert songs from the specified music block to fill up the time until the following fixed-time item or the defined duration in the settings.
 === Dummy ===
@@ Line 277: / Line 278: @@
 If you are importing music logs from an external music scheduling software, go to the //Import Settings// tab and set up the file type and location of your music logs.
+{{ :tutorials:mairlistdb:pasted:20180109-182432.png?400 }}
+Specify whether you have one file per day or per hour, or even per music block. Some formats can automatically split daily logs into hours automatically. For other formats, you have the option to split by time, title etc.
+For the source folder and/our filename format, you can use the date/time [[reference:logging_variables|logging variables]] as placeholders.
 Don't forget to set the //Source// of all relevant music blocks to //External scheduler//! The third option, //Hybrid//, will try to load the log from the specified file first, and fall back to internal scheduler if that fails.
 ==== Transitions ====
@@ Line 341: / Line 349: @@
 {{ :tutorials:mairlistdb:pasted:20140224-153823.png }}
+=== Simple Event with Load and Play Database Playlist ===
 The event is configured so that it runs each day, each hour at 0 minutes and 0 seconds (see screenshot). In the //Actions// section, add a new //Load and play database playlist// action, and leave all of its settings untouched.
@@ Line 347: / Line 357: @@
 That's it - at the top of the hour, mAirList will grab the next playlist from the database and play it. All you have to do is to turn on AUTO mode.
+=== Alternative Method using Append Database Playlist ===
+Another option is to execute the event a few minutes before the top of the hour, and use the //Append Database Playlist// action instead.
+**Important:** Check the //Load playlist of next hour// option in the event settings! (Remember it's still a few minutes before the top of the hour when the event runs.)
+If the playlist has a soft or hard fixed time on its first item (which is usually the case), mAirList will automatically fade to that first item at xx:00:00 (hard fixed time), or when the last song has finished (soft fixed time).
+The advantage of this method is that you can mix soft and hard fixed times by just changing the playlists in the database accordingly, and you can also schedule multi-hour content by removing the End of Hour marker, and leave the subsequent playlists empty in the database.
+==== Generate Playlists from an Event ====
+In a typical radio station environment, playlists for the next day(s) are generated manually from the Database application in advanced. For 24/7 unattended stations, you may choose to have the playoust process generate the playlists automatically. This is done by using the //Generate playlists// action in the Event Manager, either in another event (that runs a couple of minutes before the load/append event), or as another action inside the load/append event (take care of the correct order of actions - generate must happen first). By default, the //Generate Playlists// action will not overwrite existing playlists; so you can safely set it up as a "fallback" event, even if you plan to schedule manually in the general case.