Pluggo VST doesn't report parameter values


    Mar 07 2006 | 11:52 am
    I am experiencing a problem with vst~ and Pluggo VST plugins.
    In a patch with several vst~ objects, Pluggo plugs only reports parameter
    values, when changed inside the vst plugin, if plugs are loaded in all
    other previous vst~ objects in the patch. Some non-pluggo VST plugins
    doesn't have this problem (f.ex. freeverb-c) while others have (f.ex.
    CamelPhatFree). If values are changed by control messages from outside
    the plugin, things works as expected.
    Is this a bug? Can anyone confirm this behaviour?
    I've made an example patch to illustrate the problem.
    /Jakob
    max v2;

    • Feb 21 2003 | 9:05 am
      07/03/06, kl. 12:52 +0100 , skrev Jakob Riis:
      >I am experiencing a problem with vst~ and Pluggo VST plugins.
      >
      >In a patch with several vst~ objects, Pluggo plugs only reports parameter
      >values, when changed inside the vst plugin, if plugs are loaded in all
      >other previous vst~ objects in the patch. Some non-pluggo VST plugins
      >doesn't have this problem (f.ex. freeverb-c) while others have (f.ex.
      >CamelPhatFree). If values are changed by control messages from outside
      >the plugin, things works as expected.
      Workaround: Create a 'dummy' pluggo, that does nothing, but contains some
      parameters anyhow. And load it instantly while patcher opens [vst~ dummy].
      I know this is turning into a private conversation, sorry! :-)
      /J