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?
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.