AllDay DJ - Some Progress

[caption id="attachment_112" align="aligncenter" width="564" caption="A screenshot of the in-development playout system."][/caption]

As some of you may have cottoned on to, there are two main strands to
AllDay DJ. The first being version 2, the current release. This has a
few bugs and version 2.3 is almost ready for release (it should be
available in the next few day). It brings a bug fix for weather VTs,
"drag and drop" player, a fully revamped database manager (it now works
in much the same way as the search system), move to prepared statements
(hopefully more secure, etc.), Winamp DSP support.

 

Quite a lot for a minor release! But all should be available soon (I just need to package it up correctly).

There is also progess on AllDay DJ 3 (the planned successor to AllDay DJ 2). This version will see a nicer database backend (it's based on NHibernate and thus can sit on top of a number of DBMS systems), proper multi-threading (slightly more overhead but properly makes use of multi-core systems), cleaner GUI, users (and associated audio walls), and hopefully much more.

Just to temp you, I've attached a screenshot of the development version of AllDay DJ 3 (click on it to see the full version). Though I would stress that this software is well away from release at the moment.

Playout Systems on Linux

Look in most radio studios, you'll find some sort of playout system. It makes sense in this day in age - low cost overnight, voice tracking, less errors (usually). However, you will find most systems running on the Windows operating system.

There is a good reason for this: why force change. Windows isn't exactly unstable when doing this sort of job. Also, take it from me, developing audio apps to work cross-os is a pain the the ass. This is especially when you want to layer tracks or use more than one sound card.

STAR is in a bit of an unusual position for a radio station. We operate Linux boxes (namely Debian) with no copy of Windows in sight. So, with most playout systems on Windows, what do we make use of?

Well, until recently, it's been an in-house botch job. This has taught us one lesson, don't trust Javasound to do the job.

With Java written off, we have a number of options: Campcaster, Rivendell, Digiplay and a Windows system running on Wine.

Starting with Campcaster. This was the first option we tried with STAR but it proved to have a few too many issues for us. For one, it doesn't log tracks played in live assist mode. Oops, bit of a show stopper there for an online radio station. Secondly, the configuration options are a little too exposed. You don't want people tinkering with settings on a radio station!

Rivendell is the other big Linux option. It's certainly aimed at the pro end of the market supporting a full scheduler and powerful playout system. Possibly even a little too much for us. It was actually decided against for STAR for two reasons: the MySQL requirement (we use PostgreSQL and according to the ITS liason will never see MySQL on the server) and the work required to make the scheduler tick. We're a volunteer organisation with a high tunover (students only stay for 4 years) so any system requiring a lot of work is not an option.

Wine is the Windows compatability system for Linux. It brings the ability to run Windows programs to the Linux desktop. Great, you may think, for letting us use the playout systems on our computers. Not quite. I could only find two playout systems that worked on Wine: StationPlaylist and mAirList. Both seemed to work OK but the cost factor (for StationPlaylist) and stability (we're relying on a compatability layer here) wrote off this option.

Now for the last on the list: Digiplay. This is Warwick University's in house job (not written in Java though). It has the benefits of being simple to use and sporting a web interface (I'm not sure of the merits of this but oh well). However, there are a few issues. Sue (the automation part) seems to simply be random select at the moment and there is no mass importer (apparently RAW just rip off of CDs). The last issue could be fixed by adapting our in-house import script.

Well, the working Linux playout system seems not to exist, well not for a small vountary station. Every option seems to have some sort of serious issue, whether legal (Campcaster), complexity (Rivendell), missing features (Digiplay) or technical (Wine).

I don't really see the commercial software developers really taking Linux seriously. Let's be honest, it's not really a big issue for most in this market. However, we need to choose a system. So what did we choose:

Digiplay.

Ah well, we'd better get cracking on the scripts and fixes to make it do what we need.

EDIT: Clarified the Digiplay and Wine issues. We didn't run Digiplay on Wine.

AllDay DJ to get Winamp DSP Support

The audio library AllDay DJ is built on top of has support for the Winamp DSP plug-ins. In fact a number of other systems built on the same library take advantage of this.

Basic support has been added to the system and I will be testing it on-air soon. The benefit to the end user is a wider choice of audio processing options.

I'm currently testing it with "Tomass Limiter" and it sounds cracking. Though there is a slight issue on the segues that I hope to clear up quickly.

If it works with the oddcast DSP, that could provide streaming support with minimal effort!

With a number of bug fixes, minor changes (drag and drop, cue in player), customers will be offered the option to upgrade to version 2.3 for free upon release.