Romain, Just to give you guys a heads up, I already built a DJ Cron, which takes care of everything for us... It even tells us:
Now Playing Last Played Next to Play Records listener peak information during the set, and on finish, and will also be responsible next to make sure we have a perfect schedule down to the second, by carefully choosing what to play on the main stream. When all is done, I'll be sure to send you guys a success story for Liquidsoap! Thanks again for helping me!!! :) Nathan -----Original Message----- From: Romain Beauxis [mailto:[email protected]] Sent: Wednesday, September 09, 2009 9:43 PM To: Nathan Huebner Cc: [email protected] Subject: Re: [Savonet] #303: Large tracks take long to load Le mercredi 9 septembre 2009 21:32:15, vous avez écrit : > Liquidsoap says, ok I'll load this, and Oh since I see this is the main > fallback for receiving music, I'll go ahead and load it again! Now I have > two of the same track ready to play (...).. > > I just need to know how to tell Liquidsoap what to load. I don't know SH > programming, I'm actually a pure PHP programmer. Ok, please apologize for my previous assumption then... > But it's a real mystery > here what your software wants to receive, and how it should be received. > It's been a guessing game. The thing is that liquidsoap wants to keep in advance a queue of some requests in order to make sure that it will always have something to play. Hence the two songs that you see on the initial startup. Provided you have liquidsoap 0.9.1, you can however, use the new behaviour which will allow only one song to be requested at once. What you need is to do: request.dynamic(conservative=false, length=5., (...) That way, liquidsoap will estimate the length of the current song and only query for a new one when there are 5 (estimated) seconds remaining. The reason for this being an estimation is because mp3 format, for instance, does not allow a reliable length computation, hence computing the total length needs the decoding of the whole song, which we want to avoid :) > Once I can dynamically talk to liquidsoap using the request.create (without > every request being a duplicate, and without liquidsoap needing a new > fallback to facilitate it during this dynamic method), I'll add a fallback > playlist later. Right now I'm focusing on how to have full control over > liquidsoap using request.dynamic, so I can begin writing a scheduler in > PHP. Ok. I hope that with the above settings, you should have the full control of the scheduling in liquidsoap. I wish you success in writing a scheduler in PHP :-) Romain ------------------------------------------------------------------------------ Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july _______________________________________________ Savonet-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/savonet-users
