Using subpatch multiple times update changes once?

[hesspet]

Hello!

I was experimenting with a small subpatch. This subpatch is used 10 times in a patch. Is there a way to handle all those subpatches as "reference"? Means, when I do a change in one patch, the change should be visible in all patches with the same name?

I'm not sure if there is any chance to do so.

But if this is possible.. how?

Peter

[nay-seven]

i suppose you have try the polyphony way..?
not 10 sub-patchs but 1 with polyphony =10..?

you can also maybe use a method with buses ..?

depending a lot of you master patch of course...

[joffo78]

Wtih polyphonic patch the once in poly option on input and output is very important. It allows you to share one input or output for each subpatch. It can be use to as array input or output.

[hesspet]

The polyphony is not the solution for this finished workspace - more a sort of a playground.

I made n patches and connect them in a sort of "autonomous" machines A sort of a network. And after a while I found out, that I've have to change a generic part in, 20 or 30 of the patches. They are all copied instances, connected somewhere in the network.

So I'm a software developer and I hoped to find a way to have 20 times the same subroutine which could be changed once. My current solution: I patched the XML. Next time I'll try it in the polyhonic way to prevent such a situation.

Thanks for your help. Peter

[woodslanding]

This is a long-standing FR. I'm hoping it will show up someday. Poly works for this, but all your subroutines must be in the same subpatch, so you need to use a lot of busses if you are using them in different places. (I several hundred busses in my workspace for this reason, which would otherwise be unnecessary.... but it's worth it not to have to do every bugfix a dozen times!)

About the poly ins and outs, is there a way to make a once in poly output NOT be an array? I didn't think this was possible.

I haven't tried using an array on the input, is that also possible?

[cmodica]

It is true that the possibilitie to have a ''ref Patch'' and ''child'' could be a great think. If we made changes in a child all the others instances of this patch change too ...

I remenber something like that in MAX/MSP ... ?

[hesspet]

+1

This is something I must handle every day. References.... I miss this concept in Usine

In XML you could write a reference entity. Never tried this in Usine. Maybe it works. Must try it once. maybe Usines parser can handle it.