Jun 28, 2007 at 6:59am
Why does the select object output “symbol bang” when it receives a bang, but any other input (that doesn’t match an argument) seems to pass through the right outlet unchanged?
I commonly need to intercept a specific message and handle it, otherwise pass the input along unchanged. Because of “symbol bang” I have gotten in the habit of using route instead of select. In my experience, this behavior just gets in the way of what I am trying to do, but I figure there must be a reason for it?
The only info I could find on it was this old post:
And I thought perhaps this behavior could be used to distinguish between a true bang and a symbol bang, but that doesn’t seem to be the case. I’ve included a patch I was using to investigate this behavior. I also tried using the printit external but it didn’t shed any light on this situation.
Jun 29, 2007 at 8:51am
Adam Murray schrieb:
I’d call select an oldtimer, which was intended for single values. Just
A long time the manual claimed to pass everything which doesn’t match to
Jun 29, 2007 at 11:54am
I’m asked to sync pictures to the beat of fairly straightforward
I’m interested in alternative methods & tips for beat detection in
Jun 29, 2007 at 3:33pm
What I’ve done in the past is take a look a what I’m trying to use as
On 6/29/07, Zip Boterbloem
Jun 29, 2007 at 4:55pm
Your idea about filters is a good first step. You might have better
Have you trained bonk~? If you haven’t then this will be a problem, as
There’s a paper from the ICMC on bonk~ (IIRC it’s cited in the
Hope this helps,
You must be logged in to reply to this topic.