Beep

So I've knocked up this pretty simple patch:

I want to have multiple instances of it, so I'm opening it up through several bpatcher's within another patch. This works great for 5, 6 iterations but any more than that and my computer freezes up, max crashes and I get slightly closer to punching my computer. Nothing heavy duty is occurring within the patch, it doesn't even have any DSP elements, any idea what I'm doing wrong? I can include information regarding the functionality of the patch if you need it, however its just the multiple bpatcher instances that are causing the ball ache, the patch itself works just fine.

bpatcher-hell

So, through a process of elimination it looks like its this bit of the patch causing the grief:

any ideas why? I kind of need to send these messages to all instances of the bpatcher.

before i forget, it is [gate 1 0], not [gate 0 1] as you have it.

my guess is that you have many of these abstractions/bpatchers or whatever instantiated, but your send / receive sets are global - therefore, whenever you press one of these radiogroup buttons, the bangs are going to every single in-use bpatcher/abstraction. because you have used globals.

you need to look into unique id's, available as #0 notation. then the bangs would only send locally. i.e.:

[s #0-uni.route.off] and [r #0-uni.route.off].

p.s. - i only looked at your second posted patch.

anyway, to your problem:
my guess is that you have many of these abstractions/bpatchers or whatever instantiated, but your send / receive sets are global - therefore, whenever you press one of these radiogroup buttons, the bangs are going to every single in-use bpatcher/abstraction. because you have used globals.

you need to look into unique id's, available as #0 notation. then the bangs would only send locally. i.e.:
[s #0-uni.route.off] and [r #0-uni.route.off].

p.s. - i only looked at your second posted patch.


as pid wrote, this involve to design an, even small, messaging system.

I'm doing that with a project I'm currently working.

There are send/receive globals, used as broadcasting busses

There are specific receive built as pid wrote and popping out specific messages to specific abstractions from a java core.

as pid wrote, this involve to design an, even small, messaging system.
I'm doing that with a project I'm currently working.

There are send/receive globals, used as broadcasting busses
There are specific receive built as pid wrote and popping out specific messages to specific abstractions from a java core.

hi guys, I did design it to be a global send and receive, I wanted the press of a radio button within one bpatcher to deactivate all of the other ones in the other bpatchers. I've had to create a work around that hardwires these sends/receives to outputs/inputs from the bpatchers and then connected them within the parent patch, bit messy but it works.

bpatcher hell