Audacity Vst Plugins Linux

2021. 5. 20. 00:10카테고리 없음

> Forward To: FAQ:Recording - Troubleshooting

I switched from Ableton Live to Reaper and I am not switching back. Ableton Live is a great $1000 DAW. Reaper is an amazing DAW for $60. Any track can be anything including video. Plugin support for VST, VSTi, DirectX, Rewire and has 64/32 bit wrappers built in plus.js scripts.

VST-Linux Plugins Dexed. Synth FM; 48K Views Rating: 4.3 /5 (43 votes) “Dexed is a multi platform, multi format plugin synth that is closely modeled on the Yamaha DX7. Under the hood i. SQL8. Synth; 45K Views Rating: 4.5 /5 (16 votes) “The SQ8L is a software model (VST) of Ensoniq’s classic 1980s synth SQ80. The SQ80 features 3. The VST Plug-ins page on the Audacity Wiki contains further help for VST plug-ins, and lists a large number of VST plug-ins that have been reported to work well in Audacity. Audio Unit Plug-Ins On Mac OS X only, Audacity loads Audio Unit plug-ins from system plug-in directories. This is one plug-in that is mostly in use for Linux based machines. The full form of. Audacity supports almost all VST effect plug-ins on Linux including 'shell' VSTs that host multiple VST effects. VST plugins for all users can be placed in a 'plug-ins' folder that you must add to /usr/bin/(if you installed a packaged version of Audacity) or to /usr/local/bin(if you installed a. Calf Studio Gear.is available exclusively for LINUX-based operating systems and runs as a stand-alone effect rack connectable through Jack sound server or as plug-ins in every audio host that is able to fire up LV2 compilant devices, e.g. The highly recommended Ardour Audio Workstation. Installing LV2 plug-ins. LV2 is a more advanced evolution of the LADSPA plug-in architecture which was originally developed on Linux. Audacity supports both LV2 effects on Windows as well as GNU/Linux.

< Back to: FAQ:About Audacity

  • 2How do I uninstall Audacity?

How do I install and update Audacity?

  • Windows: See Installing and updating Audacity on Windows
  • Mac: See Installing and updating Audacity on Mac
  • GNU/Linux: See Installing and updating Audacity on Linux


Audacity Vst Plugins Linux Installer

How do I uninstall Audacity?

Note that there is no need to uninstall your previous Audacity version before updating to current Audacity, unless you are updating from 1.3.x Beta. Please see the Windows installation page.

Windows

Audacity can be uninstalled by choosing 'Add/Remove Programs' or 'Uninstall a application' in the Windows Control Panel. Select 'Audacity' from the list and follow the instructions which will launch the Audacity uninstall application. 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 retains your Audacity settings 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.

Mac

Quit Audacity then drag Audacity.app to Trash. If you are uninstalling older Audacity versions prior to 2.1.3, drag the entire folder containing Audacity to Trash.

Uninstallation retains your Audacity settings 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 ( ~/Library/Application Support/audacity/).

See also: How do I reset my Audacity configuration settings?


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

If you cannot download Audacity from our official download page https://audacityteam.org/download/ please check at http://downforeveryoneorjustme.com/ to see if the problem is with your connection. If the downloaded setup file is corrupt, it's a very good idea to clear the download list or cache in your browser or download manager then try downloading again.

If problems persist, please let us know at our feedback address.



How do I download and install the LAME MP3 encoder?

The software patent on LAME encoding library has expired, so now the LAME library for MP3 export is built-in with Audacity for Windows and Mac. Linux users will still need to download and install the free and recommended LAME third-party encoder to export MP3 files from Audacity.

Linux users should use the following instructions to download and install the free and recommended LAME third-party encoder to export MP3 files with Audacity.

  • Windows:LAME is now built-in with Audacity for Windows.
  • Mac:LAME is now built-in with Audacity for Mac.
  • Linux/Unix: See the LAME installation section on Installing and updating Audacity on Linux.




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

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 websites. Instead, following the links below to instructions to download and install the free and recommended FFmpeg third-party library.

  • Windows: See the FFmpeg installation section on Installing and updating Audacity on Windows.
  • Mac: See the FFmpeg installation section on Installing and updating Audacity on Mac.
  • GNU/Linux: See the FFmpeg installation section on Installing and updating Audacity on Linux.


What Effect, Generator and Analyzer plug-ins does Audacity support and how do I install them?

You can download and install plug-ins to add extra functionality to Audacity. Plug-ins can give you extra effects, or more audio generation and analysis capabilities.

Nyquist plug-ins provide most of the optional effects underneath the divider in the Effect menu. They are also used to provide some of Audacity's built-in audio generators and analysis tools. A wide range of additional Nyquist effect, generation and analysis plug-ins can be obtained from Download Nyquist Plug-ins on our Wiki.

VST(Virtual Studio Technology): Audacity supports almost all VST effect plug-ins on Windows, Mac and Linux including 'shell' VST's that host multiple VST effects.

LV2 is a more advanced evolution of the LADSPA plug-in architecture which was originally developed on Linux. Vamp plug-ins are usually for analyzing audio so will appear under Audacity's Analyze Menu.

To add new plug-ins please see:

  • Windows: See Installing Effect, Generator and Analyzer plug-ins on Windows.
  • Mac: See Installing Effect, Generator and Analyzer plug-ins on MAC OS X.
  • GNU/Linux: See Installing Effect, Generator and Analyzer plug-ins on Linux.
Audacity


How can I solve Audacity not appearing or crashing on launch, or crashing after I add a plug-in?

Mac: 'Audacity is already running' - error message

If you get the following error message when trying to launch Audacity it is likely that an old Audacity 'lock file' is still present.

Audacity is already running. The system has detected that another copy of Audacity is running. Running two copies of Audacity simultaneously may cause data loss or may cause your system to crash. Use the New or Open commands in the currently running Audacity process to open multiple projects simultaneously.

The lock file is in:

  • ~/Library/Application Support/audacity/SessionData

Look in the SessionData folder and delete any files and folders you find there.


Incompatible audio device or audio drivers

If the Audacity hang or crash occurs 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). See how to inspect the computer's memory dump or test its memory to diagnose crashes.

LADSPA, LV2, VST or Audio Unit plug-ins

A hang or crash could occur after you use the Plug-in Manager: Effects, Generators and Analyzers dialog to add new LADSPA, LV2, VST or Audio Unit (Mac) effects. The crash or hang could occur immediately after pressing OK in the dialog, when using an effect, when exiting Audacity or when restarting it next time.

If Audacity crashes immediately after you enable one or more effects in the Plug-in Manager dialog, the effect(s) that crashed should be disabled next time you launch Audacity. They will be relisted in Plug-in Manager as 'New' rather than 'Disabled'. If Audacity crashes when an effect is launched from the Effect Menu or applied to the audio, you can restart Audacity then try disabling the effect in the Plug-in Manager. This effect will then not be available in Effect Menu.

Sometimes it may not be obvious which effects to disable to solve a hang or crash. You might be able to identify offending effects from Audacity.zip if there is an Audacity Debug report. You can also try Windows Event Viewer (or more easily on Windows, type 'Reliability' without quotes in the Search box to open Reliability Monitor). To view Mac reports, open /Applications/Utilities/Console.app then look at the System Diagnostic Reports.

Should it remain unclear which effects are responsible, it may be useful to reset Audacity to load only the enabled effects that it had on first installation. To do this, go to Audacity's folder for application data as follows:

  • Windows:Users<username>AppDataRoamingAudacity (or type %appdata% in Explorer)
  • OS X:~/Library/Application Support/audacity/ (use Go > Go to Folder in Finder)
  • Linux:~/.audacity-data/ .

In that folder, delete the pluginregistry.cfg and pluginsettings.cfg files and restart Audacity. Then you can use the Plug-in Manager dialog to selectively enable effects to find the possible culprit.

If you discover a specific plug-in that misbehaves in Audacity, please email our feedback address. Please include any available Debug report that Audacity generates.

Resetting Audacity Preferences

The Audacity window could also fail to appear due to some Audacity configuration problem. To solve this, try resetting the Audacity Preferences.

Viruses and anti-virus scanning

Conflicts with other applications such as security or anti-virus applications can occasionally cause Audacity not to launch. Try turning off some of the more advanced behavior detection settings in the security application, or add an exception to its settings to make Audacity a trusted application. Conversely if you have not run a virus scan for a while, update your security application to the latest virus definitions and perform a thorough scan in case a newly acquired virus is the problem.


back to top


What should I do if I get errors building Audacity?

Audacity provides ready-built installer applications 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).


Windows: How can I make Audacity launch when I double-click a WAV or other audio file?

For Windows, click the Windows Start button, then Control Panel, then 'Programs'. Under 'Default Programs', click 'Make a file type always open in a specific application'. Choose '.wav', '.mp3' or your chosen extension, then click 'Change application...' and browse for Audacity to associate it with that file type.

Another method is to use the Windows Start button, type 'Run' (without quotes), press Enter, then type %windir%system32control.exe /name Microsoft.DefaultPrograms /page pageFileAssoc and press Enter.

On Windows you can instead set the default association of a file type with Audacity by right-clicking over any file of that type, choosing 'Open with' then 'Choose default application...'.

If you have two different versions of Audacity, and you want to be able to choose which one, then you will need to rename one to give them different names, such as audacity.exe and audacity_old.exe.


back to top


Mac: Why do I see 'Verifying' or 'Damaged' messages when I launch Audacity?

On OS X 10.7.5 and later, the Apple Gatekeeper feature by default verifies authorship of applications downloaded from the internet and controls whether they can be launched. Audacity is now codesigned with an Apple Developer ID to make it easier to launch Audacity securely. The first time you launch Audacity after download, Gatekeeper will verify Audacity, perhaps showing a progress dialog, but once complete you will see a standard warning saying that Audacity came from the internet and asking if you want to open it. You can safely do so.

If after verification, Gatekeeper says that Audacity is 'from an unidentified developer' or 'not downloaded from the Mac App Store', this means you have an old version of Audacity that was not codesigned. If necessary you can right-click or control-click over the Audacity application in Finder, choose 'Open', then in the dialog box that appears, choose 'Open', but we recommend you download the current version of Audacity instead.

Occasionally, you may see an error message that 'Audacity is damaged and cannot be opened, possibly with 'You should move it to the Trash.' If this message persists even if you right-click or control-click over Audacity to open it, try downloading Audacity again from http://www.audacityteam.org/download/mac.

If necessary, you can open Apple menu > System Preferences... > Security & Privacy: General tab. Under the header 'Allow apps downloaded from:', choose 'Anywhere'. On macOS Sierra 10.12, the 'Anywhere' choice is unavailable by default, but you can make the 'Anywhere' choice appear and set Gatekeeper to this choice by opening a Terminal and entering

sudo spctl --master-disable

then entering your password when prompted.

Audacity should now launch, assuming it is not a corrupted download. It would then be advisable to change the 'Anywhere' preference in Gatekeeper back to a more restrictive setting. On macOS Sierra, doing so will remove the 'Anywhere' choice once more.


How do I reset my Audacity configuration settings?

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

  • In Audacity use Tools > Reset Configuration to reset your Audacity configuration: preferences, export settings and toolbars to default settings. (Macros, plug-ins and saved user settings in Effects, Generators and analyzers are not affected).


If you cannot launch Audacity:

  • Reset Preferences by deleting 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.

For details of how to reset your Audacity settings on the three platforms please see:


See also:



> Forward To: FAQ:Recording - Troubleshooting

< Back to: FAQ:About Audacity

From Audacity Manual

Linux
Jump to: navigation, search

> Forward To: FAQ:Recording - Troubleshooting

< Back to: FAQ:About Audacity

  • 9How do I download and install the LAME MP3 encoder?
    • 9.3Linux/Unix
  • 10How do I download and install the FFmpeg Import/Export Library?


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.

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).


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 FilesAudacity (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 1.3.6 or earlier, you must update to the latest LAME MP3 encoding library. 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.


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:

  • Microsoft Visual C++ 2008 SP1 Redistributable Package (x86) for 32-bit Windows
  • Microsoft Visual C++ 2008 SP1 Redistributable Package (x64) for 64-bit Windows.

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.


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?


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.


Mac OS X: How can I solve Audacity not appearing then crashing every time I launch it?

If you launch Audacity but see nothing except a Mac crash report, this is most likely due to incompatible Audio Unit (AU) plug-ins on your system. Currently, Audacity automatically loads all Audio Units that it detects each time you launch it.

To prevent the crash it will be necessary to either edit the audacity.cfg settings file to disable loading of Audio Units, or to determine from the crash report(s) which Audio Units are failing then move them to another location where Audacity cannot detect them.

If the crash occurs after pressing on the Install VST Effects dialog, then one of the VST plug-ins you enabled in the dialog is causing the crash. In that case you can use the dialog to do one of the following:

  • Uncheck all (or individual) VST effects to prevent them loading then click
  • Click to load none of the effects but be presented with the installation dialog again at next Audacity launch.

Alternatively you can identify the VST plug-in which crashed from the Mac crash report and move it to another location.

For help with editing audacity.cfg and locating or moving AU or VST plug-ins, please see 'How to prevent Audio Unit and VST plug-ins crashing Audacity on Mac OS X' on our Wiki.

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


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?


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.

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', 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 FilesLame 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... then selecting 'MP3 Files' in the File Export 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 FilesLame 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 FilesAudacity 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 DataAudacityaudacity.cfg
    • Windows Vista/7: Users<user name>AppDataRoamingAudacityaudacity.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.
Merely exiting Audacity and deleting audacity.cfg will not prevent current 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 http://lame1.buanzo.com.ar/Lame_Library_v3.98.2_for_Audacity_on_OSX.zip from the external download site.
  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... then selecting 'MP3 Files' in the File Export Dialog.

In case of difficulty, or if you have an older version of Audacity, please view our detailed instructions on the Audacity Wiki.

Linux/Unix

Some Linux distributions (for example, Ubuntu) now 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 FFmpeg. Otherwise, users building Audacity from source must locate a compatible build of LAME in the 'Libraries' Preferences as below.

Most 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.

Audacity Vst Free

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.

Vst
  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.


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

The optional FFmpeg library allows Audacity to import and export a much larger range of audio formats including AC3, AMR(NB), M4A, MP4 and WMA and also 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.

FFmpeg 0.6.2 for Windows and Mac listed below should be used with the latest version of Audacity from http://audacity.sourceforge.net/download/.

Windows

  1. Go to the external download page
    Left-click this link, do not right-click.
  2. Look for 'For FFMpeg/LAME on Windows', then a few lines under that, left-click the link FFmpeg_v0.6.2_for_Audacity_on_Windows.exe and save the file anywhere on your computer.
  3. Double-click 'FFmpeg_v0.6.2_for_Audacity_on_Windows.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 FilesFFmpeg for Audacity' (or 'C:Program Files (x86)FFmpeg for Audacity' on a 64-bit version of Windows).
  5. Restart Audacity if it was running when you installed FFmpeg.
  6. If you have problems with Audacity detecting FFmpeg, follow the steps to manually locate FFmpeg.
  • Alternative zip download for FFmpeg 0.6.2
  1. Download http://lame3.buanzo.com.ar/FFmpeg_v0.6.2_for_Audacity_on_Windows.zip from the external download site.
  2. Extract the contents to a folder called 'FFmpeg_v0.6.2_for_Audacity_on_Windows' anywhere on your computer, then follow the instructions below to locate avformat-52.dll using the Libraries Preferences.

Mac OS X

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

In case of difficulty, please download the zip version 'FFmpeg_v0.6.2_for_Audacity_on_OSX.zip' from 'Alternative zip download for FFmpeg 0.6.2' below and follow the instructions.

  • Installer:
  1. Go to the external download page
  2. Download FFmpeg (0.6.2 OSX 10.4+ DMG)
  3. When you have finished downloading, double-click the .dmg to mount it, then go to the Finder (in Safari, the 'FFmpeg Libraries for Audacity' virtual disk image will be extracted and mounted automatically after downloading).
  4. Double-click 'FFmpeg Libraries for Audacity.pkg' to launch the standard OS X Installer.
  5. Click through the steps in the Installer, accepting the defaults in all cases; this will install the FFmpeg libraries in /usr/local/lib/audacity
  6. Restart Audacity if it was running when you installed FFmpeg
  7. If you have problems with Audacity detecting FFmpeg, follow the steps to manually locate FFmpeg.

Audacity Vst Plugins Linux Permissions

  • Alternative zip download for FFmpeg 0.6.2
  1. Download http://lame1.buanzo.com.ar/FFmpeg_v0.6.2_for_Audacity_on_OSX.zip from the external download site.
  2. Extract the contents to a folder called 'FFmpeg_v0.6.2_for_Audacity_on_OSX' anywhere you have full permissions (such as your Desktop) then follow the instructions below to locate libavformat-52.dylib using the Libraries Preferences. This is a good solution if Audacity does not recognize or work correctly with libavformat-52.dylib when installed to /usr/local/lib/audacity.
  • You can also build Audacity from SVN and link to a system copy of FFmpeg built from source, using these instructions.

Linux/Unix

Some Linux distributions (for example, Ubuntu) now 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 FFmpeg. Otherwise, users building Audacity from source must locate a compatible build of FFmpeg in the 'Libraries' Preferences as below.

You may download (or build) a suitable FFmpeg library for your own purposes. To build, obtain the source code from the FFmpeg project. 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.

If you compile Audacity from source code, it will link to the installed FFmpeg headers, which should always be compatible with an installed FFmpeg binary.

FFmpeg version information: Audacity should support building against FFmpeg 0.5 through 0.8. It may not currently be possible to build Audacity against later versions of FFmpeg.

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:

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 the library 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 library, and select it. It may have different names, such as 'avformat-52.dll' on Windows, 'libavformat-52.dylib' on Mac or 'libavformat.so.52' on Linux.
  5. Click 'Open' then 'OK', and 'OK' again to close Preferences.

'FFmpeg Library Version' should now show a number. If not, 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


Why do I receive an error when I export to an FFmpeg format?

If you receive a 'cannot find audio codec' error when exporting to an FFmpeg format, the FFmpeg library you are linking to does not support this codec. To export to this format, you will need a build of the FFmpeg library that supports this codec.

Distributable libraries will not include support for AMR WB (wide band), due to licensing issues. Exporting to AMR WB will return the error 'FFmpeg cannot find audio codec 0x 12001'. To obtain AMR WB export support, you could build FFmpeg yourself from source and enable the relevant library in the configure step.


How do I install VST plug-ins?

Audacity supports almost all VST effect plug-ins on Windows and Mac OS X. 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 . 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.

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?


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

On Windows and Mac OS X, 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).

Note: Audacity is a 32-bit application so won't see 64-bit versions of VST plug-ins, even on 64-bit operating systems.

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?


How do I install plug-ins on Linux?

Individual Nyquist and LADPSA 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). Note that updating the repository package of Audacity may remove plug-ins that are not part of the package.

Alternatively 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.

Many LADSPA plug-in packages are available in the repositories of most major Linux distributions. If Audacity is installed from a repository package it should automatically find plug-ins in their installed location of /usr/lib/ladpsa, but Audacity compiled from source may not find LADSPA plug-ins there.

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):

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 added if it does not exist. An example of how to add the LADSPA_PATH environment variable:

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:


Audacity Vst Plugins Linux Iso

> Forward To: FAQ:Recording - Troubleshooting

Free Vst Plugins For Audacity

< Back to: FAQ:About Audacity