FAQ:Installation, Startup and Plug-ins

From Audacity Development Manual

(Redirected from LAME MP3)
Jump to: navigation, search


Flag of Brazil small.jpg FAQ : Installation et greffons FAQ: Installation und Plug-Ins FAQ:Installazione e Plug-In FAQ:Instalação, Arranque e Plug-Ins FAQ:Instalación y complementos

>  Forward To: FAQ:Recording - Troubleshooting

<  Back to: FAQ:About Audacity

|< Index of Frequently Asked Questions

Contents


What should I do if I have problems downloading or installing Audacity?

If you can't download Audacity, or if the downloaded setup file is corrupt, try downloading it from our alternate servers. On the page you come to, click the link that says "Looking for the latest version?". If you want the zip version of Audacity for Mac or Windows, click on the link for the "audacity" folder then on the page you come to, click the link for the folder at the top of the list.

If you receive a corrupted file once, it's a very good idea to clear the download list or cache in your web browser or download manager before downloading again.


What should I do if I get errors building Audacity?

Audacity provides ready-built installer programs for Windows and Mac, but Audacity can also be built from source code on any platform. With a little knowledge, building is a great way to customize Audacity! For help, please see the Wiki documentation for Windows, Mac and Linux.

If you still cannot build Audacity, please ask on the Compiling Audacity board on the Forum.

  • Please tell us whether you are building from a release tarball or Audacity HEAD.
  • On Windows, please give all the instances of "ERROR" in the Visual Studio output window (including Linker errors).
  • For Mac and Linux, please provide the last lines of the configure or make output that fail.
    • For Linux, also tell us which distribution and release you are using (for example, Ubuntu 11.10 or Fedora 16).

back to top


Windows: How do I install Audacity, and do I have to uninstall a previous version first?

Save: On the download page, left-click the "installer" link to save it to your computer. Check the browser preferences if necessary to find out where your downloads are saved. Alternatively, right-click over the link, "Save Target As" or "Save Link As" and choose the location to save the file to. Then double-click the downloaded .exe file to start the installer. You must be an administrator on the computer to do this, or follow the prompts to confirm your permission to install.

Run: Using Internet Explorer and a few other browsers, you can left-click the "installer" link and select an option to "Run" the file. This launches the Audacity setup immediately. Note: Some security programs will query or block installers running from the computer's temporary space.

Updating a previous installation: If you install a new Audacity version after installing a previous one, the installer will offer to install to the same directory as the previous installation. If the previous installation was Audacity 1.2 or 2.x, the installation directory is normally Program Files\Audacity (or Program Files(x86)\Audacity on 64-bit Windows). As long as you don't change the installation directory, Audacity will install over the previous 1.2 or 2.x version, and any extra plug-ins you added to the "Plug-Ins" folder will still be available.

If the previous version was 1.3.x, please uninstall 1.3 before installing the current 2.x version. After uninstalling 1.3, any extra plug-ins you added to that version will remain, and you can move them to the "Plug-Ins" folder of the new installation.

Updating optional libraries:

  • If upgrading from Audacity 2.0.5 or earlier, you must upgrade to the latest FFmpeg library if you require import and export of M4A (AAC), AC3, AMR (narrow band) and WMA.
  • If upgrading from Audacity 1.3.6 or earlier, you must update to the latest LAME library if you require MP3 export.

Otherwise there is no need to upgrade LAME or FFmpeg unless this is indicated in the Release Notes for the new version of Audacity.

If you prefer not to use the installer (or security restrictions prevent installing programs), choose the link for the "zip" file instead. Then on Windows XP or later, right-click the downloaded file and choose the option to extract the contents. You can also use 7-Zip or other extraction utilities.

back to top


Windows: How can I fix "Application configuration incorrect" when first launching Audacity after installation?

You may see the error Application configuration incorrect or error 14001 when launching Audacity after installation. This mainly affects some Windows XP or 2000 machines. This can be fixed by downloading and installing the appropriate Microsoft "Redistributable Package" as follows:

Be sure to get the correct package according to whether you have 32-bit or 64-bit Windows. To check if you have 64-bit Windows, right-click over My Computer and choose Properties. If 64-bit is not mentioned, you have 32-bit.

back to top


Windows: How do I uninstall Audacity?

Audacity can be uninstalled by choosing "Add/Remove Programs" or "Uninstall a program" in the Windows Control Panel. Select "Audacity" from the list and follow the instructions which will launch the Audacity uninstall program. Make sure you quit Audacity before uninstalling, or you will receive errors that some files could not be removed.

If the Control Panel cannot uninstall Audacity, open the folder in which you installed Audacity and double-click "unins000.exe" (this file might have other numbers in the name). This requires "unins000.dat" (or similar) to be present in the installation folder.

If you still cannot uninstall Audacity, download the installer again. Install Audacity to the same location you installed it to before (which happens by default). This will replace the uninstall files with good copies, then you can run the uninstaller again.

Uninstallation leaves your Audacity settings intact, in case you want to install Audacity again at some time in the future. If you want to remove your settings as well, delete Audacity's folder for application data whose location is given here.

See also: How do I reset my Audacity settings?

back to top


Mac OS X: Why do I see "unidentified developer", "Mac App Store" or "damaged" messages when I launch Audacity?

On OS X 10.7.5 and later, the Apple Gatekeeper feature controls launching of applications downloaded from the internet. If Gatekeeper won't launch Audacity because it is "from an unidentified developer" or "not downloaded from the Mac App Store", right-click or control-click on the Audacity application in Finder, choose "Open", then in the dialog box that appears, choose "Open". You should then be able to launch Audacity normally on subsequent occasions.

Occasionally, you may see an error message that "Audacity is damaged and can't be opened. You should move it to the Trash." If this message persists when you right-click or control-click over Audacity, open Apple menu > System Preferences… > Security & Privacy: General tab. Under the header "Allow applications downloaded from:", choose "Anywhere". Audacity should now launch. It would now be advisable to change the "Anywhere" preference back to a more restrictive setting.

back to top


How can I solve Audacity not appearing or crashing every time I launch it?

VST plug-ins (Windows and Mac OS X)

If the hang or crash occurs after pressing OK on the Install VST Effects dialog, a VST effect is probably conflicting with Audacity.

You can restart Audacity then use the VST dialog to do one of the following.

  • Click Cancel to load none of the effects but be presented with the installation dialog again at next Audacity launch.
  • Uncheck all (or individual) VST effects to prevent them loading, then click OK. The VST effects you uncheck will not load again until you set "Rescan VST effects..." in Effects Preferences and restart Audacity.

To assist in identifying an errant plug-in, you can inspect the plugins.cfg file in the Audacity folder for application data. This file will list which VST plug-ins Audacity had managed to load before it crashed. On Mac OS X, you can identify a VST plug-in which crashed from the Mac crash report. To view saved reports, open Finder, choose Go > Go to Folder then type ~/Library/Logs/DiagnosticReports/ (or ~/Library/Logs/CrashReporter/ on OS X 10.4 and 10.5).

Alternatively if you have VST plug-ins in system VST folders that you can't or don't want to use in Audacity, you could move those folders to your Desktop when you want Audacity to scan for VST plug-ins. After the Audacity scan, move the folders back to their system location so that they will be available for other programs.

If you discover a specific VST plug-in that misbehaves in Audacity, please e-mail our feedback address.

Incompatible audio device or audio drivers

If the Audacity hang or crash occurred after you added or enabled a new audio device, try removing or disabling that device (or updating its drivers) then restart Audacity. If the problem occurred after a driver update, try rolling back to the previous set of drivers. On Windows, you can revert driver changes caused by Windows Update.

If the entire computer crashes, reboots or displays a blue screen message when you launch Audacity, this is almost always due to a bad or mismatched audio driver (or due to a system driver conflicting with your sound device). You can inspect the memory dump of the computer to identify the source of the problem.

Resetting Preferences

The Audacity window could also fail to appear due to some Audacity configuration problem. To solve this, try resetting the Audacity Preferences. Conflicts with other programs such as security or anti-virus applications can occasionally cause Audacity not to launch. Try turning off some of the more advanced behaviour detection settings in the security program, or add an exception to the program's settings to make Audacity a trusted application.

back to top


How do I reset my Audacity settings?

Uninstalling Audacity does not automatically repair or reset your settings in Audacity Preferences. If you are trying to fix a problem with Audacity, take one of the following actions.

  • Quit Audacity and reset Preferences using the audacity.cfg settings file. There is then no need to uninstall and re-install.
  • Alternatively, Windows users may run the installer and in the "Select Additional Tasks" screen, put a check in the "Reset Preferences" box. Complete the installation. On launching Audacity, a dialog will appear where you can confirm if you want to reset preferences just this once, or not.

See also: Windows: How do I uninstall Audacity?

back to top


How do I download and install the LAME MP3 encoder?

Because of software patents, Audacity cannot include MP3 encoding software or distribute such software from its own web sites. Instead, use the following instructions to download and install the free and recommended LAME third-party encoder to export MP3 files with Audacity. See the LAME Legal Issues page for more details.

Windows

  1. Go to the external LAME download page
     Left-click this link, do not right-click.
  2. Directly underneath "For FFmpeg/LAME on Windows click below:", left-click the link Lame v3.99.3 for Windows.exe and save the file anywhere on your computer.
  3. Double-click "Lame v3.99.3 for Windows.exe" to launch it (you can safely ignore any warnings that the "publisher could not be verified").
  4. Follow the Setup instructions to install LAME for Audacity, making sure not to change the offered installation location of "C:\Program Files\Lame for Audacity" (or "C:\Program Files (x86)\Lame for Audacity" on a 64-bit version of Windows).

You should now be able to export MP3s without any further configuration, choosing File > Export Audio... then selecting "MP3 Files" in the Export Audio Dialog.

Troubleshooting

Occasionally, there may be a conflict where Audacity still tries to detect the path to an older lame_enc.dll file. To correct this:

  1. Ensure there are no older versions of lame_enc.dll in any locations where Audacity detects it, namely:
    • C:\Program Files\Lame for Audacity or C:\Program Files (x86)\Lame for Audacity (this is where the installer puts the new .dll)
    • the Audacity installation folder (usually C:\Program Files\Audacity or C:\Program Files (x86)\Audacity), or in the Plug-Ins folder inside that.
  2. Exit Audacity and navigate to the audacity.cfg preferences file at:
    • Windows 2000/XP: Documents and Settings\<user name>\Application Data\Audacity\audacity.cfg
    • Windows Vista/7: Users\<user name>\AppData\Roaming\Audacity\audacity.cfg.
  3. Open audacity.cfg in a text editor such as Notepad, and delete the two lines starting with:
    • [MP3]
      MP3LibPath=
  4. Save the changes to audacity.cfg and restart Audacity
In order to see audacity.cfg, you may need to set the operating system to show hidden files and folders. See instructions for Windows 7 and Windows versions before 7.
Warning icon Merely exiting Audacity and deleting audacity.cfg will not prevent Audacity from looking for lame_enc.dll in the path used by legacy 1.2 versions of Audacity. It is thus always best to use the above four steps, which will still allow legacy 1.2 to find lame_enc.dll if required.


Mac OS X

On OS X 10.6 or later, Administrative (and occasionally, root) permissions may be needed on some machines to read the LAME library the installer places in /usr/local/lib/audacity.

In case of difficulty, please download the zip version "Lame_Library_v3.98.2_for_Audacity_on_OSX.zip" from "Alternative zip download for Lame 3.98.2" below and follow the instructions.

  • Installer
  1. Go to the external LAME download page.
  2. Download Lame Library v3.98.2 for Audacity on OSX.dmg.
  3. When you have finished downloading, double-click the .dmg to mount it, then go to the Finder (in Safari, the "Lame Library v3.98.2 for Audacity" virtual disk image will be extracted and mounted automatically after downloading).
  4. Double-click "Lame Library v3.98.2 for Audacity.pkg"; the standard OS X Installer will start
  5. Click through the steps in the Installer, accepting the defaults in all cases; this will install the LAME binary "libmp3lame.dylib" in /usr/local/lib/audacity.
  6. Audacity should detect LAME automatically when you export as MP3. If Audacity cannot find LAME:
    1. Click Audacity > Preferences then choose "Libraries" on the left.
    2. Click "Locate..." under "MP3 Export Library", then "Browse..." in the "Locate Lame" dialog.
    3. The "Where is libmp3lame.dylib?" window will open at /usr/local/lib/audacity; select "libmp3lame.dylib", click "Open" then "OK" and "OK".
  • Alternative zip download for Lame 3.98.2
  1. Download "Lame_Library_v3.98.2_for_Audacity_on_OSX.zip" from the external download page.
  2. Extract the contents of the zip to a folder called "Lame_Library_v3.98.2_for_Audacity_on_OSX" anywhere you have full permissions (such as your Desktop).
  3. Click Audacity > Preferences then choose "Libraries" on the left.
  4. Click "Locate..." under "MP3 Export Library", then "Browse..." in the "Locate Lame" dialog.
  5. Navigate to and open the folder you extracted the zip to, select "libmp3lame.dylib", click "Open" then "OK" and "OK".

This is a good solution if Audacity does not recognize or work correctly with libmp3lame.dylib when installed to /usr/local/lib/audacity.

You should now be able to export MP3s without any further configuration, choosing File > Export Audio... then selecting "MP3 Files" in the Export Audio Dialog.

In case of difficulty please view our detailed instructions on the Audacity Wiki.

Linux/Unix

You may download (or compile) then install a compatible version of the LAME MP3 encoder then locate it in Libraries Preferences.

Most Linux distributions have some sort of package manager that fetches software packages from the Internet and installs them for you. Open that package manager, search for LAME, and install it if it is not already installed.

Removal of Libraries Preferences

Some distributions (for example, Ubuntu 13.10 or previous) package Audacity with MP3 encoding and FFmpeg support already linked dynamically to the relevant system libraries. In these packaged builds there is no need to locate LAME or FFmpeg, so Audacity will have no "Libraries" Preferences.

Users compiling Audacity from source code can similarly remove the "Libraries" Preferences by configuring Audacity with --disable-dynamic-loading then build Audacity linked to both system LAME and system FFmpeg. Audacity currently requires FFmpeg 0.10 or previous, so if system FFmpeg is later you may first need to build an appropriate local version of FFmpeg 0.10 or previous to link to.

Installing LAME on Ubuntu 11.10 and later

In Ubuntu 11.10 and later the default package manager is the "Ubuntu Software Center". It is often most convenient to install the "Ubuntu Restricted Extras" as this includes LAME, FFmpeg and other useful media encoding/decoding tools.

If you wish to install only the LAME package required for MP3 export, search for LAME in the Ubuntu Software Center and install it.

Installing LAME on other Debian-based systems

The following are detailed instructions for installing LAME using the Synaptic package manager on recent Debian-based systems and in Ubuntu 11.04 and earlier.

  1. Open Synaptic:
    • In GNOME (the default desktop environment for many Debian-based systems), access Synaptic by clicking System > Administration
    • In KDE there will be a similar menu accessible from the bottom-left of the screen
  2. Enter the root password when asked for it.
  3. In the Synaptic window, choose "Settings", then “Repositories”
  4. In the "distribution Software" tab, check the box for "non free" (on Ubuntu based systems this is called "multiverse"), then hit the Close button.
  5. Back in the main Synaptic Window, type “lame” in the "Quick search" box.
  6. The search results will show the packages “lame” and “libmp3lame0” at the top of the list; mark both for installation by double-clicking.
  7. Click "Apply", and on “OK” for any warnings; the LAME software will automatically download and install.
  8. Right-click over the entry for "libmp3lame0" > Properties
  9. On the "Installed Files" tab, note the location of "libmp3lame.so.0", probably at /usr/lib/libmp3lame.so.0
  10. Close all the Synaptic windows

Locating LAME

  1. Open Audacity, click Edit > Preferences then on "Libraries" in the list on the left
  2. In "MP3 Export Library" check if a LAME version number displays to right of "MP3 Library Version". If so, LAME has been detected and you should now be able to export MP3 and skip the remainder of these instructions. If the MP3 Library is stated as "not found":
    1. Click the "Locate...” button
    2. In the "Locate Lame" dialog that appears, click "Browse"
    3. In the "Where is libmp3lame.so.0?" dialog, navigate to the location you noted in step 9, select "libmp3lame.so.0", click "Open", then "OK" and "OK" to exit Preferences

If your distribution does not have a LAME package, please view these instructions on the Audacity Wiki.

back to top


How do I download and install the FFmpeg Import/Export Library?

Bill 27Jul14: Audacity 2.0.6 requires FFmpeg 2.2.2. Everything is this section must be updated.
As well installers/binaries for Windows and Mac need to be built and links to them provided on the download page.
  • Gale 10Sep14: Please check the update.
    • Peter 13Sep14: AFAICT it all looks ok apart from the fact that on Buanzo's site, accessed from the links on this page, it is still offering the old FFmpeg not the 2.2.2 vn. I can't vouch for the veracity/efficacy of the MAC and Linux sections.

      But why do we have a non-standard H2 header for this section, that puzzles me? For a start it makes editing harder as you get more than just this section.

    • Gale 14Sep14: Thanks for proofreading. I made it a standard wiki H2. I gave Buanzo the files to upload five days ago now. They will have to be there before we release.
The optional FFmpeg library allows Audacity to import and export a much larger range of audio formats including M4A (AAC), AC3, AMR (narrow band) and WMA and also to import audio from most video files.
  • Because of software patents, Audacity cannot include the FFmpeg software or distribute it from its own web sites. Instead, use the following instructions to download and install the free and recommended FFmpeg third-party library.
Warning icon FFmpeg 2.2.2 for Windows and Mac should be used with the latest version of Audacity.

The previous FFmpeg 0.6.2 for Audacity will not be recognized by Audacity 2.0.6 and later, and FFmpeg 2.2.2 will not be recognized by Audacity versions before 2.0.6.

Windows

  1. Go to the external download page
     Left-click this link, do not right-click.
  2. Directly underneath "For FFmpeg/LAME on Windows click below:", left-click the link ffmpeg-win-2.2.2.exe and save the file anywhere on your computer.
  3. Double-click ffmpeg-win-2.2.2.exe to launch the installer (you can safely ignore any warnings that the "publisher could not be verified").
  4. Read the License and click Next, Next and Install to install the required files to C:\Program Files\FFmpeg for Audacity (or C:\Program Files (x86)\FFmpeg for Audacity on a 64-bit version of Windows).
    If you have the previous FFmpeg 0.6.2 installed to the same location, the FFmpeg 2.2.2 installation will overwrite the 0.6.2 installation with the new files. There is no need to uninstall FFmpeg 0.6.2 first.
  5. If Audacity was running when you installed FFmpeg, either restart Audacity or follow the steps to manually locate FFmpeg.
  • Alternative zip download for FFmpeg 2.2.2
  1. Go to the external download page
     Left-click this link, do not right-click.
  2. Under "For FFmpeg/LAME on Windows click below:", left-click the link ffmpeg-win-2.2.2.zip and save the file anywhere on your computer.
  3. Extract the contents to a folder called "ffmpeg-win-2.2.2" anywhere on your computer, then follow the instructions below to locate the file "avformat-55.dll" using the Libraries Preferences.

Mac OS X

  • Installer:
  1. Go to the external download page
     Left-click this link, do not right-click.
  2. Directly underneath "For FFmpeg/LAME on Mac OSX click below:", left-click the link ffmpeg-mac-2.2.2.dmg and save the file anywhere on your computer.
  3. When you have finished downloading, double-click the DMG file to mount it (if you download with Safari, the ffmpeg virtual disk image will be extracted and mounted automatically after downloading). If the DMG window is not on top, go to Finder, then under "Devices" on the left, click the "ffmpeg-mac-2.2.2" DMG.
  4. In the DMG window, double-click the "ffmpeg-mac-2.2.2.pkg" to launch the standard OS X package installer.
  5. Click through the steps in the installer, accepting the defaults in all cases. This will install the FFmpeg libraries in /Library/Application Support/audacity/libs.
  6. Restart Audacity if it was running when you installed FFmpeg then Audacity should detect FFmpeg automatically.
  7. If you have problems with Audacity detecting FFmpeg, follow the steps to manually locate FFmpeg.
  • Zip file:
  1. Go to the external download page
     Left-click this link, do not right-click.
  2. Directly underneath "For FFmpeg/LAME on Mac OSX click below:", left-click the link ffmpeg-mac-2.2.2.zip and save the file anywhere on your computer.
  3. Some Mac computers may extract the files from the zip automatically to a new folder in the download directory. Otherwise, extract the contents to a folder called "ffmpeg-mac-2.2.2" anywhere you have full permissions (such as your Desktop). Then follow the instructions below to locate libavformat.55.dylib using the Libraries Preferences.
    On OS X 10.6 or later, it is not recommended to extract the files to /usr/local/lib because on some machines, administrative or root permissions may be needed to read the FFmpeg library from there.
  • Compiling Audacity against another build of FFmpeg:

GNU/Linux

You may download (or compile) and install a compatible version of the FFmpeg or libav library for your purposes then locate it in Libraries Preferences.

If you download a pre-built library, this might be either a "shared" or "static" build. A static build consists of a single libavformat library, whereas a shared build has at least three libraries (libavformat, libavcodec and libavutil). It is recommended to use a shared build, but Audacity will also work with a static build.

To build FFmpeg, obtain the source code from the FFmpeg project. To build libav, obtain the source code from the libav project. Configure the build with --enable -shared so that it builds the necessary shared object library (.so) files. If required, you can also configure to enable or disable particular encoding/decoding libraries. When you build Audacity from our source code, it will link to the installed FFmpeg headers.

FFmpeg version support

Gale 10Sep14: ToDo-2 Placeholder P2 to change the below text about dynamic loading if bug 540 is fixed and to monitor compiling status on different distros.
Warning icon Audacity 2.0.6 supports FFmpeg 1.2 or higher (FFmpeg 2.2.3 is known to work) or libav 0.8 or higher.
  • Compiling Audacity against supported FFmpeg/libav: Dynamic loading (as in default Audacity ./configure) enables Libraries Preferences for manual loading of LAME and FFmpeg/libav but requires building against the FFmpeg project.
  • No-longer-supported FFmpeg/libav: Audacity 2.0.6 and later may still build against unsupported FFmpeg/libav (such as FFmpeg 0.8 which is system-installed on Debian Wheezy), but configuring with --disable-dynamic-loading will usually be necessary. This will cause mono WMA files to export with no audio data.
    See the "Compiling" section in the 2.0.6 or later Release Notes for more guidance.

Removal of Libraries Preferences

Some Linux distributions or versions thereof may package Audacity with MP3 encoding and FFmpeg support already linked dynamically to the relevant system libraries. In these packaged builds there is no need to locate LAME or FFmpeg, so Audacity will have no "Libraries" Preferences.

Users compiling Audacity from source code can similarly remove the "Libraries" Preferences by configuring Audacity with --disable-dynamic-loading then build Audacity linked to system LAME and to a system (or local) minimum version of FFmpeg 1.2/libav 0.8.

Locating the FFmpeg library manually

If you installed FFmpeg while Audacity was running, or if you installed FFmpeg to a non-default location, Audacity will ask you to configure Preferences to locate the FFmpeg library. To do this, access Preferences then the "Libraries" tab on the left:

Preferences Libraries notFound basic7.png

As seen in the image above, the "FFmpeg Library Version" will say "not found". To correct this:

  1. Click the Locate... button to right of FFmpeg Library:.
  2. If a "Success" message indicates Audacity has now automatically detected valid FFmpeg libraries and asks if you want to detect them manually, click No, then OK to close Preferences.
  3. If the "Locate FFmpeg" dialog appears, click Browse....
  4. Navigate to the avformat file in the folder that contains FFmpeg, and select it. The file may have different names, such as "avformat-55.dll" on Windows, "libavformat.55.dylib" on Mac or "libavformat.so.55" on Linux.
  5. Click Open then OK and OK again to close Preferences.

FFmpeg Library Version should now show a set of three version numbers for the sub-libraries of FFmpeg ("F" for libavformat version, "C" for libavcodec version and "U" for libavutil version). If you still see "not found", you may have installed the wrong libraries. Click the Download... button to obtain the correct library for your operating system. You can also choose Help > Show Log... to see diagnostic information about FFmpeg detection.

back to top


How do I install VST plug-ins?

Audacity supports almost all VST effect plug-ins on Windows and Mac OS X.

Steve 10Aug14: VST disable in Linux for 2.0.6
On Linux, native VST plug-ins are rare but are supported in principle, or there are workarounds for running Windows-only VST's on Linux.

Audacity does not support native Linux VST plug-ins, but there are workarounds for running Windows-only VST's on Linux.

On first use, Audacity scans automatically for VST effects then presents you with an Install VST Effects dialog to choose which effects to load. The VST effects that you checkmark will be loaded when you click OK. The list will include any real-time VST effects or VST instrument (VSTi) plug-ins that are detected but neither of these are currently supported and so will not load even if you enable them in the dialog.

Gale 04Aug14: Partially updated for Linux, but we need to know where Audacity looks for VST's on Linux.
  • Steve 10Aug14: ToDo VST disabled in Linux for 2.0.6. This will need updating when it is re-enabled.

To install new VST effects, place them in the “Plug-ins” folder inside the Audacity installation folder. On Windows, this is usually under Program Files (or Program Files (x86) on 64-bit Windows); on Mac OS X, it is usually in the "Applications" folder. VST effects will also be found if they are added to (or already exist in) various system locations. To display the newly added plug-ins:

  1. Go to the Effects Preferences
  2. Under "VST Effects", put a check mark in "Rescan VST effects next time Audacity is started"
  3. Restart Audacity then click OK in the "Install VST Effects" dialog to load your new plug-ins and any other VST effects which you checkmark.

There is no need to add the VST Enabler which was required by previous versions of Audacity.

See also: Why do some VST plug-ins not work or display incorrectly?

back to top


Why do some VST plug-ins not work or display incorrectly?

Audacity will by default display VST effect plug-ins with a full graphical interface where the plug-in supplies this. Any plug-in that requires to be left open while processing audio will not work correctly. Real-time VST effects and VST instrument (VSTi) plug-ins are not currently supported.

If any plug-in displays incorrectly, you can uncheck "Display VST effects in graphical mode" in the Effects Preferences to display a simpler tabular interface for the plug-in (this also affects all other plug-ins).

Gale 04Aug14: ToDo-2 64-bit builds of Audacity on Linux might see 64-bit plug-ins, needs testing.
Warning icon
  • Audacity is a 32-bit application so won't see 64-bit versions of VST plug-ins, even on 64-bit operating systems.
  • VST 3 plug-ins are not supported.

If you experience a problem with a specific VST effect plug-in in Audacity, please contact us.

See also: How do I install VST plug-ins?

back to top


What are LADSPA, LV2 or VAMP plug-ins and how do I install them?

Gale 18Aug14: Rather than carbon-copy the information about LV2 plug-ins from Effect Menu#lv2 I thought it would be better to describe LV2 and VAMP because users will see them in Effects Preferences and may not know what they are.

LV2 is a more advanced evolution of the LADSPA plug-in architecture which was originally developed on Linux. Audacity supports both LV2 and LADSPA effects on Windows and Mac OS X as well as GNU/Linux. You can download and install a set of over 90 LADSPA plug-ins for all operating systems.

There are not yet many pre-compiled LV2 plug-ins for Windows and Mac OS X, though it may be possible to compile some Linux LV2 plug-ins for other operating systems. Audacity scans for and loads all detected LV2 effects each time you launch it. To add a new LV2 effect, place its complete ".lv2" folder (not the files alone) at the top level of any of the LV2 search locations then restart Audacity.

VAMP plug-ins are usually for analyzing or labeling audio so will appear under Audacity's Analyze Menu. You can do interesting things like attempt to track beats, note pitches, chords or frequencies. VAMP plug-ins work on Windows, Mac OS X and GNU/Linux. Audacity scans for and loads all detected VAMP plug-ins each time you launch it. To add a new VAMP analysis tool, add the plugin's DLL, DYLIB or SO file and any supplied category or RDF files to any of the VAMP search locations then restart Audacity.

back to top


How do I install plug-ins on Linux?

Audacity on Linux supports a large number of Nyquist, LADSPA, LV2 and VAMP effects.

Steve 10Aug14: Native Linux effects not supported in 2.0.6.
Although rare as native Linux effects, VST effects can in principle be run in Audacity on Linux, and there are workarounds for running Windows-only VST's on Linux. See VST Effects for how to install VST effects in Audacity.

Individual Nyquist and LADSPA plug-ins can be installed by putting the plug-ins into the Audacity Plug-ins folder:

  • /usr/share/audacity/plug-ins if Audacity was installed from a repository package
  • /usr/local/share/audacity/plug-ins if you compiled Audacity from source code.

These locations are usually set as read-only, so the plug-ins will need to be copied as root (for example, by issuing an appropriate root command in the terminal, or by using the terminal to open a file manager application with root permissions).

Warning icon Updating the repository package of Audacity may remove plug-ins that are not part of the package. To solve that problem you can create a folder called .audacity-files in your home directory, create a sub-folder called plug-ins then put your plug-ins into that. (Note: the dot in the name .audacity-files indicates that it is a hidden folder). This folder is then accessible without root permissions and will not be modified by installing a new Audacity package.

Audacity installed from a repository package or compiled from source should automatically find LADSPA plug-ins installed in /usr/lib/ladspa. This may not be the case if you are compiling older source code. If necessary you can set an environment variable to indicate to Audacity where LADSPA plug-ins are installed. For Debian-based distributions this can be done by entering the following code at the command prompt (change <user> to your account user name):

export LADSPA_PATH=$LADSPA_PATH:/home/<user>/.ladspa:/usr/local/lib/ladspa:/usr/lib/ladspa

If you wish this path to be set each time you boot, the LADSPA_PATH environment variable may be added to ~/.profile or this file may be created if it does not exist. An example of how to add the LADSPA_PATH environment variable:

LADSPA_PATH=$LADSPA_PATH:/home/<user>/.ladspa:/usr/local/lib/ladspa:/usr/lib/ladspa
export LADSPA_PATH

For OpenSuse 64, LADSPA plug-ins may be found in /usr/lib64/ladspa. This path can be set by adding the following line to your /etc/environment file:

LADSPA_PATH=/usr/lib64/ladspa

LV2 and VAMP plug-ins cannot be placed in the Audacity Plug-ins folder or your .audacity-files folder. LV2 plug-ins should be installed by placing the complete .lv2 folder (not the individual files in that folder) in the root of ~/.lv2, /usr/local/lib/lv2, /usr/local/lib64/lv2, /usr/lib/lv2 or /usr/lib64/lv2. Alternatively the environment variable may be set as in this example:

export LV2_PATH=$HOME/.lv2:/usr/local/lib/lv2:/usr/lib/lv2

VAMP plug-ins may be installed in $HOME/vamp, $HOME/.vamp, /usr/local/lib/vamp or /usr/lib/vamp. Alternatively the VAMP_PATH environment variable may be set to any of those specified VAMP installation directories. VAMP plug-ins will normally be placed in the Analyze Menu of Audacity.

Warning icon Remember to restart Audacity after installing Nyquist, LADSPA, LV2 or VAMP effects.

back to top

>  Forward To: FAQ:Recording - Troubleshooting

<  Back to: FAQ:About Audacity

|< Index of Frequently Asked Questions

Personal tools