Christophe Burkman

Common situation : Once your patch is done and ready to use, you might be in the need to use it on different projects or shows or exhibitions. Each of those projects will have different values and settings inside your patch.

That's where pattrstorage and autopattr objects are useful. And since it takes me some times to achieve it, i wanted to share my work here. It is 95% inspired from this previous post :

https://cycling74.com/forums/help-multiple-identical-bpatchers-not-saving-different-state-in-parent-patch

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

But i got some problems and wanted to add more :

1- When your settings are stored, you can save them as a json file and keep one file for each specific show. I just added a subpatch which remove extension if there is one and do nothing if there is none and add .json after that. Whithout it, you might create your .json file but the path created might not have the extension, and you will have some saving/reading problems because test_01 and test_01.json are not the same at all.

2- I've added an option which allows you to save settings when you save your patch. ( take me some time until i found the [savebang] object ... face palm...

3- I've added a tab with 5 "memory" slots available inside one setting file. You can switch from one to another quickly with store and load button.

It seems to work fine for now but some bugs may pop in time. Feel free to use it and check it and tell me if anything goes wrong.

comment

prepend

textedit

textbutton

toggle

number

flonum

gate

regexp

outlet

inlet

button

combine

message

loadbang

strippath

opendialog

savedialog

savebang

route

autopattr

pattrstorage

Hi there,

Common situation : Once your patch is done and ready to use, you might be in the need to use it on different projects or shows or exhibitions. Each of those projects will have different values and settings inside your patch.
That's where pattrstorage and autopattr objects are useful. And since it takes me some times to achieve it, i wanted to share my work here. It is 95% inspired from this previous post :
https://cycling74.com/forums/help-multiple-identical-bpatchers-not-saving-different-state-in-parent-patch
Big thanks to Chris Muir.
That youtube video helped a lot too :
https://www.youtube.com/watch?v=lGxfiQE9PNM


But i got some problems and wanted to add more :

1- When your settings are stored, you can save them as a json file and keep one file for each specific show. I just added a subpatch which remove extension if there is one and do nothing if there is none and add .json after that. Whithout it, you might create your .json file but the path created might not have the extension, and you will have some saving/reading problems because test_01 and test_01.json are not the same at all.

It seems to work fine for now but some bugs may pop in time. Feel free to use it and check it and tell me if anything goes wrong.



Hi there,

Common situation : Once your patch is done and ready to use, you might be in the need to use it on different projects or shows or

Patch settings storage and file extension managment