pluggo has 2 dedicated hosts simply called "Pluggo" (for effects) and "Pluggo synth" (for vsti) made for loading vst-objects into the pluggo-environment. in PT these two dont work, because (as i picked up somewhere) PT dont allow plugins to open popup windows.

VST hosts also do not allow to open subwindows. for northpole or mda delay this is no problem, because oyu can learn their 7 parameters by heart, but i dont want to create imposcar patches blindly.

so, my personal way of dealing with this is to create a different pluggo-object for every vst-object. this is kind of boring work and should be done with scripts but ive been too lazy to learn that. (maybe 110 knows how)

for how many different plug-ins do you do that? and do you need control over the parameters of the hosted VST?

anyway, attached is an example: the "spectral_monkeyage_pi".

funny that you mention it. monkeyage and northpole were the two VSTs  whhere i´ve built a VST to VST bridge for ... in order to make them stereo. lol.

because the _pi-object looks up the spectral_monkeyage-vst everytime it opens. i use the vstplugins-folder in the max/msp folder itself.

i have never tried it but it should work to put those VST in the pluggo runtime folder, which is an unlimited, default runtime search path.

we will come back to this at a later point.