visibility of pattr objects for pattrstorage.


    May 18 2006 | 10:22 am
    I want to exclude some pattr objects out of the visibility of a
    pattrstorage.
    I haven't found any ways to achive this. I could imagine two methods,
    one method to tell pattrstorage to exclude an object (with a message)
    or to tell a pattr/autopattr object to make itself invisible for
    pattrstorage.
    The reson I need that is, I have an abstraction which translates values
    from a Midicontroler (a dial) this is fine to have it pattrified. But if
    I have multiple destinations, I need to exclude it from the visibility,
    as otherwise I get inconsistant memories, the dial remebers its values
    and throws it to wrong places...
    Another related problem is: I store VST parameters into a pattrstorage,
    but when I change the VST, the number of parameters can vary
    dramatically, I'd like to store only the relevant ones, If I choose an
    additive synth, its up to 1000 parameters, if its a delay it might be
    only two.
    Any tips how to streamline this are welcome. At the moment I keep track
    only of 64 parameters... which is not ideal.
    Storing them inside the VST preset system is not an option, as I want to
    interpolate presets (for the same VST...)
    Stefan
    --
    Stefan Tiedje------------x-------
    --_____-----------|--------------
    --(_|_ ----|-----|-----()-------
    -- _|_)----|-----()--------------
    ----------()--------www.ccmix.com

    • May 18 2006 | 11:33 am
      On 18.05.2006, at 12:22, Stefan Tiedje wrote:
      > I want to exclude some pattr objects out of the visibility of a
      > pattrstorage.
      hi stefan, check out pattrstorages 'active' message, demonstrated in
      the 'active' subpatcher!
      jan
    • May 18 2006 | 12:22 pm
      Jan Klug wrote:
      > hi stefan, check out pattrstorages 'active' message, demonstrated in
      > the 'active' subpatcher!
      just found it myself, I assumed all messages are listed in the manual,
      but in this case the help file seems more complete...
      thanks,
      Stefan
      --
      Stefan Tiedje------------x-------
      --_____-----------|--------------
      --(_|_ ----|-----|-----()-------
      -- _|_)----|-----()--------------
      ----------()--------www.ccmix.com
    • May 18 2006 | 2:53 pm
      As far as writing a general patch for interpolating VST presets goes, I have had moderate amounts of succes with two different approaches.
      Option one involves writing some array based thing in js or java and performing some kind of interpolation between array elements.
      Option number 2, which is much quicker to hook up, is to throw the vst parameter data into a jitter matrix and use jit.xfade to go between the matrices.
      The problem remains with plugs which have a gazillion parameters, performing preset morphs can become a fairly sluggish business.
      Here's my clunky Jitter patch.
    • May 18 2006 | 3:45 pm
      i also experienced very faster interpolation with jit.xfade than doing it
      directly in pattr.
      I think it is not a problem to interpolate gazillion parameters, considering
      that when you interpolate 2 matrices sized 320*240, that already
      make 76800 parameters... Maybe gazillion is more than i think, but i see
      nothing sluggish there..
      Andrew Bhas written a patch for that in the Jitter recipes.
      best
    • May 18 2006 | 4:27 pm
      what i use is this relatively simple patch (no jitter nor js) not
      sure how many elements you may store in a coll (on the same line) but
      it's more than 64 (just tried with more than 100)
      of course you could save the coll with the patcher - or coll it
      differently, according to the vst you use
      hope it can help
      best
      kasper
      --
      Kasper T. Toeplitz
      noise, composition, bass, computer
    • May 18 2006 | 4:50 pm
      Not inside Jitter there isn't. Getting the data to the vst plugin is where you can get a bottleneck.
      -A
    • May 18 2006 | 5:20 pm
      ooops, forgot to include the patch
      kasper
    • May 18 2006 | 10:52 pm
      Quote: Kasper T Toeplitz wrote on Thu, 18 May 2006 12:27
      ----------------------------------------------------
      > what i use is this relatively simple patch (no jitter nor js)
      here is one using only pattr & multislider
    • May 19 2006 | 8:32 am
      oh, nice - and the use of "get -4" will clean up my own patch!
      best
      kasper
    • May 19 2006 | 8:42 am
    • May 19 2006 | 10:14 am
      i'm also sure the bottleneck is getting the messages thru to vst~
      there will be performance problems with plugs holding to many params... one thing that might help is to qlim the output of the multislider a bit - relative to the number of parameters (i.e. the more params in plugin, the higher granulation of the interpolation messages ;)
    • Mar 17 2007 | 1:11 pm
      Excuse me for reopening this thread.
      I would like to be able to exclude a pattr from the visibility of every pattrstorage by setting an attribute -on the pattr-.
      Have a look at this patch. For obvious reasons I want to exclude the bottommost pattr:
      Is there a way to do this? If not, I'd like to make it a feature request.
      Cheers,
      Mattijs
      Quote: Jan Klug wrote on Thu, 18 May 2006 13:33
      ----------------------------------------------------
      >
      > On 18.05.2006, at 12:22, Stefan Tiedje wrote:
      > > I want to exclude some pattr objects out of the visibility of a
      > > pattrstorage.
      >
      > hi stefan, check out pattrstorages 'active' message, demonstrated in
      > the 'active' subpatcher!
      >
      > jan
      >
      >
      >
      ----------------------------------------------------
    • Mar 17 2007 | 1:25 pm
      No. I will add your feature request to pile of similar feature
      requests you surely noticed as you were searching the forum.
      jb
      Am 17.03.2007 um 14:11 schrieb Mattijs Kneppers:
      > Is there a way to do this? If not, I'd like to make it a feature
      > request.
    • Mar 17 2007 | 2:31 pm
      Thanks,
      I personally find this approach to feature requests very inspiring:
      Best,
      Mattijs
      Quote: Jeremy Bernstein wrote on Sat, 17 March 2007 14:25
      ----------------------------------------------------
      > No. I will add your feature request to pile of similar feature
      > requests you surely noticed as you were searching the forum.
      >
      > jb
      >
      > Am 17.03.2007 um 14:11 schrieb Mattijs Kneppers:
      >
      > > Is there a way to do this? If not, I'd like to make it a feature
      > > request.
      >
      >
      ----------------------------------------------------