uebergeek

Hi, I've been working with an interface abstraction something like the attached. Each row can bring up a local preset - but I want to also be able to create global presets. The local presets are created in row #1 and available in all rows, using the technique suggested by Tada here: 

https://cycling74.com/forums/duplicating-presets/

The problem is that the global presets aren't just a matter of calling up one of the local presets in each row. I want the global preset to be able to save and recall arbitrary values in the various UI objects. But when I recall a global preset I've saved this way, it doesn't restore those values - it just seems to restore whatever local presets were selected. So the UI objects show the default values saved with those local presets, rather than the values I'd explicitly set when I saved the global preset. Thought I might be able to exclude the local presets from the global preset, but it doesn't let me attach the patch cords that way.

I've looked through other forum threads, and it sounds like there's probably a way to do this with pattrstorage. But I've tried a few things and not had success. It seems that with all these presets and pattrstorage, there are quite a few moving memory parts, so it's hard for me to tell what object is doing what. Any suggestions? 

Hi,  I've been working with an interface abstraction something like the attached. Each row can bring up a local preset - but I want to also be able to create global presets. The local presets are created in row #1 and available in all rows, using the technique suggested by Tada here: https://cycling74.com/forums/duplicating-presets/

The problem is that the global presets aren't just a matter of calling up one of the local presets in each row. I want the global preset to be able to save and recall arbitrary values in the various UI objects.  But when I recall a global preset I've saved this way, it doesn't restore those values - it just seems to restore whatever local presets were selected. So the UI objects show the default values saved with those local presets, rather than the values I'd explicitly set when I saved the global preset. Thought I might be able to exclude the local presets from the global preset, but it doesn't let me attach the patch cords that way.

I've looked through other forum threads, and it sounds like there's probably a way to do this with pattrstorage. But I've tried a few things and not had success.   It seems that with all these presets and pattrstorage, there are quite a few moving memory parts, so it's hard for me to tell what object is doing what. Any suggestions?  


global-and-local-presets-together

Hi, just wondering if anyone had ideas on this? Thanks.

Hi, just wondering if anyone had ideas on this?  Thanks.


I can't look at your patch right now but i think you need to check out autopattr and pattstorage + preset.

By giving objects a "scripting name" (found in inspector tab when object is selected) you can include them in a preset, if I'm correct you can also set up a hierarchy system with nested autopattr systems.

Heres the basic tut that should get you going.

https://www.youtube.com/watch?v=wRCCYjBMTFA

I can't look at your patch right now but i think you need to check out autopattr and pattstorage + preset.
By giving objects a "scripting name" (found in inspector tab when object is selected) you can include them  in a preset, if I'm correct you can also set up a hierarchy system with nested autopattr systems.

https://www.youtube.com/watch?v=wRCCYjBMTFA


Thanks! I had a feeling it could somehow be done with pattr - that helps me narrow it down. Will give it a try next weekend.

Thanks!  I had a feeling it could somehow be done with pattr - that helps me narrow it down.  Will give it a try next weekend.


Thanks folks for your help! But I've got a strange bug, and it's still not clear to me how to debug with pattr. Using Wil's example, I created the following from the sample patch I posted earlier:

But when I go back to apply it to a simplified version of my actual patch, I get a stack overflow when reading the presets back.

The main difference that I'm aware of is the "send" objects are attached in the crashing patch - yet I've attached a few "sends" to the sample patch and that doesn't seem to break it. So I'm not sure what the difference is. Any tips on debugging pattr? There are still a few things about pattr I'm not clear about - such as the difference between names for the scripting objects that I create and ones that are pre-filled by Max - so it's possible I'm overlooking something "obvious" in the difference between the two patches.

Thanks folks for your help!  But I've got a strange bug, and it's still not clear to me how to debug with pattr.  Using Wil's example, I created the following from the sample patch I posted earlier: 

But when I go back to apply it to a simplified version of my actual patch, I get a stack overflow when reading the presets back. 

The main difference that I'm aware of is the "send" objects are attached in the crashing patch - yet I've attached a few "sends" to the sample patch and that doesn't seem to break it.   So I'm not sure what the difference is.   Any tips on debugging pattr?   There are still a few things about pattr I'm not clear about - such as the difference between names for the scripting objects that I create and ones that are pre-filled by Max - so it's possible I'm overlooking something "obvious" in the difference between the two patches.


fixed. the preset number boxes were saved as presets and when you toggled through them using the arrow button it was causing an overflow.

Aha, thanks a bunch! I needed to add a few more "excludes' to the global autopattr - i.e. the local presets and the umenus that control them. After I did that it seems to be working properly at last. Thanks again!

Aha, thanks a bunch!   I needed to add a few more "excludes' to the global autopattr - i.e. the local presets and the umenus that control them. After I did that it seems to be working properly at last. Thanks again!


also, another way to do it is to go into the inspector and remove the scripting name. the reason I wire the 'excludes' is because for some objects (live) the scripting name automatically returns. so using 'exclude' is safer but messier if you have a lot them.

Funny you should mention this.... I found that the scripting name *always* seems to return if I try to delete it - at least for every object I tried to do it on. When I save the patch and reload it, it just generates a new scripting name. Wondering if this is a bug, or something about my patch in particular? It seems to not gel with the instructions given in the tutorials to give scripting names to just those objects you want included in the preset.

Funny you should mention this....  I found that the scripting name *always* seems to return if I try to delete it - at least for every object I tried to do it on. When I save the patch and reload it, it just generates a new scripting name.   Wondering if this is a bug, or something about my patch in particular?  It seems to not gel with the instructions given in the tutorials to give scripting names to just those objects you want included in the preset.


haven't tried it yet but maybe if you add a scripting name to max objects 'before' adding the autopattr it might be the reason it keeps regeneration them. in my patch the number box and arrow did not have a scripting name so i didn't have to exclude them. i think all live objects come with a scripting name so those keep regeneration when i try to erase them. haven't tried clearing the scripting name in live objects 'before' adding the autopattr. eventually i will find time to test this idea.

Thanks! Hmm, just tested it... seemed to work at least at first with the preset objects, but still got the stack overflow unless I explicitly exclude the number boxes. Maybe I made a mistake along the way - or maybe it doesn't reliably exclude all objects. Anyway, it's probably safer to explicitly exclude those objects from autopattr - can also route/hide the patch cords to keep the patch neat. Thanks again!

Thanks!  Hmm, just tested it... seemed to work at least at first with the preset objects, but still got the stack overflow unless I explicitly exclude the number boxes. Maybe I made a mistake along the way - or maybe it doesn't reliably exclude all objects. Anyway, it's probably safer to explicitly exclude those objects from autopattr - can also route/hide the patch cords to keep the patch neat.   Thanks again!


Global and local presets together