Le Wednesday 08 April 2009 20:44:41 Robert McAuley, vous avez écrit :
> Hello all,
Hi !
> I run a radio station where users request and then vote for what song
> they want to hear next. The "voting" part is critical - each song is
> run through an election, and then that song is played immediately as
> the next song. The process is controlled via an executable program,
> and I have been using Ices' "script" input to handle this.
>
> This "immediate decision" process is the problem I am having with
> LiquidSoap and its dynamic.request input. On start of LiquidSoap, it
> executes the script twice, always keeping one song in queue ahead of
> the one currently playing. This makes the voting process on my site
> not immediate, which is not desired behaviour from my perspective.
>
> I have tried setting the "length" setting to "1.", however, that
> hasn't changed the prefetching behaviour.
>
> Is there a way to stop dynamic.request from prefetching? Or must I
> use JACK or something similar to make sure LiquidSoap does not try
> prefetching?
Ok, I understand a bit better now your issue :)
Have you try to reverse the behaviour ? I mean that, instead of letting
liquidsoap pull the next song, use a request.{queue,equeue} and push the
songs as soon as they are elected ?
In this case, the behaviour should be much more immediate, but you would have
to provide a fallback source for the cases when there are no next song on the
queue..
Romain
------------------------------------------------------------------------------
This SF.net email is sponsored by:
High Quality Requirements in a Collaborative Environment.
Download a free trial of Rational Requirements Composer Now!
http://p.sf.net/sfu/www-ibm-com
_______________________________________________
Savonet-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/savonet-users
