Stephen Powell

I'm using autopattr with pattrstorage in a number of Max4Live patchers in a performance patch. I've set up systems of saving and loading states of the patches but I'm having some odd behaviour.

If I save states using the store message with an integer, then writing to a file on the computer, everything stores fine and I can happily switch between stored states on all the different patches in my Ableton set. However. if I then switch off Ableton, load it back up and have the same file load into apttrstorage upon opening, the different states will not load correctly, but instead either won't load anything, or will load some previous version (only happens on one patch, obscurely).

An example of the asving system I'm using is attached. I have tried various combinations of autostore and parameter enable with little success.

I'm using autopattr with pattrstorage in a number of Max4Live patchers in a performance patch. I've set up systems of saving and loading states of the patches but I'm having some odd behaviour. 

Odd pattr behaviour in Max4Live patches