[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [sc-users] Re: OSC trouble Solution
i must stress again that the network and osc are your friends.
the limitations begin with machines which may start choking trying to
process all the data...
i guess this is the main design issue to consider.
you start asking yourself existential questions such as "what's the
difference between listening 250 synths and hearing density 250" etc.
our decision was to interpret those matrices dynamically. meaning
that we would get all the matrix data into sc, look at it (sclang),
and send just enough grains to the server that would sound like the
data but not every point has to be sent.
again, this is not because we couldn't send them, it's because they
would kill the server...
btw, not sure how come, but on relatively slow windows machines the
server would play 3000 synths (simple SinOsc.ar) while on relatively
fast macs it would choke on 600-700... again - no way to test that by
listening!
but server reports well...
tom
On 6 Jan 2006, at 17:06, JostM wrote:
tom tlalim wrote:
>I need to poll bus values, it would cause a hell of a lot of
messaging via SCLang if I am polling 24*6 busses at a rate of 24/
seconds.
i've had great experience with lots of messaging through sclang.
we've been sending 90 arrays of 400 slots each every second which
were then parsed by sclang, analyzed, interpreted and sent as
grains to the server,
That sounds very promising and is very helpful information, since I
was a bit afraid of reprogramming everything only to find out that
there was a bottelneck in the messaging. I haven't figured out how
to use javaosc yet, and if I don't soon, I may use SClang as a relay.
thanks very much.
jostM
_______________________________________________
sc-users mailing list
sc-users@xxxxxxxxxxxxxxx
http://www.create.ucsb.edu/mailman/listinfo/sc-users
....................
www.tomtlalim.tk
www.club-mtk.tk
www.tangiercluj.tk
....................