[chuck-users] osc listener shred woes
gelfmuse at gmail.com
Mon Apr 28 03:13:30 EDT 2008
My thoughts exactly! So, I was able to get better performance (e.g.
performance at all) after turning AirPort off. Then, just as you
said, my problem was missed events. My first thought was that it was
the subclassed event, so I put a random delay between 1 and 10 ms
right before b.broadcast(). That didn't help much. Then I remembered
the bus error...
Putting the same random delay just after
oe => now;
Made a huge difference. I'm not sure that it has to be a random
delay, though. I'll do some experimenting. Apparently, the various
shreds step on each other trying to access the OSC messages somehow.
I'm not sure how it works under the hood.
On Mon, Apr 28, 2008 at 3:03 AM, Atte André Jensen
<atte.jensen at gmail.com> wrote:
> mike clemow wrote:
> > b.broadcast();
> I think you should try adding:
> 1::samp => now;
> here (right after broadcast'ing). Not sure why, but it seems that handling
> more events in the same time-slice is problematic (or I did a mistake
> similar to yours). My problem wasn't seg faults, but missed events, so I
> might be wrong, but it might be worth a try...
> peace, love & harmony
> http://atte.dk | http://myspace.com/attejensen
> http://anagrammer.dk | http://modlys.dk
> chuck-users mailing list
> chuck-users at lists.cs.princeton.edu
More information about the chuck-users