Hi, Concerning your clock question:
2010/12/29 Cees van Egmond <[email protected]>: > Having the Clock on the output.icecast instead on the input. Is there a > special reason? The 1.0.0-beta1 code isn't working on the current svn > version. The reason for the difference is that now, the OSS/ALSA/etc inputs force their own clocks (this makes sense, the soundcard API guides the synchronization). So instead of putting the input in one clock and leaving the output in the default one, we have to write it the other way around: leave the input in the OSS clock and put the output in a separate clock. I think there's more detail on the clock page of our doc. Notably an explanation saying that as long as you use buffer() the clock() isn't strictly really needed -- but it's very preferable to leave it. I'm sorry this is a bit short, but I'm leaving for a week of holidays. 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
