is encapsulation the way to go ?
Hi :)
Learning Max for live.. lots of fun
working with max 8.. playing with some midi effects.
there are some parts of my patch that are repeated so I want to encapsulate them.
I have no idea if encapsulation is the way to go..
how do I save a sub-patch for later use, not just in the current project.
do I encapsulate? same as snippet? as template? a bit confused.
my sub patch has two attribute arguments, and when I change them, the values are not updated unless I attach a button to the left inlet of patchargs and fire it.
so how do I handle this properly ?
thanks
Have a look at the documentation "Encapsulating and Reusing Your Work".
Abstractions
Any patch you have created and saved can be used as an object in another patch, just by typing the filename of your patch into an object box as if it were an object name. Patches used in this way are called abstractions.
Snippets
A snippet is a patcher file that contains something you use often and don't want to have to constantly re-create as you work.
As far as I understand Snippets they won't automatically change in the parent patchers if you modify the snippet-file, because they are only code fragments and not objects.
Also encapsulated code does not what you want to do unless you save it as a file and then it is an abstraction.
I have never used templates and I think these also won't do what you need.
I personally would recommend [bpatcher] which also allows for having a UI visible.
wow.. thats helps.. a lot! thank you
if you use the automatic encapsulation function you will end up with a [p thing].
the [p] or [patcher] object lives only inside its mother patch.
but you can just open it, and save the content as patch from its window.
save it as "thing.maxpat" (or "thing" on mac) and then you can remove the "p" from [p thing] to make the patcher object become the [thing] object you just created.
[thing] can now be called twice by copying it, and when you edit one copy, both are changed.