1 of 35

Audacity 2.x

Audacity 2.0.0

Audacity 2.0.0 was available from 13 March 2012 until 28 June 2012 for Windows, Mac OS X and GNU/Linux. These Release Notes describe:

Changes in 2.0.0 as compared with 1.3.14
Summary of bug fixes and new features between 1.2.6 and 2.0.0
Issues with 2.0.0 which were known at time of release.

Tip: You can use CTRL + F to search this page for different words to do with the issue you are looking for. Use Command - F on Mac.

Notes for Windows:

Users upgrading to 2.0.0 from 1.3.6 or earlier must download the of the LAME MP3 encoder.
The Windows installer for 2.0.0 will replace 1.2.x installations, but install alongside 1.3.x Beta versions. As 2.0.0 also replaces the 1.3.x series, it is strongly recommended to uninstall previous Beta versions.

Changes between 1.3.14 and 2.0.0

Bug fixes

Interface

Fixed playback speed and synchronization problems when dragging clips or tracks between tracks having different sample rates.
(Windows) Removed a crash risk where shortcuts could be used to record or import in one project while importing or exporting in another.

Imports and Exports

Fixed crashes when changing the sample format of read-directly WAV or AIFF files using the Track Dropdown Menu.
Fixed a crash importing MP3 files that had duplicate metadata tags (this is a bug in current libsndfile which has been patched in Audacity; MP3 files mislabeled as WAV which have duplicate tags will still crash Audacity on Linux if Audacity has been compiled against an affected version of system libsndfile).
Fixed an issue where excessively high or corrupted sample values in the audio could corrupt exports from the start of the problem for the rest of the file, and could corrupt the rest of the project.

Effects and Analysis

Fixed crash on launch when using "Ambisonic Decoders (PC)" VST plug-ins and other plug-ins that enable additional floating point exceptions.
Fixed Plot Spectrum background could be transparent on some machines.
Bug fixes for Click Track, High Pass, Low Pass and Vocal Remover.
Chirp, Tone and Silence generators now remember their settings.

Other miscellaneous bug fixes

Changes and Improvements

New Interface preference to show the track name in the display (this is off by default).
Longer default Playback preference for effects preview and preview before cut.
Restored use of Page Up and Page Down to scroll horizontally.

Summary of bug fixes and new features between 1.2.6 and 2.0.0

Bug Fixes

Labels now accept lower case "z".
(Windows Vista/7) Pressing Stop after recording could cause a crash.
(Mac OS X) Fixed shortcut keys activating when typing in file open or save windows.
(Mac OS X) Audacity 2.0.0 fully supports Unicode, which fixes an issue where Audacity could not work with folders having non-English characters in their name.

New features

These are some of the dozens of new features in 2.0.0.

Many effects significantly improved, especially Equalization, Noise Removal and Normalize. Vocal Remover now included plus GVerb on Windows and Mac. VAMP analysis plug-ins now supported.
Improved label tracks with Sync-Lock Tracks feature in the Tracks Menu.
Multiple clips per track. Tracks and selections can be fully manipulated using the keyboard. Many more keyboard shortcuts.

Known Issues at Release

Headline issues

Large Projects

Projects with more than 2^31 samples (just over 13.5 hours at 44100 Hz) will not re-open correctly. Higher sample rates mean proportionally shorter times - so just over 6 hours at 96,000 Hz. We know the cause, and do intend to address this bug. Workaround: Before saving or closing the project, export to audio files of appropriate size, or cut and paste sections of audio containing less than 2^31 samples to new Audacity projects and save those.

Problems reopening, saving or crashing in projects

The following problems are very rare, but have the potential for losing data. The developers have not yet been able to reproduce these problems so please write to our if you encounter any of these symptoms.

When attempting to reopen the project normally:
- The .aup project file was not saved (or incompletely saved, giving a "line number" error).
- Audio that was there previously is silenced.

To avoid any problems, export a WAV or AIFF file from your project before closing it, then you can import the WAV again if the project becomes damaged.

When working in the project:
- Errors occur when saving the project or when Audacity autosaves, perhaps wrongly suggesting the disk is full or not writable (if this happens, try exporting the audio as WAV).
- Unwanted renaming or moving of .au files within the project.

Please tell us all the actions you recall both the last time you had the project open and what happened this time, including error messages. We believe having multiple projects open at once, having projects open in file manager programs or long projects with many tracks are among the possible causes.

As many as possible of the following will help us enormously if you can attach them to your report:

A copy of the saved .aup project file
A copy of the "autosave" (temporary project) file. The "autosave" file is stored inside the "AutoSave" folder in Audacity's

Changes and Improvements

CleanSpeech Mode (a customized interface with reduced menus and stored effects presets) is no longer officially supported. We may reintroduce a new system of alternative presets and simplified menus in a later Audacity. However any users who had CleanSpeech enabled in 1.3.13 or earlier 1.3 versions will still have it enabled without any way to turn it off in the program. Workaround: To turn off CleanSpeech, either turn it off in the Interface Preferences of a previous 1.3 version, or exit Audacity, open in a text editor and remove the line "CleanSpeechMode=1". Alternatively, change the value 1 to 0 to turn CleanSpeech off, and set it back to 1 to re-enable CleanSpeech.==

Program Launch

(Linux) If a Bluetooth audio device is in use on a PulseAudio system, Audacity may hang on launch on initial attempts, then after eventual launch Bluetooth will no longer work on the system. Workarounds:
- Remove and reconnect the external Bluetooth adaptor, then launch bluetooth-applet from the command line.
- To prevent Audacity affecting Bluetooth support, move /usr/share/alsa/bluetooth.conf to another location then reboot, or create a symbolic link from /var/lib/alsa/asound.state to /dev/null and reboot.

In a future version of Audacity we aim to defer loading of plug-ins until they are requested in the Effect menu. Workaround: If VST/AudioUnit effects are not needed in Audacity, force quit Audacity, open "audacity.cfg" inside Audacity's then add or edit the following as required:

[AudioUnits] Enable=0 [VST] Enable=0 Rescan=0

If plug-ins were the problem, Audacity should now launch.

Installation

(OS X 10.6 or later) Administrative (and occasionally, root) permissions may be needed on some machines to read the optional LAME and FFmpeg libraries at /usr/local/lib/audacity. In case of difficulty, please download the zip versions "Lame Library v3.98.2 for Audacity on OSX.zip" and "FFmpeg v0.6.2 for Audacity on OSX.zip" from the and extract the files to your own preferred location.

Imports and Exports

By default, the importer used depends on the import method. For example, to be able to use to import native Audacity formats like WAV and MP3, you must choose the "FFmpeg-compatible files" filter in File > Open or File > Import > Audio and always use one of those import methods. To force FFmpeg to import native Audacity formats when using File > Recent Files or dragging in, add rules for those formats in . To force FFmpeg import irrespective of the filter when using File > Open or File > Import > Audio, uncheck "Attempt to use filter in OpenFile dialog first" in Extended Import Preferences as well as adding the rule for the format.
(Linux) AAC exports produce a zero bytes file if the Audacity project rate is below 22050 Hz. Additionally, the "Quality" slider in AAC export Options has no effect on the exported bitrate. "Workaround: Export as WAV and convert to AAC using FFmpeg at the terminal.

Interface

Dragging a clip or track up or down with Time Shift Tool does not scroll the project window when tracks exist out of view above or below the scroll. Workaround: Choose View > Fit Vertically before drag, or click and hold the piece to be dragged, use up or down arrow on the keyboard to scroll to the target track, then drag and release the clip or track.
Selections locked to/only possible to click at whole seconds: We know that it is easy to check the "Snap To" box in by mistake, which means you can't then select less than a whole second or click other than at a whole second. We will look for a solution that keeps Snap To discoverable but makes it harder to enable by accident.==
(OS X) Set Rate > Other... in the Track Dropdown Menu does not display the current track rate unless that rate is in the list of set rates.

For Package Maintainers / Distributors / anyone building against 2.8.10: The upstream change in wxGTK is simple and can easily be patched into wxGTK 2.8.10 if desired: Grab , run it through dos2unix (as it seems to come with dos line-endings), and apply it to the wxGTK 2.8.10 sources (with -p3 to get the paths right if you patch from the top level of the tarball distribution).

(Linux) The OK button has focus on opening effects and other dialogs, instead of fields for changing values. This is a bug in wxGTK. To change values or settings in the dialog it is necessary to deliver a mouse click.
(Linux) Using a file manager (for example, context menu) or the command line to open further files gives an error. Even if Audacity is closed, only one file can be opened from the file manager. Workaround: Use File > Open, or (for audio files) File > New then drag the files in.
(Windows) It is not yet possible to drag .lnk shortcuts to audio files or projects into Audacity, or to drag them to the Audacity executable's icon. Workaround: Use File > Open or File > Import > Audio, or double-click the shortcut to the .aup from Windows Explorer.

Playback and Recording

(Windows Vista, 7) If you change the explicit output and/or input device selected in Device Toolbar or Devices Preferences and then change "Host", the selected devices will change back to those originally selected.
(Windows XP and earlier) Changing the default playback or recording devices in the Windows Control Panel while Audacity is open may cause all the playback or recording choices in Device Toolbar to produce silence (or to fail with "Error opening sound device"). This problem may also occur when connecting or disconnecting a USB device while Audacity is open. Workaround: Click Transport > Rescan Audio Devices then you can play or record.
(OS X and Linux) Audacity now works very well with , with the following bugs and limitations:

Effects and Analysis

Cut Preview only plays the upper track of multiple selected or Sync-Locked tracks.
LADSPA Multiband EQ may not be visible in Effect menu (occurs on Windows XP), and crashes soon after opening
Nyquist effects render the space between clips as silence. Workarounds: Edit > Clip Boundaries > Detach at Silences (this could reduce the length of clips that have silent fades) or double-click each clip and apply the effect separately to it.

Projects

Projects containing more than 2^31 samples (just over 13.5 hours of audio at 44100 Hz) will re-open empty with the entire data being seen as "orphaned files" (although the data "appears" to be in the correct location expected by the .aup file). Workaround: Before saving or closing the project, export to audio files of appropriate size, or cut and paste sections of audio containing less than 2^31 samples to new Audacity projects and save those.
It is no longer possible to use Save Project or Save Project As to overwrite another pre-existing project, even if that project is not in use. Functionality to overwrite a project not in use will be restored in a future version of Audacity when we are sure it will always be safe.
(OS X) Crash closing project window immediately after saving project: After saving a project, if you close the project window immediately the "Saving project data files" dialog completes, there will be an unexpected "Save changes?" prompt and then a crash when you choose "Yes" or "No". As long as you say "Yes", the project will be saved correctly and can be reopened normally after you restart Audacity. To be sure there is no crash, wait after "Saving project data files" completes for any "Inspecting Project Data" dialog to appear and disappear before closing the project window.

Accessibility

(Linux) If you TAB into "Snap To" in Selection Toolbar, the selection and focus will become trapped. A mouse click elsewhere will be required to free the focus. Workaround: Access the required part of Selection Toolbar with TAB or SHIFT + TAB so as to avoid Snap To. Snap To can be set on or off by exiting Audacity, show hidden files and folders then add or edit the line "SnapTo=1" or "SnapTo=0" (without quotes, for on or off respectively) in ~/.audacity-data/audacity.cfg.
Many, but not all parts of the Audacity interface are accessible on Windows to those who can't use a mouse, and/or use a screen reader. It may be possible to make more of Audacity accessible in the longer term. For details, see .

There are some accessibility bugs in the parts of Audacity that are accessible.

Toolbar buttons cannot be operated by pressing either ENTER or Space: ENTER incorrectly moves to the next control and Space starts/stops playback. However the buttons can be operated either by using their shortcut keys, or for users of screen readers by using the Jaws cursor or equivalent. Note: it will be necessary to go to the Keyboard Preferences to set a shortcut for the Play-at-speed button.
For users of JAWS and Window-eyes. when the Silence Generator dialog opens, the duration control is incorrectly read as 0 seconds. However, if you tab round to the control again, the correct value is read.
For users of all screen readers, "and" is read out before the access key character in some controls in Preferences.

Chains

(Linux) When configuring effect parameters in "Edit Chains", the "Preview" button is not intended to be functional. Pressing it may cause a crash.

Clips

Left-clicking in a stereo track to merge a clip at a split line may cause other clips to move. It is believed this only happens after having used the Track Dropdown Menu to make two mono tracks into stereo. Workaround: Select over the split line and Edit > Clip Boundaries > Join.

Compiling

(Windows) Compilation with Visual Studio 2010 is not supported or recommended. See the Wiki page for information.
(Windows) LADSPA effects cannot be categorized even when Audacity is compiled with USE_LIBLRDF defined.

Label Tracks

(Linux) In projects containing several hundred labels or more, Audacity will freeze on 100% CPU when opening the "Audacity Karaoke" window, and will freeze again while that window is open when editing a label or performing other actions on the project. Workaround: Open or place an empty label track above the one you want to use.
Typing "j", "J", "k" or"K" in a label track may activate the "move cursor" or "select to/from cursor" shortcut instead. Workaround: click Edit > Preferences: Keyboard, choose the "Edit" category then change the shortcuts for "Move Cursor to Track Start", "Move Cursor to Track End", "Select Track Start to Cursor" and "Select Cursor to Track End" to something else (or clear them).
Unless Tracks > Sync-Lock Tracks is on, pasting or inserting audio does not affect labels even if the label track is included in the selection.

Mixer Board

(Linux) Meters may not respond immediately to playback which could cause them to report incorrect peak level or not display clipping.
Meter range does not reflect a change in the dB range meter preferences until restart

Preferences

(Linux) Extended Import: Clicking "Move rule up" when there are no rules or filters causes a crash.==

Toolbars

When using Selection Toolbar in a selection format in less than whole seconds, an inaccurate value for length or cursor position may display when zoomed in. The displayed value will be the nearest whole second below the true value (for example, 59.000 seconds where the true value is 59.999 seconds). This can occur when clicking on or moving the cursor across a boundary for whole seconds, in which case you can use right arrow to show the correct value. It can also occur when generating a few samples less than a whole second or when expanding or contracting a selection.==

Miscellaneous platform-specific issues

(Mac OS X) If using Audacity when the "Hear" audio plug-in is running (or has been since boot), there will be excessive memory usage which could cause a crash: this appears to be due to buggy memory allocation in "Hear"
(Mac OS X) Very occasionally, users may find that after running Audacity, other media players don't produce any sound, or crash: to resolve this, set up your sound device in Apple Audio MIDI Setup to work in stereo, 16-bit, with a sample rate of 44100 Hz or 48000 Hz, and set the sample format and rate identically in Audacity. More help at:
(Linux) If pulseaudio is used as the audio device, repeatedly starting and stopping playback or recording in quick succession (or holding down the Play or Record button) may lead to a freeze. Workaround: bypass pulseaudio by setting the playback and recording device to an ALSA/hw choice in Device Toolbar.

Bugs requiring more investigation

(Windows Vista, 7) When a USB device is connected, the listing of inputs for the built-in sound device in Device Toolbar or Devices Preferences may become corrupt, indicating single inputs as multiple inputs. It may only be possible to record from the built-in input which is currently set as default at "Sound" in the Windows Control Panel, irrespective of the input selected in Audacity. Workaround: Try Transport > Rescan Audio Devices, or a computer reboot.
- Please report make and model number of devices that exhibit the issue, along with description of symptoms and any steps you have noticed that create the issue.
(Windows) There may be substantial delays drawing the waveform in some circumstances. These include fitting longer zoomed-in projects to the window, or when zooming in on fitted projects, also after importing files or running effects.

New features in Audacity 2.1.3 - Appendix

New shortcuts

ALT + RIGHT to Move to Next Label and ALT + LEFT to Move to Previous Label. These shortcuts allow the name of the label and its order in the labels in that track to be read by screen readers. As well as moving the edit position, these shortcuts jump playback to the requested label.

New features in Audacity 2.2.0 - Appendix

This page is an appendix to . It is an overview of further new functionality that has been introduced in Audacity 2.2.0

Details of all the major changes since 2.1.3 can be found in .

Sync-Lock

Audacity 2.2.1

Audacity 2.2.1 was released on 6 December 2017.

Changes since previous version

See the New features in Audacity 2.2.1 page for more information about improvements and other changes.

Improvements

Waveform colorways

You can optionally change the colorway of the waveforms displayed in your project. The setting is per track and not per project so you can have multiple colorways in the same project as in the image below.

Four colorways are available with the color selection made from the dropdown menu in the track's Track Control Panel.

When we made the menu changes for 2.2.0 we introduced an entry into the File menu called "Save Other" which led to a sub-menu for exporting various audio formats.

Many users were confused by this change and found it hard to find where they could export audio from. So for 2.2.1 we have changed that menu entry to be File > Export.

Bug Fixes

We fixed a bug on Mac that caused Audacity to crash with certain Chain files. Plus we fixed another Mac bug whereby opening a second project from Mac's Finder produced a second inaccessible instance of Audacity.

For those who really have to know, the list of bugs fixed in 2.2.1 is .

Supported Platforms

Windows

Audacity 2.2.1 requires the CPU to support the instruction set which should be available on any Intel hardware produced after 2001 and any AMD hardware produced after 2003. To check what SSE levels your CPU supports, you can install . If your hardware only supports SSE, you may download Audacity 2.0.6 see the page on the Audacity Website.
2.2.0 does not officially support Windows XP.

macOS / Mac OS X

Audacity 2.2.1 is for Intel Macs running OS X 10.6 and later and macOS. There are legacy versions for older OS X at .

Linux

Linux support is tested on Ubuntu Linux.
- Audacity may compile on Gentoo, Debian, Mint.
- Audacity does not currently compile on SuSE Linux.

Issues

See our for much more detail of issues with Audacity 2.2.1.

Below are listed what we believe are the most common and important issues with 2.2.1 for most users.

Timer Record

Timer Record may not reliably stop the recording on some machines. The Elapsed and Remaining Time counters may stop counting. In this case it will be necessary to force quit Audacity.
- On a few affected machines, the problem can be avoided if you leave focus on Audacity or ensure it has focus when recording is due to end.

(Linux) PULSE Audio

PulseAudio is not reliable when used with Audacity on Linux. Playback or recording may freeze, recording dropouts or fast playback may occur when using PulseAudio.
- Freezes may be caused by repeatedly starting and stopping playback or recording in quick succession (or by holding down the Play or Record button).
- Workarounds: Try launching Audacity from the terminal with the pulse latency set to 30 ms in an environment variable:

env PULSE_LATENCY_MSEC=30 audacity

If you get underruns noted in the terminal, try a higher number in the PULSE_LATENCY_MSEC command. If the problem is unchanged, try a lower number.
Alternatively, bypass pulseaudio by setting the playback and recording device to an ALSA (hw) choice in Device Toolbar. More help with this can be found here.

(Linux) MIDI

The timing of notes during MIDI playback may sound erratic on some machines. Optimizing the system for low latency MIDI playback can help to reduce the inaccuracies.

Accessibility

Far less of Audacity is properly accessible to visually impaired users than we would like. Currently the best supported platform for accessibility is Windows. We lost a lot of custom accessibility programming when we had to move to a more recent version of the wxWidgets library. A lot more detail about accessibility limitations can be found

Bugzilla

We track these and many other bugs in our 'bugzilla' database.

Click on the bug numbers to see work done on these bugs.

New features in Audacity 2.2.1

This page is an overview of the key new functionality that has been introduced in Audacity 2.2.1

Details of all the major changes since 2.2.0 can be found in Audacity 2.2.1.
2.2.1 is a very light release, basically a maintenance release, see below with one new exciting feature added. Plus we wanted to experiment with shorter release cycles.

Waveform colorways

Four colorways are available with the color selection made from the in the track's .

When we made the menu changes for 2.2.0 we introduced an entry into the File menu called "Save Other" which led to a sub-menu for exporting various audio formats.

Many users were confused by this change and found it hard to find where they could export audio from. So for 2.2.1 we have changed that menu entry to be File > Export.

Bug Fixes

Release 2.2.1 is mainly a maintenance release. Soon after the release of 2.2.0 we discovered some problematical bugs in Audacity:

- Opening a second project from Mac's Finder produces a second inaccessible instance of Audacity
- Crash applying certain chain files
- Preview fails when selection extends before zero

Links

- detailed release notes for this release of Audacity

New features in Audacity 2.3.1

This page is an overview of the key new functionality that has been introduced in Audacity 2.3.1

Details of all the major changes since 2.3.0 can be found in Audacity 2.3.1.

64-bit Mac build

The 2.3.1 release of Audacity for macOS is now a 64-bit build and will only run on modern 64-bit Macs, running OSX 10.7 or later.

Scrub Ruler

The Scrub Ruler is now turned "off" by default and is not displayed. The reason we did this was because we found too many users were accidentally clicking in the Scrub Ruler and then finding themselves stuck in Scrubbing mode.

This will only affect you if you opt to reset your preferences settings as part of the 2.3.1 installation, manually reset your preferences or install Audacity for the first time.

If you want/need to turn it back on again use either the and check the Scrub Ruler to be "on". Or right click in the Timeline and select Enable Scrub Ruler.

The Scrub and Seek commands are still readily available from the Transport menu.

Advanced Vertical Zooming

We have added a new command to the menu View > Zoom menu for turning Advanced Vertical Zooming "on" or "off".

Advanced Vertical Zooming enables you to use left-click gestures in the Vertical Scale to control zooming (this is in addition to the Simple mode vertical zooming commands available from the right-click context menu in the Vertical Scale).

In version 2.2.2 we changed the way works, splitting it into Simple and Advanced forms with the Advanced form turned off by default. Advanced mode could be turned on in Tracks Behaviors preferences but many users failed to find it there. Accordingly we introduced this new command to make this more discoverable.

Micro Fades

Micro fades (introduced in 2.3.0) can reduce the click when playback starts and stops. We've now made this an opt-in feature rather than provide it all the time, this can be set in Playback Preferences.

Regular Interval Labels improvements

We have made some improvements to Regular Interval Labels, accessed by Tools > Regular Interval Labels.

In particular we have made it possible to create range labels and not just point labels with this Tool. You can do this by specifying the label length in the new input field Length of label region (seconds)

Bug Fixes

Linux: Audacity 2.3.0 was available only for Mac and Windows, and Linux used 2.2.1. Audacity 2.3.1 is available for Linux.
Windows and Linux: Intermittent truncation of the end of a recording - see
Can't adjust Time Track envelope when Logarithmic scale selected - see

Links

- detailed release notes for this release of Audacity

Audacity 2.3.2

Audacity 2.3.2 was released on 15th May 2019.

Size and Checksums

Changes and improvements since previous version

Audacity 2.3.2 replaces all previous versions.

Audacity now includes the LAME MP3 encoder. Previously, due to now expired patents, you had to download it separately.
There is a new Select button in the track panel to select the whole track.
Audacity mod-script-pipe for driving Audacity from Python now comes with Audacity and it can be enabled via preferences.
Over 20 bugs fixed since 2.3.1. The most serious bug was that Audacity 2.3.1 would crash if append-recording to a collapsed track.

Full details of new features in the visual guide to

Supported Platforms

Windows

Audacity 2.3.2 requires the CPU to support the instruction set which should be available on any Intel hardware produced after 2001 and any AMD hardware produced after 2003.
- To check what SSE levels your CPU supports, you can install .
- If your hardware only supports SSE, you may download Audacity 2.0.6 see the page on the Audacity Website.

macOS / Mac OS X

Audacity 2.3.2 is for Intel Macs running OS X 10.7 and later and macOS.
- There are legacy versions for older OS X at .

Linux

Linux support is tested on Ubuntu Linux.
- Audacity may compile on Gentoo, Debian, Mint.
- Audacity does not currently compile on SuSE Linux.

Interactive Buglist Page

We probably track more bugs than you are interested in...

On the dynamic buglist page you can select to view:

Complete list of bugs in 2.3.1 that we have fixed for 2.3.2
Known bugs on the OS you use Mac, Windows or Linux.
Known bugs to do with accessibility or localization.
Workarounds for some bugs.

You can choose various combinations of these. However, there are probably too many minor bugs and too much detail on that for most users.

We do use this detail in our own QA work.

Highlighted Issues

Below are listed what we believe are the most common and important issues with 2.3.1 for most users.

Accessibility

Far less of Audacity is properly accessible to visually impaired users than we would like. Currently the best supported platform for accessibility is Windows. We lost a lot of custom accessibility programming when we had to move to a more recent version of the wxWidgets library.

Internationalization

Audacity is only partially translated in many languages. We also have some issues, for example, with Right-To-Left Languages.

Selected Bugzilla-Tracked Bugs

Click on the bug numbers to see work done on these bugs.

Audacity 2.4.0

Audacity 2.4.0 was released on 16th May 2020.

Checksums

Changes and improvements since previous version

Audacity 2.4.1

Audacity 2.4.1 was released on 20th May 2020.

Checksums

Changes and improvements since previous version

New features in Audacity 2.4.1

This page is an overview of prominent new functionality that has been introduced in Audacity 2.4.1

Details of all the major changes since 2.4.0 can be found in .

No new features

There were no new features in 2.4.1 - this was an emergency bug-fix release for a critical P1 bug.

Audacity 2.4.2

Audacity 2.4.2 was released on 26th Jun 2020.

Checksums

Changes and improvements since previous version

Audacity 2.4.2 replaces all previous versions.

Over 30 bugs fixed since 2.4.1

Full details of new features in the visual guide to

Supported Platforms

Windows

Audacity 2.4.2 requires the CPU to support the instruction set which should be available on any Intel hardware produced after 2001 and any AMD hardware produced after 2003.
- To check what SSE levels your CPU supports, you can install .
- If your hardware only supports SSE, you may download Audacity 2.0.6 see the page on the Audacity Website.

macOS / Mac OS X

Audacity 2.4.2 is for Intel Macs running OS X 10.7 and later and macOS.
- There are legacy versions for older OS X at .

Linux

Linux support is tested on Ubuntu Linux.
- Audacity may compile on Gentoo, Debian, Mint.
- Audacity does not currently compile on SuSE Linux.

Interactive Buglist Page

We probably track more bugs than you are interested in...

On the dynamic buglist page you can select to view:

Complete list of bugs in 2.4.1 that we have fixed for 2.4.2
Known bugs on the OS you use Mac, Windows or Linux.
Known bugs to do with accessibility or localization.
Workarounds for some bugs.

You can choose various combinations of these. However, there are probably too many minor bugs and too much detail on that for most users.

We do use this detail in our own QA work.

Highlighted Issues

Below are listed what we believe are the most common and important issues with 2.4.2 for most users.

Accessibility

Far less of Audacity is properly accessible to visually impaired users than we would like. Currently the best supported platform for accessibility is Windows. We lost a lot of custom accessibility programming when we had to move to a more recent version of the wxWidgets library.

Internationalization

Audacity is only partially translated in many languages. We also have some issues, for example, with Right-To-Left Languages.

Selected Bugzilla-Tracked Bugs

Click on the bug numbers to see work done on these bugs.

New features in Audacity 2.4.2

This page is an overview of prominent new functionality that has been introduced in Audacity 2.4.2

Version 2.4.2 is primarily a maintenance release for bug-fixing, so there are not many new features.

Details of all the major changes since 2.4.1 can be found in .

Audacity 2.0.0

Audacity 2.0.0 was available from 13 March 2012 until 28 June 2012 for Windows, Mac OS X and GNU/Linux. These Release Notes describe:

Changes in 2.0.0 as compared with 1.3.14
Summary of bug fixes and new features between 1.2.6 and 2.0.0
Issues with 2.0.0 which were known at time of release.

Tip: You can use CTRL + F to search this page for different words to do with the issue you are looking for. Use Command - F on Mac.

Notes for Windows:

Users upgrading to 2.0.0 from 1.3.6 or earlier must download the of the LAME MP3 encoder.
The Windows installer for 2.0.0 will replace 1.2.x installations, but install alongside 1.3.x Beta versions. As 2.0.0 also replaces the 1.3.x series, it is strongly recommended to uninstall previous Beta versions.

Changes between 1.3.14 and 2.0.0

Bug fixes

Interface

Fixed playback speed and synchronization problems when dragging clips or tracks between tracks having different sample rates.
(Windows) Removed a crash risk where shortcuts could be used to record or import in one project while importing or exporting in another.

Imports and Exports

Fixed crashes when changing the sample format of read-directly WAV or AIFF files using the Track Dropdown Menu.
Fixed a crash importing MP3 files that had duplicate metadata tags (this is a bug in current libsndfile which has been patched in Audacity; MP3 files mislabeled as WAV which have duplicate tags will still crash Audacity on Linux if Audacity has been compiled against an affected version of system libsndfile).
Fixed an issue where excessively high or corrupted sample values in the audio could corrupt exports from the start of the problem for the rest of the file, and could corrupt the rest of the project.

Effects and Analysis

Fixed crash on launch when using "Ambisonic Decoders (PC)" VST plug-ins and other plug-ins that enable additional floating point exceptions.
Fixed Plot Spectrum background could be transparent on some machines.
Bug fixes for Click Track, High Pass, Low Pass and Vocal Remover.
Chirp, Tone and Silence generators now remember their settings.

Other miscellaneous bug fixes

Changes and Improvements

New Interface preference to show the track name in the display (this is off by default).
Longer default Playback preference for effects preview and preview before cut.
Restored use of Page Up and Page Down to scroll horizontally.

Summary of bug fixes and new features between 1.2.6 and 2.0.0

Bug Fixes

Labels now accept lower case "z".
(Windows Vista/7) Pressing Stop after recording could cause a crash.
(Mac OS X) Fixed shortcut keys activating when typing in file open or save windows.
(Mac OS X) Audacity 2.0.0 fully supports Unicode, which fixes an issue where Audacity could not work with folders having non-English characters in their name.

New features

These are some of the dozens of new features in 2.0.0.

Many effects significantly improved, especially Equalization, Noise Removal and Normalize. Vocal Remover now included plus GVerb on Windows and Mac. VAMP analysis plug-ins now supported.
Improved label tracks with Sync-Lock Tracks feature in the Tracks Menu.
Multiple clips per track. Tracks and selections can be fully manipulated using the keyboard. Many more keyboard shortcuts.

Known Issues at Release

Headline issues

Large Projects

Problems reopening, saving or crashing in projects

When attempting to reopen the project normally:
- The .aup project file was not saved (or incompletely saved, giving a "line number" error).
- Audio that was there previously is silenced.

To avoid any problems, export a WAV or AIFF file from your project before closing it, then you can import the WAV again if the project becomes damaged.

When working in the project:
- Errors occur when saving the project or when Audacity autosaves, perhaps wrongly suggesting the disk is full or not writable (if this happens, try exporting the audio as WAV).
- Unwanted renaming or moving of .au files within the project.

As many as possible of the following will help us enormously if you can attach them to your report:

A copy of the saved .aup project file
A copy of the "autosave" (temporary project) file. The "autosave" file is stored inside the "AutoSave" folder in Audacity's

Changes and Improvements

CleanSpeech Mode (a customized interface with reduced menus and stored effects presets) is no longer officially supported. We may reintroduce a new system of alternative presets and simplified menus in a later Audacity. However any users who had CleanSpeech enabled in 1.3.13 or earlier 1.3 versions will still have it enabled without any way to turn it off in the program. Workaround: To turn off CleanSpeech, either turn it off in the Interface Preferences of a previous 1.3 version, or exit Audacity, open in a text editor and remove the line "CleanSpeechMode=1". Alternatively, change the value 1 to 0 to turn CleanSpeech off, and set it back to 1 to re-enable CleanSpeech.==

Program Launch

(Linux) If a Bluetooth audio device is in use on a PulseAudio system, Audacity may hang on launch on initial attempts, then after eventual launch Bluetooth will no longer work on the system. Workarounds:
- Remove and reconnect the external Bluetooth adaptor, then launch bluetooth-applet from the command line.
- To prevent Audacity affecting Bluetooth support, move /usr/share/alsa/bluetooth.conf to another location then reboot, or create a symbolic link from /var/lib/alsa/asound.state to /dev/null and reboot.

[AudioUnits] Enable=0 [VST] Enable=0 Rescan=0

If plug-ins were the problem, Audacity should now launch.

Installation

(OS X 10.6 or later) Administrative (and occasionally, root) permissions may be needed on some machines to read the optional LAME and FFmpeg libraries at /usr/local/lib/audacity. In case of difficulty, please download the zip versions "Lame Library v3.98.2 for Audacity on OSX.zip" and "FFmpeg v0.6.2 for Audacity on OSX.zip" from the and extract the files to your own preferred location.

Imports and Exports

By default, the importer used depends on the import method. For example, to be able to use to import native Audacity formats like WAV and MP3, you must choose the "FFmpeg-compatible files" filter in File > Open or File > Import > Audio and always use one of those import methods. To force FFmpeg to import native Audacity formats when using File > Recent Files or dragging in, add rules for those formats in . To force FFmpeg import irrespective of the filter when using File > Open or File > Import > Audio, uncheck "Attempt to use filter in OpenFile dialog first" in Extended Import Preferences as well as adding the rule for the format.
(Linux) AAC exports produce a zero bytes file if the Audacity project rate is below 22050 Hz. Additionally, the "Quality" slider in AAC export Options has no effect on the exported bitrate. "Workaround: Export as WAV and convert to AAC using FFmpeg at the terminal.

Interface

Dragging a clip or track up or down with Time Shift Tool does not scroll the project window when tracks exist out of view above or below the scroll. Workaround: Choose View > Fit Vertically before drag, or click and hold the piece to be dragged, use up or down arrow on the keyboard to scroll to the target track, then drag and release the clip or track.
Selections locked to/only possible to click at whole seconds: We know that it is easy to check the "Snap To" box in by mistake, which means you can't then select less than a whole second or click other than at a whole second. We will look for a solution that keeps Snap To discoverable but makes it harder to enable by accident.==
(OS X) Set Rate > Other... in the Track Dropdown Menu does not display the current track rate unless that rate is in the list of set rates.

(Linux) The OK button has focus on opening effects and other dialogs, instead of fields for changing values. This is a bug in wxGTK. To change values or settings in the dialog it is necessary to deliver a mouse click.
(Linux) Using a file manager (for example, context menu) or the command line to open further files gives an error. Even if Audacity is closed, only one file can be opened from the file manager. Workaround: Use File > Open, or (for audio files) File > New then drag the files in.
(Windows) It is not yet possible to drag .lnk shortcuts to audio files or projects into Audacity, or to drag them to the Audacity executable's icon. Workaround: Use File > Open or File > Import > Audio, or double-click the shortcut to the .aup from Windows Explorer.

Playback and Recording

(Windows Vista, 7) If you change the explicit output and/or input device selected in Device Toolbar or Devices Preferences and then change "Host", the selected devices will change back to those originally selected.
(Windows XP and earlier) Changing the default playback or recording devices in the Windows Control Panel while Audacity is open may cause all the playback or recording choices in Device Toolbar to produce silence (or to fail with "Error opening sound device"). This problem may also occur when connecting or disconnecting a USB device while Audacity is open. Workaround: Click Transport > Rescan Audio Devices then you can play or record.
(OS X and Linux) Audacity now works very well with , with the following bugs and limitations:

Effects and Analysis

Cut Preview only plays the upper track of multiple selected or Sync-Locked tracks.
LADSPA Multiband EQ may not be visible in Effect menu (occurs on Windows XP), and crashes soon after opening
Nyquist effects render the space between clips as silence. Workarounds: Edit > Clip Boundaries > Detach at Silences (this could reduce the length of clips that have silent fades) or double-click each clip and apply the effect separately to it.

Projects

Projects containing more than 2^31 samples (just over 13.5 hours of audio at 44100 Hz) will re-open empty with the entire data being seen as "orphaned files" (although the data "appears" to be in the correct location expected by the .aup file). Workaround: Before saving or closing the project, export to audio files of appropriate size, or cut and paste sections of audio containing less than 2^31 samples to new Audacity projects and save those.
It is no longer possible to use Save Project or Save Project As to overwrite another pre-existing project, even if that project is not in use. Functionality to overwrite a project not in use will be restored in a future version of Audacity when we are sure it will always be safe.
(OS X) Crash closing project window immediately after saving project: After saving a project, if you close the project window immediately the "Saving project data files" dialog completes, there will be an unexpected "Save changes?" prompt and then a crash when you choose "Yes" or "No". As long as you say "Yes", the project will be saved correctly and can be reopened normally after you restart Audacity. To be sure there is no crash, wait after "Saving project data files" completes for any "Inspecting Project Data" dialog to appear and disappear before closing the project window.

Accessibility

(Linux) If you TAB into "Snap To" in Selection Toolbar, the selection and focus will become trapped. A mouse click elsewhere will be required to free the focus. Workaround: Access the required part of Selection Toolbar with TAB or SHIFT + TAB so as to avoid Snap To. Snap To can be set on or off by exiting Audacity, show hidden files and folders then add or edit the line "SnapTo=1" or "SnapTo=0" (without quotes, for on or off respectively) in ~/.audacity-data/audacity.cfg.
Many, but not all parts of the Audacity interface are accessible on Windows to those who can't use a mouse, and/or use a screen reader. It may be possible to make more of Audacity accessible in the longer term. For details, see .

There are some accessibility bugs in the parts of Audacity that are accessible.

Toolbar buttons cannot be operated by pressing either ENTER or Space: ENTER incorrectly moves to the next control and Space starts/stops playback. However the buttons can be operated either by using their shortcut keys, or for users of screen readers by using the Jaws cursor or equivalent. Note: it will be necessary to go to the Keyboard Preferences to set a shortcut for the Play-at-speed button.
For users of JAWS and Window-eyes. when the Silence Generator dialog opens, the duration control is incorrectly read as 0 seconds. However, if you tab round to the control again, the correct value is read.
For users of all screen readers, "and" is read out before the access key character in some controls in Preferences.

Chains

(Linux) When configuring effect parameters in "Edit Chains", the "Preview" button is not intended to be functional. Pressing it may cause a crash.

Clips

Left-clicking in a stereo track to merge a clip at a split line may cause other clips to move. It is believed this only happens after having used the Track Dropdown Menu to make two mono tracks into stereo. Workaround: Select over the split line and Edit > Clip Boundaries > Join.

Compiling

(Windows) Compilation with Visual Studio 2010 is not supported or recommended. See the Wiki page for information.
(Windows) LADSPA effects cannot be categorized even when Audacity is compiled with USE_LIBLRDF defined.

Label Tracks

(Linux) In projects containing several hundred labels or more, Audacity will freeze on 100% CPU when opening the "Audacity Karaoke" window, and will freeze again while that window is open when editing a label or performing other actions on the project. Workaround: Open or place an empty label track above the one you want to use.
Typing "j", "J", "k" or"K" in a label track may activate the "move cursor" or "select to/from cursor" shortcut instead. Workaround: click Edit > Preferences: Keyboard, choose the "Edit" category then change the shortcuts for "Move Cursor to Track Start", "Move Cursor to Track End", "Select Track Start to Cursor" and "Select Cursor to Track End" to something else (or clear them).
Unless Tracks > Sync-Lock Tracks is on, pasting or inserting audio does not affect labels even if the label track is included in the selection.

Mixer Board

(Linux) Meters may not respond immediately to playback which could cause them to report incorrect peak level or not display clipping.
Meter range does not reflect a change in the dB range meter preferences until restart

Preferences

(Linux) Extended Import: Clicking "Move rule up" when there are no rules or filters causes a crash.==

Toolbars

When using Selection Toolbar in a selection format in less than whole seconds, an inaccurate value for length or cursor position may display when zoomed in. The displayed value will be the nearest whole second below the true value (for example, 59.000 seconds where the true value is 59.999 seconds). This can occur when clicking on or moving the cursor across a boundary for whole seconds, in which case you can use right arrow to show the correct value. It can also occur when generating a few samples less than a whole second or when expanding or contracting a selection.==

Miscellaneous platform-specific issues

(Mac OS X) If using Audacity when the "Hear" audio plug-in is running (or has been since boot), there will be excessive memory usage which could cause a crash: this appears to be due to buggy memory allocation in "Hear"
(Mac OS X) Very occasionally, users may find that after running Audacity, other media players don't produce any sound, or crash: to resolve this, set up your sound device in Apple Audio MIDI Setup to work in stereo, 16-bit, with a sample rate of 44100 Hz or 48000 Hz, and set the sample format and rate identically in Audacity. More help at:
(Linux) If pulseaudio is used as the audio device, repeatedly starting and stopping playback or recording in quick succession (or holding down the Play or Record button) may lead to a freeze. Workaround: bypass pulseaudio by setting the playback and recording device to an ALSA/hw choice in Device Toolbar.

Bugs requiring more investigation

(Windows Vista, 7) When a USB device is connected, the listing of inputs for the built-in sound device in Device Toolbar or Devices Preferences may become corrupt, indicating single inputs as multiple inputs. It may only be possible to record from the built-in input which is currently set as default at "Sound" in the Windows Control Panel, irrespective of the input selected in Audacity. Workaround: Try Transport > Rescan Audio Devices, or a computer reboot.
- Please report make and model number of devices that exhibit the issue, along with description of symptoms and any steps you have noticed that create the issue.
(Windows) There may be substantial delays drawing the waveform in some circumstances. These include fitting longer zoomed-in projects to the window, or when zooming in on fitted projects, also after importing files or running effects.

New features in Audacity 2.3.0

This page is an overview of the key new functionality that has been introduced in Audacity 2.3.0

Details of all the major changes since 2.2.2 can be found in Audacity 2.3.0.

Punch and Roll Recording

We have introduced Punch and Roll Recording into Audacity as one of our most popular and long-standing feature requests.

It is Accessed by: Transport > Recording > Punch and Roll Record or more simply using its shortcut Shift + D.

This enables you to correct errors easily during the course of a recording session.

You can stop, back up over a mistake, and continue recording, resulting in one track that eliminates the errors and is properly timed, without the use of cutting, pasting, and clip-moving commands, or mixing of multiple tracks.
You can do rough editing as you go, with minimal interruption of your performance and less work left until afterwards.

This is likely to be very useful to voiceover artists and audiobook authors enabling them to make rapid corrections of fluffs as they progress.

Be aware that this is not punch-in patch repair - the repair recording carries on rolling (as the command name implies) until you specifically stop it.

Movable pinned Playhead/Recordhead

We have made the pinned playhead/recordhead movable on the Timeline, enabling you to choose whereabouts on the Timeline you want it to be pinned for playback and recording

The default pinned position is the center of the Timeline as before, but you can change this by clicking on the pinned head and dragging it along the Timeline while you are playing or recording. A double-click on the head will restore it to its default position in the center of the Timeline.

You may find that a pinned Playhead/Recordhead position right of center will be more useful during recording, including Punch and Roll recording, but a position back in the middle may be more useful if you are playing, especially if you are scrubbing and seeking.

Scrubbing and Seeking always use un-pinned playhead

By default, scrubbing and seeking will ignore the pinned playhead (if it is turned on) and will play with an unpinned playhead. This will cause the playhead to move with the waveform remaining static.

You can change this by turning "off" the option for "Always scrub unpinned" in Playback preferences. This will cause the playhead to remain static and the waveform will move under it while scrubbing and seeking.

The un-pinned head is probably the easier way to work with scrubbing and seeking.

Play-at-Speed

The Play-at-Speed Toolbar (formerly called the "Transcription Toolbar") now enables you to make dynamic changes to the playback speed as you play audio using the Transcription toolbar to set the required speed. Formerly you had to stop playback and restart it to get the changed speed.

The Play-at-Speed toolbar has also been made resizable, so you can stretch it by dragging the right end rightwards, and so get a longer slider with more precision to it. At the same time as we made this change we also made the Mixer toolbar resizable, to give more precision over the main volume and playback settings if you want it.

Batch Processing

A collection of features added to Audacity for 2.3.0 are related. They come from a project to improve batch processing. Listed here, they are described in more detail in following sections. The project led to improved:

feature (replaces Chains), for repetitive tasks that can be done without using a scripting language.
Scripting using a scripting language such as Python running outside Audacity.
The project led to the new tools menu, and the new submenus with many new commands.

Macros command replaces Chains

The old Chains command (for batch processing and effect automation) has been replaced by an extended command. Macros can do everything that Chains did before, however there are now many more commands it can use - including new commands that have been created specially for batch processing.

We have changed the user interface integrating the functionality so that you now can view, edit and apply your macros from the same single dialog window, simplifying the usage of macros.

Re-setting the parameters for commands in macros has been simplified. Now double clicking on a command in a displayed chain will pop up the parameter settings dialog for that command.
The dialog window can be reduced in size and scope by using the Shrink button. This reduced 'Macro Palette' dialog can apply macros to your project, but does not edit them.
Many more commands are now available to Macros. Previously the commands were mostly effects. Now nearly all menu items are included.

A new menu item Tools has been created, with customizable tools.

Chains feature renamed as 'Macros'.
Extended documentation on using Macros for presets and other tasks.
Dialogs have help buttons
Some new prebuilt macros are available in Tools, and you can configure and add your own.

We have created a new submenu from the File Menu called Save Project

This replaces the former Save Project and Save Project As commands and these move into the new submenu. The Save Compressed Copy of Project... is also moved to the new submenu (it was in File > Export formerly).

Most importantly we have added a new command to that menu File > Save Project > Save Lossless Copy of Project. This is the now the safe and recommended way to make a safety backup copy of a project as you work on it. This could serve either as a single backup copy of the project, or as one of several incremental copies of the project in the state it had at a particular date and time. Unlike "Save As..." using this command will leave your current project open enabling you to continue working on it.

New Scriptables submenus

New Extra > Scriptables I and Extra > Scriptables II submenus in the Extra menu

24 New functions in these menus
- These are likely to be particularly useful to VI users.
- Actions that are currently done by mouse that can now be done by keyboard.

Nyquist effects translated

Nyquist effects now support translation, and the ones shipped with Audacity are translated.

Help Buttons

We added help buttons ? to the Macros full and reduced dialogs, to the Export dialogs, to some error message dialogs and to some other dialogs that did not previously have them.

Increased legibility of trackname display

Increased legibility of trackname display. the Track Name overlay now has a background.

Half-wave option for collapsed tracks

For collapsed tracks there is now an option settable in Tracks Preferences to show the upper half of the wave display only in order to show a little more detail.

Sliding Stretch replace Sliding Time Scale / Pitch Shift

The effect that was formerly named "Sliding Time Scale / Pitch Shift" has been renamed to Sliding Stretch for this release.

This is a simple name change, no other changes have been made to the effect. The change has been made mainly to reduce verbosity in the menu along with an attempt to make the command name more meaningful.

Overwriting existing projects

In response to many user requests for this we have changed Audacity so that is now possible to overwrite pre-existing projects with File > Save Project or File > Save Project As....

In doing so you will get the following warning message and please note that for safety reasons this warning cannot be turned off.

Use dialog for the name of new labels

There is a new option in Tracks Behaviors Preferences for: "Use dialog for the name of new label".

This is off by default, but when enabled creating a label will pop up a dialog box for you to enter the label name (rather than the default behavior of opening the new label itself for editing). When the dialog is closed, focus is returned to the track which was the focus before the dialog opened. This functionality is primarily provided to aid Visually Impaired users who use screen readers, but may be useful to normally sighted users too.

The shortcuts for clip navigation have been changed

Select > Clip Boundaries > Previous Clip is now Alt + , - was Alt + P
Select > Clip Boundaries > Next Clip is now Alt + . - was Alt + N

Bug Fixes

Windows: Queen Mary 1.7.1 Vamp plug-ins crash Audacity on opening Plug-in Manager - see
Inconsistent behavior when recording with a selection defined see
Ctrl + M does not open label for editing - see

Links

- detailed release notes for this release of Audacity

New features in Audacity 2.4.0

This page is an overview of prominent new functionality that has been introduced in Audacity 2.4.0

Details of all the major changes since 2.3.3 can be found in Audacity 2.4.0.

For this release the audio time position has been removed from the Selection Toolbar and created a new toolbar, the Time Toolbar. It is a read-only toolbar which displays the current audio position. The larger size of numbers makes it easy to read when, for example, you are recording an instrument you are playing and are further from the computer screen and keyboard than when directly editing the audio.

When Playing or Recording Time Toolbar dynamically shows the current playhead or recordhead position.

When Audacity is not Playing or Recording it will display either the current cursor position or the beginning of the current selection if present.

Time Toolbar provides a larger display, easily readable at a glance, for the current audio position. It is a double-height toolbar with a default display of roughly 1.5x previous size.
You can resize to full double height , shrink it smaller or just remove the toolbar if you don't need it. It can be redocked in various positions in either tooldock and can be floated if you wish
The time display format can be changed independently of the Selection Toolbar's time format.

Export and Import of settings in effects

Previously in Audacity you could only use the Export and Import buttons for VST and AU effects. This has now been extended to all effects that have a Manage button.

Import...

Imports presets which you have exported using the Export option (below) on this or other machines or which you have exported from other software that supports a compatible preset.

Export...

Exports an effect's current settings as presets (in a text file) for use in Audacity on other users or machines via Import or for use in other software that supports import of a compatible preset.

Note carefully that this Export creates a single exported text file with just the current settings in the effect. It does NOT export your entire set of User Presets.

The equalization effects: Filter Curve EQ and Graphic EQ:

In common with all other effects these now facilitate the import of pre-existing equalization curves for use in the effect.

Many published curves, such as those on the , and curves you may have exported in earlier versions of Audacity with the old Equalization effect, are in .XML format.

Multi-view

This is an advanced feature for expert users enabling Spectrogram and Waveform displays of the same audio shown simultaneously in the same track.

Spectrograms and Waveforms have different strengths and weaknesses:

Waveforms show you overall loudness best. You might see the danger of imminent clipping. Precision in cutting and splicing is also best performed in Waveform view.
Spectrograms show you frequencies. In vocals, for example, you can see how vowel sounds change over time. The onset of new sounds, when another sound is playing, often shows up more clearly in Spectrograms.

Choose whichever one gives you the best information for the task in hand.

To get a split Multi-view for a track select Multi-view from the track's Track Control Panel dropdown menu.

Opus Export

Opus has been added as an export option to the File > Export > Export Audio and File > Export > Export Multiple commands.

It is accessed from those commands then choosing Opus (OggOpus) Files (FFmpeg) from the Save as type dropdown menu in the Export dialog:

This Opus Export replaces the previous "opus" export from the (external program) option in the Export dialogs, which never worked for "opus", always giving a failure error message.

Opus Export is only available on Windows and Linux for now - we aim to provide it on Mac in a future release - see .

Changed behaviors for resizing and moving labels

The gestures for resizing and moving labels has been changed slightly in this release. This was done in fixing a couple of bugs that were found relating to label editing.

Point label

You can move a point label by clicking and dragging its circle handle.
You can turn a point label into a region label by clicking and dragging either of its chevron handles.

You can also move a point label by holding the Shift key down while clicking and dragging the circle or either of its chevron handles.

Using this shift-modified click&drag with a point label avoids any risk of accidentally creating a region label.

Region label

You can change the length of a region label by clicking and dragging its circle or either of its chevron handles.
You can move a region label by holding the Shift key while clicking and dragging its circle or either of its chevron handles.
In the case where two region labels meet you can adjust the junction point where they meet by clicking and dragging their shared circle handle.

There is now a slight visual cue to distinguish between a point label and a region label that is too short to display at the current zoom level.

The region never collapses down to a single line, rather there is always a line for each edge of the region resulting in a double line, slightly visibly thicker.

Spectrograms now show Clip Boundaries

Spectrogram views have changed, they now show Clip Boundaries, the dark vertical lines in the image below.

Formerly these clip boundaries were only shown on Waveform views.

This change also affects the new display.

Selecting Waveform dB

This used to be accomplished with the TCP dropdown menu, it is now in the Waveform Vertical Scale' context menu.

A right-click in the Vertical Scale will bring up a dropdown context menu enabling swapping between Linear Waveform (default) and Waveform dB views.

Scrubbing using the keyboard

Two new shortcut commands have been added to facilitate scrubbing from the keyboard.

These are:

I: Scrub Forwards
U: Scrub Backwards

they are part of the Standard default set of keyboard shortcuts.

After pressing one of these scrubbing keys playback continues until the key is released. Playback starts from the cursor position or the start of a time selection if there is one. Scrubbing is not limited by any selection that may be present.

If one of the keyboard scrubbing keys is being held down, and the other keyboard scrubbing key is pressed scrubbing immediately changes direction, and does not stop when the original key is released.

The speed of playback is determined by the zoom level. If the zoom level is normal playback speed is one half of the normal playback speed. Zooming in (Ctrl + 1) halves the playback speed, zooming out (Ctrl + 3) doubles the playback speed. There are minimum and maximum playback speeds of one sixteenth and 3x, respectively.

If you want to use keyboard scrubbing at normal speed, just press Ctrl + 2 to return to normal zoom level followed by Ctrl + 3 to zoom out one level.

Two new commands have been added to the Tracks menu to enable you to simultaneously Mute or Unmute all the currently selected tracks.

Tracks > Mute/Unmute > Mute Tracks
Tracks > Mute/Unmute > Unmute Tracks

These operate on all selected audio tracks in the project, as if you had used the Mute buttons from the Track Control Panel on each selected track.

Changes to Play/Record head pinning

The mechanism for toggling the Play and Record head from its default unpinned position to a pinned position on the Timeline has been changed. This was done to try to prevent users accidentally turning on pinned head and then not knowing how to revert to the default unpinned. When the head is pinned the head remains static and the waveforms will move as the audio is played or recorded.

Formerly a single click on the head icon at the left of the icon would toggle between the two modes. Now when you click on that icon a context menu is displayed:

From this menu you can choose to select or un-select Pinned Play Head.

The same context menu is available when you right-click in the Timeline - alternatively unpinned or pinned head can also be selected in Transport > Transport Options.

If you miss the availability of single click functionality to achieve toggling the head mode it is easy to set up a single-key custom shortcut.

New effects and a new analyzer

Loudness Normalization

A new effect, "Loudness Normalization", has been added. As its name suggests, it normalizes for loudness.

Use Loudness Normalization to change the level of the audio (normally reduce it to recommended limits).

It is based on EBU R 128 recommendations on limiting the loudness of audio signals.

Why use Loudness Normalization rather than Normalize or Amplify?

Using Loudness Normalization rather than Normalize or Amplify helps you more easily set the required LUFS loudness target when normalizing.
When preparing audio for television or radio programs, podcasts and some websites you may be subject to loudness restrictions on the audio. Loudness is usually measure in LUFS (Loudness Units Full Scale). The LUFS level restrictions can vary by application. For example, the level for television in the US is normally -24 LUFS, the EBU (European Broadcasting Union) recommends -23 LUFS. Out of all the standards this one is the most serious in that a television network can get its broadcast license revoked for a violation.

Measure RMS

A simple analyzer to measure the RMS (Root Mean Square) levels in a track.

The example above is the measurement of a typical stereo track.

If you use this analyzer on a mono track you will just get a single figure shown.

Noise Gate

Another new effect has been added, "Noise Gate", which can be used to reduce the level of sound below a specified threshold level.

A noise gate is a kind of "dynamics processor" that allows audio above a specified threshold level to pass through unaffected (gate "open"), and stops or reduces sounds below the threshold level (gate "closed").

Noise Gates may be used to cut the level of residual noise between sections of a recording. This Noise Gate has a number of settings that allow it to be effective, unobtrusive and well suited to most types of audio.

Spectral Delete

A new effect has been added to the spectral editing effects.

The Spectral Delete effect acts on a spectral selection to delete a spectral selection from the audio.

For this we have used a higher than default "Window Size" of 4096 in the spectrogram settings, because that shows the accuracy of the frequency cut much better.

The Spectral Selection Toolbar has been enabled and floated to aid and show the accurate selection range.

Searching the Manual

For this release we have added a page to the Manual on Searching the Manual.

For various technical reasons we cannot provide a Search box/button for the Manual. So this new page provides some useful workarounds.

The page can readily be accessed from any Manual page you are on from the Reference section of the left-hand navigation bars.

There is also an entry for it in the Quick Help section on the Manual's front page.

Bug Fixes

Over 100 bugs have been fixed for this release, including over 50 priority 1 and priority 2 bugs.

Here is a small selection of some of the most important.

Key P1 bugs fixed

P1 - Mac: Audacity does not run properly on macOS 10.15 Catalina
P1 - Equalization effects have no Import or Export for curves
P1 - Graphic EQ sliders have no frequency labels

Key P2 bugs fixed

P2 - Export as WAV does not remember the previously used setting
P2 - Rendering a single track unnecessarily moves the track to project bottom
P2 - Rendering a single track unnecessarily strips it of its properties

Links

- detailed release notes for this release of Audacity

New features in Audacity 2.3.3

This page is an overview of the key new functionality that has been introduced in Audacity 2.3.3

Details of all the major changes since 2.3.2 can be found in Audacity 2.3.3.

Maintenance release

2.3.3 is a maintenance release to reorganize the structure of the underlying code. This is so that we can make better changes for the user experience in the future.

There are no new and almost no changed features in this release. However, we have fixed many long standing bugs, at the same time as making the restructuring. We are also taking the opportunity to retire some features which are better done by other approaches.

Earlier we had set ourselves a target of 20% live bugs out of total bugs by August 2019. Two years ago 35% of bugs were live bugs, and the live bugs total was just over 600. We actually met our target early, by 1st June 2019. As at 1st September we were at 16% live bugs with just 356 live bugs. See in the Audacity Wiki.

Two bugs we fixed which noticeably change behavior are:

Quality slider now works for AAC/M4A Export

An important bug-fix for this release is that we have finally made the Quality slider work when exporting AAC/M4A files. Formerly, although you could move the slider, the setting of slider was ignored by Audacity and it used always a constant bit rate (CBR) 196 kbps (stereo) file or 98 kbps (mono) file.

This was - M4A Quality slider has no control of bitrate setting or AAC quality

Leading blank space treated as silence on Export

For this release we have added a feature where by default when exporting audio any leading blank space in the tracks or project to be exported is treated as silence and appropriate leading silence will pad the exported audio.

Previously many users were confused when they had carefully positioned their audio with an initial offset (white/gray space) that when they Exported the track this offset was ignored and the exported file started immediately with the audio with no offset.

This particularly confused multi-track users who export and subsequently re-import tracks and are surprised/puzzled when their tracks no longer line up properly.

This makes for greater consistency in Audacity with regard to pre-existing behaviors:

leading blank space has always been treated as silence when playing such an offset audio track
if a track has embedded blank white/gray space between audio clips, upon export those embedded chunks are rendered as silence to preserve the relative positioning of the clips.
Mix&Render has always preserved leading blank white/gray offsets

There is a new option in Import/Export Preferences where you can turn this off and revert to Audacity's previous behavior with leading blank space ignored on Export.

A use case for turning this "on" is track-based multiple export where you have "songs" lined up one after the other on different tracks - and in this case you probably do not want the offsets exported as long silences at the start of "songs".

This was - Audio offset not honored in Export/Export Multiple/Export Selection

Exports are now based on "What you hear is what you get"

From this version onwards when making multi-track exports the export will be based entirely upon the track hear when preview playing the audio in the project prior to Export.

I also means than any grayed-out tracks will not be exported.

Formerly with the Solo Button behavior set to the expert mode "Multi-Track" in Tracks Behaviors" preferences the exports were instead based on the state of the Mute buttons, using the Solo buttons could leave some tracks grayed out and not playable on preview, but still exported on Export.

Users who leave the Solo Button set to its default Simple mode will notice no difference as a result of this change.

This was - When Solo button is "Multi-track" Export is not accurate - can lead to data loss

Equalization effect split

The former Equalization effect has now been split into two separate effects. We did this as part of fixing some bugs with the effect:

Filter Curve - equalization using drawn curves

Graphic EQ - equalization using sliders

End-of-life retired functionality

For this maintenance release we have decided to withdraw some pieces of functionality which are considered to be no longer useful or relevant.

Nyquist Workbench End of Life

The optional module Nyquist Workbench has been declared obsolete for version 2.3.3 onwards.

We plan to replace it later with a modern alternative . A lot of the important functionality is already built into the Nyquist prompt in Audacity.

Vocal Remover End of Life

We have finally decided to no longer ship the legacy effect Vocal Remover with Audacity. It has been superseded for a while now by the newer and more powerful Vocal Reduction and Isolation effect. We upgraded the effect slightly with this release, so that it now can also do exactly what the old effect did.

New users who install 2.3.3 as their first Audacity will not see Vocal Remover in the effect menu. Upgraders from earlier versions of Audacity will still find this legacy effect in their effects list (because it was supplied as a Nyquist plug-in). If you no longer wish to see it in the Effect menu simply mark it as Disabled in the Plug-in Manager.

On-Demand loading of aliased files End of Life

Audacity previously had a feature where Audacity projects could depend on uncompressed audio files (for example WAV and AIFF) that were stored outside the Audacity project and folder. This saved space but was rather dangerous, as the project could become unusable if the files were moved or renamed.

The space saving made some sense back in 1999 when disk storage was more expensive. Nowadays it does not make sense. It causes far more problems than the space saving is worth. Previously we had defaults set to always copy audio into projects, and not try and save space. Now we have removed the option of this ill advised space saving. Audacity will still work with old projects that do this, but for new projects audio will always be copied in.

Normalize on Load feature

Audacity previously had a 'mis-feature' called 'Normalize on Load' which gave the option of always normalizing newly imported audio (an option that was settable in preferences). Normalizing or alternatively compression should usually only be done as one of the last steps in producing audio, for example if one knows the audio is destined to go into an MP3 file or CD.

Bug Fixes

We have fixed many bugs in the course of this maintenance release:

Click on the bug number for full details in the bug thread.

P1 - Mac - FFmpeg Custom options dialog opens behind Export Audio dialog
P1 - Crash when opening Equalization settings in a Macro
P1 - Linux: Incorrect behaviors in "Manage Macro"

Equalization bugs

P1 - Equalization: EQ control points can disappear if the points are at the same frequency
P1 - Equalization: presets under the Manage button do not save custom EQ curves
P1 - Graphic EQ ( and Filter Curve): Manage button does not work

Links

- detailed release notes for this release of Audacity

Audacity 2.0.1

Audacity 2.0.1 was available from 29 June 2012 until 23 August 2012 for Windows, Mac OS X and GNU/Linux. These Release Notes describe:

Changes in 2.0.1 as compared with 2.0.0
Issues with 2.0.1 which were known at time of release.

Tip: You can use CTRL + F to search this page for different words to do with the issue you are looking for. Use Command - F on Mac.

Notes for Windows:

Users upgrading to 2.0 versions from 1.3.6 or earlier must download the of the LAME MP3 encoder.
The Windows installer for 2.0 versions will replace 1.2.x or any previous 2.0.x installation, but install alongside legacy 1.3.x Beta versions. It is strongly recommended to uninstall previous Beta versions.

Changes between 2.0.0 and 2.0.1

Bug fixes

Interface

Selection Toolbar: a value for the previous whole second displayed if the value was close to a whole second.
Finding zero crossings could cause the selection to expand into white space at either side of the clip.
Clips did not drag to another track if mouse was over a selection.
Mixer Board: Rendering four tracks resulted in a redundant Track Strip followed by a crash.

Imports, Exports and Files

Exporting to WAV or AIFF led to a "Libsndfile says" error or corrupted output due to order of metadata in imported files.
(Mac) Fixed crashes importing MP3 files on PPC machines.
(Linux Ubuntu) .Aup files could not be associated with Audacity (they opened in the web browser instead).

Effects and Analysis

Normalize: Fixed issues where normalization could be to wrong value if applied with DC offset correction, or if applied to "read-directly" WAV and AIFF files before On-Demand completed.
Sliding Time Scale: fixed an audible discontinuity at the beginning of the processed selection; fixed a serious quality problem on Linux 64-bit.

Other miscellaneous bug fixes

Including fix to prevent zooming with mouse wheel or ball scrolling the content off-screen.

Changes and Improvements

Shortcuts can now be added in Keyboard Preferences to items in the Generate, Effect or Analyze menus, including user-added plug-ins.
Nyquist Effect plug-ins can now be added to Chains.
New "Paulstretch" effect for extreme slowdown without pitch change.
New "Sample Data Export" Analyze effect for exporting a file containing amplitude values for each sample in the selection.

Known Issues at Release

Headline issues

Large Projects

Problems reopening, saving or crashing in projects

When attempting to reopen the project normally:
- The .aup project file was not saved (or incompletely saved, giving a "line number" error).
- Audio that was there previously is silenced.

To avoid any problems, export a WAV or AIFF file from your project before closing it, then you can import the WAV again if the project becomes damaged.

When working in the project:
- Errors occur when saving the project or when Audacity autosaves, perhaps wrongly suggesting the disk is full or not writable (if this happens, try exporting the audio as WAV).
- Unwanted renaming or moving of .au files within the project.

As many as possible of the following will help us enormously if you can attach them to your report:

A copy of the saved .aup project file
A copy of the "autosave" (temporary project) file. The "autosave" file is stored inside the "AutoSave" folder in Audacity's

Accessibility

Many, but not all parts of the Audacity interface are accessible on Windows to those who can't use a mouse, and/or use a screen reader. It may be possible to make more of Audacity accessible in the longer term. For details, see
There are some accessibility bugs in the parts of Audacity that are accessible:
- Toolbar buttons cannot be operated by pressing either ENTER or Space: ENTER incorrectly moves to the next control and Space starts/stops playback. However the buttons can be operated either by using their shortcut keys, or for users of screen readers by using the Jaws cursor or equivalent. Note: it will be necessary to go to the Keyboard Preferences to set a shortcut for the Play-at-speed button.

Chains

(Linux) When configuring effect parameters in "Edit Chains", the "Preview" button is not intended to be functional. Pressing it may cause a crash.

Compiling

(Windows) Compilation with Visual Studio 2010 is not supported or recommended. See the Wiki page for information.
(Windows) LADSPA effects cannot be categorized even when Audacity is compiled with USE_LIBLRDF defined.
(Linux) Audacity does not build if configured --without-ffmpeg.

Effects and Analysis

(Windows 64-bit) There is no HKEY_LOCAL_MACHINE\SOFTWARE\ registry key where Audacity detects VST plug-ins. The HKEY_CURRENT_USER key searched is HKEY_CURRENT_USER\Software\VST\VSTPluginsPath instead of the expected HKEY_CURRENT_USER\SOFTWARE\Wow6432Node\VST .
Cut Preview only plays the upper track of multiple selected or Sync-Locked tracks.
LADSPA Multiband EQ may not be visible in Effect menu (occurs on Windows XP), and crashes soon after opening

Envelopes and Clips

A clip may now be vertically dragged from inside a selection region, but if that region extends over an adjoining clip there may be unexpected behavior:
- one channel of a stereo clip may jump sideways
- a mono clip may fail to horizontal-drag in its new track

Imports and Exports

Files containing PCM audio but misnamed as MP3 cause a freeze or crash if an Extended Import rule is set in Preferences to force import of MP3 files using the MP3 importer.
(Linux) Exports using "M4A (AAC) Files" are very slow irrespective of the AAC encoder FFmpeg is configured to use. Workaround: choose (external program) when exporting, entering an appropriate path and command (for example, /usr/bin/ffmpeg -i - "%f") to run FFmpeg using Audacity's command-line encoder.
(Linux) Files exported using the FFmpeg native AAC encoder included with many system versions of FFmpeg are of very poor quality. This is an issue with the library itself. Workaround: When compiling FFmpeg, configure with the libfaac encoder thus: --disable-encoder=aac --enable-libfaac. Note that libfaac has an issue not present in the native FFmpeg encoder that saved files are short at the end by about 3000 samples.

Installation

(OS X 10.6 or later) Administrative (and occasionally, root) permissions may be needed on some machines to read the optional LAME and FFmpeg libraries at /usr/local/lib/audacity. In case of difficulty, please download the zip versions "Lame Library v3.98.2 for Audacity on OSX.zip" and "FFmpeg v0.6.2 for Audacity on OSX.zip" from the and extract the files to your own preferred location.

Interface

Selections locked to/only possible to click at whole seconds: We know that it is easy to check the "Snap To" box in by mistake, which means you can't then select less than a whole second or click other than at a whole second. We will look for a solution that keeps Snap To discoverable but makes it harder to enable by accident.
(Linux) On Linux systems using wxGTK 2.8.12 without Unity, closing Preferences will lead to loss of the Audacity Menu Bar (only "Fi" from "Files" will be visible). On Ubuntu using the Unity shell, a small black square will appear, but the Audacity menu in the Global Menu is unaffected. Workaround: Resize (or maximize/unmaximize) the Audacity window after closing Preferences. Solution: This is a wxGTK bug, as reported here () and fixed in changeset 67929 (). To resolve this problem, wxGTK 2.8.12 needs to be patched on the target system, ideally by updating the distribution package. This fix will be included in wxGTK 2.8.13

(Linux) If the warning for importing uncompressed audio files appears before importing a WAV or AIFF, the Play/Stop shortcut may not play the file after import. Workaround: Click the Play button, or click in the waveform or background before using the Play/Stop shortcut. Alternatively, disable the warning in Warnings Preferences.
(OS X) Set Rate > Other... in the Track Dropdown Menu does not display the current track rate unless that rate is in the list of set rates.
(Windows) It is not yet possible to drag .lnk shortcuts to audio files or projects into Audacity, or to drag them to the Audacity executable's icon. Workaround: Use File > Open or File > Import > Audio, or double-click the shortcut to the .aup from Windows Explorer.

Keyboard Shortcuts

(Windows) SHIFT + A (Play/Stop and Set Cursor) and custom unmodified shortcuts for playback or recording write a label at the cursor position if the label track has the yellow focus border. Workaround: use up or down arrow to move focus out of the label track before using the shortcut.
Shortcuts for Generators, Effects and Analyzers where you have to add your own key binding are not currently exported.

Label Tracks

(Linux) In projects containing several hundred labels or more, Audacity will freeze on 100% CPU when opening the "Audacity Karaoke" window, and will freeze again while that window is open when editing a label or performing other actions on the project. Workaround: Open or place an empty label track above the one you want to use.
Typing "j", "J", "k" or"K" in a label track may activate the "move cursor" or "select to/from cursor" shortcut instead. Workaround: click Edit > Preferences: Keyboard, choose the "Edit" category then change the shortcuts for "Move Cursor to Track Start", "Move Cursor to Track End", "Select Track Start to Cursor" and "Select Cursor to Track End" to something else (or clear them).
Unless Tracks > Sync-Lock Tracks is on, pasting or inserting audio does not affect labels even if the label track is included in the selection.

Miscellaneous platform-specific issues

(Linux) If pulseaudio is used as the audio device, repeatedly starting and stopping playback or recording in quick succession (or holding down the Play or Record button) may lead to a freeze. Workaround: bypass pulseaudio by setting the playback and recording device to an ALSA/hw choice in Device Toolbar.
(Mac OS X) If using Audacity when the "Hear" audio plug-in is running (or has been since boot), there will be excessive memory usage which could cause a crash: this appears to be due to buggy memory allocation in "Hear"
(Mac OS X) Very occasionally, users may find that after running Audacity, other media players don't produce any sound, or crash: to resolve this, set up your sound device in Apple Audio MIDI Setup to work in stereo, 16-bit, with a sample rate of 44100 Hz or 48000 Hz, and set the sample format and rate identically in Audacity. More help at:

Mixer Board

Soloing or unsoloing a track in Mixer Board when in "Standard" Solo button mode may not immediately update the Solo button or waveform greyed/ungreyed state in the project window. Workaround: Click anywhere in (or task switch back to) the project window to refresh it (on Mac, you must click in the waveform or Track Control Panel or wait for the tracks to scroll when playing).
If you change the meter range in Preferences this is not reflected in the Mixer Board meters until restart.
(Linux) Meters may not respond immediately to playback which could cause them to report incorrect peak level or not display clipping.

Playback and Recording

(OS X and Linux) Audacity now works very well with , with the following bugs and limitations:
- Clicking in the input meter to start monitoring will crash Audacity if it has not yet used JACK for playback or recording in that session. Workaround: Before recording the first track in a session, click "Pause" then "Record" to enable the recording meter.
- The best way to connect to available JACK inputs and outputs is directly from Device Toolbar. Use Transport > Rescan Audio Devices when necessary, for example to make new JACK applications ports available to Audacity. See here for details.

Preferences

"Retain labels when they define the edge of a selection" in Interface Preferences does not retain the label when deleting a selection that is fully inside that label (touches both its edges).
(Linux) Extended Import: Clicking "Move rule up" when there are no rules or filters causes a crash.

Program Launch

(Linux) If a Bluetooth audio device is in use on a PulseAudio system, Audacity may hang on launch on initial attempts, then after eventual launch Bluetooth will no longer work on the system. Workarounds:
- Remove and reconnect the external Bluetooth adaptor, then launch bluetooth-applet from the command line.
- To prevent Audacity affecting Bluetooth support, move /usr/share/alsa/bluetooth.conf to another location then reboot, or create a symbolic link from /var/lib/alsa/asound.state to /dev/null and reboot.

[AudioUnits] Enable=0 [VST] Enable=0 Rescan=0

If plug-ins were the problem, Audacity should now launch.

Projects

There are currently no message box warnings when projects run out of disk space. If you run out of disk space when editing or recording, patches of silent or corrupted audio will appear, which will also be present if you save and reopen the project. Be aware that every edit on a track takes as much in disk space as if you were recording that track, due to the ability to undo and redo. You can go to View > History and discard Undo levels to free up space.
(OS X) Crash closing project window immediately after saving project: After saving a project, if you close the project window immediately the "Saving project data files" dialog completes, there will be an unexpected "Save changes?" prompt and then a crash when you choose "Yes" or "No". As long as you say "Yes", the project will be saved correctly and can be reopened normally after you restart Audacity. To be sure there is no crash, wait after "Saving project data files" completes for any "Inspecting Project Data" dialog to appear and disappear before closing the project window.

Toolbars

(Windows XP) Transport and Edit Toolbar buttons all display as Pause buttons. The buttons may redraw correctly if you hover over them. Please let us know if solves the issue.

Bugs requiring more investigation

(Windows Vista, 7) When a USB device is connected, the listing of inputs for the built-in sound device in Device Toolbar or Devices Preferences may become corrupt, indicating single inputs as multiple inputs. It may only be possible to record from the built-in input which is currently set as default at "Sound" in the Windows Control Panel, irrespective of the input selected in Audacity. Workaround: Try Transport > Rescan Audio Devices, or a computer reboot.
- Please report make and model number of devices that exhibit the issue, along with description of symptoms and any steps you have noticed that create the issue.
(Windows) There may be substantial delays drawing the waveform in some circumstances. These include fitting longer zoomed-in projects to the window, or when zooming in on fitted projects, also after importing files or running effects.

Audacity 2.0.2

Audacity 2.0.2 was available from 24 August 2012 to 20 January 2013 for Windows, Mac OS X and GNU/Linux. These Release Notes describe:

Changes in 2.0.2 as compared with 2.0.1
The most significant issues with 2.0.2 which were known at time of release

Tip: You can use CTRL + F to search this page for different words to do with the issue you are looking for. Use Command - F on Mac.

Notes for Windows:

Users upgrading to 2.0.x versions from 1.3.6 or earlier must download the of the LAME MP3 encoder.
The Windows installer for 2.0.x versions will replace 1.2.x or any previous 2.0.x installation, but install alongside legacy 1.3.x Beta versions. It is strongly recommended to uninstall previous Beta versions.

Changes between 2.0.1 and 2.0.2

Bug fixes

Interface

"Retain labels" Interface Preference did not retain labels for a region that snapped exactly to both label edges.
Projects did not save the track selected state.
(OS X, Linux) Timer Record: Interlinking of the Start, End and Duration controls was broken.
(Windows) JAWS screen-reader did not read the "Draw curves" and "Graphic EQ" radio buttons in Equalization correctly.

Envelopes and Clips

Exporting (or any render operation) on a track containing split lines could create clicks at the split lines.

Effects and Analysis

Normalize could crash if the track name contained "%".

Changes and Improvements

Duration controls when generating at a point now default to hh:mm:ss + milliseconds format. Selection Toolbar also defaults to that format on first installation or resetting preferences.
Toolbars visual improvements:
- "Snap To" in Selection Toolbar now has an explanatory tooltip

Known Issues at Release

Headline issues

Large Projects

Problems reopening, saving or crashing in projects

When attempting to reopen the project normally:
- The .aup project file was not saved (or incompletely saved, giving a "line number" error).
- Audio that was there previously is silenced.

To avoid any problems, export a WAV or AIFF file from your project before closing it, then you can import the WAV again if the project becomes damaged.

When working in the project:
- Errors occur when saving the project or when Audacity autosaves, perhaps wrongly suggesting the disk is full or not writable (if this happens, try exporting the audio as WAV).
- Unwanted renaming or moving of .au files within the project.

As many as possible of the following will help us enormously if you can attach them to your report:

A copy of the saved .aup project file
A copy of the "autosave" (temporary project) file. The "autosave" file is stored inside the "AutoSave" folder in Audacity's

Accessibility

(Linux) If you TAB into "Snap To" in Selection Toolbar, the selection and focus will become trapped. A mouse click elsewhere will be required to free the focus. Workaround: Access the required part of Selection Toolbar with TAB or SHIFT + TAB so as to avoid Snap To. Snap To can be set on or off by exiting Audacity, show hidden files and folders then add or edit the line "SnapTo=1" or "SnapTo=0" (without quotes, for on or off respectively) in ~/.audacity-data/audacity.cfg.
Many, but not all parts of the Audacity interface are accessible on Windows snd Mac to those who can't use a mouse, and/or use a screen reader. It may be possible to make more of Audacity accessible in the longer term. For details, see
There are some accessibility bugs in the parts of Audacity that are accessible:

Chains

Chains do not currently support export as AIFF, Other uncompressed files or any formats supported by FFmpeg.
You cannot set export format options or export sample rate in the Chain. If you need to specify export options other than the current default, import or generate some audio, File > Export, select the audio type, click "Options..." then choose and save the option and cancel the export.
(Linux) When configuring effect parameters in "Edit Chains", the "Preview" button is not intended to be functional. Pressing it may cause a crash.

Compiling

(Windows) Compilation with Visual Studio 2010 is not supported or recommended. See the Wiki page for information.
(Windows) LADSPA effects cannot be categorized even when Audacity is compiled with USE_LIBLRDF defined.
(Linux) Audacity does not currently compile against very recent FFmpeg (0.10 or later are known to be affected)

Effects and Analysis

(Windows 64-bit) There is no HKEY_LOCAL_MACHINE\SOFTWARE\ registry key where Audacity detects VST plug-ins. The HKEY_CURRENT_USER key searched is HKEY_CURRENT_USER\Software\VST\VSTPluginsPath instead of the expected HKEY_CURRENT_USER\SOFTWARE\Wow6432Node\VST .
Cut Preview only plays the upper track of multiple selected or Sync-Locked tracks.
LADSPA Multiband EQ may not be visible in Effect menu (occurs on Windows XP), and crashes soon after opening

Envelopes and Clips

A clip may now be vertically dragged from inside a selection region, but if that region extends over the edge of the clip into space or into an adjoining clip there may be unexpected behavior:
- one channel of a stereo clip may jump sideways
- a mono clip may fail to horizontal-drag in its new track

Imports and Exports

(Linux) Exports using "M4A (AAC) Files" are very slow irrespective of the AAC encoder FFmpeg is configured to use. Workaround: choose (external program) when exporting, entering an appropriate path and command (for example, /usr/bin/ffmpeg -i - "%f") to run FFmpeg using Audacity's command-line encoder.
(Linux) Files exported using the FFmpeg native AAC encoder included with many system versions of FFmpeg are of very poor quality. This is an issue with the library itself. Workaround: When compiling FFmpeg, configure with the libfaac encoder thus: --disable-encoder=aac --enable-libfaac. Note that libfaac has an issue not present in the native FFmpeg encoder that saved files are short at the end by about 3000 samples.
(Linux) Mono AAC files import as stereo if FFmpeg uses the libfaad decoder. This is again an issue with the library itself.

Installation

(OS X 10.6 or later) Administrative (and occasionally, root) permissions may be needed on some machines to read the optional LAME and FFmpeg libraries at /usr/local/lib/audacity. In case of difficulty, please download the zip versions "Lame Library v3.98.2 for Audacity on OSX.zip" and "FFmpeg v0.6.2 for Audacity on OSX.zip" from the and extract the files to your own preferred location.

Interface

Selections locked to/only possible to click at whole seconds: We know that it is easy to check the "Snap To" box in by mistake, which means you can't then select less than a whole second or click other than at a whole second. We have added a tooltip when you hover over "Snap To" which we hope will help, and will monitor if users are still enabling Snap To in error.
(Linux) If Audacity is configured with the option to use libsamplerate, an action involving resampling outside libsamplerate's limits of 1/256 to 256x will cause the progress dialog to hang, or possibly a crash.
(Linux) The OK button has focus on opening effects and other dialogs, instead of fields for changing values. This is a bug in wxGTK. To change values or settings in the dialog it is necessary to deliver a mouse click.

(Linux) If the warning for importing uncompressed audio files appears before importing a WAV or AIFF, the Play/Stop shortcut may not play the file after import. Workaround: Click the Play button, or click in the waveform or background before using the Play/Stop shortcut. Alternatively, disable the warning in Warnings Preferences.
(OS X) Set Rate > Other... in the Track Dropdown Menu does not display the current track rate unless that rate is in the list of set rates.
(Windows) It is not yet possible to drag .lnk shortcuts to audio files or projects into Audacity, or to drag them to the Audacity executable's icon. Workaround: Use File > Open or File > Import > Audio, or double-click the shortcut to the .aup from Windows Explorer.

Keyboard Shortcuts

(Windows) SHIFT + A (Play/Stop and Set Cursor) and custom unmodified shortcuts for playback or recording write a label at the cursor position if the label track has the yellow focus border. Workaround: use up or down arrow to move focus out of the label track before using the shortcut.
Shortcuts for Generators, Effects and Analyzers where you have to add your own key binding are not currently exported.

Label Tracks

Typing "j", "J", "k", "K" or other shortcuts in a label track may activate the shortcut instead of typing in the label. Workaround: In many cases, Edit > Undo then Edit > Redo will allow you to type in the label. Otherwise, click Edit > Preferences: Keyboard, choose the correct category, then clear the affected shortcuts or change them to include a CTRL + SHIFT modifier or other modifier than SHIFT.
(Linux) In projects containing several hundred labels or more, Audacity will freeze on 100% CPU when opening the "Audacity Karaoke" window, and will freeze again while that window is open when editing a label or performing other actions on the project. Workaround: Open or place an empty label track above the one you want to use.
Unless Tracks > Sync-Lock Tracks is on, pasting or inserting audio does not affect labels even if the label track is included in the selection.

Miscellaneous platform-specific issues

(Linux) If pulseaudio is used as the audio device, repeatedly starting and stopping playback or recording in quick succession (or holding down the Play or Record button) may lead to a freeze. Workaround: bypass pulseaudio by setting the playback and recording device to an ALSA/hw choice in Device Toolbar.
(Mac OS X) If using Audacity when the "Hear" audio plug-in is running (or has been since boot), there will be excessive memory usage which could cause a crash: this appears to be due to buggy memory allocation in "Hear"
(Mac OS X) Very occasionally, users may find that after running Audacity, other media players don't produce any sound, or crash: to resolve this, set up your sound device in Apple Audio MIDI Setup to work in stereo, 16-bit, with a sample rate of 44100 Hz or 48000 Hz, and set the sample format and rate identically in Audacity. More help at:

Mixer Board

Soloing or unsoloing a track in Mixer Board when in "Standard" Solo button mode may not immediately update the Solo button or waveform greyed/ungreyed state in the project window. Workaround: Click anywhere in (or task switch back to) the project window to refresh it (on Mac, you must click in the waveform or Track Control Panel or wait for the tracks to scroll when playing).
If you change the meter range in Preferences this is not reflected in the Mixer Board meters until restart.
(Linux) Meters may not respond immediately to playback which could cause them to report incorrect peak level or not display clipping.

Playback and Recording

(OS X and Linux) Audacity now works very well with , with the following bugs and limitations:
- Clicking in the input meter to start monitoring will crash Audacity if it has not yet used JACK for playback or recording in that session. Workaround: Before recording the first track in a session, click "Pause" then "Record" to enable the recording meter.
- The best way to connect to available JACK inputs and outputs is directly from Device Toolbar. Use Transport > Rescan Audio Devices when necessary, for example to make new JACK applications ports available to Audacity. See here for details.

Preferences

(Linux) Extended Import: Clicking "Move rule up" when there are no rules or filters causes a crash.
(Linux) On Linux systems using wxGTK 2.8.12 without Unity, closing Preferences will lead to loss of the Audacity Menu Bar (only "Fi" from "Files" will be visible). On Ubuntu using the Unity shell, a small black square will appear, but the Audacity menu in the Global Menu is unaffected. Workaround: Resize (or maximize/unmaximize) the Audacity window after closing Preferences. Solution: This is a wxGTK bug, as reported here () and fixed in changeset 67929 (). To resolve this problem, wxGTK 2.8.12 needs to be patched on the target system, ideally by updating the distribution package. This fix will be included in wxGTK 2.8.13.

Program Launch

(Linux) If a Bluetooth audio device is in use on a PulseAudio system, Audacity may hang on launch on initial attempts, then after eventual launch Bluetooth will no longer work on the system. Workarounds:
- Remove and reconnect the external Bluetooth adaptor, then launch bluetooth-applet from the command line.
- To prevent Audacity affecting Bluetooth support, move /usr/share/alsa/bluetooth.conf to another location then reboot, or create a symbolic link from /var/lib/alsa/asound.state to /dev/null and reboot.

In a future version of Audacity we aim to defer loading of plug-ins until they are requested in the Effect menu. Workaround: If VST/AudioUnit effects are not needed in Audacity, force quit Audacity, then open Audacity's . Open audacity.cfg (or create it if it does not exist) then add or edit the following lines:

[AudioUnits] Enable=0 [VST] Enable=0 Rescan=0

If plug-ins were the problem, Audacity should now launch.

Projects

There are currently no message box warnings when projects run out of disk space. If you run out of disk space when editing or recording, patches of silent or corrupted audio will appear, which will also be present if you save and reopen the project. Be aware that every edit on a track takes as much in disk space as if you were recording that track, due to the ability to undo and redo. You can go to View > History and discard Undo levels to free up space.
(OS X) Crash closing project window immediately after saving project: After saving a project, if you close the project window immediately the "Saving project data files" dialog completes, there will be an unexpected "Save changes?" prompt and then a crash when you choose "Yes" or "No". As long as you say "Yes", the project will be saved correctly and can be reopened normally after you restart Audacity. To be sure there is no crash, wait after "Saving project data files" completes for any "Inspecting Project Data" dialog to appear and disappear before closing the project window.

Toolbars

Meter Toolbar vertical orientation is not remembered across sessions, and resizing the meters reverts from vertical to horizontal.
(Windows XP) Transport and Tools Toolbar buttons all display as Pause buttons. The buttons may redraw correctly if you hover over them. Workaround: You can use for the buttons instead.

Bugs requiring more investigation

(Windows Vista, 7) When a USB device is connected, the listing of inputs for the built-in sound device in Device Toolbar or Devices Preferences may become corrupt, indicating single inputs as multiple inputs. It may only be possible to record from the built-in input which is currently set as default at "Sound" in the Windows Control Panel, irrespective of the input selected in Audacity. Workaround: Try Transport > Rescan Audio Devices, or a computer reboot.
- Please report make and model number of devices that exhibit the issue, along with description of symptoms and any steps you have noticed that create the issue.
(Windows) There may be substantial delays drawing the waveform in longer projects. These include:

Lower rated issues

Only issues deemed of sufficient impact and importance to release-note are listed on this page. You can search the complete list of bugs on Audacity Bugzilla or for particular categories of bugs thereon by visiting Bug Lists.

Audacity 2.0.3

Audacity 2.0.3 was available from 21 January 2013 until 05 September 2013 for Windows, Mac OS X and GNU/Linux. These Release Notes describe:

Changes in 2.0.3 as compared with 2.0.2
The most significant issues with 2.0.3 which were known at time of release.

Related article(s):

Known Issues for problems with 2.0.3 that have been reported since its release date.
Release Notes 2.0.2
Release Notes 2.0.1

Tip: You can use CTRL + F to search this page for different words to do with the issue you are looking for. Use Command - F on Mac.

Notes for Windows:

Users upgrading to 2.0.x versions from 1.3.6 or earlier must download the of the LAME MP3 encoder.
The Windows installer for 2.0.x versions will replace 1.2.x or any previous 2.0.x installation, but install alongside legacy 1.3.x Beta versions. It is strongly recommended to uninstall previous Beta versions.

Changes between 2.0.2 and 2.0.3

Bug fixes

General

Crash using Undo whilst time-shifting a track.
Crash using Repair if the selection extended into an empty track.
Export Multiple didn't prevent export if there was no audio or all audio was muted. This allowed export of small invalid files.

Time Track

Loop Play of a speeded-up track inserted silence.
Playback and rendering was significantly inaccurate, creating audible and visual glitches.

Accessibility

The mnemonics character "&" was read out by screen readers in most of the Preferences choices.
NVDA did not read static text in most dialogs. Text can now be read by using INSERT + B.
JAWS and Window-eyes misread the "Duration" control in Silence Generator.
Toolbar buttons could not be pressed by ENTER

Changes and Improvements

Resampling

The SoX Resampler library (libsoxr) has replaced libresample in Audacity releases, offering both higher quality and greater speed. .

Time Tracks new features

"Set Range" now changes only the range of the Time Track, preserving the pitch/speed set by any existing warp points.
Vertical scale added with options for linear and logarithmic display and interpolation.
Upper and lower speed limits will now be remembered when saving and reopening a project in 2.0.3. Warp points in projects saved by previous Audacity versions will be correctly restored in 2.0.3.

New effects

Studio Fade Out (uses a filtered "S" curve).
Adjustable Fade (accessible effect for creating partial fades and adjustable fade shapes).
Bass and Treble (replaces Bass Boost).

General

Real sample rates up to 384000 Hz are now supported for playback and recording in high resolution devices (the maximum is up to 192000 Hz for Windows DirectSound host).
Labeled Regions in Edit Menu is renamed to "Labeled Audio" and now allows splits to be placed at point labels. Labeled audio regions that touch without overlapping are treated as separate regions. Overlapping labeled audio regions are treated as a single region.
New Croatian translation of Audacity.

Compilation

CMake is required in order to build libsoxr.

Known Issues at Release

Headline issues

Large Projects

Problems reopening, saving or crashing in projects

When attempting to reopen the project normally:
- The .aup project file was not saved (or incompletely saved, giving a "line number" error).
- Audio that was there previously is silenced.

To avoid any problems, export a WAV or AIFF file from your project before closing it, then you can import the WAV again if the project becomes damaged.

When working in the project:
- Errors occur when saving the project or when Audacity autosaves, perhaps wrongly suggesting the disk is full or not writable (if this happens, try exporting the audio as WAV).
- Unwanted renaming or moving of .au files within the project.

As many as possible of the following will help us enormously if you can attach them to your report:

A copy of the saved .aup project file
A copy of the "autosave" (temporary project) file. The "autosave" file is stored inside the "AutoSave" folder in Audacity's

Accessibility

(Linux) If you TAB into "Snap To" in Selection Toolbar, the selection and focus will become trapped. A mouse click elsewhere will be required to free the focus. Workaround: Access the required part of Selection Toolbar with TAB or SHIFT + TAB so as to avoid Snap To. Snap To can be set on or off by exiting Audacity, show hidden files and folders then add or edit the line "SnapTo=1" or "SnapTo=0" (without quotes, for on or off respectively) in ~/.audacity-data/audacity.cfg.
Many, but not all parts of the Audacity interface are accessible on Windows and Mac to those who can't use a mouse, and/or use a screen reader. It may be possible to make more of Audacity accessible in the longer term. For details, see
There are some accessibility bugs in the parts of Audacity that are accessible:

Chains

Chains do not currently support export as AIFF, Other uncompressed files or any formats supported by FFmpeg.
You cannot set export format options or export sample rate in the Chain. If you need to specify export options other than the current default, import or generate some audio, File > Export, select the audio type, click "Options..." then choose and save the option and cancel the export.
(Linux) When configuring effect parameters in "Edit Chains", the "Preview" button is not intended to be functional. Pressing it may cause a crash.

Compiling

(Linux) New libsoxr resampling library: Default ./configure will enable a new library for resampling and disable libresample and libsamplerate (the previous resampling libraries). is required to build libsoxr. We strongly recommend libsoxr for its combination of high quality and high speed.
- Only one resampling library is permitted. If you enable either libresample or libsamplerate in configure, libsoxr will not be enabled. Any configure of resampling libraries other than libsoxr only will enable one only of libresample, libsamplerate or libsoxr in that order of precedence; however the intermediate configure output may suggest that other libraries will be favored.

Effects and Analysis

LADSPA generate plug-ins may fail to generate into an empty track or into white space separating audio clips. Workaround: Before using the LADSPA generator, generate audio using any of the Audacity Generators above the divider in the Generate Menu, then generate into that audio selection.
Truncate Silence may not truncate a silence that appears from Selection Toolbar to be the same as the specified "min silence duration". Sometimes the length displayed in Selection Toolbar is not exactly the same as the actual selection, due to the sampling of the audio. It won't be off by more than a sample though, which is a very tiny error.
(Windows 64-bit) There is no HKEY_LOCAL_MACHINE\SOFTWARE\ registry key where Audacity detects VST plug-ins. The HKEY_CURRENT_USER key searched is HKEY_CURRENT_USER\Software\VST\VSTPluginsPath instead of the expected HKEY_CURRENT_USER\SOFTWARE\Wow6432Node\VST .

Envelopes and Clips

A clip may now be vertically dragged from inside a selection region, but if that region extends over the edge of the clip into space or into an adjoining clip there may be unexpected behavior:
- one channel of a stereo clip may jump sideways
- a mono clip may fail to horizontal-drag in its new track

Imports and Exports

Files containing PCM audio but misnamed as MP3 cause a freeze or crash if an Extended Import rule is set in Preferences to force import of MP3 files using the MP3 importer.
(Linux) After opening a sufficiently long audio file, opening a second file of any size leads to locked GUI/console messages until first file completes play.
(Linux) Custom FFmpeg Export dialog does not respond to ENTER after clicking in the Formats or Codec selector.

Installation

(OS X 10.6 or later) Administrative (and occasionally, root) permissions may be needed on some machines to read the optional LAME and FFmpeg libraries at /usr/local/lib/audacity. In case of difficulty, please download the zip versions "Lame Library v3.98.2 for Audacity on OSX.zip" and "FFmpeg v0.6.2 for Audacity on OSX.zip" from the and extract the files to your own preferred location.
(Linux) When self-compiling Audacity, LICENSE.txt and README.txt are installed into the root of the documentation directory instead of the $(AUDACITY_NAME) directory inside that.

Interface

Selections locked to/only possible to click at whole seconds: We know that it is easy to check the "Snap To" box in by mistake, which means you can't then select less than a whole second or click other than at a whole second. We have added a tooltip when you hover over "Snap To" which we hope will help, and will monitor if users are still enabling Snap To in error.
(Linux) If Audacity is configured with the option to use libsamplerate, an action involving resampling outside libsamplerate's limits of 1/256 to 256x will cause the progress dialog to hang, or possibly a crash.
(Linux) The OK button has focus on opening effects and other dialogs, instead of fields for changing values. This is a bug in wxGTK. To change values or settings in the dialog it is necessary to deliver a mouse click.

(Linux) If the warning for importing uncompressed audio files appears before importing a WAV or AIFF, the Play/Stop shortcut may not play the file after import. Workaround: Click the Play button, or click in the waveform or background before using the Play/Stop shortcut. Alternatively, disable the warning in Warnings Preferences.
(OS X) Set Rate > Other... in the Track Dropdown Menu does not display the current track rate unless that rate is in the list of set rates.
(Windows) It is not yet possible to drag .lnk shortcuts to audio files or projects into Audacity, or to drag them to the Audacity executable's icon. Workaround: Use File > Open or File > Import > Audio, or double-click the shortcut to the .aup from Windows Explorer.

Keyboard Shortcuts

(Windows) SHIFT + A (Play/Stop and Set Cursor) and custom unmodified shortcuts for playback or recording write a label at the cursor position if the label track has the yellow focus border. Workaround: use up or down arrow to move focus out of the label track before using the shortcut.
Shortcuts for Generators, Effects and Analyzers where you have to add your own key binding are not currently exported into the XML file. Shortcut changes for any commands are not applied after importing the XML file and pressing OK in Preferences.

Label Tracks

Typing "j", "J", "k", "K" or other shortcuts in a label track may activate the shortcut instead of typing in the label. Workaround: In many cases, Edit > Undo then Edit > Redo will allow you to type in the label. Otherwise, click Edit > Preferences: Keyboard, choose the correct category, then clear the affected shortcuts or change them to include a CTRL + SHIFT modifier or other modifier than SHIFT.
(Linux) In projects containing several hundred labels or more, Audacity will freeze on 100% CPU when opening the "Audacity Karaoke" window, and will freeze again while that window is open when editing a label or performing other actions on the project. Workaround: Open or place an empty label track above the one you want to use.
Unless Tracks > Sync-Lock Tracks is on, pasting or inserting audio does not affect labels even if the label track is included in the selection.

Miscellaneous platform-specific issues

(Linux) If pulseaudio is used as the audio device, repeatedly starting and stopping playback or recording in quick succession (or holding down the Play or Record button) may lead to a freeze. Workaround: bypass pulseaudio by setting the playback and recording device to an ALSA/hw choice in Device Toolbar.
(Mac OS X) If using Audacity when the "Hear" audio plug-in is running (or has been since boot), there will be excessive memory usage which could cause a crash: this appears to be due to buggy memory allocation in "Hear"
(Mac OS X) Very occasionally, users may find that after running Audacity, other media players don't produce any sound, or crash: to resolve this, set up your sound device in Apple Audio MIDI Setup to work in stereo, 16-bit, with a sample rate of 44100 Hz or 48000 Hz, and set the sample format and rate identically in Audacity. More help at:

Mixer Board

Soloing or unsoloing a track in Mixer Board when in "Standard" Solo button mode may not immediately update the Solo button or waveform greyed/ungreyed state in the project window. Workaround: Click anywhere in (or task switch back to) the project window to refresh it (on Mac, you must click in the waveform or Track Control Panel or wait for the tracks to scroll when playing).
If you change the meter range in Preferences this is not reflected in the Mixer Board meters until restart.
(Linux) Meters may not respond immediately to playback which could cause them to report incorrect peak level or not display clipping.

Playback and Recording

(Windows) When you install Audacity for the first time or launch it after resetting Preferences, Audacity will choose a specific output and input device rather than the Sound Mapper devices that are the current Windows default devices. Workaround: If you lose playback audio or only record silence for this reason, use to change the devices as needed, then Audacity will remember them.
The Transport menu lacks Audacity's two combined "Play/Stop" commands, but these have shortcuts which can be used instead.
- "Play/Stop": Use SPACE. This starts or stops playback, returning the cursor to the start position when stopped.

Preferences

(Linux) Extended Import: Clicking "Move rule up" when there are no rules or filters causes a crash.

Program Launch

(Linux) If a Bluetooth audio device is in use on a PulseAudio system, Audacity may hang on launch on initial attempts, then after eventual launch Bluetooth will no longer work on the system. Workarounds:
- Remove and reconnect the external Bluetooth adaptor, then launch bluetooth-applet from the command line.
- To prevent Audacity affecting Bluetooth support, move /usr/share/alsa/bluetooth.conf to another location then reboot, or create a symbolic link from /var/lib/alsa/asound.state to /dev/null and reboot.

In a future version of Audacity we aim to defer loading of plug-ins until they are requested in the Effect menu. Workaround: If VST/AudioUnit effects are not needed in Audacity, force quit Audacity, then open Audacity's . Open audacity.cfg in a text editor (or create audacity.cfg if it does not exist) then in the editor, make the audacity.cfg content to be only the following:

NewPrefsInitialized=1 [AudioUnits] Enable=0 [VST] Enable=0 Rescan=0

If plug-ins were the problem, Audacity should now launch.

(Windows) A dialog which is scanning for VST plug-ins will be seen on every launch of Audacity even when no VST plug-ins are present, if other DLL files are present in the Audacity Plug-Ins folder. Workaround: If VST effects are not required, choose Edit > Preferences, then under "Enable Effects", uncheck "VST", OK.

Projects

There are currently no message box warnings when projects run out of disk space. If you run out of disk space when editing or recording, patches of silent or corrupted audio will appear, which will also be present if you save and reopen the project. Be aware that every edit on a track takes as much in disk space as if you were recording that track, due to the ability to undo and redo. You can go to View > History and discard Undo levels to free up space.
(OS X) Crash closing project window immediately after saving project: After saving a project, if you close the project window immediately the "Saving project data files" dialog completes, there will be an unexpected "Save changes?" prompt and then a crash when you choose "Yes" or "No". As long as you say "Yes", the project will be saved correctly and can be reopened normally after you restart Audacity. To be sure there is no crash, wait after "Saving project data files" completes for any "Inspecting Project Data" dialog to appear and disappear before closing the project window.

Time Tracks

The lower and upper speed limits are not stored in the project, so will be restored to their default values of 90 and 110 respectively when reopening or recovering a project, or if removing a Time Track then undoing removal. Please make a note of the correct values before closing the project or the Time Track.

Toolbars

(OS X and Linux) Using keyboard Undo while dragging envelope points or sample points will crash Audacity (this affects Envelope Tool, Draw Tool and Multi-Tool).
Meter Toolbar vertical orientation is not remembered across sessions, and resizing the meters reverts from vertical to horizontal.
(Windows XP) Transport and Tools Toolbar buttons all display as Pause buttons. The buttons may redraw correctly if you hover over them. Workaround: You can use for the buttons instead.

Bugs requiring more investigation

(Linux) If Audacity is compiled with the option to use libsamplerate and the default "Best Sinc Interpolator" for high-quality conversion is used, Tracks > Resample may lead to truncation of the waveform. Workaround: change the project rate to the desired rate, export the track and re-import it.
(OS X and Linux) After using Tracks > Mix and Render or File > Save Project, some keyboard shortcuts such as Play/Stop or opening a new project window have no effect.
(Windows Vista) If you change the input volume in Audacity and then record, the volume is reset to its original level. This appears to occur mostly with a few specific USB devices, and sometimes only on Vista SP1, so it is currently hard for us to fix. Workaround: Check if the manufacturer supplies their own drivers for the device and try those. See if upgrading to Vista SP2 or Windows 7 helps.

Lower rated issues

(OS X) Audacity can crash when importing files that have Unicode names or folder paths, or when manipulating any files or folders in Finder that have Unicode names or paths then importing any audio files into Audacity. Workaround: Not working with Unicode names or folder paths is the best solution. Otherwise, reboot the computer until the problem stops happening. There is some evidence that importing into a project window that already contains audio may reduce the tendency to crash.
Dither (corrective soft noise) is applied by default when it should not be applied when exporting to most formats having the same or higher bit depth than the project. For example, this occurs if exporting to 16-bit WAV, 16-bit FLAC or MP3 from a 16-bit project. OGG is unaffected. Workarounds: Set "High Quality" dither to "None" in the Quality Preferences. To fix any files that have already been affected, see this Forum topic.
"Shaped dither" (the default type ) is more audible than intended when exporting a stereo file unless exporting to FLAC (or to OGG which does not apply dither). Workaround: Dither is recommended if you export from a 32-bit or 24-bit project to a 16-bit file. You can set dither to "None" in the "High-quality Conversion" section of ., but it is recommended instead to choose "Triangle" dither which will be less audible than the current "Shaped" dither.
Exports using Audacity's default "shaped" dither may be corrupted with near-silent audio flatlined at -1 if the project contains invalid data (such as a click at an excessive level). All further exports in that Audacity session will then be corrupted (even from different, valid data). Workaround: Go to the Quality Preferences and change "Dither" under "High-quality Conversion" to "Rectangle" or "Triangle" dither, or to "None".
Files containing PCM audio but misnamed as MP3 cause a freeze or crash if an Extended Import rule is set in Preferences to force import of MP3 files using the MP3 importer.
ID3 metadata tags in imported MP3 or MP2 files may display incorrectly if the metadata is UTF-16 encoded. The tags will seem to have Chinese characters and these incorrect tags will also be present if the files are re-exported. Workaround: Before importing the file into Audacity, open it in a tag editor or an audio application that can edit tags. If the tags are seen correctly, save the file in that application. On Windows you can use for this purpose.
Audacity may freeze if using the Nero AAC encoder to export via (external program). It is reported this only occurs when using multiple CPU cores. Workaround: Export to AAC directly by adding to your computer, or set Audacity to use only one CPU core.
Custom FFmpeg Export: many combinations of formats and codecs are incompatible, as are some combinations of general options and codecs. Some files may be exported as zero kb files.
WAVEX (Microsoft) headers: GSM 6.10 files cannot be exported, and U-Law/A-Law files may not be playable.
WMA: no metadata is exported if using the older FFmpeg 0.5 library due to a bug in FFmpeg. Metadata is supported in FFmpeg 0.6 but applications other than Audacity may not see all the tags.
(Linux) After opening a sufficiently long audio file, opening a second file of any size leads to locked GUI/console messages until first file completes play.
(Linux) Custom FFmpeg Export dialog does not respond to ENTER after clicking in the Formats or Codec selector.
(Linux) Exports using "M4A (AAC) Files" are very slow irrespective of the AAC encoder FFmpeg is configured to use. Workaround: choose (external program) when exporting, entering an appropriate path and command (for example, /usr/bin/ffmpeg -i - "%f") to run FFmpeg using Audacity's command-line encoder.
(Linux) Files exported using the FFmpeg native AAC encoder included with many system versions of FFmpeg are of very poor quality. This is an issue with the library itself. Workaround: When compiling FFmpeg, configure with the libfaac encoder thus: --disable-encoder=aac --enable-libfaac. Note that libfaac has an issue not present in the native FFmpeg encoder that saved files are short at the end by about 3000 samples.
(Linux) Mono AAC files import as stereo if FFmpeg uses the libfaad decoder. This is again an issue with the library itself.
(OS X and Linux) Entering a backslash "\" in a file name when saving a project gives a "Could not save project. Path not found." error.
(OS X and Linux) When using Export Multiple, asterisks (*) or question marks (?) in labels are wrongly rejected as illegal characters, and forward slashes (/) cause a false "cannot export audio" warning. Workaround: To force use of * or ? (and / on OS X), export each region with File > Export Selection instead (/ is illegal in a file or folder name on Linux).
(OS X) Files imported from iTunes could create invalid characters in the .aup project file in previous Beta versions of Audacity. If you re-open such a project in the current release, an error "reference to invalid character number" may occur. Workaround: Save and open a back-up copy of the .aup file in a text editor, turn off word wrap, then in the line indicated in the error message, remove the string of characters that starts with &# and ends with a semi-colon (;). There is more help with fixing this .
(Windows Vista, 7) Audacity will crash if attempting to open WAV files while they are still being rendered by the open source Psycle tracker program.
If WAV/AIFF files are imported into a project using "Read Directly" import but then become unavailable, warnings are given when playing, recording, applying effects and exporting, but not all editing and project save actions are warned.
If you import an audio file from a folder other than the one you last exported to, you cannot export over that file without changing the export directory manually.
Metadata:
- Album art and lyrics in imported metadata are lost when exporting.
- Tags other than the seven default tags will be rewritten as custom TXXX tags, which will cause them not to be seen in applications like Windows Media Player and iTunes. Common tag examples include "Album Artist", "BPM" and "Composer".
"Background on-demand loading" for FFmpeg (in the Libraries Preferences) does not currently allow changing the focus of waveform computation by clicking in the track. You can apply an effect to a selection wherever the normal waveform has appeared, but if you do so before the normal waveform has appeared, the audio will be silenced.
By default, the importer used depends on the import method. For example, to be able to use to import native Audacity formats like WAV and MP3, you must choose the "FFmpeg-compatible files" filter in File > Open or File > Import > Audio and always use one of those import methods. To force FFmpeg to import native Audacity formats when using File > Recent Files or dragging in, add rules for those formats in . To force FFmpeg import irrespective of the filter when using File > Open or File > Import > Audio, uncheck "Attempt to use filter in OpenFile dialog first" in Extended Import Preferences as well as adding the rule for the format.
Export Multiple does not pass metadata common to all tracks to the Metadata Editor windows for each track. Workaround: Export by unchecking "Show Metadata Editor before export step" in Import / Export Preferences, then enter any tags common to all tracks at File > Open Metadata Editor... before exporting. Audacity will then silently add the common and automatically generated Track Title and Track Number tags for each exported file.
Import > Raw Data... imports files as noise if the Quality Preferences are set to 24-bit.
WAV and AIFF exports will fail without warning if you import a WAV or AIFF by , delete the file and its track then export new audio to the same file name and location as the deleted file. Workaround: Set the Preference in the above link to "Make a copy" of uncompressed files when importing.
(Linux) AAC exports produce a zero bytes file if the Audacity project rate is below 22050 Hz. Additionally, the "Quality" slider in AAC export Options has no effect on the exported bitrate. "Workaround: Export as WAV and convert to AAC using FFmpeg at the terminal.
On a fresh installation of Audacity or , the optional FFmpeg library cannot be used for import of native Audacity formats such as WAV, AIFF or MP3. Workaround: Open Preferences and click "OK".
When importing a MIDI track, the channel selection buttons to left of the track are not currently available.

(Linux) Exports using "M4A (AAC) Files" are very slow irrespective of the AAC encoder FFmpeg is configured to use. Workaround: choose (external program) when exporting, entering an appropriate path and command (for example, /usr/bin/ffmpeg -i - "%f") to run FFmpeg using Audacity's command-line encoder.
(Linux) Files exported using the FFmpeg native AAC encoder included with many system versions of FFmpeg may be of poor quality. This is an issue with the library itself. Workaround: When compiling FFmpeg, configure with the libfaac encoder thus: --disable-encoder=aac --enable-libfaac --enable-nonfree. Note that libfaac has an issue not present in the native FFmpeg encoder that saved files are short at the end by about 3000 samples. Alternatively build the VisualOn AAC encoder library and configure FFmpeg with --disable-encoder=aac --disable-encoder=libfaac --enable-libvo-aacenc.
(Linux) Mono AAC files import as stereo if FFmpeg uses the libfaad decoder. This is again an issue with the library itself.
Audacity may freeze if using the Nero AAC encoder to export via (external program). It is reported this only occurs when using multiple CPU cores. Workaround: Export to AAC directly by adding to your computer, or set Audacity to use only one CPU core.
WAVEX (Microsoft) headers: GSM 6.10 files cannot be exported, and U-Law/A-Law files may not be playable.
Files containing PCM audio but misnamed as MP3 cause a freeze or crash if an Extended Import rule is set in Preferences to force import of MP3 files using the MP3 importer.
ID3 metadata tags in imported MP3 or MP2 files may display incorrectly if the metadata is UTF-16 encoded. The tags will seem to have Chinese characters and these incorrect tags will also be present if the files are re-exported. Workaround:"' Before importing the file into Audacity, open it in a tag editor or an audio application that can edit tags. If the tags are seen correctly, save the file in that application. On Windows you can use for this purpose.
(Linux) After opening a sufficiently long audio file, opening a second file of any size leads to locked GUI/console messages until first file completes play.
(Linux) Custom FFmpeg Export dialog does not respond to ENTER after clicking in the Formats or Codec selector.
(Mac OS X) Dragging audio files to Audacity's icon in the Dock will only import the file for WAV, AIFF, AU, MP2, MP3, OGG, FLAC and M4A. Workaround: Rename MP4 files (audio or video) to M4A extension. Alternatively the files may be dragged to the Audacity icon in the folder where you have Audacity installed, dragged into the open Audacity window or imported using the Audacity menus.
(Mac OS X) Exporting using (external program) will crash using the built-in commands or if the absolute path is entered incorrectly or its accompanying command syntax is incorrect. See for how to browse to the correct path and enter the correct syntax.
(OS X and Linux) When using Export Multiple, asterisks (*) or question marks (?) in labels are wrongly rejected as illegal characters, and forward slashes (/) cause a false "cannot export audio" warning. Workaround: To force use of * or ? (and / on OS X), export each region with File > Export Selection instead (/ is illegal in a file or folder name on Linux).
(OS X) Files imported from iTunes could create invalid characters in the .aup project file in previous Beta versions of Audacity. If you re-open such a project in the current release, an error "reference to invalid character number" may occur. Workaround: Save and open a back-up copy of the .aup file in a text editor, turn off word wrap, then in the line indicated in the error message, remove the string of characters that starts with &# and ends with a semi-colon (;). There is more help with fixing this .
(Windows Vista, 7) Audacity will crash if attempting to open WAV files while they are still being rendered by the open source Psycle tracker program.
If WAV/AIFF files are imported into a project using "Read Directly" import but then become unavailable, warnings are given when playing, recording, applying effects and exporting, but not all editing and project save actions are warned.
If you import an audio file from a folder other than the one you last exported to, you cannot export over that file without changing the export directory manually.
Metadata:
- Album art and lyrics in imported metadata are lost when exporting. Workaround: Copy the lyrics (or search for them online) then add them back to the exported file in your favorite media player. Extract the album art using a tag editor such as (or use or iTunes to search online for the art) then add the art back to the exported file using your media player.
- Tags other than the seven default tags will be rewritten as custom ID3 TXXX tags, which will cause them not to be seen in applications like Windows Media Player and iTunes. Common tag examples include "Album Artist", "BPM" and "Composer".
"Background on-demand loading" for FFmpeg (in the Libraries Preferences) does not currently allow changing the focus of waveform computation by clicking in the track. You can apply an effect to a selection wherever the normal waveform has appeared, but if you do so before the normal waveform has appeared, the audio will be silenced.
(Linux): When exporting to MIDI over an existing file, no overwrite warning is given.
By default, the importer used depends on the import method. For example, to be able to use to import native Audacity formats like WAV and MP3, you must choose the "FFmpeg-compatible files" filter in File > Open or File > Import > Audio and always use one of those import methods. To force FFmpeg to import native Audacity formats when using File > Recent Files or dragging in, add rules for those formats in . To force FFmpeg import irrespective of the filter when using File > Open or File > Import > Audio, uncheck "Attempt to use filter in OpenFile dialog first" in Extended Import Preferences as well as adding the rule for the format.
Export Multiple does not pass metadata common to all tracks to the Metadata Editor windows for each track. Workaround: Export by unchecking "Show Metadata Editor before export step" in Import / Export Preferences, then enter any tags common to all tracks at File > Open Metadata Editor... before exporting. Audacity will then silently add the common and automatically generated Track Title and Track Number tags for each exported file.
Import > Raw Data... imports files as noise if the Quality Preferences are set to 24-bit Default Sample Format. Set this to 16-bit or 32-bit float instead.
WAV and AIFF exports will fail without warning if you import a WAV or AIFF by , delete the file and its track then export new audio to the same file name and location as the deleted file. Workaround: Set the Preference in the above link to "Make a copy" of uncompressed files when importing.
(OS X) Audio files containing a backslash (\) in the name will fail "Could not open file" if you import them using File > Open... , File > Import > Audio... or File > Open Recent. This is a bug in wxWidgets. Workaround: Drag the file into the Audacity window instead.
Dither (corrective soft noise) is applied by default when it should not be applied when exporting to most formats having the same or higher bit depth than the project. For example, this occurs if exporting to 16-bit WAV, 16-bit FLAC or MP3 from a 16-bit project. OGG is unaffected. Workarounds: Set "High Quality" dither to "None" in the . To fix any files that have already been affected, see .
On a fresh installation of Audacity or , the optional FFmpeg library cannot be used for import of native Audacity formats such as WAV, AIFF or MP3. Workaround: Open Preferences and click "OK".
When importing a MIDI track, the channel selection buttons to left of the track are not currently available.

Audacity 2.0.5

Audacity 2.0.5 was available from 21 October 2013 until 28 September 2014. These Release Notes describe:

Changes in this version relative to previous.
The most significant issues with this version known at time of release.

Tip: You can use CTRL + F to search this page for different words to do with the issue you are looking for. Use Command - F on Mac.

Notes for Windows:

The Windows installer for 2.0.x versions will replace 1.2.x or any previous 2.0.x installation, but install alongside legacy 1.3.x Beta versions. It is strongly recommended to uninstall previous Beta versions.
The language choice in the Windows EXE Audacity installer only selects the language for the installer. The language Audacity runs in is determined by the "Format" for date and time in the "Region and Language" section of the Windows Control Panel. To change the Audacity language, please see these .

Changes Since Previous Version

Bug fixes

Shaped dither was corrupted and too loud on all stereo exports except FLAC.
Keyboard Preferences: some Edit and Align commands for different sub-menus showed the same name.
Recordings stopped with "Stop and Set Cursor" shortcut could not be undone.
In locales that use comma for decimal separator:

Changes and Improvements

Tracks Menu:
The separate commands that aligned track start or end with the cursor or with selection start are combined into "Cursor/Selection Start" commands.
"Align and Move Cursor" renamed to "Move Selection when Aligning".
Label Tracks:

Known Issues at Release

Headline issues

Large Projects

Projects with 2^31 samples or more (just over 13.5 hours at 44100 Hz) will not re-open correctly. Higher sample rates mean proportionally shorter times - so just over 6 hours at 96,000 Hz. We know the cause, and do intend to address this bug. Workaround: Before saving or closing the project, export to audio files of appropriate size, or cut and paste sections of audio containing less than 2^31 samples to new Audacity projects and save those.

Problems reopening, saving or crashing in projects

When attempting to reopen the project normally:
- The .aup project file was not saved (or incompletely saved, giving a "line number" error).
- Audio that was there previously is silenced.

To avoid any problems, export a WAV or AIFF file from your project before closing it, then you can import the WAV again if the project becomes damaged.

When working in the project:
- Errors occur when saving the project or when Audacity autosaves, perhaps wrongly suggesting the disk is full or not writable (if this happens, try exporting the audio as WAV).
- Unwanted renaming or moving of .au files within the project.

As many as possible of the following will help us enormously if you can attach them to your report:

A copy of the saved .aup project file
A copy of the "autosave" (temporary project) file. The "autosave" file is stored inside the "AutoSave" folder in Audacity's .

Preferred behaviours - please vote

Snap-To in Selection Toolbar causes clicks to snap to the nearest unit. So, clicking in-between a CDDA or other frame may jump to the next or previous frame, depending where you click. We know some users of frames require to always snap to the previous frame. We'd like to hear your views on which behaviour is best. Please let us know at our .

Accessibility

Many, but not all parts of the Audacity interface are accessible on Windows and Mac to those who can't use a mouse, and/or use a screen reader. It may be possible to make more of Audacity accessible in the longer term. For details, see
There are some accessibility bugs in the parts of Audacity that are accessible:
- In projects having more than one track, using ENTER to change which track is selected, applying an edit then undoing it will change the track focus or selectedness. Workaround: Change track selectedness with the mouse if possible, or modify the selected range with keyboard or mouse after changing the track selectedness.

Chains

Chains do not currently support export as AIFF, Other uncompressed files or any formats supported by FFmpeg.
You cannot set export format options or export sample rate in the Chain. If you need to specify export options other than the current default, import or generate some audio, File > Export, select the audio type, click "Options..." then choose and save the option and cancel the export.

Compiling

(Linux) New libsoxr resampling library: Default ./configure will enable a new library for resampling and disable libresample and libsamplerate (the previous resampling libraries). is required to build libsoxr. We strongly recommend libsoxr for its combination of high quality and high speed.
- Only one resampling library is permitted. If you enable either libresample or libsamplerate in configure, libsoxr will not be enabled. Any configure of resampling libraries other than libsoxr only will enable one only of libresample, libsamplerate or libsoxr in that order of precedence; however the intermediate configure output may suggest that other libraries will be favored.

Effects (VST and Audio Units)

(OS X) The following plug-ins may cause Audacity to crash if they are used after starting Audacity.
- AURoundTripAAC from "Apple audio mastering tools" (this requires OS X 10.6 or later so may crash on 10.4 or 10.5).

Effects and Analysis

LADSPA generate plug-ins may fail to generate into an empty track or into white space separating audio clips. Workaround: Before using the LADSPA generator, generate audio using any of the Audacity Generators above the divider in the Generate Menu, then generate into that audio selection.
Nyquist plug-ins: In locales where comma is the decimal separator, entering a comma in a text input box that has no associated slider will produce an error message, or only result in the whole number before the comma (for example, in Regular Interval Labels). Workaround: Use a dot (period) as the decimal separator.
Truncate Silence may not truncate a silence that appears from Selection Toolbar to be the same as the specified "min silence duration".

Envelopes and Clips

A clip may now be vertically dragged from inside a selection region, but if that region extends over the edge of the clip into space or into an adjoining clip there may be unexpected behavior:
- one channel of a stereo clip may jump sideways
- a mono clip may fail to horizontal-drag in its new track

Imports and Exports

(Linux) Exports using "M4A (AAC) Files" are very slow irrespective of the AAC encoder FFmpeg is configured to use. Workaround: choose (external program) when exporting, entering an appropriate path and command (for example, /usr/bin/ffmpeg -i - "%f") to run FFmpeg using Audacity's command-line encoder.
(Linux) Files exported using the FFmpeg native AAC encoder included with many system versions of FFmpeg are of very poor quality. This is an issue with the library itself. Workaround: When compiling FFmpeg, configure with the libfaac encoder thus: --disable-encoder=aac --enable-libfaac. Note that libfaac has an issue not present in the native FFmpeg encoder that saved files are short at the end by about 3000 samples.
(Linux) Mono AAC files import as stereo if FFmpeg uses the libfaad decoder. This is again an issue with the library itself.

Installation

(OS X 10.6 or later) Administrative (and occasionally, root) permissions may be needed on some machines to read the optional LAME and FFmpeg libraries at /usr/local/lib/audacity. In case of difficulty, please download the zip versions "Lame Library v3.98.2 for Audacity on OSX.zip" and "FFmpeg v0.6.2 for Audacity on OSX.zip" from the and extract the files to your own preferred location.

Interface

(Linux) If Audacity is configured with the option to use libsamplerate, an action involving resampling outside libsamplerate's limits of 1/256 to 256x will cause the progress dialog to hang, or possibly a crash.
(Linux) Using a file manager (for example, context menu) or the command line to open further files gives an error. Even if Audacity is closed, only one file can be opened from the file manager. Workaround: Use File > Open, or (for audio files) File > New then drag the files in.
(OS X and Linux) In some locales, Preferences text may be truncated or overlapped, or dropdown boxes truncated.

(Windows) It is not yet possible to drag .lnk shortcuts to audio files or projects into Audacity, or to drag them to the Audacity executable's icon. Workaround: Use File > Open or File > Import > Audio, or double-click the shortcut to the .aup from Windows Explorer.
(Windows) The Audacity executable cannot be added to the Explorer "Open with" context menu if you have another version of Audacity on the system which is also called "audacity.exe". Workaround: either use the "Open with" dialog to browse to the executable each time, or rename the executable to or some other unique name.
Dragging a clip or track up or down with Time Shift Tool does not scroll the project window when tracks exist out of view above or below the scroll. Workaround: Choose View > Fit Vertically before drag, or click and hold the piece to be dragged, use up or down arrow on the keyboard to scroll to the target track, then drag and release the clip or track.

Keyboard Shortcuts

(Windows) SHIFT + A (Play/Stop and Set Cursor) and custom unmodified shortcuts for playback or recording write a label at the cursor position if the label track has the yellow focus border. Workaround: use up or down arrow to move focus out of the label track before using the shortcut.

Label Tracks

Typing "j", "J", "k", "K" or other shortcuts in a label track may activate the shortcut instead of typing in the label. Workaround: In many cases, Edit > Undo then Edit > Redo will allow you to type in the label. Otherwise, click Edit > Preferences: Keyboard, choose the correct category, then clear the affected shortcuts or change them to include a CTRL + SHIFT modifier or other modifier than SHIFT.
(Linux) In projects containing several hundred labels or more, Audacity will freeze on 100% CPU when opening the "Audacity Karaoke" window, and will freeze again while that window is open when editing a label or performing other actions on the project. Workaround: Open or place an empty label track above the one you want to use.
Unless Tracks > Sync-Lock Tracks is on, pasting or inserting audio does not affect labels even if the label track is included in the selection.

Miscellaneous platform-specific issues

(Linux) A playback or recording freeze with pulseaudio may occur if repeatedly starting and stopping playback or recording in quick succession (or holding down the Play or Record button). Workaround: Bypass pulseaudio by setting the playback and recording device to an ALSA (hw) choice in Device Toolbar.
(Mac OS X) If using Audacity when the "Hear" audio plug-in is running (or has been since boot), there will be excessive memory usage which could cause a crash: this appears to be due to buggy memory allocation in "Hear"
(Mac OS X) Very occasionally, users may find that after running Audacity, other media players don't produce any sound, or crash: to resolve this, set up your sound device in Apple Audio MIDI Setup to work in stereo, 16-bit, with a sample rate of 44100 Hz or 48000 Hz, and set the sample format and rate identically in Audacity. More help at:

Mixer Board

Soloing or unsoloing a track in Mixer Board when in "Standard" Solo button mode may not immediately update the Solo button or waveform greyed/ungreyed state in the project window. Workaround: Click anywhere in (or task switch back to) the project window to refresh it (on Mac, you must click in the waveform or Track Control Panel or wait for the tracks to scroll when playing).
If you change the meter range in Preferences this is not reflected in the Mixer Board meters until restart.
(Linux) Meters may not respond immediately to playback which could cause them to report incorrect peak level or not display clipping.

Playback and Recording

Append Record with Transport > Overdub (on/off) enabled may cause periodic playthrough of previously recorded audio. If you use the Stop button or SPACE to stop the previous recording instead of SHIFT + A (Stop and Set Cursor), this may reduce occurrences of the issue.
(OS X and Linux) Audacity now works very well with , with the following bugs and limitations:
- Clicking in the input meter to start monitoring will crash Audacity if it has not yet used JACK for playback or recording in that session. Workaround: Before recording the first track in a session, click "Pause" then "Record" to enable the recording meter.

Preferences

(Linux) Extended Import: Clicking "Move rule up" when there are no rules or filters causes a crash.

Program Launch

(Linux) If a Bluetooth audio device is in use on a PulseAudio system, Audacity may hang on launch on initial attempts, then after eventual launch Bluetooth will no longer work on the system. Workarounds:
- Remove and reconnect the external Bluetooth adaptor, then launch bluetooth-applet from the command line.
- To prevent Audacity affecting Bluetooth support, move /usr/share/alsa/bluetooth.conf to another location then reboot, or create a symbolic link from /var/lib/alsa/asound.state to /dev/null and reboot.

Projects

There are currently no message box warnings when projects run out of disk space. If you run out of disk space when editing or recording, patches of silent or corrupted audio will appear, which will also be present if you save and reopen the project. Be aware that every edit on a track takes as much in disk space as if you were recording that track, due to the ability to undo and redo. You can go to View > History and discard Undo levels to free up space.
(OS X and Linux) Entering a backslash "\" in a file name when saving a project gives a "Could not save project. Path not found." error.
(OS X) Crash closing project window immediately after saving project: After saving a project, if you close the project window immediately the "Saving project data files" dialog completes, there will be an unexpected "Save changes?" prompt and then a crash when you choose "Yes" or "No". As long as you say "Yes", the project will be saved correctly and can be reopened normally after you restart Audacity. To be sure there is no crash, wait after "Saving project data files" completes for any "Inspecting Project Data" dialog to appear and disappear before closing the project window.

Time Tracks

The lower and upper speed limits are not stored in the project, so will be restored to their default values of 90 and 110 respectively when reopening or recovering a project, or if removing a Time Track then undoing removal. Please make a note of the correct values before closing the project or the Time Track.

Toolbars

(OS X and Linux) Using keyboard Undo while dragging envelope points or sample points will crash Audacity (this affects Envelope Tool, Draw Tool and Multi-Tool).
Transcription Toolbar does not play slower than 0.1x speed although the slider range goes down to 0.01x. Workaround: Use Effect > Change Speed instead to modify the audio, specifying your required negative Percent Change.
Meter Toolbar vertical orientation is not remembered across sessions, and resizing the meters reverts from vertical to horizontal.

Undo, Redo and History

If you change the Mute/Solo button state on any track(s) before recording or before applying an effect or edit, Undo of the record or edit undoes the Mute/Solo changes. Workaround: Select the track or its audio after changing the Mute/Solo state (other than by using ENTER to select the focused track).

Bugs requiring more investigation

(Linux) If Audacity is compiled with the option to use libsamplerate and the default "Best Sinc Interpolator" for high-quality conversion is used, Tracks > Resample may lead to truncation of the waveform. Workaround: change the project rate to the desired rate, export the track and re-import it.
(OS X and Linux) After using Tracks > Mix and Render or File > Save Project, some keyboard shortcuts such as Play/Stop or opening a new project window have no effect.
(Windows Vista) If you change the input volume in Audacity and then record, the volume is reset to its original level. This appears to occur mostly with a few specific USB devices, and sometimes only on Vista SP1, so it is currently hard for us to fix. Workaround: Check if the manufacturer supplies their own drivers for the device and try those. See if upgrading to Vista SP2 or Windows 7 helps.

Audacity 2.1.0

Audacity 2.1.0 was available from 29 March 2015 to 15th July 2015.

Tip: You can use CTRL + F to search this page for different words to do with the issue you are looking for. Use Command - F on Mac.

Users upgrading to this release from Audacity 2.0.5 or earlier who had FFmpeg installed will see a notice that FFmpeg needs to be reconfigured. Please visit https://manual.audacityteam.org/o/man/faq_installation_and_plug_ins.html#ffdown for a link to the recommended 2.2.2 version of FFmpeg for Windows and Mac OS X, and for information for Linux.
Shortcuts created in previous Audacity versions for the Generate, Effect and Analyze menus will not be recognized by 2.1.0 and cannot be imported from an XML file. However the shortcuts can be recreated and will then be respected. The previous bindings can still be viewed in the [NewKeys] section of the .

Extra notes for Mac OS X:

Audacity 2.1.0 cannot import MP4, M4A, MOV or ALAC files unless you install the library. After installing FFmpeg, use File > Import > Audio... or File > Open... and choose the "FFmpeg-compatible files" file type before selecting the file(s) to import.
This problem is already fixed in our source code, so will be fixed in the next 2.1.1 release.

Extra notes for GNU/Linux:

Some Linux distributions are supplying Audacity builds that are unstable because built with wxWidgets 3.x which . This applies for example to Ubuntu "Daily Builds", and Debian Jessie (Testing). Please check then the "Build Information" tab to check the version of wxWidgets that Audacity is built with. To avoid issues you can build wxWidgets 2.8.12 then compile Audacity against wxWidgets 2.8.12.

Extra notes for Windows:

The Windows installer for 2.0.x versions will replace legacy 1.2.x or any previous 2.0.x installation, but install alongside legacy 1.3.x Beta versions. It is strongly recommended to uninstall previous Beta versions before installing current Audacity.
The language choice in the Windows EXE Audacity installer only selects the language for the installer.

Changes since previous version

Improvements

Effects:
- LADSPA, VST and Audio Unit (OS X) effects now support real-time preview, save/load of user presets and saving effect settings across sessions. Note: Real-time preview does not yet support latency compensation.
- VST effects now support import/export of FXB preset banks.

Bug Fixes

Interface:
- Typing "j" or "k" in a label track activated the "move cursor" shortcut.
- Spectrogram log (f) view displayed incorrectly until vertically zoomed.

Addendum:

The previous Audacity 2.0.6 version fixed an issue that projects did not reopen correctly if they contained tracks having 2^31 samples or greater of audio (just over 13.5 hours at 44100 Hz).

Known Issues at Release

Accessibility

Many, but not all parts of the Audacity interface are accessible on Windows and Mac to those who can't use a mouse, and/or use a screen reader. It may be possible to make more of Audacity accessible in the longer term. For details, see
There are some accessibility bugs in the parts of Audacity that are accessible (or behavior may vary according to the specific screen reader).
- If you place the cursor or select a region using Selection Toolbar, apply an edit that moves the cursor/region then Undo, the cursor/region does not revert to its position before making the edit but reverts to its position before using Selection Toolbar. Workaround: Use the mouse or the

Chains

Audacity's built-in generators don't yet work with Chains. Plug-in generators should work.
Chains do not currently support export as AIFF, Other uncompressed files or any formats supported by FFmpeg.
Noise Reduction" does not yet support storing its parameters in a Chain. Noise Reduction will run at its current settings if used in a Chain.

Compiling

(Linux) New libsoxr resampling library: Default ./configure will enable a new library for resampling and disable libresample and libsamplerate (the previous resampling libraries). is required to build libsoxr. We strongly recommend libsoxr for its combination of high quality and high speed.
- Only one resampling library is permitted. If you enable either libresample or libsamplerate in configure, libsoxr will not be enabled. Any configure of resampling libraries other than libsoxr only will enable one only of libresample, libsamplerate or libsoxr in that order of precedence; however the intermediate configure output may suggest that other libraries will be favored.

Effects (Audio Units) (OS X)

All User Presets you select in the export dialog are exported at the same current settings you see in the effect, not at the preset's currently saved setting. This means that:
- To export a preset as saved you must first load it from User Presets before selecting it in the export dialog
- You cannot export more than one preset at a time at different settings.

Effects (VST and Audio Units)

(OS X and GNU/Linux): When saving VST effect presets, the FXP or XML file extension is not automatically offered in the file name, and not added by Audacity if you omit it. Make sure the extension you add is the same as that shown in the "File Format" drop-down menu, otherwise the preset will not be loadable.
(OS X) The following plug-ins may cause Audacity to crash if they are used after starting Audacity.
- AURoundTripAAC from "Apple audio mastering tools" (this requires OS X 10.6 or later so may crash on 10.4 or 10.5).

Effects and Analysis

LADSPA generate plug-ins may fail to generate into an empty track or into white space separating audio clips. Workaround: Before using the LADSPA generator, generate audio using any of the Audacity Generators above the divider in the Generate Menu, then generate into that audio selection.
Nyquist plug-ins: In locales where comma is the decimal separator, entering a comma in a text input box that has no associated slider will produce an error message, or only result in the whole number before the comma (for example, in Regular Interval Labels). Workaround: Use a dot (period) as the decimal separator.
(Linux) Sliding Time Scale / Pitch Shift may crash randomly in Audacity built with pre-2.0.2 versions of libsbsms.

Effects (real-time preview)

Real-time preview doesn't yet compensate for the latency many plug-ins introduce in order to provide smooth processing of audio. Real-time preview therefore may have small gaps in the audio, or timing artifacts may be audible when previewing multiple tracks. Compensation is applied when applying the effect, unless you disable compensation in the options for the effect).
Unlike with built-in effects, it is necessary to select a track to open a real-time preview effect (VST, LADSPA or Audio Units), and to select audio in a track to apply the effect.

Envelopes and Clips

A clip may now be vertically dragged from inside a selection region, but if that region extends over the edge of the clip into space or into an adjoining clip there may be unexpected behavior:
- one channel of a stereo clip may jump sideways
- a mono clip may fail to horizontal-drag in its new track

Exports

(Linux) Exports using "M4A (AAC) Files" are very slow irrespective of the AAC encoder FFmpeg is configured to use. Workaround: choose (external program) when exporting, entering an appropriate path and command (for example, /usr/bin/ffmpeg -i - "%f") to run FFmpeg using Audacity's command-line encoder.
(Linux) Files exported using the FFmpeg native AAC encoder included with many system versions of FFmpeg may be of poor quality. This is an issue with the library itself. Workaround: When compiling FFmpeg, configure with the libfaac encoder thus: --disable-encoder=aac --enable-libfaac --enable-nonfree. Note that libfaac has an issue not present in the native FFmpeg encoder that saved files are short at the end by about 3000 samples. Alternatively build the VisualOn AAC encoder library and configure FFmpeg with --disable-encoder=aac --disable-encoder=libfaac --enable-libvo-aacenc.

Imports and Exports

AAC exports using "M4A (AAC) Files (FFmpeg)" with project rate below 22050 Hz produce a zero bytes file if the linked to FFmpeg is configured with the default AAC encoder or libfaac. This will not affect the recommended builds of FFmpeg for Windows and Mac OS X which are built with libvo-aacenc. Workaround: You can export AAC below 22050 Hz using default-configured FFmpeg by choosing (external program) export instead.
Files containing PCM audio but misnamed as MP3 cause a freeze or crash if an Extended Import rule is set in Preferences to force import of MP3 files using the MP3 importer.
ID3 metadata tags in imported MP3 or MP2 files may display incorrectly if the metadata is UTF-16 encoded. The tags will seem to have Chinese characters and these incorrect tags will also be present if the files are re-exported.

Imports and Exports (FFmpeg)

In the "Custom FFmpeg Export" dialog, saved or imported presets do not load. Attempting to import a preset crashes Audacity unless the "ffmpeg_presets.xml" file in Audacity's folder for application data is empty or does not exist.
M4A (AAC) exports: The Quality Slider in "Specify AAC Options" has no effect if the FFmpeg library is built with the libvo-aac encoder, as are recommended builds of FFmpeg for Windows and Mac OS X. Workaround: You can specify a constant bit rate if you select "Custom FFmpeg Export". Click the Options... button, choose "mp4" in the formats list and "libvo_aacenc" in the codecs list, then set bit rate in bits per second. Up to 320000 bps (320 kbps) is supported. Given the alternative AAC encoders for FFmpeg also have problems as described in these notes, you can instead export as WAV and convert to AAC in iTunes on Windows and Mac.

Installation

(OS X 10.6 or later) Administrative (and occasionally, root) permissions may be needed on some machines to read the optional LAME libraries at /usr/local/lib/audacity. In case of difficulty, please download the zip version "Lame Library v3.98.2 for Audacity on OSX.zip" from the and extract the files to your own preferred location.

Interface

(Linux) Opening the Audio Track Dropdown Menu to change settings may result in that track changing sample rate or sample format to match that of other tracks.
(Linux) If Audacity is configured with the option to use libsamplerate, an action involving resampling outside libsamplerate's limits of 1/256 to 256x will cause the progress dialogue to hang, or possibly a crash.
(Mac OS X) Audacity will crash when you OK or dismiss the track Gain or Pan adjustment dialog if you open that dialog by double-clicking the Gain or Pan slider in the Track Control Panel. Workaround: Open the adjustment dialog using the shortcuts SHIFT + G (to open the gain dialog) or SHIFT + P (to open the pan dialog).

(OS X 10.5.8 PPC) "The How to Get Help" window that appears by default on launch of Audacity cannot be moved or closed. The Audacity Log window may also be affected. Workaround: To stop the Welcome Screen appearing, open Audacity > Preferences: Interface and uncheck "Show How to Get Help". You can also quit Audacity, open Finder, Go > Go to Folder and type ~/Library/Application Support/audacity/ . Open audacity.cfg,select all the text and delete it. Then type the following at the top of the file:
NewPrefsInitialized=1 [GUI] ShowSplashScreen=0
Save the changes to audacity.cfg then restart Audacity.
(Windows) It is not yet possible to drag .lnk shortcuts to audio files or projects into Audacity, or to drag them to the Audacity executable's icon. Workaround: Use File > Open or File > Import > Audio, or double-click the shortcut to the .aup from Windows Explorer.

Keyboard Shortcuts

(Windows) SHIFT + A (Play/Stop and Set Cursor) and custom unmodified shortcuts for playback or recording write a label at the cursor position if the label track has the yellow focus border. Workaround: use up or down arrow to move focus out of the label track before using the shortcut.

Label Tracks

(Linux) In projects containing several hundred labels or more, Audacity will freeze on 100% CPU when opening the "Audacity Karaoke" window, and will freeze again while that window is open when editing a label or performing other actions on the project. Workaround: Open or place an empty label track above the one you want to use.
Unless Tracks > Sync-Lock Tracks is on, pasting or inserting audio does not affect labels even if the label track is included in the selection.
Yellow "snap" guidelines do not appear in re-opened projects or imported label tracks when dragging a selection to a label edge if "Snap To" is checked and a high resolution Selection Format chosen. Formats affected include "hh:mm:ss + CDDA frames (75 fps)", "hh:mm:ss + milliseconds" and "hh:mm:ss + samples".

Miscellaneous platform-specific issues

(Linux) A playback or recording freeze, recording dropouts or fast playback may occur when using PulseAudio. Freezes may be caused by repeatedly starting and stopping playback or recording in quick succession (or by holding down the Play or Record button). Workarounds: Try launching Audacity from the terminal with the pulse latency set to 30 ms in an environment variable:
env PULSE_LATENCY_MSEC=30 audacity
If you get underruns noted in the terminal, try a higher number in the PULSE_LATENCY_MSEC command. If the problem is unchanged, try a lower number. Alternatively, bypass pulseaudio by setting the playback and recording device to an ALSA (hw) choice in Device Toolbar.
(Mac OS X) If using Audacity when the "Hear" audio plug-in is running (or has been since boot), there will be excessive memory usage which could cause a crash: this appears to be due to buggy memory allocation in "Hear"

Mixer Board

Soloing or unsoloing a track in Mixer Board when in "Standard" Solo button mode may not immediately update the Solo button or waveform greyed/ungreyed state in the project window. Workaround: Click anywhere in (or task switch back to) the project window to refresh it (on Mac, you must click in the waveform or Track Control Panel or wait for the tracks to scroll when playing).
(Windows and Linux) If Mixer Board is open and more tracks are added so that the horizontal scrollbar must be used, newly added tracks may not be visible or newly deleted tracks may show as empty space. Workaround: To see all the tracks without redundant space, close and reopen the project then reopen Mixer Board.
If you change the meter range in Preferences this is not reflected in the Mixer Board meters until restart.

Playback and Recording

Append Record with Transport > Overdub (on/off) enabled may cause periodic playthrough of previously recorded audio. If you use the Stop button or SPACE to stop the previous recording instead of SHIFT + A (Stop and Set Cursor), this may reduce occurrences of the issue.
(OS X and Linux) Audacity now works very well with , with the following bugs and limitations:
- Clicking in the input meter to start monitoring will crash Audacity if it has not yet used JACK for playback or recording in that session. Workaround: Before recording the first track in a session, click "Pause" then "Record" to enable the recording meter.

Program Launch

(Linux) If a Bluetooth audio device is in use on a PulseAudio system, Audacity may hang on launch on initial attempts, then after eventual launch Bluetooth will no longer work on the system. Workarounds:
- Remove and reconnect the external Bluetooth adaptor, then launch bluetooth-applet from the command line.
- To prevent Audacity affecting Bluetooth support, move /usr/share/alsa/bluetooth.conf to another location then reboot, or create a symbolic link from /var/lib/alsa/asound.state to /dev/null and reboot.

Projects

There are currently no message box warnings when projects run out of disk space. If you run out of disk space when editing or recording, patches of silent or corrupted audio will appear, which will also be present if you save and reopen the project. Be aware that every edit on a track takes as much in disk space as if you were recording that track, due to the ability to undo and redo. You can go to View > History and discard Undo levels to free up space.
(OS X and Linux) Entering a backslash "\" in a file name when saving a project gives a "Could not save project. Path not found." error.
(OS X) Crash closing project window immediately after saving project: After saving a project, if you close the project window immediately the "Saving project data files" dialog completes, there will be an unexpected "Save changes?" prompt and then a crash when you choose "Yes" or "No". As long as you say "Yes", the project will be saved correctly and can be reopened normally after you restart Audacity. To be sure there is no crash, wait after "Saving project data files" completes for any "Inspecting Project Data" dialog to appear and disappear before closing the project window.

Spectrograms

The displayed level of the upper, lower and center frequency lines is slightly inaccurate in linear Spectrogram view, and may drift up or down above the true level when zooming in or out on the vertical scale. You can use Spectrogram log(f) view or set the frequencies accurately in Spectral Selection Toolbar.

Sync-Locked Track Groups

If Sync-Locked Track Groups are enabled but "Editing a clip can move other clips" in Tracks Preferences is disabled, sometimes not all sync-lock-selected tracks will be affected by Timeline-changing edits, and sometimes audio clips may be removed. You can Edit > Undo any unwanted changes.

Time Tracks

The lower and upper speed limits are not stored in the project, so will be restored to their default values of 90 and 110 respectively when reopening or recovering a project, or if removing a Time Track then undoing removal. Please make a note of the correct values before closing the project or the Time Track.

Toolbars

Draw Tool: Holding CTRL to only move one sample then pressing Z (COMMAND + Z on Mac) to undo while still holding the mouse button will cause that track to be removed. The removal of that track cannot be undone.
(OS X and Linux) Draw Tool: Using keyboard Undo while dragging sample points will crash Audacity (this affects Draw Tool and Multi-Tool).
(Mac OS X) Audacity will crash if you File > Close a project window with Screenshot Tools open. Audacity > Quit Audacity does not crash.

Bugs requiring more investigation

Very occasionally, Audacity projects may reopen with missing block files, orphan block files and/or silenced audio data. There may be unwanted renaming or moving of AU files within the project. We believe having multiple projects open at once or having projects open in file manager programs are among the possible causes. See Bug:137 for more background to this.
The AUP file may be saved with references to only a few of the AU files, again leading to "orphan block file" warnings. Sometimes the AUP file may not be found after saving and closing the project.

(Linux) If Audacity is compiled with the option to use libsamplerate and the default "Best Sinc Interpolator" for high-quality conversion is used, Tracks > Resample may lead to truncation of the waveform. Workaround: change the project rate to the desired rate, export the track and re-import it.
(Windows Vista) If you change the input volume in Audacity and then record, the volume is reset to its original level. This appears to occur mostly with a few specific USB devices, and sometimes only on Vista SP1, so it is currently hard for us to fix. Workaround: Check if the manufacturer supplies their own drivers for the device and try those. See if upgrading to Vista SP2 or Windows 7 helps.
- Please report make and model number of devices that exhibit the issue, also the drivers and exact version of Vista and Service Pack in use (for example, Vista 32-bit, SP1)

Audacity 2.1.1

Audacity 2.1.1 was current from 16th July 2015 to 19th January 2016.

Tip: You can use CTRL + F to search this page for different words to do with the issue you are looking for. Use Command - F on Mac.

GNU/Linux:

Some Linux distributions are supplying Audacity builds that are unstable because built with wxWidgets 3.x which Audacity does not yet support. This applies for example to Ubuntu "Daily Builds", Ubuntu Vivid and Debian Jessie (Testing). Audacity 2.1.1. will now issue a warning at start up if it was built with wx3 by mistake. You can find out more about this here: Incorrect wxWidgets Version. To avoid issues you can build wxWidgets 2.8.12 then compile Audacity against wxWidgets 2.8.12.

Mac OS X:

Audacity 2.1.1 when released supported OS X 10.5 to 10.10.x.
- Audacity 2.1.1 will be the final version to support PPC Mac, but does not support Audio Units on PPC Mac.

Windows:

The Windows installer for 2.1.1 versions will replace legacy 1.2.x or any previous 2.x installation, but install alongside legacy 1.3.x Beta versions. It is strongly recommended to uninstall previous Beta versions before installing current Audacity.
MP3 Encoding: Users upgrading to Audacity 2.1.1 versions from 1.3.6 or earlier must download the

Changes since previous version

Improvements

Effects
- Built-in effects now support presets.
- New Limiter effect replaces Hard Limiter effect.
- New Crossfade Clips effect to apply a simple crossfade to a selected pair of clips in a single audio track.

Bug Fixes

Crashes
- Crash using Undo while dragging sample points
- Crash using File > Close on project window when Screenshot Tools was open.

Known Issues at Release

Accessibility

Many, but not all parts of the Audacity interface are accessible on Windows and Mac to those who can't use a mouse, and/or use a screen reader. It may be possible to make more of Audacity accessible in the longer term. For details, see
There are some accessibility bugs in the parts of Audacity that are accessible (or behavior may vary according to the specific screen reader).
- Some interface text or markings remain in black when using High Contrast light-on-dark themes, so cannot be read properly.

Bugs requiring more investigation

(Windows Vista or later) On upgrading to current Audacity from earlier versions, "error opening sound device" occurs when recording from the inbuilt sound device where there was no error in the previous Audacity with the same device configuration and operating system. Workaround: Use Transport > Rescan Audio Devices, or go to "Sound" in the Windows Control Panel and click OK. Note that if devices listed in Device Toolbar are disabled in "Sound" then the error is legitimate - you will need to enable those devices.
- Please report make and model number of sound devices that exhibit the issue, along with driver version number. Please first ensure your sound device drivers are up-to-date and not generic Microsoft drivers - help available here.
(Windows Vista) If you change the input volume in Audacity and then record, the volume is reset to its original level. This appears to occur mostly with a few specific USB devices, and sometimes only on Vista SP1, so it is currently hard for us to fix.

Chains

Audacity's built-in generators don't yet work with Chains. Plug-in generators should work.
Chains do not currently support export as AIFF, Other uncompressed files or any formats supported by FFmpeg.
LV2 effects cannot yet store their parameters in Chains so if non-default parameters are required in a Chain these must be set for each Audacity session in File > Edit Chains before running the Chain.

Compiling

The minsrc tarball contains a superfluous (but harmless) .deps folder in lib-src/mod-nyq-bench.
(Windows) LADSPA effects cannot be categorized even when Audacity is compiled with USE_LIBLRDF defined.
(Linux) Audacity may not always compile against supported versions of libav or FFmpeg. Audacity 2.0.6 and later supports FFmpeg 1.2 to 2.3.x (or libav 0.8 to 0.10.x).

Effects

"Plug-in Manager" dialog:'
- The dialog may include some VST instruments or VST 3 effects but these are not supported so will not load even if enabled.

Effects (Audio Units) (OS X)

All User Presets you select in the export dialog are exported at the same current settings you see in the effect, not at the preset's currently saved setting. This means that:
- To export a preset as saved you must first load it from User Presets before selecting it in the export dialog
- You cannot export more than one preset at a time at different settings.

Effects (LADSPA)

(Windows) When Region and Language format for the computer is set to a language using comma as decimal separator (for example, French or German), effect settings cannot be changed from the Manage menu to Factory Defaults or to saved User Presets. Also, current settings are not saved after Audacity is quit.

Effects (LV2)

(Mac OS X and Linux) LV2 instruments that Audacity should ignore because they are incompatible are listed in Plug-in Manager (64-bit Linux may not be affected). These plug-ins will not work in Audacity even if you re-enable them.

Effects (Real-time preview)

Real-time preview doesn't yet compensate for the latency many plug-ins introduce in order to provide smooth processing of audio. Real-time preview therefore may have small gaps in the audio, or timing artifacts may be audible when previewing multiple tracks. Compensation is applied when applying the effect, unless you disable compensation in the options for the effect).

Effects (Vamp)

Input cannot be made using the text boxes. Use the slider instead to adjust values.

Effects (VST and Audio Units)

(OS X and GNU/Linux): When saving VST effect presets, the FXP or XML file extension is not automatically offered in the file name, and not added by Audacity if you omit it. Make sure the extension you add is the same as that shown in the "File Format" drop-down menu, otherwise the preset will not be loadable.
(Windows) In some VST effects you cannot preview a Factory Preset or User Preset after you select it unless you select it while playing. If the preset is selected while playback is stopped it will be applied to the waveform when you press "Apply", but you won't hear that preset in the effect until you restart Audacity.
(Windows and Mac OS X) When running VST effects in the controls of many plug-ins do not visibly respond when loading a preset file from the "Load" button

Effects and Analysis

(Windows 64-bit) There is no HKEY_LOCAL_MACHINE\SOFTWARE\ registry key where Audacity detects VST plug-ins. The HKEY_CURRENT_USER key searched is HKEY_CURRENT_USER\Software\VST\VSTPluginsPath instead of the expected HKEY_CURRENT_USER\SOFTWARE\Wow6432Node\VST .
"Play" or "Preview" features that are included in a few Nyquist plug-ins do not work on Mac OS X and may cause Audacity to freeze or crash on Linux.
Analyze > Plot Spectrum and Contrast do not currently appear in Plug-In Manager: Effects so cannot be disabled.

Click the "Save / Manage Curves..." button
Select the "unnamed" item
Click the "Rename" button
Type a name for the curve

Next time you use Equalization, select the saved preset using the "Select Curve" dropdown.

Noise reduction: Preview is not possible if the sample rate of the project is different from the rate of the track to be processed - an error message appears "Sample rate of the noise profile must match that of the sound to be processed" (even if that condition is met). Providing the noise profile rate does match the track rate, you can still apply the effect. Alternatively, change the project rate temporarily to the rate of the track.
Nyquist plug-ins: In locales where comma is the decimal separator, entering a comma in a text input box that has no associated slider will produce an error message, or only result in the whole number before the comma (for example, in Regular Interval Labels). Workaround: Use a dot (period) as the decimal separator.
Truncate Silence when run on multiple selected tracks only looks for and truncates "silence" regions which are common to

Envelopes and Clips

A clip may now be vertically dragged from inside a selection region, but if that region extends over the edge of the clip into space or into an adjoining clip there may be unexpected behavior:
- one channel of a stereo clip may jump sideways
- a mono clip may fail to horizontal-drag in its new track

Exports

WAVEX (Microsoft) headers: GSM 6.10 files cannot be exported with WAVEX headers. Use WAV headers instead (note that GSM 6.10 only supports mono). A-Law and U-Law files with WAV headers may not be playable - use WAV headers instead. Choose "Other uncompressed files" then "Options..." to export to GSM 6.10 or A-/U-Law with WAV headers.
(Linux) Exports using "M4A (AAC) Files" are very slow irrespective of the AAC encoder FFmpeg is configured to use. Workaround: choose (external program) when exporting, entering an appropriate path and command (for example, /usr/bin/ffmpeg -i - "%f") to run FFmpeg using Audacity's command-line encoder.
(Linux) Files exported using the FFmpeg native AAC encoder included with many system versions of FFmpeg may be of poor quality. This is an issue with the library itself. Workaround:

Imports and Exports

(Mac OS X) Importing and Exporting FLAC files is slower than in Audacity 2.1.0.
A-Law, U-Law and ADPCM export formats must be chosen by selecting "Other uncompressed files" then clicking the "Options..." button. We hope to redesign the export list in due course to make these formats easier to find and choose.
AAC exports using "M4A (AAC) Files (FFmpeg)" with project rate below 22050 Hz produce a zero bytes file if the linked to FFmpeg is configured with the default AAC encoder or libfaac. This will not affect the recommended builds of FFmpeg for Windows and Mac OS X which are built with libvo-aacenc. Workaround: You can export AAC below 22050 Hz using default-configured FFmpeg by choosing (external program) export instead.

Imports and Exports (FFmpeg)

In the "Custom FFmpeg Export" dialog, imported presets do not load.
M4A (AAC) exports: The Quality Slider in "Specify AAC Options" has no effect if the FFmpeg library is built with the libvo-aac encoder, as are recommended builds of FFmpeg for Windows and Mac OS X. Workaround: You can specify a constant bit rate if you select "Custom FFmpeg Export". Click the Options... button, choose "mp4" in the formats list and "libvo_aacenc" in the codecs list, then set bit rate in bits per second. Up to 320000 bps (320 kbps) is supported. Given the alternative AAC encoders for FFmpeg also have problems as described in these notes, you can instead export as WAV and convert to AAC in iTunes on Windows and Mac.

Installation

(OS X 10.6 or later) Administrative (and occasionally, root) permissions may be needed on some machines to read the optional LAME libraries at /usr/local/lib/audacity. In case of difficulty, please download the zip version "Lame Library v3.98.2 for Audacity on OSX.zip" from the and extract the files to your own preferred location.
(Windows) In the Audacity installer, selecting the language to use during installation now selects the language Audacity will run in, even if Windows is running in a different language.

Interface

Audacity crashes after quit if quit from the Task Manager (Windows), Dock (Mac OS X) or Taskbar (Linux) while "About Audacity" is open. Any unsaved audio is saved correctly before the crash.
Audacity may freeze when Track-Control-Panel-dragging a track from the bottom to top of a project containing several dozen tracks or more. Workaround: Use the commands to move the focused track to the top (or upwards).
(Linux) Using a file manager (for example, context menu) or the command line to open further files gives an error. Even if Audacity is closed, only one file can be opened from the file manager. Workaround: Use File > Open, or (for audio files) File > New then drag the files in.

(Windows) It is not yet possible to drag .lnk shortcuts to audio files or projects into Audacity, or to drag them to the Audacity executable's icon. Workaround: Use File > Open or File > Import > Audio, or double-click the shortcut to the .aup from Windows Explorer.
(Windows) The Audacity executable cannot be added to the Explorer "Open with" context menu if you have another version of Audacity on the system which is also called "audacity.exe". Workaround: either use the "Open with" dialog to browse to the executable each time, or rename the executable to or some other unique name.
(OS X 10.5.8 PPC) "The How to Get Help" window that appears by default on launch of Audacity cannot be moved or closed. The Audacity Log window may also be affected. Workaround:

NewPrefsInitialized=1 [GUI] ShowSplashScreen=0

Save the changes to audacity.cfg then restart Audacity.

Dragging a clip or track up or down with Time Shift Tool does not scroll the project window when tracks exist out of view above or below the scroll. Workaround: Choose View > Fit Vertically before drag, or click and hold the piece to be dragged, use up or down arrow on the keyboard to scroll to the target track, then drag and release the clip or track.
Sync-Locked Tracks are not affected by all actions that change the length of a track in the Sync-Locked Track Group. Applying Paulstretch or using the Audio Track dropdown menu to change sample rate will leave the other Sync-Locked tracks desynchronised.

Keyboard Shortcuts

(Windows) SHIFT + A (Play/Stop and Set Cursor) and custom unmodified shortcuts for playback or recording write a label at the cursor position if the label track has the yellow focus border. Workaround: use up or down arrow to move focus out of the label track before using the shortcut.

Label Tracks

(Linux) In projects containing several hundred labels or more, Audacity will freeze on 100% CPU when opening the "Audacity Karaoke" window, and will freeze again while that window is open when editing a label or performing other actions on the project. Workaround: Open or place an empty label track above the one you want to use.
Unless Tracks > Sync-Lock Tracks is on, pasting or inserting audio does not affect labels even if the label track is included in the selection.
Yellow "snap" guidelines do not appear in re-opened projects or imported label tracks when dragging a selection to a label edge if "Snap To" is checked and a high resolution Selection Format chosen. Formats affected include "hh:mm:ss + CDDA frames (75 fps)", "hh:mm:ss + milliseconds" and "hh:mm:ss + samples".

Localization

When Audacity's Interface Preferences are set to "System" language, a computer locale set to Traditional Chinese results in Audacity displaying in Simplified Chinese, and a Brazilian Portuguese computer locale results in Audacity displaying in European Portuguese. To change the Audacity language as required please see .

Miscellaneous platform-specific issues

(Mac OS X) If using Audacity when the "Hear" audio plug-in is running (or has been since boot), there will be excessive memory usage which could cause a crash: this appears to be due to buggy memory allocation in "Hear"
(Mac OS X) Very occasionally, users may find that after running Audacity, other media players don't produce any sound, or crash: to resolve this, set up your sound device in Apple Audio MIDI Setup to work in stereo, 16-bit, with a sample rate of 44100 Hz or 48000 Hz, and set the sample format and rate identically in Audacity. More help at:
(Linux) A playback or recording freeze, recording dropouts or fast playback may occur when using PulseAudio. Freezes may be caused by repeatedly starting and stopping playback or recording in quick succession (or by holding down the Play or Record button). Workarounds:

env PULSE_LATENCY_MSEC=30 audacity

If you get underruns noted in the terminal, try a higher number in the PULSE_LATENCY_MSEC command. If the problem is unchanged, try a lower number. Alternatively, bypass pulseaudio by setting the playback and recording device to an ALSA (hw) choice in Device Toolbar.

Mixer Board

Soloing or unsoloing a track in Mixer Board when in "Standard" Solo button mode may not immediately update the Solo button or waveform greyed/ungreyed state in the project window. Workaround: Click anywhere in (or task switch back to) the project window to refresh it (on Mac, you must click in the waveform or Track Control Panel or wait for the tracks to scroll when playing).
(Windows and Linux) If Mixer Board is open and more tracks are added so that the horizontal scrollbar must be used, newly added tracks may not be visible or newly deleted tracks may show as empty space. Workaround: To see all the tracks without redundant space, close and reopen the project then reopen Mixer Board.
If you change the meter range in Preferences this is not reflected in the Mixer Board meters until restart.

Modules

(Windows, Mac OS X) Modules originally shipped with obsolete 1.3.x versions of Audacity will cause Audacity to crash once at launch if they exist in a "modules" folder alongside the Audacity executable and are enabled in Modules Preferences.

Moonphase

Very occasionally, Audacity projects may reopen with missing block files, orphan block files and/or silenced audio data. There may be unwanted renaming or moving of AU files within the project. We believe having multiple projects open at once or having projects open in file manager programs are among the possible causes. See Bug:137 for more background to this.
The AUP file may be saved with references to only a few of the AU files, again leading to "orphan block file" warnings. Sometimes the AUP file may not be found after saving and closing the project.

Playback and Recording

Append Record with Transport > Overdub (on/off) enabled may cause periodic playthrough of previously recorded audio. If you use the Stop button or SPACE to stop the previous recording instead of SHIFT + A (Stop and Set Cursor), this may reduce occurrences of the issue.
(Mac OS X) The default 100 ms "Audio to buffer" setting in Audacity's Recording Preferences (which also affects playback) is too high for many USB or firewire devices. There may be immediate clicky playback of good audio and more rarely, recordings may be corrupted with clicks after a period of time. Set Audio to buffer as low as you can consistent with still getting a good recording, or use the built-in output or input instead.
(OS X Yosemite or Mavericks) 'Random occasional crashes may occur after recording or monitoring in a second project window then zooming or fitting the project in that window.

Program Launch

(Linux) If a Bluetooth audio device is in use on a PulseAudio system, Audacity may hang on launch on initial attempts, then after eventual launch Bluetooth will no longer work on the system. Workarounds:
- Remove and reconnect the external Bluetooth adaptor, then launch bluetooth-applet from the command line.
- To prevent Audacity affecting Bluetooth support, move /usr/share/alsa/bluetooth.conf to another location then reboot, or create a symbolic link from /var/lib/alsa/asound.state to /dev/null and reboot.

Projects

There are currently no message box warnings when projects run out of disk space. If you run out of disk space when editing or recording, patches of silent or corrupted audio will appear, which will also be present if you save and reopen the project. Be aware that every edit on a complete track takes as much in disk space as if you were recording that entire track, and partial edits take proportional amounts of space, due to the ability to undo and redo. You can go to View > History and discard Undo levels to free up space.
(OS X and Linux) Entering a backslash "\" in a file name when saving a project gives a "Could not save project. Path not found." error.
(OS X) Crash closing project window immediately after saving project: After saving a project, if you close the project window immediately the "Saving project data files" dialog completes, there will be an unexpected "Save changes?" prompt and then a crash when you choose "Yes" or "No". As long as you say "Yes", the project will be saved correctly and can be reopened normally after you restart Audacity. To be sure there is no crash, wait after "Saving project data files" completes for any "Inspecting Project Data" dialog to appear and disappear before closing the project window.

Scrubbing

When you hold CTRL then left-click to start scrub or double-click to start scroll-scrub there is no indication that scrubbing is active. Move the mouse pointer to be sure scrubbing is active.
Scrubbing disables the Pause button and the Pause command in the Transport menu but neither of these is grayed out as inactive.
Scrubbing unintentionally captures clicks in some toolbar areas. This may suspend scrubbing, especially if the toolbar is undocked. Click again in the waveform to resume scrubbing. Long-clicking in some docked toolbars while scrubbing (for example on the Zoom buttons or on the Mixer Toolbar sliders) performs an unwanted seek. The region over which scrubbing operates may be reduced in a future version of Audacity.

Spectrograms

The displayed level of the upper, lower and center frequency lines is slightly inaccurate in linear Spectrogram view, and may drift up or down above the true level when zooming in or out on the vertical scale. You can use Spectrogram log(f) view or set the frequencies accurately in Spectral Selection Toolbar.
A created in either Spectral Selection view currently only works with the three specific and those effects can only be used in either Spectral Selection view. All other effects and for example cut or delete will act on the entire spectrum in the time range regardless of the spectral selection.

Sync-Locked Track Groups

If Sync-Locked Track Groups are enabled but "Editing a clip can move other clips" in Tracks Preferences is disabled, sometimes not all sync-lock-selected tracks will be affected by Timeline-changing edits, and sometimes audio clips may be removed. You can Edit > Undo any unwanted changes.

Time Tracks

The lower and upper speed limits are not stored in the project, so will be restored to their default values of 90 and 110 respectively when reopening or recovering a project, or if removing a Time Track then undoing removal. Please make a note of the correct values before closing the project or the Time Track.

Toolbars

Meter Toolbar vertical orientation is not remembered across sessions, and resizing the meters reverts from vertical to horizontal.
(Windows XP) Transport and Tools Toolbar buttons all display as Pause buttons. The buttons may redraw correctly if you hover over them. Workaround: You can use for the buttons instead.

User Interface

(OS X Yosemite) Random occasional crashes may occur when importing or exporting files or when opening/saving projects. If you have found steps that almost always reproduce this crash, please write to with details and include the crash report from /Library/Logs/DiagnosticReports/.

A-Law, U-Law and ADPCM export formats (also RF64 for PCM exports larger than 4 GB in size) must be chosen by selecting "Other uncompressed files", ensure the "Header" is "WAV (Microsoft)", then from the "Encoding" dropdown menu select your desired encoding. We may redesign the export list in due course to make these formats easier to find.
AAC exports using "M4A (AAC) Files (FFmpeg)" with project rate below 22050 Hz produce a zero bytes file if the linked to FFmpeg is configured with the default AAC encoder or libfaac. This will not affect the recommended builds of FFmpeg for Windows and Mac OS X which are built with libvo-aacenc. Workaround: You can export AAC below 22050 Hz using default-configured FFmpeg by choosing (external program) export instead.
Exports chosen using the "Other uncompressed files" type may be saved with incorrect extension and so not be playable - on Windows and OS X, AIFF extension is always used regardless of format and on Linux, the extension for the last saved format is always used. Workaround: Add a period and the correct extension for the format (or on Mac OS X, change the supplied extension). Be sure to add the correct extension, because Audacity may not warn if an inappropriate extension is added.
Files containing PCM audio but misnamed as MP3 cause a freeze or crash if an Extended Import rule is set in Preferences to force import of MP3 files using the MP3 importer.
ID3 metadata tags in imported MP3 or MP2 files may display incorrectly if the metadata is UTF-16 encoded. The tags will seem to have Chinese characters and these incorrect tags will also be present if the files are re-exported. Workaround: Before importing the file into Audacity, open it in a tag editor or an audio application that can edit tags. If the tags are seen correctly, save the file in that application. On Windows you can use for this purpose.
Importing multiple files at once into new project windows using File > Open... or the command-line may show incorrect Timeline length including corrupt or missing values. Clicking above Mute/Solo will show the correct length of the track. If the Timeline length is incorrect, you can zoom in or out to get the correct length (and refit the project if you want). Multiple import into the same project window is not affected.
The Import / Export Preference "When importing audio files, Normalize all tracks in project" will cause import of WAV/AIFF files using "Read the files directly from the original" to lock up at the Normalize step. If you require normalize on import for WAV/AIFF, please change the Import / Export Preference to "Make a copy... before editing".
(Linux) Importing a file will cause the export dialog to always offer AIFF extension irrespective of the selected export format. Workaround: Remove the period (dot) and extension from the file name or add the correct extension, then the file will export correctly.
(Linux) After opening a sufficiently long audio file, opening a second file of any size leads to locked GUI/console messages until first file completes play.
(Linux) Custom FFmpeg Export dialogue does not respond to ENTER after clicking in the Formats or Codec selector.
(Mac OS X) When browsing to and opening LAME from the required libmp3lame.dylib file may be grayed out and unselectable. Choose "Dynamic Libraries" or "All Files" in the "File type:" dropdown. This will let you select the file and open it even if it still appears grayed out.
(Mac OS X) Dragging audio files to Audacity's icon in the Dock will only import the file for WAV, AIFF, AU, MP2, MP3, OGG, FLAC and M4A. Workaround: Rename MP4 files (audio or video) to M4A extension. Alternatively the files may be dragged to the Audacity icon in the folder where you have Audacity installed, dragged into the open Audacity window or imported using the Audacity menus.
(OS X 10.10) iTunes files cannot be opened from Media > Music in Audacity's file open dialogs. You could drag your iTunes "Music" folder to the Finder sidebar to give quicker access in Audacity open dialogs.
(OS X and Linux) When using Export Multiple, asterisks (*) or question marks (?) in labels are wrongly rejected as illegal characters, and forward slashes (/) cause a false "cannot export audio" warning. Workaround: To force use of * or ? (and / on OS X), export each region with File > Export Selection instead (/ is illegal in a file or folder name on Linux).
(OS X) Audio files cannot be dragged into the Audacity window. You can drag files to the Audacity icon in /Applications or in the Dock, or import the file from within Audacity.
(OS X) Files imported from iTunes could create invalid characters in the .aup project file in previous Beta versions of Audacity. If you re-open such a project in the current release, an error "reference to invalid character number" may occur. Workaround: Save and open a back-up copy of the .aup file in a text editor, turn off word wrap, then in the line indicated in the error message, remove the string of characters that starts with &# and ends with a semi-colon (;). There is more help with fixing this .
(Windows Vista, 7) Audacity will crash if attempting to open WAV files while they are still being rendered by the open source Psycle tracker program.
If WAV/AIFF files are imported into a project using "Read Directly" import but then become unavailable, warnings are given when playing, recording, applying effects and exporting, but not all editing and project save actions are warned.
If you import an audio file from a folder other than the one you last exported to, you cannot export over that file without changing the export directory manually.
"Background on-demand loading" for FFmpeg (in the Libraries Preferences) does not currently allow changing the focus of waveform computation by clicking in the track. You can apply an effect to a selection wherever the normal waveform has appeared, but if you do so before the normal waveform has appeared, the audio will be silenced.
(Linux): When exporting to MIDI over an existing file, no overwrite warning is given.
By default, the importer used depends on the import method. For example, to be able to use to import native Audacity formats like WAV and MP3, you must choose the "FFmpeg-compatible files" filter in File > Open or File > Import > Audio and always use one of those import methods. To force FFmpeg to import native Audacity formats when using File > Recent Files or dragging in, add rules for those formats in . To force FFmpeg import irrespective of the filter when using File > Open or File > Import > Audio, uncheck "Attempt to use filter in OpenFile dialog first" in Extended Import Preferences as well as adding the rule for the format.
Export Multiple does not pass metadata common to all tracks to the Metadata Editor windows for each track. Workaround: Export by unchecking "Show Metadata Editor before export step" in Import / Export Preferences, then enter any tags common to all tracks at File > Open Metadata Editor... before exporting. Audacity will then silently add the common and automatically generated Track Title and Track Number tags for each exported file.
Import > Raw Data... imports files as noise if the Quality Preferences are set to 24-bit Default Sample Format. Set this to 16-bit or 32-bit float instead.
WAV and AIFF exports will fail without warning if you import a WAV or AIFF by , delete the file and its track then export new audio to the same file name and location as the deleted file. Workaround: Set the Preference in the above link to "Make a copy" of uncompressed files when importing.
(OS X) Audio files containing a backslash (\) in the name will fail "Could not open file" if you import them using File > Open... , File > Import > Audio... or File > Open Recent. This is a bug in wxWidgets. Workaround: Drag the file into the Audacity window instead.
Dither (corrective soft noise) is applied by default when it should not be applied when exporting to most formats having the same or higher bit depth than the project. For example, this occurs if exporting to 16-bit WAV, 16-bit FLAC or MP3 from a 16-bit project. OGG is unaffected. Workarounds: Set "High Quality" dither to "None" in the . To fix any files that have already been affected, see .
Metadata:
- Album art and lyrics in imported metadata are lost when exporting. Workaround: Copy the lyrics (or search for them online) then add them back to the exported file in your favorite media player. Extract the album art using a tag editor such as (or use or iTunes to search online for the art) then add the art back to the exported file using your media player.
- Tags other than the seven default tags will be rewritten as custom ID3 TXXX tags, which will cause them not to be seen in applications like Windows Media Player and iTunes. Common tag examples include "Album Artist", "BPM" and "Composer".
WMA and APE (Monkeys Audio): "Artist Name" is not seen on importing the file (Audacity bug)
- Other metadata import/export may not always be consistent. This may depend on the program that created the imported tags and the program used to read the exported tags.
On a fresh installation of Audacity or , the optional FFmpeg library cannot be used for import of native Audacity formats such as WAV, AIFF or MP3. Workaround: Open Preferences and click "OK".
When importing a MIDI track, the channel selection buttons to left of the track are not currently available.

Audacity 2.1.3

Audacity 2.1.3 was released on 17 March 2017.

Tip: You can use CTRL + F to search this page for different words to do with the issue you are looking for. Use Command - F on Mac.

Mac OS X

Audacity 2.1.3 provides partial support for macOS 10.12 (Sierra). Gatekeeper on macOS 10.12 can cause some plug-ins to go missing and other problems. Full details at .
Audacity 2.1.3 is for Intel Macs running OS X 10.6 and later and macOS. There are legacy versions for older OS X at .

Windows

Audacity 2.1.3 requires the CPU to support the instruction set which should be available on any Intel hardware produced after 2001 and any AMD hardware produced after 2003. To check what SSE levels your CPU supports, you can install . If your hardware only supports SSE, you may download Audacity 2.0.6 see the page on the Audacity Website.

Changes since previous version

Improvements

(Windows) is now supported (there should be no "Internal PortAudio Error" or failure to find any devices as long as the built-in audio devices are enabled).
(macOS) We now support Trackpad and Magic Mouse horizontal scroll without SHIFT key and Trackpad pinch and expand to zoom at the pointer.
PortAudio upgraded to r1966 - includes Windows 10 fix.

These links should be right, once the manual is moved

Added to Manual.
Added to Manual.

Bug Fixes

Many bugs from 2.1.2 fixed. Some examples:

Incorrect calculation of free disk space when using 24 bit audio.
(Windows) ReaPlugs plugins froze Audacity upon interacting with the plugin.
In 2.1.2, closing an effect window using the red close button at top left rather than the button on the dialog led to a crash.
(Mac and Linux) Nyquist effects were excessively slow when a label track was present. This fix has also speeded up Nyquist effects generally compared to Audacity 2.1.2.

Known Major Issues at Release

Use CTRL + F (COMMAND + F on Mac) to search this page for a word or phrase that describes the issue you want to know about.
You can also search the entire Audacity bugs database by multiple keywords at or view the .

Accessibility

Many, but not all parts of the Audacity interface are accessible on Windows and Mac (read the alert above about Mac) to those who can't use a mouse, and/or use a screen reader. It may be possible to make more of Audacity accessible in the longer term. For details, see
There are some accessibility bugs in the parts of Audacity that are accessible (or behavior may vary according to the specific screen reader).
- Toolbars that show disabled at View > Toolbars and are then re-enabled will launch undocked if Audacity has already been restarted. Workaround: perform View > Toolbars > Reset Toolbars before enabling any disabled toolbars.

Analysis effects

(Linux Ubuntu) On high resolution monitors, Plot Spectrum may initialize with the lower part of the display and the effect controls off the bottom of the monitor. As a Workaround: you could try holding ALT and pressing E on your keyboard to export a text file of the plot.

Application Launch

If Audacity 2.1.1 or earlier had the interface language set to "Simplified" (an optional English language that can remove menu items) then current Audacity will show an error on each launch "Language "en-simple" is unknown". No menu items will be hidden. Workaround: To prevent the error occurring at each launch, open Preferences then OK which changes the language to English.
- Simplified menus are also not currently supported in any other languages, but no errors are shown. Menu items that should be hidden will be shown starting with an "!" exclamation mark.
(Linux) If a Bluetooth audio device is in use on a PulseAudio system, Audacity may hang on launch on initial attempts, then after eventual launch Bluetooth will no longer work on the system.

Bugs requiring more investigation

Bass and Treble is a real-time preview effect but may sometimes not be openable when audio is already playing, or adjusting the effect controls may not be audible. You can still apply the effect to the audio as expected.
(Windows Vista or later) On upgrading to current Audacity from earlier versions, "error opening sound device" occurs when recording from the inbuilt sound device where there was no error in the previous Audacity with the same device configuration and operating system. Workaround: Use Transport > Rescan Audio Devices, or go to "Sound" in the Windows Control Panel and click OK. Note that if devices listed in Device Toolbar are disabled in "Sound" then the error is legitimate - you will need to enable those devices.

Chains

Audacity's built-in generators don't yet work intuitively with Chains. In particular, using the generator from the Generate Menu resets the Chain to use the settings last used from the Generate Menu. Plugin generators should work better with Chains.
Chains do not currently support export as AIFF, Other uncompressed files or any formats supported by FFmpeg.
For some effects (Equalization is a known example) parameters stored in Chains may not persist are not independent of the settings saved when running the effect from the Effect Menu. Changing the effect parameters from the Effect menu will thus change the effect parameters stored in the Chain and vice-versa. Workaround: For Equalization, you can use Save / Manage Curves... to save the required curve as a named curve, then choose that curve from the "Select Curve:" dropdown when setting the parameters for the Chain command.

Compiling

Audacity cannot build against wxWidgets compiled with STL. . There will be many errors of the form "cannot convert ‘const wxString’ to ‘const wxChar*". The best approach to a solution has not been decided, but if you would like to help with this please start a discussion on our mailing list.
(Windows) LADSPA effects cannot be categorized even when Audacity is compiled with USE_LIBLRDF defined.
(Linux) Audacity may not always compile against supported versions of libav or FFmpeg. Audacity 2.0.6 and later supports FFmpeg 1.2 to 2.3.x (or libav 0.8 to 0.10.x).

Effects

Plug-in Manager dialog:
- The dialogue may include some VST instruments or VST 3 effects but these are not supported so will not load even if enabled.
(macOS) After upgrading to 2.1.3 from previous Audacity, the Generate, Effect or Analyze Menu will show working duplicate copies of shipped Nyquist plug-ins if you have not yet deleted the old /Applications/Audacity/Plug-ins folder. Duplicates or single copies of other previously shipped plug-ins might appear even if they no longer exist, in which case they will fail to run.

Effects (Audio Units) (OS X)

All User Presets you select in the export dialog are exported at the same current settings you see in the effect, not at the preset's currently saved setting. This means that:
- To export a preset as saved you must first load it from User Presets before selecting it in the export dialog
- You cannot export more than one preset at a time at different settings.

Effects (Audio Units) (macOS)

AU effects cannot show graphical interface if Audacity is set in its Preferences to a language that uses comma as decimal separator. French however is a known exception to this.

Effects (LV2)

In LV2 effects that operate in textual mode, any saved User Presets are not recalled but reset the effect to default settings. In graphical LV2 effects, resetting to defaults or recalling a saved User Preset may not affect the controls.
Many LV2 plug-ins can only be used in Chains at default parameters. Attempting to edit the parameters in the Edit Chains > Select Command window may crash Audacity. MDA and swh LV2s are among those affected.
MDA LV2 plug-ins on macOS crash Audacity if applied in a Chain, even at default parameters.

Effects (Nyquist)

Nyquist effects may crash Audacity if used on extremely long selections containing more than 2^31 samples (just over 13.5 hours at 44100 Hz). Workaround Apply the effect to multiple shorter regions (you can drag the selection back on itself to create a region contiguous with the previous one).
Many Nyquist plug-ins will fail or may be sluggish if the track selection is too long, or could cause Audacity to crash. This is because the maximum selection length is limited by the amount of available ram, up to a maximum of 2 GB. Workaround: Unless you know that a particular Nyquist plug-in is safe to use with long selections, do not select more than about 1 hour of audio (44100 Hz sample rate) at a time. For higher sample rates the limit is proportionally less. If necessary, apply the effect to sections of 1 hour or less.

Effects (Real-time preview)

Real-time preview doesn't yet compensate for the latency many plugins introduce in order to provide smooth processing of audio. Real-time preview therefore may have small gaps in the audio, or timing artifacts may be audible when previewing multiple tracks. Compensation is applied when applying the effect, unless you disable compensation in the options for the effect.
(MacOS) Audacity CPU use will be 100% if a non-Real time preview effect (such as most built-in effects) or other modal dialogue is open at the same time as any Audio Unit effect or a graphical VST or LV2 effect. This is currently necessary to prevent a modal dialogue freezing Audacity when certain graphical VST or Audio Unit effects are running. Workaround: Excessive CPU use will not occur if you open the Manage button in the VST or LV2 effect then disable the option for graphical interface. Excessive CPU use will occur even with AU effects running in textual interface.

Effects (Vzmp)

(Windows) Installing the latest 1.7.1 "Queen Mary" Vamp plugins to any of the causes Audacity to crash when clicking any of the three "Add/Remove Plug-ins" menu items. You can use the 1.7 plug-ins from instead.

Effects (VST and Audio Units)

If the track rate or project rate is other than 44100 Hz, metering, equalization and time-based effects such as delay or reverb may give unexpected real-time preview results. Providing the project rate matches the track rate, then as a Workaround: click "Apply" in the effect, Edit > Undo in the Audacity menus, then preview.
(OS X and GNU/Linux): When saving VST effect presets, the FXP or XML file extension is not automatically offered in the file name, and not added by Audacity if you omit it. Make sure the extension you add is the same as that shown in the "File Format" drop-down menu, otherwise the preset will not be loadable.
(Windows and Mac OS X) When running VST effects in the controls of many plug-ins do not visibly respond when loading a preset file from the "Load" button

Effects and Analysis

(Windows 64-bit) There is no HKEY_LOCAL_MACHINE\SOFTWARE\ registry key where Audacity detects VST plug-ins. The HKEY_CURRENT_USER key searched is HKEY_CURRENT_USER\Software\VST\VSTPluginsPath instead of the expected HKEY_CURRENT_USER\SOFTWARE\Wow6432Node\VST.
"Play" or "Preview" features that are included in a few Nyquist plug-ins do not work on Mac OS X and may cause Audacity to freeze or crash on Linux.
"Classic Filters" which can be enabled at Add / Remove Plug-ins has no vertical scale for the graph.

Envelopes and Clips

A new clip created with Split New will often fail to drag back into its original track because the new clip may not be sample-aligned with the track it came from. If you CTRL-drag and the clip won't go back, you can Edit > Undo Time Shift to put the clip back. Disabling the "Enable dragging of left and right selection edges" might sometimes make it easier to drag the clip back.
If audio is created at other than time zero, a selection made in that clip could act on the sample before the first visually selected sample but not act on the last visually selected sample. If fully selecting such a clip or dragging to or from its left border, the first sample will appear unselected despite being selected.
In a few cases, pasting into a track containing clips could remove the envelope points in the clip being pasted into.

Exports

WAVEX (Microsoft) headers: GSM 6.10 files cannot be exported with WAVEX headers. Use WAV headers instead (note that GSM 6.10 only supports mono). A-Law and U-Law files with WAV headers may not be playable - use WAV headers instead. Choose "Other uncompressed files" then "Options..." to export to GSM 6.10 or A-/U-Law with WAV headers.
When exporting, tracks with Mute button down are excluded from the export mix as intended but currently no warning is provided about this.
(Linux) Exports using "M4A (AAC) Files" are very slow irrespective of the AAC encoder FFmpeg is configured to use. Workaround: choose (external program) when exporting, entering an appropriate path and command (for example, /usr/bin/ffmpeg -i - "%f") to run FFmpeg using Audacity's command-line encoder.

Imports and Exports

A-Law, U-Law and ADPCM export formats (also RF64 for PCM exports larger than 4 GB in size) must be chosen by selecting "Other uncompressed files", ensure the "Header" is "WAV (Microsoft)", then from the "Encoding" dropdown menu select your desired encoding. We may redesign the export list in due course to make these formats easier to find.
AAC exports using "M4A (AAC) Files (FFmpeg)" with project rate below 22050 Hz produce a zero bytes file if the linked to FFmpeg is configured with the default AAC encoder or libfaac. This will not affect the recommended builds of FFmpeg for Windows and Mac OS X which are built with libvo-aacenc. Workaround: You can export AAC below 22050 Hz using default-configured FFmpeg by choosing (external program) export instead.
After saving a project or importing audio, export always offers .aiff extension if you choose "Other uncompressed files", even if you choose other than AIFF header.

Imports and Exports (FFmpeg)

Custom FFmpeg Export dialog: It is necessary to save a preset before exporting it but there is no error message when exporting from an empty presets list and no advice in the interface that presets must be saved before export.
M4A (AAC) exports: The Quality Slider in "Specify AAC Options" has no effect if the FFmpeg library is built with the libvo-aac encoder, as are recommended builds of FFmpeg for Windows and Mac OS X. Workaround: You can specify a constant bit rate if you select "Custom FFmpeg Export". Click the Options... button, choose "mp4" in the formats list and "libvo_aacenc" in the codecs list, then set bit rate in bits per second. Up to 320000 bps (320 kbps) is supported. Given the alternative AAC encoders for FFmpeg also have problems as described in these notes, you can instead export as WAV and convert to AAC in iTunes on Windows and Mac.
M4A/MP4 (AAC): Artist and Year metadata is not exported or imported due to a bug in FFmpeg 2.2.2.

Installation

Although first installation of Audacity will default audio export and project save to the user's Documents folder, TXT and XML exports such as for labels files, Plot Spectrum or keyboard bindings may offer to export elsewhere.
- On Windows the offered location will be the Audacity installation folder - if you are not running Audacity as Administrator, you must change the export folder in order to save the file.
- On Mac, keyboard bindings will open first time in Applications if you have not already exported or saved any files. You must change the export directory to save if you are not running as administrator. If you cancel keyboard bindings export after it offers the Applications directory, all other TXT and XML exports will then default to saving in Applications.

Interface

Audacity does not alert you if it cannot write to its configuration or settings files or cannot remove its temporary settings files. The problem could occur due to interaction with a virus checker (this is most likely on Windows) or due to permissions problems.
- If the problem occurs, you might find a change you made in Preferences does not take hold, or that changing the settings in an effect then trying to apply the effect won't run the effect. On Windows, you will also find a build up of aud*.tmp or plu*.tmp files in Audacity's though these are noted at Help > Show Log... .
If Audacity is displayed on or mainly on a secondary monitor, some dialogs still open on the primary monitor instead of the secondary monitor.

(Windows) It is not yet possible to drag .lnk shortcuts to audio files or projects into Audacity, or to drag them to the Audacity executable's icon. Workaround: Use File > Open or File > Import > Audio, or double-click the shortcut to the .aup from Windows Explorer.
(Windows) The Audacity executable cannot be added to the Explorer "Open with" context menu if you have another version of Audacity on the system which is also called "audacity.exe". Workaround: either use the "Open with" dialogue to browse to the executable each time, or rename the executable to or some other unique name.
Dragging a clip or track up or down with Time Shift Tool does not scroll the project window when tracks exist out of view above or below the scroll. Workaround: Choose View > Fit Vertically before drag, or click and hold the piece to be dragged, use up or down arrow on the keyboard to scroll to the target track, then drag and release the clip or track.

LAME

(Mac) If you use Libraries Preferences to locate LAME manually, it is necessary to change the "File type:" filter to the choice for Dynamic Libraries or All Files in order to make libmp3lame.dylib selectable.

Label Tracks

The Tracks preference "Type to create a label" for typing in the focused label track doesn't work if you play audio then arrow-key into the label track to give it focus. Workaround: During playback, either use CTRL + B to add a label at the selection then type, or make a different selection in the label track then type.
The frequency range stored in a Region label created in a Spectrogram track with Spectral Selection enabled can only be modified by "Edit..." from the label's right-click context menu.
- Currently there is no validation on OK'ing the entered frequency value, so invalid values can be entered with unexpected results.

Launching Audacity

(Mac El Capitan) Audacity may not launch and a "Can't be opened" message will be displayed. Console log messages may refer to "Could not store lsd-identifiers file at /private/var/db/lsd/com.apple.lsdschemes.plist".
- Workarounds: Right-click or CTRL-click over Audacity.app, choose "Show Package Contents", then in the "MacOS" folder, double-click the "Audacity" executable. This will launch a Terminal window and Audacity will also launch. Alternatively you can try resetting the LaunchServices database by running the following Terminal command then rebooting:

sudo /System/Library/Frameworks/CoreServices.framework/Frameworks/LaunchServices.framework/Support/lsregister -kill -r -domain local -domain system -domain user ; killall Dock

Localization

For languages that use comma decimal separator, comma can only be used in effects on OS X by choosing that language in Audacity Preferences. This applies even if Mac system language is set to a comma-separated locale. On all systems, comma separator in effects after choosing a comma-separated language in Audacity Preferences requires that language to be installed on the system.
(Linux Ubuntu/Debian): If Ubuntu or Debian is installed in a right-to-left (RTL) language such as Hebrew or Arabic, most of the Audacity interface will be empty and thus unusable. The only guaranteed solution is to set system language to English in system settings then restart the computer and change Audacity language to Hebrew at Edit > Preferences..., "Interface". There will still be some less serious RTL issues.
(Linux) If system locale is set to Valencian and Audacity language in Interface Preferences is set to "System", Audacity will be in Catalan.

Miscellaneous platform-specific issues

(Mac OS X) If using Audacity when the "Hear" audio plug-in is running (or has been since boot), there will be excessive memory usage which could cause a crash: this appears to be due to buggy memory allocation in "Hear"
(Mac OS X) Very occasionally, users may find that after running Audacity, other media players don't produce any sound, or crash: to resolve this, set up your sound device in Apple Audio MIDI Setup to work in stereo, 16-bit, with a sample rate of 44100 Hz or 48000 Hz, and set the sample format and rate identically in Audacity. More help at:
(Linux) A playback or recording freeze, recording dropouts or fast playback may occur when using PulseAudio. Freezes may be caused by repeatedly starting and stopping playback or recording in quick succession (or by holding down the Play or Record button). Workarounds:

Mixer Board

Soloing or unsoloing a track in Mixer Board when in "Multi-track" Solo button mode may not immediately update the Solo button or waveform greyed/ungreyed state in the project window. Workaround: Click anywhere in (or task switch back to) the project window to refresh it (on Mac, you must click in the waveform or Track Control Panel or wait for the tracks to scroll when playing).
(Windows and Linux) If Mixer Board is open and more tracks are added so that the horizontal scrollbar must be used, newly added tracks may not be visible or newly deleted tracks may show as empty space. Workaround: To see all the tracks without redundant space, close and reopen the project then reopen Mixer Board.
If you change the meter range in Preferences this is not reflected in the Mixer Board meters until restart.

Modules

(Windows, Mac OS X) Modules originally shipped with obsolete 1.3.x versions of Audacity will cause Audacity to crash once at launch if they exist in a "modules" folder alongside the Audacity executable and are enabled in Modules Preferences.

Moonphase

Very occasionally, Audacity projects may reopen with missing block files, orphan block files and/or silenced audio data. There may be unwanted renaming or moving of AU files within the project. We believe having multiple projects open at once or having projects open in file manager programs are among the possible causes. See Bug:137 for more background to this. The AUP file may be saved with references to only a few of the AU files, again leading to "orphan block file" warnings. Sometimes the AUP file may not be found after saving and closing the project. Sometimes errors occur when saving the project or when Audacity autosaves, perhaps wrongly suggesting the disk is full or not writable (if this happens, try exporting the audio as WAV). Please write to our feedback address if you encounter any of the above symptoms. As many as possible of the following will help us enormously if you can attach them to your report: A copy of the saved AUP project file A copy of the AUTOSAVE (temporary project) file. This file is stored inside the "AutoSave" folder in Audacity's application data folder. For problems that occur when reopening or working in a project, the log file at Help > Show Log..

Playback and Recording

Append Record with Transport > Overdub (on/off) enabled may cause periodic playthrough of previously recorded audio. If you use the Stop button or SPACE to stop the previous recording instead of SHIFT + A (Stop and Set Cursor), this may reduce occurrences of the issue.
Clicking in Timeline Quick-Play plays from the editing cursor or plays the selection instead of playing from the click position as intended if Snap To is enabled and Selection Format is seconds, hh:mm:ss or dd:hh:mm:ss. As Workaround, click exactly above the yellow snap line.
Having mouse-dragged a selection in the waveform, you must now on Windows and Linux release the mouse before you can use SPACE to play or stop. This is because we now disallow shortcuts with mouse down for greater safety. On MacOS, shortcuts are currently still allowed with mouse down but this may change. The best current

Preferences

(Linux) If your project window is not maximised and you OK in Preferences with a label track present, the project window will be resized very narrow and there will be an assert in the terminal and possibly the project. Audacity will not be usable if a whited out assertion dialogue appears in the project window.

Projects

Importing an audio file or opening an AUP file may no longer permanently set the Save Project path to where the file came from. After closing the project, Save Project reverts to its previous path. Also if you import an audio file or open an AUP file after importing a MIDI or Labels file, Save Project may not change its path even temporarily.
There are currently no message box warnings when projects run out of disk space. If you run out of disk space when editing or recording, patches of silent or corrupted audio will appear, which will also be present if you save and reopen the project. Be aware that every effect applied to a complete track takes as much in disk space as if you were recording that entire track, and partial changes take proportional amounts of space, due to the ability to undo and redo. You can go to View > History and discard Undo levels to free up space.
(OS X and Linux) Entering a backslash "\" in a file name when saving a project gives a "Could not save project. Path not found." error.

Scrubbing and Seeking

Currently we allow Scrub or Seek to be paused, but there are two problems if Pause is used:
- Unlike during other paused playback, menu items cannot be clicked on in order to stop playback and carry out the requested action. If you pause scrubbing, press ESC, SPACE or the Stop button when you want to edit.
- If you start Scrub or Seek by menu item, Scrub Toolbar button or shortcut then engage Pause, move the mouse then release Pause, moving or dragging will not start Scrub or Seek. If you click and release in Scrub Ruler then engage Pause, move the mouse then release Pause, moving the mouse will not start Scrub.

Spectrograms

A created in Spectrogram view currently only works with the three specific . These effects can also only be used while in Spectrogram view and require that Spectral Selection be checked "on" in either the Track Control Panel for the track or in Spectrogram Preferences. All other effects and for example cut or delete will act on the entire spectrum in the time range regardless of the spectral selection.

Sync-Locked Track Groups

If Sync-Locked Track Groups are enabled but "Editing a clip can move other clips" in Tracks Preferences is disabled, sometimes not all sync-lock-selected tracks will be affected by Timeline-changing edits, and sometimes audio clips may be removed. You can Edit > Undo any unwanted changes.

Time Tracks

The lower and upper speed limits are not stored in the project, so will be restored to their default values of 90 and 110 respectively when reopening or recovering a project, or if removing a Time Track then undoing removal. Please make a note of the correct values before closing the project or the Time Track.

Timer Record

(Mac) The Timer Record setup, "Waiting" and "Progress" dialogs may show the date in UK dd/mm/yy format even if the language in System Preferences is set to "US English". The exact behaviour may depend on the machine or version of OS X.
(MacOS and Linux) If Timer Record is set to "Exit Audacity" after recording completes, a crash will be reported on exit. The project and/or audio file will be still be saved correctly.

Toolbars

Toolbars fail to arrange correctly when maximizing or restoring the size of the main project window. As Workarounds:Try resizing instead, for example resize larger until the toolbars fill the space, then maximize. If that doesn't help, select "View > Toolbars > Reset Toolbars" then manually rearrange the toolbars the way that you want them.
(Windows) Hover tooltips for toolbar buttons are only shown when the button is active (enabled).
Meter Toolbar vertical orientation is not remembered across sessions, and resizing the meters reverts from vertical to horizontal.

Audacity 2.x

Audacity 2.0.0

Changes between 1.3.14 and 2.0.0

Bug fixes

Interface

Imports and Exports

Effects and Analysis

Other miscellaneous bug fixes

Changes and Improvements

Summary of bug fixes and new features between 1.2.6 and 2.0.0

Bug Fixes

New features

Known Issues at Release

Headline issues

Large Projects

Problems reopening, saving or crashing in projects

Changes and Improvements

Program Launch

Installation

Imports and Exports

Interface

Playback and Recording

Effects and Analysis

Projects

Accessibility

Chains

Clips

Compiling

Label Tracks

Mixer Board

Preferences

Toolbars

Miscellaneous platform-specific issues

Bugs requiring more investigation

New features in Audacity 2.1.3 - Appendix

New shortcuts

Label Navigation

New features in Audacity 2.2.0 - Appendix

Sync-Lock

Audacity 2.2.1

Changes since previous version

Improvements

Waveform colorways

"Save Other" reverts to "Export" in the File menu

Bug Fixes

Supported Platforms

Windows

macOS / Mac OS X

Linux

Issues

Timer Record

(Linux) PULSE Audio

(Linux) MIDI

Accessibility

Bugzilla

New features in Audacity 2.2.1

Waveform colorways

"Save Other" reverts to "Export" in the File menu

Bug Fixes

Links

New features in Audacity 2.3.1

64-bit Mac build

Scrub Ruler

Advanced Vertical Zooming

Micro Fades

Regular Interval Labels improvements

Bug Fixes

Links

Audacity 2.3.2

Size and Checksums

Changes and improvements since previous version

Supported Platforms

Interactive Buglist Page

Highlighted Issues

Audacity 2.4.0

Checksums

Changes and improvements since previous version

Audacity 2.4.1

Checksums

Changes and improvements since previous version