Problem with re-enabling plug-ins since upgrade to 2.2.2

[lespaulplayer621]

I have very similar crash log as ericb7799, almost identical actually. So I think that this similarity can confirm, that although we have different computer configurations the reason of our problem is probably the same.

[ericb7799]

no lespaulplayer621, I was mistaken and evidently it’s a normal log from FFMPEG.
See Steve’s last post. Well, back to square one as to any answer as to a cause.
In any case, so far the workaround is to just click “OK” through all the error messages.
Not the ideal fix, and it’s time consuming and inconvienient but at least can still get everything working.
Hopefully they figure out a proper fix in an update or something soon.

[mexikiwimike]

I have the same error occurring with a range of paid/demo plugins.

I installed 2.2.2 using the Windows Installer to the default location.

I have successfully installed and used other plugins (.ny) but have had no joy with paid/demo VST plugins.

[SenorN]

I have the same problem: added VST plug-ins won't register and don't appear under the Effects window. I ran Audacity as an administrator and that didn't help. (Running Windows 7 Home Premium, Version 6.1.7601 Service Pack 1 Build 7601, fully updated and Audacity 2.2.2

[steve]

Before reporting problems with plug-ins, please ensure that you have the current version of Audacity (available via the Audacity website), and have read the current documentation.


When reporting problems with plug-ins, it is essential that you include the following information:

• Version of Audacity (example: 3.1.4)
• Name of the plug-in
• Plug-in type (example: VST, VSTi, VST3, AU, RTAS, AAX ...)
• Plug-in format (32-bit / 64-bit)
• Plug-in version
• Where was the plug-in obtained (link)
• Plug-in website address
• Version type: Full commercial / Full freeware / Demo / Trial / Other (please specify)
• Why do you think that this plug-in is compatible with Audacity? (example; "I used it successfully in Audacity 1.2.6" / "The plug-in website says it is compatible with Audacity 3.1.4")

[lespaulplayer621]

Before reporting problems with plug-ins...

Thanks for your advice steve, but I think that everyone in this forum thread provided that kind of information. Maybe they are not so precise and exhaustive as you suggest, but in my view they are meaningful enough to fix the issue with plugins. Everyone here uses Audacity 2.2.2. and has a problem with VST plugins, so I think that the developers of Audacity should concern on that informations.

Also I have one suggestion - if every kind of plugin worked completely fine in previous version of Audacity, so maybe the developers of this program should give us download option for Audacity 2.2.1.? Then we can continue our work on version which worked well, and the developers can continue works on fixing the issue with plugins.

[steve]

if every kind of plugin worked completely fine in previous version of Audacity

It didn't.
64-bit VST plug-ins are not supported.
VST3 plug-ins are not supported.
VSTi plug-ins are not supported.
Most plug-ins that have proprietary "protection" are not supported (this includes many of the expensive commercial plug-ins).
Plug-ins that require dongles are not supported.
Plug-ins that require MIDI support are not supported.
RTAS plug-ins are not supported.

Most of the above information may be found in the Audacity manual, but with over 500 pages in the manual it is not always easy to find what you need.

"It's not working" is not a question we can answer.
If a plug-in is not working, we need to know which plug-in, whether it is a supported plug-in type, if it's a free plug-in that we are not familiar with then we can try it and report back to the user IF they tell us where to get it from.

Audacity 2.2.1 is available from the OldFoss website, but it has a serious bug: viewtopic.php?f=46&t=99026
There has been no change to VST or AU support in recent Audacity releases, so if a plug-in does not work in Audacity 2.2.2 it is unlikely to work in earlier versions of Audacity. However, there have been recent changes to how plug-ins are enabled. This is described in the manual here: https://manual.audacityteam.org/man/man ... yzers.html

[bubby]

hey all, I am using windows 10 and tried all the fixes said here, but unfortunately, none worked.
what i did instead was just go to the audacity homepage and find a link to download audacity version 2.2.1
I know that's not necessarily a "fix" (since not every type of plugin worked in the 2.1 version) but its at least something.
if you were curious, i was trying to install gvst plugins, and this worked fine for me.

[waxcylinder]

2.2.1 has a VERY serious bug that can cause loss of your project data.

If you insist on using 2.2.1 do NOT ever use "File > Save As..." to save your current project - only us File > Save or its shortcut Ctrl+S

WC

[ericb7799]

The plug-in registry issue noted in my post above unfortunately is now exponentially worse on Audacity 2.3.0. In 2.2.2 woud only encounter the errors when using add/remove efects, and the unfriendly workaround was to just click ok through all the errors. This was not the most elegant of workarounds and depending on number of plug-ins would take a long period of time. However, this would only have to be done once or when adding or removing plug-ins. The new version 2.3.0, however, not only did not fix the issue but is exponentially worse. In 2.3.0 the errors now occur immediately upon launching the app, when closing a project, when opening a new project, in addition to adding or removing plug-ins. in my case this translates to having to click through 30 minutes of error messages just to open the app, and again another 30 minutes of clicking through the errors just close a project or open a new project. This effectively makes version 2.3.0 completely unuseable in my case. The probem is not limited to Windows and the exact same issues occur on my Mac as well. We never found the cause to the problem in 2.2.2 but at least the app was useable, which is not the case here with 2.3.0. Anyone have any ideas what can be done with this?