A new version of the current development release mAirList 3.0 has been released today. mAirList 3.0.3 contains numerous bug fixes and enhancements. Owners of an SAS-enabled broadcast mixer from Lawo can enjoy the new remote control interface to it.
mAirList 3.0.3 can be downloaded from the download section on www.mAirList.com.
Here’s the complete list of changes:
I’m happy to announce that the latest version of the current development release, mAirList 3.0.2, has been released today. It contains numerous bug fixes and improvements (in particular lower cpu utilization), as well as some exciting new features.
Most notably, it is now possible to set “track markers” to any position inside a file, assign a artists and title to them, and include them in the logging mechanism. This is very useful when you have long audio files of e.g. pre-recorded shows but want to the separate songs broadcasted in that show appear in your website playlist in real time. The markers can be edited by hand, or you can import a cue sheet (*.cue) file.
mAirList 3.0.2 is available from our download page.
Here’s the complete list of changes in this version:
Deutsch
English[*] sqlite3.dll now included in download archive
[-] Fixed time not cleared correctly
[*] RadioDB: support for Ramp2, Ramp3, StartNext, HookIn, HookFade, HookOut
[-] Added "MinChars" setting in GUI.ini, section "DatabaseSearch"
[*] mAirListDB: easier setup and folder/storage administration
[+] Genre is imported from ID3v1 und ID3v2
[*] Item Properties dialog: removed obsolete "Details" tab
[-] DB: "Delete folder" doesn't work
[-] Notification Scripts: OnPlayerEOFWarning not working
[+] Added remote commands for toggling cart player loop and hook mode
[*] Redesigned action configuration dialogs
[*] Changed action list XML format
[-] Old style browser: all tabs displayed in one line
[+] Added actions for loading playlists from databases
[+] Database playlist browser: added load/append menu
[-] High CPU load when opening long playlists
[-] Player might hang at Cue Out when Cue Out is close to EOF
[-] DB: Database browser shows deleted artists
[-] Cartwall window position not restored correctly
[*] Changed event list file (*.mle) format, can still read old-style files
[*] Parameters of all serial ports are now managed on a central configuration
page Miscellaneous -> Serial Ports. In the configuration of SAS, D.MAX and
Serial Remote, as well as the "send data to serial port" action,
only pick the port now. Check configuration after upgrade!
[+] Item properties dialog: New page "Cue Data"
[*] Changed PlaylistItem XML format to reflect new cue data structures
[*] Scripting: Dropped ICuePosition, added ICueData. Also introduced new
GetCuePosition and SetCuePosition methods in IPlaylistItem for easier
access to cue position values.
[-] PFL cannot be switched off during automation
[+] Track marker cue data is included in logging (start log only)
[-] Scripting: Serial port closed in between calls to ComPort()
[-] PFL Player does not send PFLOff message to notification scripts
[-] Notification scripts: Several procedures not called
[*] Notification scripts: Removed "Item" parameter from all player-related
events. PlayerControl might be nil now if the player has been destroyed
already (e.g. when the Extra PFL window has already been closed at the
time the notification script is called)
[+] Notification scripts: Added OnPlayerStateChange and OnCartPlayerStateChange
One purpose of this blog is to give you a little background information on the development of mAirList, talk about things which could be done or will be done, and initiate some discussion about the future of this software. This is what the new category “Future and Research” is for, and you are welcome to leave your comments.
As mentioned earlier in the forum, one of the prominent (although not too visible) features of mAirList 3 is that it is very modular. First, we have this set of modules you can see in mAirListConfig, each of which can be enabled or disabled depending on your license file. This makes it very easy to offer different editions of mAirList, as I now do. These modules, along with the components which make up the GUI of mAirList, can easily be put together to build a new software. In this article, I will show you a small example which gives you an idea of the consequences of this ultra-modularity. Read the rest of this entry »