This is an old revision of the document!
Table of Contents
mAirList 6.0
THIS PAGE IS WORK IN PROGRESS!
This page describes the new features and other notable changes in mAirList 6.0.
Note that not all features are available in all licenses/editions.
The complete changelog can be found http://download.mairlist.com/mAirList/v6.0/Changelog.txt here.
New Features
Playout
Database and Scheduling
Other
Important Changes
User who are upgrade from earlier version should read the following note carefully, because some changes in this release may break existing configurations or workflows.
No "Desktops" anymore
mAirList 6 drops the “desktop” feature found in earlier version. Instead, the playlists(s), open cartwall tabs, and open browser pages, can be saved separately in .mlp
, .mcpx
and .mlb
files. Likewise, there are now default files for all three kinds (default0.mlp
, default.mcpx
, default.mlb
, found in the config
folder) which replace the earlier standard.mlt
desktop template. You will find commands to save these default files in the respective menus of the playlist, cartwall, and browser.
Single Event Scheduler
There is now only one, global Event Scheduler per playout instance, accessible through the Events button in the main toolbar. The yellow events button was removed from the playlist control bar.
No Hook Mode anymore
The old Hook Mode feature found in the playlist players and cartwall was replaced by the revamped Hook Container items; you can find commands to create hook containers, and add them to the playlist or cartwall, in the playlist context menu.
Removed "Hide played items" option
The Hide played items option and button was removed from the playlist configuration and control bar. Played/skipped items will always remain visible until they are eventually moved to the Recycle Bin.
Logging On Air status
When playback of an item is started, mAirList will remember whether the instance was in “on air” or “off air mode” at that time. This flag is applied when doing “stop logging” at the end of the playlist: If a logging interface is set to operate only in “on air” mode, the stop logging will always take place if the item was started in on air mode, even if you switched to off air in the meantime. This will give consistent output in start/stop logging.
The on air status is also passed as an additional parameter to background scripts using the OnItemStart' and
OnItemStop'' procedures. You must manually adjust the definition of the procedures when migrating old script code to mAirList 6.
Old:
procedure OnItemStart(Item: IPlaylistItem; Region: byte; UniqueID: string); procedure OnItemStop(Item: IPlaylistItem; Region: byte; UniqueID: string; Duration: TTimeValue);
New:
procedure OnItemStart(Item: IPlaylistItem; Region: byte; OnAir: boolean; UniqueID: string); procedure OnItemStop(Item: IPlaylistItem; Region: byte; OnAir: boolean; UniqueID: string; Duration: TTimeValue);
Live Feed devices
In earlier releases, the input audio device for Live Feed items was set directly inside the item properties dialog. In mAirList 6, you only select one of 8 Live Feed Input devices now, and the actual assignment to a physical audio device is done in the Audio Devices section of the config app. This facilitates the scheduling of Live Feed items from other computers than the actual playout PC.
DBServer authentication
mAirListDB Server uses a new style of user authentication now, designed along the license of the popular OAuth2 standard.
On the server side, there is a brand new user management dialog where you create or modify users and their respective permissions.
On the client side, no username/password is stored in the local configuration anymore. Instead, you log in in order to retrieve an authentication token, which is then used to perform the actual database access.
REST remote control authentication
The REST remote control uses the same new user management and authentication found in the DBServer.
Note to developers: Anonymous access is not supported anymore. While you can still use HTTP Basic authentication with username and password, we recommend that you use the new OAuth2-style authentication end point in order to retrieve an auth token, and then use HTTP Bearer authentication.