Re: [Audacity-devel] GUI support for VST committed

[Gale (A. Team) <ga...@au...>]

Leland (Audacity Team) wrote:
> I just committed the resurrected GUI support for VST effects.  This time 
> it's using the VeSTige VST header.
>
> I'm sure there will be issues found since there are MANY VST effects in 
> the wild, so we might have to tweak it here and there.  I was also 
> hoping folks could give it a try and give feedback on layout and such.

Leland, having tried the GSnap VST for Windows (see the thread about
AutoTalent), I find that GSnap has two entries in the Effect menu (whether
VST GUI mode is on or not), if vst-bridge.dll is in the Plug-Ins folder. Was
this expected? 

One Gsnap entry says just "GSnap" (this is the one added when the bridge is
present - it's tabular, with the crippled functionality we're used to, and
appears irrespective of mode). 

The other entry says "GVST:GSnap" and has the GUI when GUI is enabled, and a
more functional tabular interface when it isn't. Most other VST's I tried
before now (for example the Kjaerhus Classic series) just appear once
whether the bridge is present or not. These ones have no prefix and colon in
the name. 

I think this may be something of an issue if people install 2.0 into
C:\Program Files\Audacity so keeping the bridge in their Plug-Ins folder. I
"think" the plan is the default installation folder will be C:\Program
Files\Audacity (Unicode) for the Unicode 2.0 release. Can/should we suppress
the duplicate instances when the bridge is present? Or could the installer
look for and remove the bridge from C:\Program Files\Audacity\Plug-Ins? That
may not be appreciated if people are trying 2.0 out installed into another
folder.   



Gale 



-- 
View this message in context: http://n2.nabble.com/GUI-support-for-VST-committed-tp2944625p3059880.html
Sent from the audacity-devel mailing list archive at Nabble.com.