Hi! The length parameter says how much data should be available in advance. In conservative mode, only the queued data is taken into account as "available in advance". In non-conservative mode (now default) the remaining time of the current track (if any) is added to that amount.
One last thing concerning the queue: the duration of the queued files is only approximated, and the default duration of 30s will often be used. On Mon, Dec 27, 2010 at 9:58 PM, Jean-Francois Mauguit <[email protected]> wrote: > Length is harder to understand. Is it the length of the remaining played > sound before liquidsoap calls the script ? > For eg, if i put 60., is liquidsoap calling the script defined in the > request.dynamic 60 seconds before the end of the currently played track ? Yes in non-conservative mode. But with 60, since the default duration is 30, there is a possibility that liquidsoap queues two files to get 60s of available data before starting playing the first one, at which point it will realize that it's much longer than 30s. > If I don't put length, liquidsoap is calling 10 seconds before the end of the > currently played track which is sometimes to short (especially if the script > failed to retrieve information from our primary server and has to switch to > the secondary). Yes, 10s can be too short when request resolution is complex. I hope my explanations will allow you to fine tune your settings. Cheers, -- David ------------------------------------------------------------------------------ Learn how Oracle Real Application Clusters (RAC) One Node allows customers to consolidate database storage, standardize their database environment, and, should the need arise, upgrade to a full multi-node Oracle RAC database without downtime or disruption http://p.sf.net/sfu/oracle-sfdevnl _______________________________________________ Savonet-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/savonet-users
