Pattr and Pattrstorage in m4l behaviour


    Jul 03 2018 | 12:42 am
    I try to describe the problem I have as well as possible: I have a [pattr] and a [pattrstorage] in an m4l patcher. When I load data (blob/path via dragndrop) into the pattr, the pattr stores all values in ableton/m4l. Now I can save/write the data to a json file via "write" with [pattrstorage] . So far, so good.
    Now when I read a json file from my hard disk (read via pattrstorage), it loads all the data I need now into pattr. BUT the data is not stored in the pattr(ableton/m4l)! It shows everything correctly in the Pattr Window, but when I save and reload the Ableton set, it shows my old value, not the previous loaded value.
    It seems that pattr ignores the pattrstorage loaded values when saving.
    I have experimented a lot with it and it seems to be the only solution to connect the [pattr] output via a [trigger s] to the input of the [pattr] object. Now the pattr restores the correct value when reloading the Ableton set.
    In short: the values loaded via pattrstorage (read) are not stored within pattr/ableton, even when they show up in the pattr window.
    Why pattr does not save loaded pattrstore values? Is that a fault, am I missing something?

    • Jul 03 2018 | 12:54 am
      For better understanding, here is a m4l patch.
      - drop a jpeg (1) - save ableton set - reload ableton set -> pattr will show the jpeg(1) filename - write the json file with the path information - save ableton set - reload ableton set -> pattr will show the jpeg(1) filename - drop a NEW/different jpeg(2) file - save ableton set - reload ableton set -> pattr will show the NEW jpeg(2) filename - read the json file you have saved - save ableton set - reload ableton set -> pattr will show the OLD jpeg(1) filename
      if you enable the disabled cords from [t s] in the patch, the patch is working as espected.