ceelopez

When using multiple bpatchers is it possible to stop all bpatchers receiving midi other than the one that is selected via a tab?

stop-bpatchers-from-recieving-midi

[gate] is your friend. Just close is when the bpatcher is not selected.

Hi Jan, thanks for the reply. Do you by any chance know how to set the gate up to work in this way when all the bpatchers are running into a thispatcher like in this

I don't have time to document these right now but you can probably figure them out. Basically, there's the ability to have a global passcode. When you set that (or change it) other objects will get initialized if they have the same passcode, i.e.e through the BangOnGlobalPasscodeMatch or the IntOnGlobalPasscodeMatch

There's also a PassthruIfMatchesGlobalPasscode and if you feed your raw MIDI through that, then it will only get through if the passcode of that particular instance matches the global pass code.

The system uses regular expressions so you can have some patchers that will respond to multiple passcodes.

I use this all over the place to quickly switch from one group of patches to another without having to reload anything.

The objects are attached in the zip file


I use route objects and named patches for this. Basically I have a [route #1] at the very input of the patcher, and then the first argument is the name of the patcher.

That way I can do messages like "mypatcher midinote 40 100". It's like pseudo-osc - in fact, my osc gets parsed the same way.

Oh, and in this scenario it's easy to make it[route #1 all] and just sum their outputs, so that you have a global as well.

Thanks for the replies guys. I'm definitely gonna be having a lot of fun trying out your suggestions.

This is my very first attempt at trying to build something in Max for Live so I am very much at the newbie stage. I am actually building a midi cc controller with multiple tabs. The reason for my inquiry is that I have the first 8 dials in my first tab automapped to index 1-8 so that the rotary knobs on my hardware controller are automatically assigned to those dials. I would like it so that when I select the second, tab my hardware controller's knobs will be automatically assigned to the dials in that bpatcher too.

The problem is this. If I have 8 dials in my first bpatcher automapped to index 1-8 and then the 8 dials in my second bpatcher automapped to index 1-8 and then the 8 dials in my third bpatcher automapped to index 1-8, turning a knob on my hardware controller seems to randomly control one dial in any of the three bpatchers regardless of which bpatcher is selected via the tab. Will any of these solutions solve this problem or am I fighting a losing battle here?

Thanks for the replies guys. I'm definitely gonna be having a lot of fun trying out your suggestions.
This is my very first attempt at trying to build something in Max for Live so I am very much at the newbie stage. I am actually building a midi cc controller with multiple tabs. The reason for my inquiry is that I have the first 8 dials in my first tab automapped to index 1-8 so that the rotary knobs on my hardware controller are automatically assigned to those dials. I would like it so that when I select the second, tab my hardware controller's knobs will be automatically assigned to the dials in that bpatcher too.
The problem is this. If I have 8 dials in my first bpatcher automapped to index 1-8 and then the 8 dials in my second bpatcher automapped to index 1-8 and then the 8 dials in my third bpatcher automapped to index 1-8, turning a knob on my hardware controller seems to randomly control one dial in any of the three bpatchers regardless of which bpatcher is selected via the tab. Will any of these solutions solve this problem or am I fighting a losing battle here?


Stop bpatchers from recieving midi