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, fallbacks, > hooks for live events, and all that related stuff, but have my primary > playlist still sriven by my API.
If it's really a pull behavior that you need then request.dynamic() fits the bill. As usual, beware: unlike ezstream, liquidsoap will prepare tracks in advance before playing them (you can tweak the parameters of the preparation queue, see liquidsoap -h request.dynamic) so you might want to split your current API into a submitting and a feedback function (which would be called on_metadadata() when the track is actually being played). There are a couple mails on the list about that. Have fun, David ------------------------------------------------------------------------------ SF.Net email is Sponsored by MIX09, March 18-20, 2009 in Las Vegas, Nevada. The future of the web can't happen without you. Join us at MIX09 to help pave the way to the Next Web now. Learn more and register at http://ad.doubleclick.net/clk;208669438;13503038;i?http://2009.visitmix.com/ _______________________________________________ Savonet-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/savonet-users
