Pattrstorage & pattr priority


    Oct 06 2006 | 8:09 am
    Hi Jeremy,
    sorry if this was discussed ages ago :
    As the doc says so, is there any reason that a pattrstorage object in a top-level patcher could not be able to reflect the priorities of pattr obejcts being loaded from abstractions or subpatchers ? It would be so useful, when pattr-priority is essential for your DSP module to work great (in other words, the order in wich you recall parameters is essential for your module to work properly), if a large patch containing a lot of those modules could be quickly stored into a global pattrstorage (a session) without problems (due to the priority of parameters, sorry, again :).
    You follow me ?
    Salut,
    _M

    • Oct 06 2006 | 8:40 am
      Do you mean:
      - A higher-level pattrstorage should inherit priorities from a lower- level pattrstorage if in greedy mode?
      or
      - The pattr object itself should have a @priority attribute to "hint" to pattrstorage that its priority should be set to a certain value when the patch is analyzed?
      or
      - ?
      jb
      Am 06.10.2006 um 10:09 schrieb Manuel Poletti:
      > Hi Jeremy, > > sorry if this was discussed ages ago : > > As the doc says so, is there any reason that a pattrstorage object > in a top-level patcher could not be able to reflect the priorities > of pattr obejcts being loaded from abstractions or subpatchers ? > It would be so useful, when pattr-priority is essential for your > DSP module to work great (in other words, the order in wich you > recall parameters is essential for your module to work properly), > if a large patch containing a lot of those modules could be quickly > stored into a global pattrstorage (a session) without problems (due > to the priority of parameters, sorry, again :). > > You follow me ? > > Salut, > > _M >
    • Oct 06 2006 | 8:54 am
      On Oct 6, 2006, at 10:40 AM, Jeremy Bernstein wrote:
      > Do you mean: > > - A higher-level pattrstorage should inherit priorities from a > lower-level pattrstorage if in greedy mode? >
      YES !!!
      > - The pattr object itself should have a @priority attribute to > "hint" to pattrstorage that its priority should be set to a certain > value when the patch is analyzed?
      This could be very useful as well.
      _M
    • Oct 06 2006 | 8:59 am
      Am 06.10.2006 um 10:54 schrieb Manuel Poletti:
      > > On Oct 6, 2006, at 10:40 AM, Jeremy Bernstein wrote: > >> Do you mean: >> >> - A higher-level pattrstorage should inherit priorities from a >> lower-level pattrstorage if in greedy mode? >> > > YES !!!
      If I write it on my list, will it make you happy? I don't anticipate working on any major updates to pattrstorage for the next while, but the time will come.
      >> - The pattr object itself should have a @priority attribute to >> "hint" to pattrstorage that its priority should be set to a >> certain value when the patch is analyzed? > > This could be very useful as well.
      This has come up many, many times. And I still don't know about it. But OK. .
      jb.
    • Oct 06 2006 | 9:44 am
      > If I write it on my list, will it make you happy?
      Yes, anyway ! Euh... whenever you'd feel it's more fun to compute a little more, I'd be VERY happy :)
      Many thanks,
      _M
    • Oct 06 2006 | 10:07 am
      It's not a question of computing v. not computing. It's a question of >what< one computes. You may find yourself very, very happy with the stuff being worked on these days. But you'll have to wait and see!
      jb
      Am 06.10.2006 um 11:44 schrieb Manuel Poletti:
      > Euh... whenever you'd feel it's more fun to compute a little more, > I'd be VERY happy :)
    • Oct 06 2006 | 4:39 pm
      if my vote counts (which it doesnt im sure :P) Id love these features myself.
      Thanks,
      v a d e //
      www.vade.info abstrakt.vade.info
      On Oct 6, 2006, at 4:59 AM, Jeremy Bernstein wrote:
      > > Am 06.10.2006 um 10:54 schrieb Manuel Poletti: > >> >> On Oct 6, 2006, at 10:40 AM, Jeremy Bernstein wrote: >> >>> Do you mean: >>> >>> - A higher-level pattrstorage should inherit priorities from a >>> lower-level pattrstorage if in greedy mode? >>> >> >> YES !!! > > If I write it on my list, will it make you happy? I don't > anticipate working on any major updates to pattrstorage for the > next while, but the time will come. > >>> - The pattr object itself should have a @priority attribute to >>> "hint" to pattrstorage that its priority should be set to a >>> certain value when the patch is analyzed? >> >> This could be very useful as well. > > This has come up many, many times. And I still don't know about it. > But OK. . > > jb.
    • Apr 19 2007 | 10:02 pm
      me too....
    • Apr 19 2007 | 10:02 pm
      (sorry for this double post... an error page with the forum...)
    • Apr 21 2007 | 12:23 am
      I need to throw in a "me too" for this.
      I rarely feel this strong about a feature request.
      I'm replacing years of my own state-saving logic with pattr. I have tons of patches that I reuse in many different situations. The lack of "@priority" hampers the benefits of making reusable patches, i.e., every time I reuse one, I have to once again manually add the priorities of its controls to the pattrstorage handling the particular environment.
      Since the hierarchical "::" path leading down to the patches changes from situation to situation, I can't simply cut and paste information.
      If the pleas of one more person might shift the (ahem) priority of adding "@priority", then consider this a plea.
      Adam
      > - The pattr object itself should have a @priority attribute to "hint" > to pattrstorage that its priority should be set to a certain value > when the patch is analyzed?