pattrstorage with setstoredvalue in M4L

    Aug 25 2011 | 9:14 am
    Hello Maxers,
    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.
    thanks. Stan

    • Aug 27 2011 | 11:03 am
      anyone ? please
    • Sep 03 2011 | 2:42 pm
    • Sep 04 2011 | 8:17 am
      hmmm. maybe you are not setting up your pattrstorage correctly for M4L?
      in M4L there is only one way pattrstorage can work.
      1. check 'parameter mode enable'
      2. check 'initial enable'
      3. 'parameter visibility' - 'stored only'
      4. other stuff optional but NO scripting name
      did you do this?
      in M4L, all dirty stuff is handled automatically for you, to fit with live automation / store system etc.
      any use? or am i way off the mark?
    • Sep 04 2011 | 9:36 am
      Thanks for you answer pid. Yes, I did it this way.. I think.
      So here is the simple patch:
      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 ?