special [midiformat] needed for [vst~]


    Aug 03 2006 | 6:06 am
    I'm about to build an ugly abstract to take care of this, but I feel like
    complaining anyway.
    [midiformat] is great. It outputs a midi event in its true form, as several
    successive integers. cool.
    [vst~] takes the message |midievent $1 $2 $3|
    The problem is that to turn [midiformat]'s output into something usable for
    [vst~], you have to group the successive integer outputs from [midiformat]
    into a list. Easy enough with [zl group 3] in the case of notes, but what
    about pgm change? That's only 2 integers out of [midiformat]! [zl group]
    messes everything up if it gets 2 integers when its looking for 3! [thresh]
    could work, but it's too slow separate the notes when chords are played!
    For this case, we need an object that acts just like [midiformat], but
    outputs lists.
    cheese

    • Aug 03 2006 | 6:48 am
      >I'm about to build an ugly abstract to take care of this, but I feel
      >like complaining anyway.
      >
      >[midiformat] is great. It outputs a midi event in its true form, as
      >several successive integers. cool.
      >
      >[vst~] takes the message |midievent $1 $2 $3|
      >
      >The problem is that to turn [midiformat]'s output into something
      >usable for [vst~], you have to group the successive integer outputs
      >from [midiformat] into a list. Easy enough with [zl group 3] in the
      >case of notes, but what about pgm change? That's only 2 integers out
      >of [midiformat]! [zl group] messes everything up if it gets 2
      >integers when its looking for 3! [thresh] could work, but it's too
      >slow separate the notes when chords are played!
      >
      >For this case, we need an object that acts just like [midiformat],
      >but outputs lists.
      >
      or just make your lists of integers ( 2 or 3) and [prepend midiformat]?
      should work, i think
      kasper
      --
      Kasper T. Toeplitz
      noise, composition, bass, computer
    • Aug 03 2006 | 7:41 am
      You may use [thresh] to separate the lists :
      f.e
      f.e chanfrault | aka | personal computer music
      > >>>>>> http://www.personal-computer-music.com
      > >>>>>> |sublime music for a desperate people|
      cheese wrote:
      > I'm about to build an ugly abstract to take care of this, but I feel
      > like complaining anyway.
      >
      > [midiformat] is great. It outputs a midi event in its true form, as
      > several successive integers. cool.
      >
      > [vst~] takes the message |midievent $1 $2 $3|
      >
      > The problem is that to turn [midiformat]'s output into something
      > usable for [vst~], you have to group the successive integer outputs
      > from [midiformat] into a list. Easy enough with [zl group 3] in the
      > case of notes, but what about pgm change? That's only 2 integers out
      > of [midiformat]! [zl group] messes everything up if it gets 2
      > integers when its looking for 3! [thresh] could work, but it's too
      > slow separate the notes when chords are played!
      >
      > For this case, we need an object that acts just like [midiformat], but
      > outputs lists.
      >
      >
      > cheese
      > ------------------------------------------------------------------------
      >
      >
    • Aug 03 2006 | 7:46 am
      OK, the abstract took less time than the email. It's just a wrapper for
      [midiformat] with a right outlet that outputs the MIDI event as a list.
      cheese
      max v2;
      On 8/2/06, cheese < fraudulentfromage@gmail.com> wrote:
      >
      > I'm about to build an ugly abstract to take care of this, but I feel like
      > complaining anyway.
      >
      > [midiformat] is great. It outputs a midi event in its true form, as
      > several successive integers. cool.
      >
      > [vst~] takes the message |midievent $1 $2 $3|
      >
      > The problem is that to turn [midiformat]'s output into something usable
      > for [vst~], you have to group the successive integer outputs from
      > [midiformat] into a list. Easy enough with [zl group 3] in the case of
      > notes, but what about pgm change? That's only 2 integers out of
      > [midiformat]! [zl group] messes everything up if it gets 2 integers when its
      > looking for 3! [thresh] could work, but it's too slow separate the notes
      > when chords are played!
      >
      > For this case, we need an object that acts just like [midiformat], but
      > outputs lists.
      >
      >
      > cheese
      >
      --
      ---------------------
      Powerbook G3/500 640/40 - Stilll great for audio!
      Max/MSP, Live 4, DP4, & various hardware synths
    • Aug 03 2006 | 1:14 pm
      > or just make your lists of integers ( 2 or 3) and [prepend midiformat]?
      >
      > should work, i think
      >
      > kasper
      thats true, just _abuse midiformat and it will work
      like you want. the objetcs knowsn nothing about midi,
      it simply performs a certain formatting on the input
      given.
      alternatively .. hmm .. try to see the controller
      interpretation as a part of the program, an not as
      a part of plug-in hosting. :)
    • Aug 03 2006 | 6:47 pm
      > alternatively .. hmm .. try to see the controller
      > interpretation as a part of the program, an not as
      > a part of plug-in hosting. :)
      That was where I came from! I'm not entirely sure that it was a good idea to
      switch to using midi internally in my patch, but it uses far fewer objects
      than my "proprietary" protocol that I switched from. Midi is easier for the
      routing of events to multiple devices, and it's nice to just be able to
      stick all the different events into [midiformat] and into a bus.
      What do others use internally?
      cheese