Yet another question about pattrstorage & interpolation mode

    Sep 29 2009 | 10:16 am
    Hello all
    so finally I made it work with regular pattr objects instead of autopattr to save & recall presets, but now I have the following problem:
    If I want to suppress interpolation for all unnecessary objects, I choose none in the dropdown menu from the interpolation column in the clientwindow, but unfortunately these settings are NOT saved with my patch, every time I reopen it, they are all back to linear interpolation... I also tried to change this in the inspector window for all pattr objects, but it doesn't work either...
    Maybe something obvious I missed
    Thanks in advance for your help - again

    • Sep 29 2009 | 1:34 pm
      I just tried, and it seems they get saved fine over here. Looking at the save file format, the interp data is definitely in there. Note how pattr object 'joo2' its interpolation was left to linear mode and is not saved, the rest is.
      "box" : {
      "maxclass" : "newobj",
      "varname" : "u607008823",
      "text" : "pattrstorage",
      "numinlets" : 1,
      "fontsize" : 10.0,
      "numoutlets" : 1,
      "outlettype" : [ "" ],
      "patching_rect" : [ 330.0, 130.0, 64.0, 18.0 ],
      "id" : "obj-1",
      "fontname" : "Arial",
      "interp" : {
      "joo" : [ 0, 0.0 ],
      "joo3" : [ 2, 4.0 ]
      "saved_object_attributes" : {
      "client_rect" : [ 100, 100, 500, 600 ],
      "storage_rect" : [ 200, 200, 800, 500 ]
    • Sep 29 2009 | 4:26 pm
      yes, well once again, if I make a small test patch on the side it does work indeed, but not in my big patch with hundreds of objects to restore...
      btw, I think your code is incomplete (this is not copy compressed from max 5, is it ?), cannot do anything with it - copy & paste in max does not work.
      thanks anyway
    • Sep 30 2009 | 8:36 am
      Yup, that code is not complete, I just copied a little bit of patcher to show that the info is indeed in there.
      Try to find the pattrstorage object if you open your patch as text, and see whether the interps are in there.
      Debugging big patches is always a lot more difficult than with small patches, because the amount of mistakes you could have made so far increases exponentially. There have been problems in Max where things ceased to work correctly when load increased, but not many. Maybe try to make a small example and then copy objects until you have a few hundred?