Hey, Tnx for the detailed information, im going to try on playing with the lenght of the queues and stuff.
On Sun, 2008-05-11 at 13:19 +0200, David Baelde wrote: > Hi, > > As Romain said, there is a not-so-visibly-documented detail about the > queues. In liquidsoap, we like our operators to be sure that they can > stream audio. The extreme case is when they are infallible, and thus > suitable for streaming to listeners. In other case it simply > guarantees that you can switch safely to some source, it's ready > stream won't disappear in the meantime. > > So, queues have two parts. The primary queue contains ready requests, > that is ready chunks of stream. The secondary queue contains requests > that have not yet been resolved -- resolving means downloading and > checking the track. You can see details about these two queues in the > "trace <RID>" command output. Because the primary queue is about > assurance of streaming, you can't delete anything from it. However, > there is no reason except software architecture for not being able to > exchange two ready songs, and a couple other harmless changes. > > All in all, the design could probably be enhanced, and will probably > be. This probably won't occur soon, unless someone makes a good > proposition (that means simple). Don't hesitate to give a try. > > Until a better design, you probably want to minimize the number of > tracks in this annoying primary queue. You can do that, thanks to the > parameters "length" and "default_duration" (see liquidsoap -h > request.equeue). For example, use request.queue(length=20., > your_source) and you'll have only one track in advance in the primary > queue instead of two currently -- or is it really three currently ? Afaik its 2. > > Cheers, Regards, Frank (Aim) ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ Savonet-devl mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/savonet-devl
