preset object fourth outlet not working?


    Jan 11 2011 | 2:00 am
    Hi-
    The preset object indicates that it is supposed to send the preset number that has just been stored out the fourth outlet, but I cannot get anything to be output. Am I understanding this functionality correctly?
    I have tried on both Windows 7 and OSX. Not sure if this is a bug or user error/misunderstanding.
    Thanks a lot.
    -Halsey

    • Jan 13 2011 | 10:56 pm
      works fine here
      Max 5.1.7
      OS 10.6.6
    • Jan 18 2011 | 4:25 am
      thanks for checking...glad to hear it's working somewhere!
      I'm on:
      OS 10.6.5
      Max 5.1.7
      and I still cannot get it to work. Oddly, I tried shift-clicking to store the preset and that does in fact work, but sending a 'store 1' message does not send anything out the fourth outlet. And unfortunately, I need to automate some things with presets, so I will not be able to shift-click.
      {
      "boxes" : [ {
      "box" : {
      "maxclass" : "message",
      "text" : "clearall",
      "id" : "obj-6",
      "fontname" : "Arial",
      "fontsize" : 12.0,
      "numinlets" : 2,
      "numoutlets" : 1,
      "patching_rect" : [ 147.0, 106.0, 49.0, 18.0 ],
      "outlettype" : [ "" ]
      }
      }
      , {
      "box" : {
      "maxclass" : "comment",
      "text" : " "linecount" : 2,
      "id" : "obj-4",
      "fontname" : "Arial",
      "fontsize" : 12.0,
      "numinlets" : 1,
      "presentation_rect" : [ 336.0, 194.0, 0.0, 0.0 ],
      "numoutlets" : 0,
      "patching_rect" : [ 336.0, 194.0, 150.0, 34.0 ]
      }
      }
      , {
      "box" : {
      "maxclass" : "comment",
      "text" : " "id" : "obj-2",
      "fontname" : "Arial",
      "fontsize" : 12.0,
      "numinlets" : 1,
      "numoutlets" : 0,
      "patching_rect" : [ 262.0, 106.0, 150.0, 20.0 ]
      }
      }
      , {
      "box" : {
      "maxclass" : "number",
      "id" : "obj-5",
      "fontname" : "Arial",
      "fontsize" : 12.0,
      "numinlets" : 1,
      "numoutlets" : 2,
      "patching_rect" : [ 284.0, 195.0, 50.0, 20.0 ],
      "outlettype" : [ "int", "bang" ]
      }
      }
      , {
      "box" : {
      "maxclass" : "message",
      "text" : "store 1",
      "id" : "obj-3",
      "fontname" : "Arial",
      "fontsize" : 12.0,
      "numinlets" : 2,
      "numoutlets" : 1,
      "patching_rect" : [ 203.0, 107.0, 54.0, 18.0 ],
      "outlettype" : [ "" ]
      }
      }
      , {
      "box" : {
      "maxclass" : "preset",
      "id" : "obj-1",
      "numinlets" : 1,
      "numoutlets" : 4,
      "patching_rect" : [ 203.0, 142.0, 100.0, 40.0 ],
      "outlettype" : [ "preset", "int", "preset", "int" ]
      }
      }
      ],
      "lines" : [ {
      "patchline" : {
      "source" : [ "obj-6", 0 ],
      "destination" : [ "obj-1", 0 ],
      "hidden" : 0,
      "midpoints" : [ ]
      }
      }
      , {
      "patchline" : {
      "source" : [ "obj-1", 2 ],
      "destination" : [ "obj-5", 0 ],
      "hidden" : 0,
      "midpoints" : [ ]
      }
      }
      , {
      "patchline" : {
      "source" : [ "obj-3", 0 ],
      "destination" : [ "obj-1", 0 ],
      "hidden" : 0,
      "midpoints" : [ ]
      }
      }
      , {
      "patchline" : {
      "source" : [ "obj-1", 3 ],
      "destination" : [ "obj-5", 0 ],
      "hidden" : 0,
      "midpoints" : [ ]
      }
      }
      ]
      }
    • Jan 18 2011 | 5:02 am
      You are right, with "store 1" the outlet is not giving you the info. but there is an easy workaround. Since you have to send it a number to store, you already "know" the number!! so there is no need for it to output.
      does this solve your problem?
    • Jan 18 2011 | 1:29 pm
      hey...thanks for this idea. it should work for my situation. still strikes me as weird that the preset object does not behave consistently in this regard; I wonder if this is on purpose or a bug? C74, any comments?!
      thanks again for the workaround; should do the trick!
    • Oct 28 2012 | 8:29 pm
      I'm having the same problem (but in Max 6) and came across this thread via google. I can work around it, but this is either a bug, or a flaw in the documentation, which doesn't make this clear.