Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revision | Last revisionBoth sides next revision |
tutorials:mairlistdb:music-scheduling [2020/01/09 09:48] – Generate Playlists from an Event tw | tutorials:mairlistdb:music-scheduling [2020/01/09 09:48] – [Set up an Hourly Event for Automation] tw |
---|
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. | 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 === | ==== 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. | 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. |