Using “Actions”, you can execute various tasks in mAirList, bound to (timed) events.

Actions can be used in various places:

• In the Event Scheduler
• As “Actions on Start” or “Actions on Stop” in the properties of any playlist item
• Inside any Trigger in the Cartwall
• In any of the “standard action lists” (managed on the Actions page in the config app):
  • After Startup
  • Before Shutdown
  • When playlist runs empty during automation
  • When entering ON AIR mode
  • When entering OFF AIR mode
  • When PFL output is started
  • When PFL output if stopped
  • When non-player PFL output is started
  • When non-player PFL output if stopped
• In the “Action Menu” in the playout window (also managed on the Actions page in the config app) – a new button Actions will appear in the main toolbar as soon as you add actions to this list, with a dropdown menu that contains the actions you defined.
• In the Stream Monitor
• etc.

All of the places that support actions, mentioned above, have a section in the GUI where you manage the list of actions to be executed. For example, this is how it looks in the Event Editor:

The toolbar contains buttons to add, delete and configure events, and to load/save the entire list from/to XML files.

The configuration settings largely depend on the type of action – see description below. But all actions have the same Options tab:

The following settings are found here:

• Custom Title: Enter a custom title for the action if desired; particularly useful for the Action Menu.
• Enable substitution of variables: If enabled, you can use logging variables, e.g. for the current date/time, in the action configuration. This setting applies to all actions that accept filenames.
• Show confirmation dialog when run manually: Applies to the Action Menu which will request confirmation from the user before executing the action when this option is set.
• Time adjustment: This setting allows you to change the current/date time (only for the scope of this action) while the action is executed. In particular, it will affect the date/time that is used for the substituation of logging variables.
• Affected playlist: Select the playlist that this action should work on; mainly applies to all actions that manipulate the playlist (e.g. “Load and play playlist”).

This section describes all available actions and their options.

Executes any of the remote control commands.

Serves as a container for other actions, can be used to nest actions for easier management.

Normally, when an action fails due to an error, the execution of the entire action list is aborted. When you add an Emergency actions action to the end of the list however, the execution will jump to that emergency actions and execute all actions found inside it. If you are a developer, this is pretty much like a try..finally block.

Just a dummy…

Downloads a file via HTTP or FTP and saves it under the given filename. Can be used together with the Event Scheduler to implement a very simple download manager.

Send an e-mail. Enter the recipient, subject and body. Note: Sender address and name as well as the SMTP server must be configured in the config app first.

Runs a script (*.mls file).

Sends data to a serial port, which must already be open (e.g. by using a Serial Port Remote Control). The data is sent in ANSI encoding by default. In order to send binary data, enter a dollar sign followed by the hexadecimal data, e.g. $C0BA0003.

Inserts the specified file at the top of the playlist, or below the currently playing item. You can use logging variables in the filename if substitution is enabled on the Options tab.

Inserts the specified file at the top of the playlist, or below the currently playing item, and starts it immediately. You can use logging variables in the filename if substitution is enabled on the Options tab.

This action only works in AUTO mode, as it uses the AUTOMATION x NEXT command internally. In ASSIST mode, the file is only inserted but not played.

Same as above, but for files on HTTP/FTP servers. Enter a URL instead of a local filename.

Note: All “Playlist” actions accept logging variables inside the filename if substitution is enabled on the Options tab.

Loads the specified playlist file. The current playlist content (except for any playing items) is discarded.

Loads the specified playlist file, and issues an AUTOMATION NEXT command so that the automation jumps to the first item. Only works in AUTO mode.

Inserts a playlist file at the top of the current playlist, or below the currently active item.

Inserts a playlist file at the top of the current playlist, or below the currently active item, then issues an AUTOMATION NEXT command so that the automation jumps to the first item. Only works in AUTO mode.

Appends the specified playlist file to the current playlist.

Shuffles the current playlist content.

Switches to AUTO mode.

Switches to ASSIST mode.

Equivalent to clicking the PLAY button in the automation toolbar.

Equivalent to clicking the NEXT button in the automation toolbar.

Equivalent to clicking the STOP button in the automation toolbar.

Inserts a stream playlist item at the top of the playlist, or after the currently active item. Enter the URL and an optional title for the stream. Also specifiy whether this should be an infinite stream, or a stream item with a particular duration.

Insert a stream playlist item, and issue an AUTOMATION x NEXT command so that it is played instantly. Only works in AUTO mode.

Same as the actions for playlist files described above, but for playlists loaded from a database (e.g. mAirListDB).

Select the database connection to load from (defaults to the first active connection) and the sub-playlist (defaults to the master playlist) to use.

An optional postprocessing script can be specified that is run on the playlist before it is loaded/inserted/appended. The playlist can be accessed through CurrentPlaylist from the script.

Several options are available:

• Load the playlist for the next hour (instead of the current hour): Playlists are stored in an hourly grid in the database. Normally these actions would load the playlist for the current hour, which is perfectly fine if the action is run exactly at the top of the hour. But sometimes you run the action a few minutes before the top of the hour, in particular when using the Append database playlist action. In this case, check this option so the playlist for the next hour is used. You an also used the time adjustment on the Options tab if you need to move further ahead or back.
• Set fixed time on first element: If checked, a fixed time (for the corresponding hour) will be set on the first item of the playlist, so that the automation jumps to that item at the given time. This is for database playlists that don't have any kind of “Start of hour” marker (with a fixed time) themselves.
• Use soft fixed time: Used together with Set fixed time on first element, a soft fixed time is being used instead of a hard one.
• Use an extra Dummy element for fixed time: Used together with the two aforementioned options, the fixed time is not applied to the first item of the playlist, but an extra dummy item is inserted that carries the fixed time; the first item remains untouched.
• Skip to current time: Skip all items that have a planned playback time before the current time. Useful when using Load database playlist as an Action after startup to load the current database playlist when mAirList starts. Does not cue into the exact position of the first song!
• Update advertising: Runs the Update Advertising function before loading the playlist.
• If advertising was updated, save playlist to database: Stores any changes made by Update Advertising back into the database.
• Report an error if the playlist is empty: If the database playlist is empty, an error is reported, execution of the action list is aborted, and any possible Emergency Actions are executed.
• Report an error if the postprocessing script fails: Same as above, in case the postprocessing script raises an error.
• Report error and underrun count to System Log: For debugging and monitoring purposes.

These actions refer to the Windows Audio Mixer (not widely used anymore in Vista and later).

Mutes the specified channel in the mixer.

Unmutes the specified channel in the mixer.

These actions refer to the built-in Streaming Encoder.

Establishes the encoder connection, equivalent to clicking the Connect button in the Encoder Status window.

Terminates the encoder connection, equivalent to clicking the Disconnect button in the Encoder Status window.

Use this action to switch any of the encoder inputs (Mic, Line, Aux, …) on or off. This is the same as clicking the LINE or MIC button in the Encoder Status window.

Unmutes the local audio output of the encoder (to the audio device set as encoder playback device in the config).

Mutes the local audio output.

The actions in this section are used to control any Aircheck Recorder. The recorder must have a Remote ID set in the screen object properties, and you must enter the same ID in the action configuration.

The same as clicking the Open button in the Aircheck Recorder window. The filename is selected automatically based on the recorder configuration.

Starts recording, or resumes it if it is paused. Equivalent to the Record button in the Aircheck Recorder window.

Equivalent to the Pause button in the Aircheck Recorder window.

Equivalent to the Close button in the Aircheck Recorder window.

These actions refer to the File Recorder.

Starts a new recording. See the File Recorder documentation for a description of all options and settings.

Stops one or more recordings, based on the Recording ID.

These actions refer to the SAS Remote Control (Lawo/Studer/…). The documentation for the actions can be found here.

These actions refer to the remote control for DHD mixing consoles. The documentation of the actions can be found here.

Executes any fader start command on another mAirList instance, using REST Remote Control on the server side.

Select the hostname, port and optionally path of the REST remote to send the command to.

Authentication can be carried out via username/password, or an auth token.

The actions in this section refer to the MusicMaster Nexus API binding.

Looks for any unscheduled positions in the current playlist, and checks if they have been scheduled meanwhile, and if yes, replaces the dummy item with the actual audio item.

Syncs any changes made from the MusicMaster side in the current schedule. This is one-way synchronization from MusicMaster to mAirList! Local changes will be lost.