Hi Gabriel,

I think you've been caught by a recent update in all request queue
sources. Just check if you have a parameter named "conservative" for
request.dynamic(). If so, you can restore the old behavior by setting
it to true.

2009/7/18 Gabriel Afana <[email protected]>:
> It doesn't queue the next track and waits until just before the current song
> ends before queuing the next track.  Because of the design of my system,
> this destroys the entire scheduling.

Most people didn't do things like you do, and for them it was
impractical that liquidsoap resolved requests so much in advance. So
we changed our code to take into account the duration of the currently
played file in deciding when to prepare the next one.

I hope this solves your issue. By the way, if I understand correctly,
you're relying on log messages to interact with liquidsoap: I would
recommend that you use more solid means, like on_track() or
on_metadata() callbacks.
-- 
David

------------------------------------------------------------------------------
Enter the BlackBerry Developer Challenge  
This is your chance to win up to $100,000 in prizes! For a limited time, 
vendors submitting new applications to BlackBerry App World(TM) will have
the opportunity to enter the BlackBerry Developer Challenge. See full prize  
details at: http://p.sf.net/sfu/Challenge
_______________________________________________
Savonet-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/savonet-users

Reply via email to