no midi events for vst... ?


    Jun 16 2008 | 8:51 pm
    hi
    making exactly the same (easy) patch on 2 mac, PPC and Intel works on PPC not on Intel
    _patch:
    _[vst~] object, a "plug" message - with this message I call the "Ohm Force Ohmicide" plug-in _switch on audio
    _and I send a [midievent 144 60 60] to the vst~ (the Ohmicide accepts midinotes to control some of its parameters, the "melohman" presets section)
    in the case of my PPC (maxmsp 4.5.7, macOS 10.4.11) it all works as it should (the preset changes)
    in the case of the intel (maxmsp 4.6, macos 10.5.2), max says "effect doesn't want events" (and the preset does not change)
    *********
    I also tried the plug from PPC (it IS UB) in the Intel, same problem............
    so it seems there is something which changed with the vst........
    (now I am only afraid to receive an answer saying that all I have to do is to pay $ 199, and that C74 does not care about 4.6......... no, please!?)
    best
    kasper -- Kasper T. Toeplitz noise, composition, bass, computer http://www.sleazeArt.com

    • Jun 16 2008 | 9:52 pm
      There was a bug related to midievent handling in vst~ which got fixed in Max 5. This looks to me like that bug.
      Sorry no, we won't be updating the 4.6 version of vst~.
      -A
    • Jun 17 2008 | 8:33 am
      >There was a bug related to midievent handling in vst~ which got >fixed in Max 5. This looks to me like that bug. > >Sorry no, we won't be updating the 4.6 version of vst~. >
      don't know - for sure so far it seems to happen only with OHMForce plugs (or related - GMedia's Oddity........)
      I just moved to Intel - and to 4.6 - and am discovering that this "painless" transition (also from max 4.5 to 4.6) is not painless at all, quite a lot of things do not work as they did (had quite some problems with one of the GRM tools, which GRM fixed since then)
      now of course hearing that only the "hello kitty" version of max, released less than 2 months ago (or so) is supported is not good news (especially when I am beginning to see/hear people who had the time to check the demo of 5 and decided NOT to upgrade.... )
      hummm
      thanks for the quick answer, anyhow
      kasper -- Kasper T. Toeplitz noise, composition, bass, computer http://www.sleazeArt.com
    • Jun 17 2008 | 2:31 pm
      A workaround is to roll a preset manager for those plugs and do the state changes yourself. I use them all the time this way. They are very well behaved plugs, and Ohmicide is fantastic.
      -A
    • Jun 17 2008 | 8:14 pm
      hi andrew
      would it be ONLY the preset problem (which is what I pointed first, when speaking about Ohmicide) it would be half-bad - as yes, i usually do my own preset systems for plug-ins.
      still the "half-bad" is there as it is something that worked (in 457) but does not, anymore (in 46).
      then it becomes worst since I discovered that none of the OHM force plug-ins does recognise the "midievent" message (and they all did in max 457)
      which means that VSTi such as Symptohm (from ohm force) or Oddity (by Gmedia, but actually done by OhmForce) do not work, or at least do not understand "midievent" - which is (as far as I Know) the only way to send them notes - or midi-notes. Well, pitches..
      I did not have the opportunity to try how minimosta or other Gmedia plug-ins behave (and if anyone could, that would be great) but i am afraid it is the same - and those very plug-ins do work in 457 (and as you said, you -C74 - know vst~ in 46 is broken, or has a problem with midievent)
      _of course i did send email(s) about it to ohm force.......
      _I also understand you (C74) are excited about your latest release.... fine.... but since it is not only an upgrade to max 4 but a big change (I read it was "similar to the change of macOS from 9 to X") I belive it is easy to understand some people do not want to change it just because it's there (especially when you have concerts, projects etc - not the best moment to change your main software). So it is not only a question of the look of max5, of the upgrade price, or of a bigger cpu charge....
      just feels like a "we don't care"
      anyhow, all the best
      kasper -- Kasper T. Toeplitz noise, composition, bass, computer http://www.sleazeArt.com
    • Jun 18 2008 | 4:22 pm
      Ok - try this one.
      It's a 4.6 version which should work right with midievents.
      You're on your own if you want to use it. Please let me know if you spot any problems.
      If it seems to work ok I'll put it up on incrementals.
      -A
    • Jun 18 2008 | 4:26 pm
      bump
    • Jun 20 2008 | 10:12 am
      hi, I had the same problem with Magenta. Does not want midievent. So how is the new one working?
      Also, Andrew I wish we could make an au~ object under Max 5. Many plug-in companies are shifting their focus to au currently.
    • Jun 20 2008 | 10:58 am
      >hi, >I had the same problem with Magenta. Does not want midievent. So >how is the new one working? >
      beautifully
      kasper
    • Nov 09 2008 | 1:14 pm
      Hi... It seems that vst~ have problems with midievent globally... I'm simply using it with synths, and some note-on and note-off events drop out.
      So i'm interesting in another version of thas vst~ object. I tried to download the one below, but it seems it is only a Mac version, and i use a PC. Is there a way to get this vst~ object for windows ?
      Thank you,
      Regards
      Fred CAZAUX