The Edit Event dialog lets you edit an event, i.e., defining the date and time rules for execution, and specifying the action.
This is an optional field which lets you describe what the event does. It is meant for easier administration and documentation.
Next, specify on which days the event should be executed. You can choose whether to run the event each day, only on certain weekdays, only once (a year) or at user defined days.
In the user-defined fields, you can enter lists and/or ranges of values. The allowed values are 1..31 for the day, 1..12 for the month and 1..7 (monday through sunday) for the week day. Use a comma to separate values and a hyphen to define ranges. Lists and ranges can be mixed. Examples (for the weekday field): “1” (only monday), “1-5” (monday through friday), “2, 5-7” (tuesday, friday, saturday and sunday).
Specify the time at which the event should be executed. The options are: each hour at a given minute and second; only once a day at a given time; or user defined. See the data section above for the format for the user defined fields. The allowed intervals are 0..23 for hour, 0..59 for minute and 0..59 for second.
If an event is supposed to expire at a given time, you can specify the date and time here. Otherwise, it will run forever.
The Event Scheduler is most useful in automation mode to schedule items and playlists. However, it can also be used in assist mode. You can specify for each single event whether to be run in automation and/or assist mode.
Finally, specify the action to take when the event occures. Most actions require a parameter (e.g., filename) to be specified in the Parameter field appearing below. The following options are available:
No action is taken. This is useful for testing purposes, or for disabling an event temporarily.
A file is inserted into the playlist and played automatically. This does only work in automation mode, and corresponds to the steps (1) insert a file after the one currently playing and (2) clicking NEXT.
Inserts a file into the playlist, but does not play it immediately. In case automation is enabled, it will be played when the current item is finished.
Load a playlist (.mlp/.mlt or .m3u format). The current playlist is replaced, but the item currently playing will not be removed until it is finished.
As above, but the playlist is automatically started by issuing a NEXT command to the automation. Does only work in automation mode.
Appends a playlist at the end of the current one.
Runs a mAirListScript script. See Chapter 10, Scripting.
Executes a faderstart command.