I’m reading a lot of issues with 2.1.2, and as I have a working 2.1.1, I guess the thing to do is just wait for the fixes? yes/no?
Also - installing 2.1.2 wipes out all plugins and settings - is it best to merge rather than overwrite the installation on the Mac (mini)
Robert
It is not recommended to use alpha builds of Audacity as a general rule, unless you want a specific fix that has been made therein. And even then, there may be other bugs new to the alpha build that still have to be ironed out.
In principle, installing 2.1.2 should not affect Audacity settings in any way. The only way to reset Audacity settings is to quit Audacity then delete ~/Library/Application Support/audacity/audacity.cfg.
Some keyboard shortcuts for items in cascading menus may fail in 2.1.2 due to a bug that has now been fixed.
When you are installing into the same directory, both “Keep newer” and “Replace all” will update your files with the newer copies that are in the installer.
“Keep newer” retains any files in your existing Audacity folder that are not in the new installation and updates files that are in the new installation.
“Replace all” deletes any files in your existing Audacity folder that are not in the new installation. For example if you had plug-ins that were not shipped with Audacity, “Replace all” would delete them.
Gale
Generally, 2.1.2 is stable. I haven’t found any real problems. The loss of drag and drop import functionality is the only thing I can think of that is missing and that worked in 2.1.1.
It’s also easy to install both versions, if you keep in mind that they’ll share some settings. You just need to rename the programs from “Audacity” to “Audacity 2.1.1” and the other one to “Audacity 2.1.2”.
There’s also the “portable install”, that will make your install independent:
http://wiki.audacityteam.org/wiki/Portable_Audacity
I’m currently testing plugins and it’s generally better than 2.1.0. But that’s a feeling, not an objective observation.
Installing 2.1.2 will not delete plugins. But you need to “scan” your plugins folder again an enable those you want.
If that’s the case it’s a bug, assuming you did not delete pluginregistry.cfg.
If you think there is a bug here, can you be specific about which plugins and the exact path where they are located.
Thanks
Gale
It’s not a bug - I deleted pluginregistry.cfg repeatedly after installing bad plugins and to make sure the registry wouldn’t influence further testing.
I’m quite pleased most plugins work without a hitch. Only Java based plugins seem to crash a lot. But that’s probably due to the Java versions on my Mac and I’m not wasting my time with it as there aren’t that many Java based VST’s around. There’s only one useful VST that springs to mind: GonioMeter. I’m sure I’ll find another one with similar - or better - functionality…
When you are installing into the same directory, both “Keep newer” and “Replace all” will update your files with the newer copies that are in the installer.
“Keep newer” retains any files in your existing Audacity folder that are not in the new installation and updates files that are in the new installation.
“Replace all” deletes any files in your existing Audacity folder that are not in the new installation. For example if you had plug-ins that were not shipped with Audacity, “Replace all” would delete them.
Ok, so what I did the other day, was download the DMG file, and in the Installation window, dragged the Audacity folder to the Applications folder.
It asked me if I wanted to Merge it with the existing folder, or Replace the existing folder. I thought ok, it should be smart enough to keep settings, so I opted for Replace.
That’s what it did. Wiped out the original directory completely, and replaced it with the new one. I then discovered that none of the plugins I had previously were now available.
It didn’t even look like it had found all the configs…
In principle, installing 2.1.2 should not affect Audacity settings in any way. The only way to reset Audacity settings is to quit Audacity then delete ~/Library/Application Support/audacity/audacity.cfg.
Not having the time to fiddle around and find al the plugins and the ffmpeg and mp3 things was well, I deleted it, and Restored from backup, the original Audacity folder. Which fortunately came up and worked again. So I’m back to 2.1.1 until I have the time and inclination to try again. 
I’m new to Mac OS X and I don’t yet know exactly what the “merge” option does, but a simple way round that problem is to make a backup copy of
Applications/Audacity/Plug-ins before you install the new version.
Note that some of the plug-ins in the new version of Audacity may have been updated, so you should avoid overwriting them with your old versions.
Apparently Apple renamed the functions I mentioned at some point in newer versions of OS X. So, “Replace” is the same as the “Replace all” I mentioned and “Merge” is the same as the “Keep newer” I mentioned.
Apple is not being very intuitive here in my opinion, but Replace did what you asked for, and basically gave you what was in the Audacity DMG and removed everything else.
Short of us making a PKG installer that specifies exactly what happens, you have to use the tools that Apple give you.
Just use Merge, or “Keep newer” on older OS X.
LAME and FFmpeg should usually be installed in system locations and if so should not be affected by upgrading from 2.1.1 to 2.1.2.
What plugins did you lose? VST? If so, install those in system locations ~/Library/Audio/Plug-Ins/VST or /Library/Audio/Plug-Ins/VST.
Also note that any plugins that you can put in the “Plug-ins” folder in the Audacity installation folder can be put instead in the ~/Library/Application Support/audacity/Plug-Ins/ folder. That way you don’t lose plugins if files get accidentally replaced during installation.
If you install plugins and libraries in system locations that also lets you rename the “Audacity” folder after installation as the version number it is, so you know what version you have. When you install the new Audacity version, delete the folder for the older version, unless you want to keep it.
Gale
I’m playing it really safe sticking with Audacity 2.0.0. Haven’t been able to successfully download later versions. But I think Koz offered most effective advice. I quit Audacity, connected usb, then connected to Audacity and got my options for Audio CODEC back. Thank you. All is well now. Maybe I’ll wait for 2.1.2a also.
BrendaT
This is where you download Audacity http://audacityteam.org/download/mac.
“a” means alpha, the work in progress for the next released version.
2.1.2 alpha already exists. You do not want that, as you are not a developer or tester. Wait for 2.1.3.
Gale