Hi,
>From liquidsoap -h input.harbor:
<snip>
* buffer :: float (default 2.)
Duration of the pre-buffered data.
* max :: float (default 10.)
Maximum duration of the buffered data.
</snip>
In more details, "buffer" is the amount of data that is pre-buffered
before the harbor input starts replaying that data inside liquidsoap's
pipes. While this data is being replayed, the amount of buffered data
can vary: go up when the network is fast (or the liquidsoap pipe is
slow or unused), or go down when the network is too slow (or you're
doing something not recommended which makes data flow too fast in the
pipes). The "max" setting is there to avoid that liquidsoap consumes
too much memory, and limits the amount of buffered data. It's crucial
to have max>buffer, but apart from that, I'd say you don't need to
care about "max".
On Wed, Feb 10, 2010 at 6:50 PM, em...@mccurly.de <em...@mccurly.de> wrote:
> liq often falls back to the playlist.
> or iss there any way, or howto, to avoid interruptions of the live
> broadcast?
Increasing the initial buffer will delay the next deconnection if your
network isn't good enough. A buffer can amortize local up-and-downs,
but cannot counter-balance an insufficient bandwidth. If you're
persuaded that the bandwidth shouldn't be an issue, there's also the
possibility that liquidsoap is going too fast compared to the harbor
client (I doubt it but it's been seen before); this would result in
very regular deconnection.
Hope that helps,
--
David
------------------------------------------------------------------------------
SOLARIS 10 is the OS for Data Centers - provides features such as DTrace,
Predictive Self Healing and Award Winning ZFS. Get Solaris 10 NOW
http://p.sf.net/sfu/solaris-dev2dev
_______________________________________________
Savonet-users mailing list
Savonet-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/savonet-users
