Hi, I have a trouble with creating a system which would allow me to record midi CC automation into multiple arrays and store it as a preset which I could later recall with program change. I tried using [clone] but it doesn’t store the insides of the abstraction. I would like to make it flexible in a way that it doesn’t know in advance how many presets will be stored and it would dynamically create the instances when needed. Can anyone steer me in the right direction?

@5tepan Yes, you cannot save data inside an abstraction as they are all the same.

To create the arrays dynamically they would have to be written outside clone.
E.G........ this.zip
David.

@whale-av This is really cool, thanks.

@5tepan It is also possible to store data from abstractions in the main patch using [savestate].

Ok, I tried to implement this approach, but it fails when I add dynamic creating/deleting of the arrays.

Basically what I want to achieve is a matrix of arrays, which would contain the midi CC automation. For each preset there would be different row, and in every row there could be up to 127 arrays. Each array has unique name with the given coordinates. Every time an array is created I want to delete the previous one placed on the same spot (if there is any) to avoid duplicates. For that I'm using [mouse x y, cut(. Maybe I could use the [find( message, but I don't know how.

This is my first try to do dynamic patching and the patch seems to crash a lot.
Is it a robust method to do it or should I use something else?
preset_system.zip

Also I wonder what are the -s -f -k flags used for.

@5tepan This all seems overkill to me. I would go with [text] for a preset system.

@ingox Yes, I feel like that too. So you suggest creating a [text] object instead of each array? In practice each preset would contain cca 2-8 automation slots with aproximately 1000 values in each one.

@5tepan Yes, it should probably work. Just one [text] object and one line instead of each array.

Data structures ? their main utility is to let you store, organize, and recall, via message or via the gui options they provide, flexible amount of data organized in patterns.

The -f and -s symbol are for using array with data structure. The -k is for the text define object to store its data when you close the patch.