Hi all! 2011/12/30 David Baelde <[email protected]>: > On Thu, Dec 29, 2011 at 3:54 PM, Facundo Suárez <[email protected]> wrote: >>> What LS Team told us to avoid a buffer overrun, is to create a sink to flush >>> the buffer. >> >> Is it a better solution? Can you explain how to set it up? Please !! > > The solution Frederic described, using output.dummy, is the "sink to > flush the flush the buffer". I agree with his description. To avoid > issues with names, however, there's a simpler recipe: replace > input.harbor(...) with output.dummt(input.harbor(...)). > > Now I should insist that this is not a solution in general, it only > avoids overruns caused by liquidsoap not using the source. If you have > LOTS of overrun messages, you're probably in this case. Otherwise, > probably not. > > Also, we should think of a way to not need the dummy output to avoid > stupid overruns like this.
I had looked at making input.harbor an active source in the past. I did not really understand well how it worked at that time, but it also was not a good thing as some people may want to have a non-active source. It would be nice, however, to have a parameter for that, but I don't this it'll work with the type system. Another alternative would be to alias output.dummy(input.harbor) to something like input.active.harbor.. Romain ------------------------------------------------------------------------------ Ridiculously easy VDI. With Citrix VDI-in-a-Box, you don't need a complex infrastructure or vast IT resources to deliver seamless, secure access to virtual desktops. With this all-in-one solution, easily deploy virtual desktops for less than the cost of PCs and save 60% on VDI infrastructure costs. Try it free! http://p.sf.net/sfu/Citrix-VDIinabox _______________________________________________ Savonet-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/savonet-users
