IS there any way to filter out bangs, whilst allowing valuable information like number, to pass through.
In this patch, any change in the number box at the top sends out a bang. The match at the bottom blocks these bangs until the "one" is detected, at which point it lets the one through, along with all the bangs. Instead of just a single bang.
Please help this tired and amateur max learner out.
Sorry if this is short, it'sthe 3rd time i've typed this out. my computer is hobbling.
I did what both you guys suggested, and it didn't act as planned.
I can get a number through, but I want the number, without all the bangs that come through with it. One is fine, i'd expect that because the number changed. But once it isn't changing any longer, I'd like the bangs not to come through.
This code has the route object in, with route bang as suggested.
> I did what both you guys suggested, and it didn't act as planned.
> I can get a number through, but I want the number, without all the bangs
> that come
> through with it. One is fine, i'd expect that because the number changed.
> But once it isn't
> changing any longer, I'd like the bangs not to come through.
You need to use the [change] object. See my modification of your example
Philip Reeder wrote:
> Hello, I've been using max for a little while, and there's one
> problem I keep coming up against.
> Bangs seem to flow through the whole of a patch. Is there any way to
> filter out a bang (that might be caused by a metro at the top of a
> patch for instance), yet allow numbers etc. to pass through?
Did you ever read the help file of button? I guess not!
This is very basic. button accepts anything and converts it into a bang.
Your example patch seems to have nothing to do with the above question,
none of the patchchords does carry a bang and toggle never outputs a bang.
If you want to filter any type, look into route. [route bang] for
example would filter bangs.
I added some comments into your patch, which might explain some of your