Hi Peter, Although it sounds like a good idea to make flows asynchronous, it seems not so important right now, because a network latency will create a latency in the icecast output anyway. The key thing in my opinion is to protect the ALSA stuff from the latency, because it tends to not recover very well as the logs show.
So, it'll probably help if you isolate ALSA in a separate clock -- I say probably because in principle there is already a buffer in your ALSA input, which should provide such protection. Another thing to try (with or without a separate clock) is pulseaudio instead of ALSA; it tends to cope better with timing issues. Hope this helps, -- David ------------------------------------------------------------------------------ Special Offer -- Download ArcSight Logger for FREE! Finally, a world-class log management solution at an even better price-free! And you'll get a free "Love Thy Logs" t-shirt when you download Logger. Secure your free ArcSight Logger TODAY! http://p.sf.net/sfu/arcsisghtdev2dev _______________________________________________ Savonet-users mailing list Savonet-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/savonet-users
