lightningkite

Is there any object that will let through an initial message but then block all further messages. I will be using it to set buffer size in my live looper but don't want each subsequent recording to keep setting the buffer size afterward. Can anyone help me out?

need-to-let-through-initial-message-but-block-subsequent-messages

The solution I might use would involve onebang. It only deals with bangs, but you can whip up all sorts of solutions with it. There was a similar thread recently where there were several solutions presented. 

https://cycling74.com/forums/onebang-for-numbers

The solution I might use would involve onebang. It only deals with bangs, but you can whip up all sorts of solutions with it. There was a similar thread recently where there were several solutions presented. https://cycling74.com/forums/onebang-for-numbers


I can't get to a Max machine right now to create an example patch, but you can have a [trigger] object tied to the output of a [gate]. The [trigger] can pass through your info, then have second output to close the gate. You can use a [loadmess] or argument within [gate] so the patch opens with the desired [gate] outlet opened up. I do this often enough that I created a reusable patch for myself and called it something like "gate_autoclose".

I can't get to a Max machine right now to create an example patch, but you can have a [trigger] object tied to the output of a [gate].  The [trigger] can pass through your info, then have second output to close the gate.  You can use a [loadmess] or argument within [gate] so the patch opens with the desired [gate] outlet opened up.  I do this often enough that I created a reusable patch for myself and called it something like "gate_autoclose".


Thanks for the information guys. Everything is working now.

Need to let through initial message but block subsequent messages.