Baek Santarek

I would like to create a very specific abstraction that is available only in a certain patch and hidden from other patches.

I would love to use the benefits of abstractions (create/edit once, use many times) but I don't want to clutter my object autocompletion list (when creating new objects) with them because of their specific purpose that is of no use in other patches.

I would love to use the benefits of abstractions (create/edit once, use many times) but I don't want to clutter my  object autocompletion list  (when creating new objects) with them because of their specific purpose that is of no use in other patches.

Hello,
I would like to create a very specific abstraction that is available only in a certain patch and hidden from other patches.
I would l

is-it-possible-to-create-"local"-abstractions

Could you elaborate, please? How would that help me? Thank you!

instead of encapsulating whatever you want to have in your abstraction, put it in a bpatcher with "Embed patcher in parent" on. and copy it

And would this allow me to edit guts of all instances of the bpatcher from one place (same as with abstractions)?

And would that allow me to edit all instances of copied bpatcher at once (same as with abstractions)?

Because I cannot get abstraction-like editing to work.

When I embed the patcher in parent, after copying it to multiple instances I am then unable to edit all the bpatchers from one source file.

Embed if you want to change only one instance, do not embed if you want to change all - read the documentation !

Sorry, I don't think we are on the same page (or I seriously misunderstood what you are suggesting). I am just basically trying to get an abstraction that behaves completely like an abstraction 

but is only available to certain patchers (i.e. not globally available to all max search paths)

. Nothing more, nothing less. I thought there would be an elegant way without having to move the source patchers for abstractions to folders outside of Max search path.

I will probably try to use Projects instead.

Sorry, I don't think we are on the same page (or I seriously misunderstood what you are suggesting). I am just basically trying to get an abstraction that behaves completely like an abstraction but is only available to certain patchers (i.e. not globally available to all max search paths). Nothing more, nothing less. I thought there would be an elegant way without having to move the source patchers for abstractions to folders outside of Max search path.

yeah. For needs like this I use Bpatchers. They do all you describe (plus give an UI, should you need it)

yeah. For needs like this I use Bpatchers. They do all you describe (plus give an UI, should you need it)
use some other way if you want
best
k

I am still trying to understand what you are suggesting. I am sorry.

Please, explain how does bpatcher let me edit all instances' guts (not arguments!) of an abstraction at once while hiding the source patch from other patchers? Embedding it makes this impossible from what I have tried.

Please, explain how does bpatcher let me edit all instances' guts (not arguments!) of an abstraction at once while hiding the source patch from other patchers? Embedding it makes this impossible  from what I have tried.

that is why i would love to be able to turn off custom packages in the package manager.

Hey, this sounds like a great use case for projects!

Hi, Sam! Looking forward to your youtube video on this ;-D ! Enjoying your channel! Keep it up!

Is it possible to create "local" abstractions?