[sc-users] Re: OSCresponderNode: limits on simultaneity?

[Dan Stowell]

No-one? I'd be really grateful for a response from anyone who's used
OSCresponderNode plenty. I'm still getting these dropouts, and I've
tried everything I can to eliminate them.

Best
Dan



2006/11/30, Dan Stowell <danstowell at gmail.com>:
> Hi -
>
> Is there any limit on an OSCresponderNode firing many times
> near-simultaneously? i.e. could its function be running multiple times
> at the same time? Not sure how it is threaded.
>
> I'm running some experiments which involve a simple OSCresponderNode like this:
>
>         oscresp = OSCresponderNode(server.addr, '/tr', { |time, responder, msg|
>                 rawtimesfiles[msg[2]].write(msg[3].asString ++ "\n");
>         }).add;
>
> ...and getting some definite dropouts in the values being written to
> the files. Typically about a dozen synths could be sending a trigger
> back at exactly the same time.
>
> I'm pretty sure the synths' triggering is firing since the audible
> results don't sound like they're missing things out, so either the OSC
> messages aren't all being sent, or they're not all reaching the
> client, or there's a problem with trying to deal with them all
> concurrently.
>
> Thanks for any tips -
> Dan
>
> --
> http://www.mcld.co.uk
>


-- 
http://www.mcld.co.uk