Laveine

I need some help to find a good way to work with a patch that I continue to ameliorate and that I'm already using with some presets in a project.

My main patch contains a pattrstorage, and several copies of the same bpatcher. It works fine until I open, (modify) and save the original bpatcher : pattrstorage doesn't keep the data saved before modifying the bpatcher.

I put here a simple example, with the bpatcher not embed in the main patch;

because that's what I want : beginning to save presets and still have the possibility to do changes easily/rapidly in the bpatcher that will be applied to all the copies.

we can see also in the storagewindow that pattrstorage lost sometimes some objects linked to their autopattr, or just keep elements of one copy in its list.

Is there a special attribute for this (I've tried some), or is it a bad procedure?

I need some help to find a good way to work with a patch that I continue to ameliorate and that I'm already using with some presets in a project.  

I put here a simple example, with the bpatcher not embed in the main patch;
because that's what I want : beginning to save presets and still have the possibility to do changes easily/rapidly in the bpatcher that will be applied to all the copies. 

pattrstorage-lost-data-when-changingsaving-a-bpatcher

naming the 'autopattr' with a "#1", and giving an argument to each copy of the bpatcher in the main patch do the job.

pattrstorage lost data when changing/saving a bpatcher