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

[Leland <le...@au...>]

Gale (Audacity Team) wrote:
> 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? 
> 
Unfortunately, yes. There's no way for the bridge or the new VST fella 
to know about each other, so there will most like be dups.

> 
> 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.   
> 
If we think the new VST code is good enough, the how about we have the 
Ladspa loader specifically look for and ignore the vst-bridge.dll?  This 
way ppl can pop back and forth between versions and they won't get any 
dups in 2.0.

Leland