preset storage

    Feb 03 2013 | 6:11 am
    Greetings. i have written here before looking for some help, and got a little ways, but am feeling stuck < I am relatively new to this and need something fairly simple. , I need a 64 slot memory storage that I can cycle through starting at A1 to D16. (a1, to 16, b1 to b16, c1 to c16 and d1 to d 16) I would like to be able to cycle through these forwards and backwards manually with the press of a button (forward or backward). Also I need to be able to output those values A1 through D16 (as described above) on some kind menu or screen so users know which preset is being used.
    I have run into numerous issues I don know how to deal with.. if anyone could please help me build this, I would be grateful. Thanks

    • Feb 04 2013 | 10:52 pm
      So what did you try and where did it fail?
    • Feb 04 2013 | 11:06 pm
      As always, you're going to get way better feedback if you show us your work. In the whilemean, you could take a look at this series of pattr tutorials at
      and investigate some low-level Max objects (incdec, counter) and the umenu's scrolling mode (see under the "more about menus" tab in the umenu help file).
    • Feb 04 2013 | 11:12 pm
      here's a start for you regarding umenu in scrolling mode:
    • Feb 05 2013 | 4:02 am
      ok i have something to share, but I have forgotten how to upload the code. How do I export that for you to have a look at?
      thanks for replies
    • Feb 05 2013 | 7:59 am
      ok thanks, here it is. There are a few notes inside that describe the problems.
    • Feb 05 2013 | 8:49 am
      you've uploaded the wrong patch
    • Feb 05 2013 | 9:24 am
      sorry .. I copied over the one I made, so i had to re do it.. so much work!
      Ok try this:
    • Feb 05 2013 | 11:02 am
      here's a way of doing what you want-- you need to isolate the preset object from the menu object and the (new) control buttons. the red patch cords do this. Note the use of the inc-dec object allows the use of cycling through forwards or backwards-- you could have done this with buttons too but this is easier. also use the rightmost outlet of the preset object let other objects know a preset has been stored
      btw if you don't want the 'S' placeholder in the menu just subtract 1 from the output of preset object and change the conditionals to 0 and 63
    • Feb 05 2013 | 8:34 pm
      Thank you so very much this all seems to work just as I need it to! The only issue I have is that the buttons used are not midi mappable. Is there an easy way to replace those without messing the whole thing up? The Up & Down buttons I had in the previous version had some sort of wiring I dont understand, but they were midi mappable which is what I need.
    • Feb 05 2013 | 9:42 pm
      i'm not sure what you mean by midi mappable-- all objects are able to be mapped to or from midi in max. but if you want to use a live.object, just use these buttons with inc and dec:
      note I changed the message boxes' triggering from last patch (my error)
    • Feb 05 2013 | 10:55 pm
      thank you! just wondering what you meant about the last part about 'message boxes' triggering from last patch' I didnt notice anything strange or different in this code, other than the buttons being replaced.
      you are so awesome for helping , thanks again!
    • Feb 06 2013 | 12:16 am
      sorry double post
    • Feb 06 2013 | 1:09 am
      no worries just trying to build up a bit of good karma... the message boxes with 'set 64' and 'set 1' in them are preceded by a trigger object [t b b] and I'd connected the wrong outlets of these to the recipient objects, so i just swapped them, (and deleted the deferlow objects required to stop it crashing)-- anyway works now