plugmultiparam bugreport, 4th outlet of vst~ blues


    Dec 11 2006 | 4:25 pm
    I think this is a bug in plugmultiparam. In a pluggo with a multislider connected to plugmultiparam, loaded in Max with vst~, no parameter index and value are output from the 4th outlet of vst~, when multislider is changed with the mouse inside the plug, or when programs are changed. Only when option click -> Undo Last Change, Randomize All, Evolve All and Copy All From Program is used inside the plug output is OK.
    I have been testing this issue on MaxMSP 4.5.7/Pluggo 3.5.4, PPC G4 and MaxMSP 4.6.2/Pluggo 3.6.1, PPC G3, both running Mac OS 10.4.8
    I'm transmitting the data from the vst~ outlet to other machines using udpsend/udpreceive, and it would be really usefull to have plugmultiparam working for this purpose.
    The following patches should show the bevaviuor.
    build a pluggo from this:
    load the plug with this
    Cheers, Jakob

    • Dec 11 2006 | 6:35 pm
      Hi,
      Yep - this is a known restriction - it has been round for ages.
      Unfortunately - there's almost nothing which can be done to workaround it.
      -A
    • Dec 11 2006 | 11:58 pm
      > >Yep - this is a known restriction - it has been round for ages. OK, wasn't aware of that. Why this restriction?
      > >Unfortunately - there's almost nothing which can be done to workaround it. I made sort of a workaround, an abstraction using a bunch of pp objects instead. Works as plugmultiparam - same arguments. Requires Lobjects. Save as abstraction, I call it pmp...
      Cheers, J
    • Dec 12 2006 | 12:25 am
      12/12/06, kl. 0:58 +0100 , skrev Jakob Riis:
      >> >>Unfortunately - there's almost nothing which can be done to workaround it. >I made sort of a workaround, an abstraction using a bunch of pp objects >instead. Works as plugmultiparam - same arguments. Requires Lobjects. >Save as abstraction, I call it pmp... sorry, I posted a wrong version before, here is the right one: