multiple unique bpatchers
can someone help me find a link to a tutorial/reading on instantiating multiple independent instances of a bpatcher? the built in tutorial doesn't include this (or i can't understand it) and I'm having trouble understanding how to make instances not reference each other. I think I understand using patcherargs - but I'm wondering about simply connecting to inlets on each instance. IE create a bpatcher with a few inlets. Instantiate it a few times, connect stuff to those inlets on each instance; have each bpatcher process their input independently. Thanks!
independent from each other is normally how bpatchers work. unless you are using send/receive, global variables, or named objects with fixed names.
what part, what objects in your bpatchers current do not work?
Hi Roman. Thanks for your time. In building a demo patch to post my issue, I realized my mistake! I was using #0 s/r incorrectly. The Bpatchers are working as you describe.
Cheers.
This is what I came up with, standing on the shoulders of giants:
1) Create the instance with @args [prefix] (naming it [prefix] as well)
2) Pass the prefix on to the "prepend" in the bpatcher
3) Then send any data to [prefix].
The output is [prefix] [data], so that you know where it is coming from.
Here is the whole thing:
And then you build a routine to put them all where you want them.
This is where things get complicated.
Watch this space.