redhexagonal

I want to use identical embedded bpatchers inside another bpatcher, so that I can use a preset in each to store some parameters in those patches that I don't want exposed to pattrstorage.

When I first embed the inner patchers, their parameters are all still named "dial" so that pattrstorage sees them as "TopLevelPatch::F3::dial 35" for instance. But if I save the top level patch, close and reopen it, the names of the dials get a number after them , like dial[3] which makes it harder for me to extract this data. Why is this happening, and how can I make it so all the embedded patchers have the same parameter names within them?

Try embedding the innermost patches in this patch and saving the resulting patch, then reopening it.

I want to use identical embedded bpatchers inside another bpatcher, so that I can use a preset in each to store some parameters in those patches that I don't want exposed to pattrstorage.
When I first embed the inner patchers, their parameters are all still named "dial" so that pattrstorage sees them as "TopLevelPatch::F3::dial 35" for instance. But if I save the top level patch, close and reopen it, the names of the dials get a number after them , like dial[3] which makes it harder for me to extract this data. Why is this happening, and how can I make it so all the embedded patchers have the same parameter names within them?

naming-irregularities-in-nested-bpatchers

Ok, so i got this to work by using lots of named pattr objects instead of autopattr. I dont know why autopattr adds numbers to my parameter names but i guess i cant use it for this, unless someone can explain whats going on?

Ok, so i got this to work by using lots of named pattr objects instead of  autopattr. I dont know why autopattr adds numbers to my parameter names but i guess i cant use it for this, unless someone can explain whats going on?


i don't have the patch Inner.maxpat, so it's not possible to completely open your patch, but there can be only one object with a particular scripting name at any patcher level, so maybe that's why max will automatically add the [1]. It's actually possible to manage this with regexp or sprintf or combine or stuff like this, but i'm not sure it's your problem here becasue the patch is incomplete.

The thing is, I can have several objects at the same level (but in different patchers) if the patchers are not embedded, or if I use pattr. Its when I use autopattr with embedded patchers that I get numbers added to the parameters.

So in this example with embedded patchers, the bpatchers in GGGG which use autopattr always have numbers after parameter "none" but in the FFFF bpatcher, the embedded sub patchers using patter all have parameters named "none" with no numbers. It just seem like autopattr is getting confused.

So in this example with embedded patchers, the  bpatchers in GGGG which use autopattr always have numbers after parameter "none" but in the FFFF bpatcher, the embedded sub patchers using patter all have parameters named "none" with no numbers. It just seem like autopattr is getting confused.

Not sure if you already know this, but it took me forever to find this feature.

If you add a #1 to the beginning of a parameter script name inside a bpatcher, such as #1scriptname, then you can simply add whatever number you want in the main bpatcher inspector argument line by adding a number, such as bpatcher argument "1" ,will name all those # parameters 1scriptname. You can also name #0 with no argument but it will accumulate numbers over time. Can you name the embedded bpatchers #1 and add a number with the main bpatch?

Not sure if you already know this, but it took me forever to find this feature.
If you add a #1 to the beginning of a parameter script name inside a bpatcher, such as #1scriptname, then you can simply add whatever number you want in the main bpatcher inspector argument line by adding a number, such as bpatcher argument "1" ,will name all those # parameters 1scriptname. You can also name #0 with no argument but it will accumulate numbers over time. Can you name the embedded bpatchers #1 and add a number with the main bpatch?


Not sure that will help with autonaming, but thats very useful generally, thanks, I was wondering how to do that for a while now.

Still not sure why autopattr adds the numbers but pattr seems to be a workaround.

Not sure that will help with autonaming, but thats very useful generally, thanks, I was wondering how to do that for a while now.
Still not sure why autopattr adds the numbers but pattr seems to be a workaround.


I still haven't found a solution for this - whenever i embed a number of bpatchers the parameters get numbers after their names, which i don't want. Its like Max thinks they are in the same patch.

I still haven't found a solution for this - whenever i embed a number of  bpatchers the parameters get numbers after their names, which i don't want. Its like Max thinks they are in the same patch.

naming irregularities in nested bpatchers?