Stan

i have a simple question: Is it an intended behavior that the setstoredvalue message to a pattrstorage object will not set the dirty flag in a ableton live set ? So if the content of pattrstorage has changed in this way, it will not be saved in the live set. arrrgh

Otherwise the store message works as expected and sets the dirty flag.

i have a simple question: Is it an intended behavior that the setstoredvalue message to a pattrstorage object will not set the dirty flag in a ableton live set ? So if the content of pattrstorage has changed in this way, it will not be saved in the live set. arrrgh
Otherwise the store message works as expected and sets the dirty flag.

pattrstorage-with-setstoredvalue-in-m4l

hmmm. maybe you are not setting up your pattrstorage correctly for M4L?

in M4L there is only one way pattrstorage can work.

3. 'parameter visibility' - 'stored only'

4. other stuff optional but NO scripting name

in M4L, all dirty stuff is handled automatically for you, to fit with live automation / store system etc.

I have found a practical workaround for me (with the store message). So its ok for me, but may be the setstoredvalue behavior should be changed ?

Thanks for you answer pid.
Yes, I did it this way.. I think.

I have found a practical workaround for me (with the store message). So its ok for me, but may be the setstoredvalue behavior should be changed ?


pattrstorage with setstoredvalue in M4L