I just installed 2.03 on my iMac 10.7.5 and I get a Registry Error, not installed correctly. The program will start and run but I can’t save/export/copy, etc. I had an older version installed. Is there an un-installer or what else might be causing the problem.
Thanks,
Joe B
This has happened before. Somehow we managed to produce a Windows error on a Mac. I’m not sure this is an advance.
https://forum.audacityteam.org/t/registry-error-with-mac-version/29098/3
So it’s not a one-off. You’re both on iMacs, too.
Koz
What exactly happens when you try to select and copy some audio? What happens when you try to export an AIFF?
That error is not in our source code. I believe it must be coming from some plug-in Audacity is trying to load.
Follow these steps.
Audacity > Quit Audacity.
In Finder, Go > Go to Folder,
Type
~/Library/Preferences/
Delete the file “audacity Preferences” if it exists.
Type
~/Library/Application Support/audacity/
Open the file “audacity.cfg” if it exists, otherwise create it. Edit audacity.cfg so it contains this text only and no other text
NewPrefsInitialized=1
[AudioUnits]
Enable=0
[VST]
Enable=0
Rescan=0
This disables Audacity from loading VST or Audio Unit plug-ins. Save audacity.cfg and launch Audacity. Do you still see the error?
Gale
OK, that worked but now I can’t do anything with effects. How does this help? I guess that a plug-in is causing an issue so does that mean I have to manually go thru and figure out which one it is?
Thanks, I do appreciate the swift response. I have a gig where I want to play a song but it’s loaded with hisses and pops which audacity did a beautiful job removing but now I can’t export it. Hmmmmm, I have an idea…
I’ll get back in a few
THX
Joe B
Well the bad news is that with the modified .cfg I can’t export as well. The GOOD news is that when I put the original .cfg back in (I DO back stuff up) I still threw the error but now the export and everything appears to work. I still get the registry error but I’m convince it’s a plug-in. No worries, I can live with the message if it lets me export the scrubbed audio which it did.
Thanks again for the help!
Joe B
Hooray 
Though it would be good to know where that error is coming from (and ideally, to fix it).
Since you are able to run Audacity, try going into Preferences, and in the Effect section, disable VST, then restart Audacity. Does that remove the error?
There is no reason that the .cfg I suggested:
NewPrefsInitialized=1
[AudioUnits]
Enable=0
[VST]
Enable=0
Rescan=0
would prevent you exporting. It would set Audacity back to its default export directory and it’s possible that might create an issue if you had no permission to write there, but you could change the export folder to a location where you did have permission.
It’s really a process of elimination to find the plug-in that causes that error. You can narrow it down to a VST or Audio Unit plug-in by disabling first VST only in Effects Preferences then restart Audacity, and then if necessary disable Audio Units and restart.
Here are the locations from which Audacity loads VST and Audio Units (assuming the problem isn’t to do with a VST in the Audacity Plugins folder):
VST:
~/Library/Audio/Plug-Ins/VST
/Library/Audio/Plug-Ins/VST
Audio Unit:
~/Library/Audio/Plug-Ins/Components
/Library/Audio/Plug-Ins/Components
Note those are four different locations (~/Library is your user library).
Gale