Tim Sutton

Hi, I'm new to Pluggo interfaces, and can't figure out why my VST build seems to ignore my plugconfig parameters for window sizes. Even though I'm using useviews 0 1 1 1 it still defaults to the parameters view, and my setsize and defaultview parameters seem to be ignored as well. (I just see the top left corner of my patch)

I've tried building the tutorial patches that use interfaces, and they work no problem. I hope I'm just missing something stupid here - this is driving me crazy!

Hi, I'm new to Pluggo interfaces, and can't figure out why my VST build seems to ignore my plugconfig parameters for window sizes.  Even though I'm using useviews 0 1 1 1 it still defaults to the parameters view, and my setsize and defaultview parameters seem to be ignored as well.  (I just see the top left corner of my patch)

#C useviews 0 1 1 1;
#C numprograms 8;
#C preempt 1;
#C sigvschange 1;
#C sigvsdefault 32;
#C setsize 400 320;
#C defaultview Interface 4 60 0;
#C dragscroll 1;
#C noinfo;
#C setprogram 1 "Default" 0 0. 0.8;
#C uniqueid 128 149 13;
#C initialpgm 1;

I've tried building the tutorial patches that use interfaces, and they work no problem.  I hope I'm just missing something stupid here - this is driving me crazy!

difficulty-with-interface-views

I haven't double checked your plugconfig real hard, but is that uniquid 

really unique to this plug-in as it should be? If you change it does it 

I haven't double checked your plugconfig real hard, but is that uniquid 
really unique to this plug-in as it should be?  If you change it does it 
help?
   -Tim


Brilliant!  Works like a charm.. thanks!


> Brilliant! Works like a charm.. thanks!

Cool. Just so you understand what happened here (and for the list 

The Pluggo engine identifies plug-ins by their uniqueid number, as do 

many VST hosts. So when you loaded a plug-in that has the same uniqueid 

as another plug-in, that other plug-in's plugconfig was being used 

Having two plug-in's with the same id can have a lot of seemingly 

mysterious consequences, so it's good to check when things are acting funny.

Tim Sutton wrote:
> Brilliant!  Works like a charm.. thanks!

Cool.  Just so you understand what happened here (and for the list 
archives)...

The Pluggo engine identifies plug-ins by their uniqueid number, as do 
many VST hosts.  So when you loaded a plug-in that has the same uniqueid 
as another plug-in, that other plug-in's plugconfig was being used 
instead of your plugconfig.

Having two plug-in's with the same id can have a lot of seemingly 
mysterious consequences, so it's good to check when things are acting funny.

Great - this explains the sense I had of something not being 'refreshed' in the build process. I kept checking my VST files to make sure the host was loading the most recent version. Can the unique ID be changed at will (to avoid having to re-save new patchers as new filenames)?

Great - this explains the sense I had of something not being 'refreshed' in the build process.  I kept checking my VST files to make sure the host was loading the most recent version.  Can the unique ID be changed at will (to avoid having to re-save new patchers as new filenames)?


well if you use a host program for testing your pluggos

which makes troouble when 2 version of your plug-in

have the same unique ID, try another host, or remove the

older version from its plug-i folder when you are going 

well if you use a host program for testing your pluggos
which makes troouble when 2 version of your plug-in
have the same unique ID, try another host, or remove the
older version from its plug-i folder when you are going 
to test a new build.


Right - I think I was at one point overwriting my old plugins, but perhaps not. I definitely started creating new versions at some point.

Right - I think I was at one point overwriting my old plugins, but perhaps not.  I definitely started creating new versions at some point.

difficulty with Interface views