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

[Dan Stowell]

Josh,

Thanks for this - yes, it's possible that kind of limit is what's
hitting me. I suppose a UGen to store numbers sequentially in a buffer
could be one solution - back to Xcode for me then...

Thanks
Dan


2006/12/1, Joshua Parmenter <josh at realizedsound.net>:
> Hi Dan,
>
> One thing I noticed while trying to grab audio data and throwing it
> into the lang from the OSCresponder is a limit of about 100 triggers
> per second... anything more then that, and there was overload and
> missed triggers. I wound up making a UGen that would do the
> calculations for me on the Server, then I would output a value to a
> control bus. I'm not sure if you can do something similar in your
> approach, but this is the only type of 'limitation' that I have ever
> hit with the responders.
>
> Josh
>
> On Dec 1, 2006, at 9:46 AM, Dan Stowell wrote:
>
> > 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
> > _______________________________________________
> > sc-users mailing list
> > sc-users at create.ucsb.edu
> > http://www.create.ucsb.edu/mailman/listinfo/sc-users
>
> ******************************************
> Joshua D. Parmenter
> http://www.realizedsound.net/josh/
>
> "Every composer – at all times and in all cases – gives his own
> interpretation of how modern society is structured: whether actively
> or passively, consciously or unconsciously, he makes choices in this
> regard. He may be conservative or he may subject himself to continual
> renewal; or he may strive for a revolutionary, historical or social
> palingenesis." - Luigi Nono
>
>
>
> _______________________________________________
> sc-users mailing list
> sc-users at create.ucsb.edu
> http://www.create.ucsb.edu/mailman/listinfo/sc-users
>


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