Jakob Riis

I've had troubles with the 4th outlet of vst~ before. And now I

discovered a new issue that I think must have been introduced with my

switch from MaxMSP 4.5 on PPC to MaxMSP 4.6 on intelmac.

The problem is that when a new preset program are selected inside the

user interface of a Plugggo vst plug-in, no parameter values are

reported out the 4th outlet of the vst~ object. I need this

functionality for a multiuser system where we exchange data from the vst

parameter values over udp network. (Things are OK when sliders etc. are

moved inside the plug, and I have a workaround to get the values when

new program presets are selected outside the plug-in.)

MacBook Pro, 2.2 GHz Intel Core 2 Duo, Max OS X 10.4.10.

This patch should illustrate the problem:

I've had troubles with the 4th outlet of vst~ before. And now I
discovered a new issue that I think must have been introduced with my
switch from MaxMSP 4.5 on PPC to MaxMSP 4.6 on intelmac.

The problem is that when a new preset program are selected inside the
user interface of a Plugggo vst plug-in, no parameter values are
reported out the 4th outlet of the vst~ object. I need this
functionality for a multiuser system where we exchange data from the vst
parameter values over udp network. (Things are OK when sliders etc. are
moved inside the plug, and I have a workaround to get the values when
new program presets are selected outside the plug-in.)

My setup is:
MacBook Pro, 2.2 GHz Intel Core 2 Duo, Max OS X 10.4.10.
MaxMSP 4.6.3, Jitter 1.6, Pluggo 3.6.1

Jakob Riis
New! jr.abstractions for MaxMSP
http://www.sonicescape.net/maxmsp/
__________________________________


vst~ 4th outlet revisited