Brandon Casci wrote:
> Actually, a DJ does not hit the button. Right now I have ezstream sourcing
> icecast. It executes an external script, which hits an API to get a track
> uri. The web API contains my track selection logic.
>
> I was thinking of using liquid soap to handle requests, jingles, f
Actually, a DJ does not hit the button. Right now I have ezstream sourcing
icecast. It executes an external script, which hits an API to get a track
uri. The web API contains my track selection logic.
I was thinking of using liquid soap to handle requests, jingles, fallbacks,
hooks for live events
On Tue, Dec 16, 2008 at 7:26 PM, Romain Beauxis wrote:
> If you want to be able to reload the playlist, you have to use string.ref,
> which is at the moment the only way to define persistent values in liquidsoap
> (this is a classic issue with functional programming).
Romain meant non-persitent,
Le Tuesday 16 December 2008 18:42:50 Brandon Casci, vous avez écrit :
> When the playlist is
> over, the dj process just hits the API URL which gets a new playlist
> populated by my rotation logic. Can I do something similar with liquidoap?
Surely, yes !
I guess it should be done using a request.
Hello
It looks like liquidsoap meets most of my needs. The fallback and time based
playlist features are great. The only thing is, due to copyrights, there are
certain song combinations and frequencies I have to honor. In my existing
application, I call a web service (the dj process and the API ar
