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

[Gale A. <ga...@au...>]

| From Leland <le...@au...> 
| Wed, 20 May 2009 01:49:59 -0500
| Subject: [Audacity-devel] GUI support for VST committed
> 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.
> 
> I have an option to add to Preferences that disables the GUI and falls 
> back to a plain text based dialog.  Doing this will allow us to get rid 
> of the vst-bridge, while still leaving an option for VI users.

Thanks, Leland.

OK, so are we free to mention this to users the next time one complains
they don't get the fancy display they were expecting in their VST effect,
or that it did not work?

Is the intention this will be in the 1.3.8 Release barring technical
problems?  

 
>  Please note that this is not VSTGUI support.  That's a different
> animal and is not needed by a VST host.

So we are not distributing the VSTGUI code that (possibly) we could 
have done, or anything of Steinberg - just the reverse-engineered 
LMMS headers? And when we update FAQs we do not need to mention 
anything about "downloading the VST SDK"?

And we still have a policy of pretending Beta does not exist on the 
FAQs on the main site, so any updates about this will only be on 
the version of the FAQs here:
http://www.audacityteam.org/manual/index.php?title=FAQ

until 1.4 comes out? 

 
> The effects are looked for in the Audacity "VST", "plugins", and 
> "plug-ins" directories.
> 
> On the Mac, /Users/<user>/Library/Audio/Plug-Ins/VST and 
> /Library/Audio/Plug-Ins/VST are also searched.
> 
> On Windows, registry key HKLM\Software\VST\VSTPluginsPath is also searched.

So if Windows users have plug-ins in:

    *  The path specified by the VST_PATH environment variable, if
        different  

    *  C:\Program Files\Steinberg\VSTPlugins 

they will now not have their plug-ins detected, which they would have
done using the vst-bridge? 

There are some older VST plug-ins on Mac aren't there (I forget what
they are called right now). Will these still be expected to work? 

 
Thanks


Gale