Hi, On Sat, Apr 9, 2011 at 4:58 PM, Davit Barbakadze <[email protected]> wrote: > What does it mean "if you run several outputs that do not share much > (any) code"? Actually outputs that I run do share some code, like > several functions that mix in jingles, wouldn't this approach work in > this case? I'm getting: > Error when initializing source ...: a source cannot belong to two > clocks (wallclock_4814[src_4819[],src_4803[]], wallclock_4830[]).
Most operators must live within a single clock: their input and output streams must follow the same pace. The main exception is the buffering operator that uses a buffer to allow different paces at its input and output. Basically, if you have two outputs that rely on the same source, you can't separate them in two different clocks. (The error you get simply says this: the source at ... is shared between two clocks, which is forbidden.) The only solution is to use buffers to loosen the dependency explicitly. (You can find an example in the clocks documentation page, involving input.oss(), output.icecast() and output.file().) I hope this clarifies the situation and helps you go further. However, if you can't easily try the clocks "solution", don't spend too much time on it: it's not necessarily a solution. At this point I'm not sure what the source of the problem is: CPU, multiple cores, soundcard I/O, network lag? Can you eliminate some of those? Cheers, -- David ------------------------------------------------------------------------------ Xperia(TM) PLAY It's a major breakthrough. An authentic gaming smartphone on the nation's most reliable network. And it wants your games. http://p.sf.net/sfu/verizon-sfdev _______________________________________________ Savonet-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/savonet-users
