After installing 1.3.8 I get an error message of "Can't load module. 'Chorus Effect". Clicking ok just makes a beep and the box reappears with 'dehaupt MatchGate' instead of 'Chorus Effect', then eventually with 'dehaupt to CVtoMIDI_CC' instead of MatchGate. The only way to stop this is to forcibly end the task.
??? I just tried uninstalling 1.3.7 before installing 1.3.8 but same deal.
I'm using Vista SP2.
"Can't load module X" after 1.3.8 install
Forum rules
Audacity 1.3.x is now obsolete. Please use the current Audacity 2.1.x version.
The final version of Audacity for Windows 98/ME is the legacy 2.0.0 version.
Audacity 1.3.x is now obsolete. Please use the current Audacity 2.1.x version.
The final version of Audacity for Windows 98/ME is the legacy 2.0.0 version.
Re: "Can't load module X" after 1.3.8 install
You have some VST effects installed on your computer that are incompatible with Audacity 1.3.8
Try upgrading to Audacity 1.3.9 available from here: http://wiki.audacityteam.org/index.php? ... tly_Builds
Try upgrading to Audacity 1.3.9 available from here: http://wiki.audacityteam.org/index.php? ... tly_Builds
9/10 questions are answered in the FREQUENTLY ASKED QUESTIONS (FAQ)
Re: "Can't load module X" after 1.3.8 install
Hmmm, did the 1.3.9 install but same result. Although this time it started scanning my VST's - got stuck on one of them and then the never-ending error box appeared... 
Re: "Can't load module X" after 1.3.8 install
I've not got Windows or VST's so I can't test this - is there any way to tell Audacity to disable VST support before it starts scanning?
9/10 questions are answered in the FREQUENTLY ASKED QUESTIONS (FAQ)
Re: "Can't load module X" after 1.3.8 install
Hmm. Could this be done simply by renaming the "Plug-Ins" folder?stevethefiddle wrote:I've not got Windows or VST's so I can't test this - is there any way to tell Audacity to disable VST support before it starts scanning?
-
billw58
- Forum Staff
- Posts: 5600
- Joined: Wed Aug 12, 2009 2:10 am
- Operating System: macOS 10.15 Catalina or later
Re: "Can't load module X" after 1.3.8 install
Once Audacity has scanned for VST effects, and written something to the "plugins.cfg" file, it should not scan again on startup. See this thread: http://forum.audacityteam.org/viewtopic ... 16&t=14801jademan wrote:Hmm. Could this be done simply by renaming the "Plug-Ins" folder?stevethefiddle wrote:I've not got Windows or VST's so I can't test this - is there any way to tell Audacity to disable VST support before it starts scanning?
I wouldn't rename the plug-ins folder since that would eliminate all your plug-ins. Do you know which VST effect is causing the hang? Try removing all VST effects from your plug-ins folder, start Audacity, quit Audacity, add one VST back, start Audacity, etc. until you identify which effect is causing the problem.
-- Bill