Dani Joss

Either I missed something or this is unpredictable...

Working with Max 7 on osx mavericks. If I create a slider, bind it to a patter, then make a pattrstorage, change priority and interpolation modes, then save, the file appears to be saved correctly (I can see the values in the text file, both with opening as text and when I copy the objects directly). If I load the patch, or just paste the objects to a new one, or whatever combination I can think of, these reset to their defaults (0 and linear). Also, any attributes I give the pattrstorage (flags etc) are not loaded either. Values and stored presets work fine.

{
    "boxes" : [         {
            "box" :             {
                "maxclass" : "message",
                "text" : "clientwindow",
                "id" : "obj-5",
                "numinlets" : 2,
                "numoutlets" : 1,
                "patching_rect" : [ 393.0, 299.0, 79.0, 22.0 ],
                "outlettype" : [ "" ],
                "style" : ""
            }

        }
,         {
            "box" :             {
                "maxclass" : "newobj",
                "varname" : "u199000645",
                "text" : "pattrstorage",
                "id" : "obj-3",
                "numinlets" : 1,
                "numoutlets" : 1,
                "patching_rect" : [ 313.0, 343.0, 75.0, 22.0 ],
                "outlettype" : [ "" ],
                "style" : "",
                "interp" :                 {
                    "u671000647" : [ 4, -3.0 ]
                }
,
                "saved_object_attributes" :                 {
                    "client_rect" : [ 4, 44, 358, 172 ],
                    "parameter_enable" : 0,
                    "storage_rect" : [ 583, 69, 1034, 197 ]
                }

            }

        }
,         {
            "box" :             {
                "maxclass" : "newobj",
                "varname" : "u671000647",
                "text" : "pattr",
                "id" : "obj-2",
                "numinlets" : 1,
                "numoutlets" : 3,
                "patching_rect" : [ 247.0, 203.0, 40.0, 22.0 ],
                "outlettype" : [ "", "", "" ],
                "style" : "",
                "restore" : [ 80 ],
                "saved_object_attributes" :                 {
                    "parameter_enable" : 0
                }

            }

        }
,         {
            "box" :             {
                "maxclass" : "slider",
                "varname" : "slider",
                "id" : "obj-1",
                "numinlets" : 1,
                "numoutlets" : 1,
                "patching_rect" : [ 200.0, 165.0, 20.0, 140.0 ],
                "parameter_enable" : 0,
                "outlettype" : [ "" ],
                "style" : ""
            }

        }
 ],
    "lines" : [         {
            "patchline" :             {
                "source" : [ "obj-5", 0 ],
                "destination" : [ "obj-3", 0 ],
                "hidden" : 0,
                "disabled" : 0
            }

        }
,         {
            "patchline" :             {
                "source" : [ "obj-2", 1 ],
                "destination" : [ "obj-1", 0 ],
                "hidden" : 0,
                "disabled" : 0
            }

        }
 ],
    "appversion" :     {
        "major" : 7,
        "minor" : 0,
        "revision" : 1,
        "architecture" : "x86",
        "modernui" : 1
    }

}


Clearly the interpolation value is specified in the pattrstorage, correctly with the pattr's auto-generated name. If I load this (or paste it), the pattstorage appears "initialised", with the interp to linear. Copying it again reveals the inter value gone.

. I have a gigantic patch that I won't trouble you with that for some reason reopens with these values as specified. However, if I open it as a patcher object (typing it into an object box), the interp values are gone. Am I missing something? Is there a patcher or object attribute that I must set? Or is this just a bug? Btw I tried pasting this into Max 6 and got the same thing...

Crazy thing is, this happens sometimes. I have a gigantic patch that I won't trouble you with that for some reason reopens with these values as specified. However, if I open it as a patcher object (typing it into an object box), the interp values are gone. Am I missing something? Is there a patcher or object attribute that I must set? Or is this just a bug? Btw I tried pasting this into Max 6 and got the same thing...

pattrstotage-interpolation-and-priority-saved-but-not-loaded

Ok I made some progress, I figured out that one 

 name the patter object in order for this to work (despite the fact that it appears to be working). Otherwise, the pattrstorage thinks it is a new object every time.

However, the problem with my big patch remains. I've narrowed it down to timing issues with loading the patch. I'll see if I can figure it out and, if not, I'll post a new topic. But if you've come across this before, please let me know if you can help.

Ok I made some progress, I figured out that one must name the patter object in order for this to work (despite the fact that it appears to be working). Otherwise, the pattrstorage thinks it is a new object every time.

Thanks again, if anyone is reading this.


I've the same problem. I use a patch with several autopattr objects in some subpatchs. Sometime I loose the priority in the pattrstorage. I try also to read from a old .json file but only values are corrects. Do you think I need to name every patter object in my patch ?

Hello DANI,
I've the same problem. I use a patch with several autopattr objects in some subpatchs. Sometime I loose the priority in the pattrstorage. I try also to read from a old .json file but only values are corrects. Do you think I need to name every patter object in my patch ?
Thank you and sorry for my english ...
Claudio


I've been having similar problems, but this thread helped clear up a fundamental misunderstanding: The priority and interp values for client objects are stored with the patcher, not with the .json (preset) file.

Since those values kept disappearing, I've been trying to track down the problem by saving the preset file, closing the patch without saving (because I'd only changed values in the clientwindow, not in the patch itself), reopening the patch, and wondering why all my priority & interp settings were gone.

Maybe this is stated clearly somewhere in the documentation, but I couldn't find it. Anyway, there may still be problems with disappearing settings in large files and subpatchers, etc - I haven't tested that yet, but I'll report back if I'm still having problems.

So I guess a good rule of thumb is: values in the storagewindow are saved in the .json file, while values in the clientwindow are saved with the patcher. Sounds so simple when you say it like that; maybe it should be included in the documentation.

I've been having similar problems, but this thread helped clear up a fundamental misunderstanding: The priority and interp values for client objects are stored with the patcher, not with the .json (preset) file. 

So I guess a good rule of thumb is: values in the storagewindow are saved in the .json file, while values in the clientwindow are saved with the patcher.  Sounds so simple when you say it like that; maybe it should be included in the documentation.


Pattrstorage interpolation and priority saved but not loaded