I've updated the roadmap:
http://wiki.sourcefabric.org/x/R4Nw

We release approximately every six weeks.

Perhaps you could give me some overview of what your plans are and we could
see how we might work together?


On Thu, Aug 18, 2011 at 5:41 AM, Albert FR <
airtime-dev@lists.sourcefabric.org> wrote:

> **
> ok, good to know [image: Wink]
> I saw the APi will be only available on the 2.1, that's correct ?
>

We havent built the API interface yet (only the engine), so we need ideas
from you as to what you want it to do.

Could you give us some background as to what you do? Do you work for a
radio station? What are you trying to build?

What are you working on though? What is the project?

Are you allowed to say what you are working on?

Paul Baranowski wrote on Thu, 18 August 2011 14:30

We havent built the API interface yet (only the engine), so we need ideas
from you as to what you want it to do.

Could you give us some background as to what you do? Do you work for a
radio station? What are you trying to build?

Hi, I'm a developer/manager with KRUI-FM, and I thought I'd jump in here with some thoughts, since we have a few specific needs that we hope an API can meet. We really enjoy Airtime and we hope to transition both our stations to the software within the next year.

We are looking to implement two major features which we need in Airtime to put the system on our main station. The first is a "Button Bar" feature -- a graphical display of a grid of buttons, each set to a specific playlist or song file value. If the button is a playlist, it would play a track (a song or, in our case, a PSA, grant spot, or Legal ID) at random from the playlist, and then would stop after one track. This feature is essential to our daily routine with our current (old) software, so much so that I'm surprised it's not in Airtime already .

The second is some sort of auto-populating shuffle playlist of the entire song library. This algorithm should be able to select a "legal ID" to play at the top of every hour, and select spots to play intermittently as well. Ideally we would like to be able to fine tune the algorithm as much as possible, perhaps, for example, selecting a grouping of heavy emphasis tracks more than others.

With these two features, we will be able to implement Airtime as a better automation system than our current, 7-year-old proprietary software.

From there, it would be wonderful to get Airtime talking with our website music logging system, which we wrote in house. These calls would be simple enough, I think, just a list of all the played tracks system-wide, with artist, album, song name, and a timestamp.

Hi, Albert. Thanks for the response.

Albert FR wrote on Wed, 12 October 2011 07:43

the most of you want to do is explain and possible directly now

you you just have to modify the ls_script.liq

an example : http://savonet.sourceforge.net/doc-svn/complete_case.html

What we are wanting to do is to create a button bar which would play our grant spot rotations, legal ID rotations, etc. on push. Forcing promos every 5 songs (or at a certain time of day) is great for all-digital music stations, but we still plan to have many shows using CDs and vinyl well into the future, and that's not even mentioning our talk shows. Our DJs need to be able to press a button to play a legal ID right away, not by selecting a playlist and then selecting one of the legal IDs to play, since there are frequent cases where DJs need to fill time quickly when something unexpected happens. It doesn't have to be the 4x4 grid we're used to, but the core concept of having a few buttons that will select a random track from the rotation and then play the track is still necessary. Creating a UI feature like this would have to be at the Airtime level, not the Liquidsoap level (correct me if I'm wrong).

That said, it does look like Liquidsoap would solve most of our issues with an automation mode and with playing legal IDs, promos, etc on a schedule. But it would still be nice to have a top-level feature that allows us to automate programming (or at least mass populate a playlist), so we don't have to sacrifice usability to get things working. After all, the main reason we love Airtime is that it's very user friendly.

You can always suggest some features for our upcoming hackathon for Airime. If they are doable in 48hours and there's enough pressure from you guys - who knows:) http://forum.sourcefabric.org/index.php/t/4051/

J.