Audacity 1.39 problems with VST plugins, 1.38 is fine..why?

[takm]

I'm using Windows 7, and while using audacity 1.39, i found that it didn't find some of the VST plugins i have installed. But if i downgraded to 1.38 it will find them all, 1.38 would only work if compatibility mode with XP SP3 was enabled. The plugin in question is the Amplitube 2... does anyone know why i'm having this problem???

[jademan]

takm,

This is a discussion foum; the people perusing here may not be ready to deal with this issue. Since no one has replied yet, would you consider re-posting under the appropriate beta forum ?

[steve]

Audacity 1.3.8 uses the "VST bridge" plug-in (as it had no VST support on its own).
Audacity 1.3.9 now has built in VST support and should be used without the VST bridge.

There's an awful lot of VST plug-ins to test, so developing VST support is likely to be ongoing for quite a while.

[Gale Andrews]

Audacity 1.3.8 uses the "VST bridge" plug-in (as it had no VST support on its own).
Audacity 1.3.9 now has built in VST support and should be used without the VST bridge.

Actually, 1.3.8 was the first version to offer the new VST GUI support without need of the "VST Bridge" Enabler. The difference is probably that while 1.3.8 loaded every plug-in it could find each time it launched, 1.3.9 scans for plug-ins only the first time it finds any, keeping a record of those it does find. On each launch thereafter, it only loads the plug-ins it found and recorded that first time. We made this change so that every launch of Audacity would not be slowed up by a complete rescan.

So to have Audacity detect newly added VST effects, you have to go to the Effects tab of Preferences, check "Rescan VST effects next time Audacity is started", click OK, and restart Audacity. See this "Click here before posting" topic for more details.


Gale