[Savonet-users] Shampoo, a webradio administration platform

[okay_awright <oka...@dd...>]

Hi everyone,

I'm a long time user of Liquidsoap (since 0.7 IIRC), it's rock-solid and
its features are amazing. And it actually is in production for my web
radios since that time, without interruption.

In order to manage web radio stations from A to Z, I've just developed a
web-based solution that takes care of everything Liquidsoap doesn't.
I've called it Shampoo - because the two together provide a rather clean
solution IMO.
It's based on ideas and concepts borrowed from the old Radiopilote, my
past similar (and close source) platform - that suffered from
limitations my users were fed up with, workflows from real radio
stations, and my own experience as a web radio host (for 3 years now).

A few features are still missing and of course bugs need to be ironed
out before it's fully operational. But it's really near final completion.

It uses webservices to communicate with Liquidsoap - because the
application is quite modular, and tasks can be split between different
machines that need to communicate all the time, hence webservices.
I've got an experimental Perl adapter that takes care of the webservice
layer to speak with Liquidsoap, via request.dynamic() and calls to
system(), get_process_lines() and get_process_output(). But since radio
timetables are now handled by Shampoo, I have some difficulties making
the two behave well together.
I'd like to know if, and how, Liquidsoap can:
-broadcast a specific track at a specific time, or at least make sure an
entry from the queue won't be played before some time stamp. Like adding
a new time property to Liquidsoap's internal queue. This timestamp is
dynamically computed and cannot be specified in the configuration file.
-can play a track for a specified duration only. Like before, this
duration cannot be part of the configuration file.
And, finally, if a webservice of some sort (REST, SOAP, whatever) is
planned in replacement or to complete the Telnet interface.

Maybe we can work out something together, if you think these features
could be interesting to add, like a communication interface and more
convenient bridges between the two applications.
I can explain in detail how things currently work in Shampoo if you're
interested.

The project has just been published for public consumption and I'm
actively looking for collaborators and contributors. It's released under
one of the GPL licences so feel free to take a look.

http://java.net/projects/shampoo
http://shampoo.ddcr.biz/pages/Home
https://www.ohloh.net/p/shampoogwt

-- 
best regards,

okay_awright
<okay_awright AT ddcr DOT biz>