best way to save presets ?


    Dec 27 2006 | 9:28 pm
    I would like to know how people save their preset parameters for effects. For example, I have a granular synth patch, and I need to use different parameters for different cues in a piece. I also would like to copy the preset to some other pieces without problem.
    The preset object in Max/MSP lose all the stored info if it is copied and pasted to another patch if I do not save all the info in a text file.
    Are there other convieniet or better ways to save and load presets of different parameters ?
    Thanks.

    • Dec 27 2006 | 9:52 pm
      pattr, pattrstorage.
      On Dec 27, 2006, at 4:28 PM, Cheng Chien-Wen wrote:
      >
      > I would like to know how people save their preset parameters for
      > effects. For example, I have a granular synth patch, and I need to
      > use different parameters for different cues in a piece. I also
      > would like to copy the preset to some of my piece without problem.
      >
      > The preset object in Max/MSP lose all the stored info if it is
      > copied and pasted to another patch if I do not save all the info in
      > a text file.
      >
      > Are there other convieniet or better ways to save and load presets
      > of different parameters ?
      >
      > Thanks.
      v a d e //
      www.vade.info
      abstrakt.vade.info
    • Dec 27 2006 | 11:36 pm
      Coll.
      b
      Cheng Chien-Wen wrote:
      > I would like to know how people save their preset parameters for effects. For example, I have a granular synth patch, and I need to use different parameters for different cues in a piece. I also would like to copy the preset to some of my piece without problem.
      >
      > The preset object in Max/MSP lose all the stored info if it is copied and pasted to another patch if I do not save all the info in a text file.
      >
      > Are there other convieniet or better ways to save and load presets of different parameters ?
      >
      > Thanks.
      >
      --
      barry threw :: sound | (if you would see the stars clearly,
      http://www.barrythrew.com | look hard at the surrounding darkness)
      bthrew(at)gmail(dot)com | -Ooka Makoto
      857-544-3967 |
    • Dec 29 2006 | 7:48 pm
      Definitely use coll or pattr. I usually use coll and can then use the preset object (as a selector only) to pick which coll I'm storing/accessing/clearing. With some fiddling you can have a huge number of presets to select from, and upon choosing between them (like when you unpack a list of parameter values) you can run them through a line object for glide/portamento/interpolation. Of course, pattr gives you even more options for interpolation.
      Note that colls inside bpatchers (i.e., naming them #1coll_foo etc.) will NOT be saved. They need to be in a bona fide patch, not an instance. (If anyone has info on this I'd like to hear it, I had thought they would be saved if they were given unique names....) To save these individual instance colls you need to send them out to the parent patch and prepend an index number to them, then store them in a "supercoll" which is a coll of your colls.
      I only use preset for development and testing stuff, and in any final project, only for boolean settings like a string of gates (where interpolation won't matter). There, they can be easy and helpful.
      --CJ
    • Dec 30 2006 | 11:50 am
      I've been doing it using preset objects. It works fine for me but maybe that's because the only settings I need to save are from user interface objects like dials and rsliders.
      Because it was all happening inside a poly~ in which every voice had different settings and a unique preset file and I wanted to be able to add more voices conveniently I saved the settings from one normal-ish voice and then used that as a default for any voice that found itself without a preset file to load.
      This is the bit that does it. It will only work inside a poly~ and it is set up to only save and load preset 1.
      max v2;
    • Jan 01 2007 | 7:40 am
      Thank you very much for sharing ideas.