Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Audacity 3.7.1 was released on Dec 12, 2024
Changelogs and release notes for historic versions of Audacity
Changelogs and release notes for current versions of Audacity
Audacity 3.7.3 was released on 13 Mar 2025
This is a hotfix release. It contains the following change:
Reverted deleting edges of clips being non-destructive due to a large range of unforseen side-effects.
This fixes joining clips becoming offset
This fixes cutting always creating new clips
This fixes "detach at silences" and "truncate silences" creating a bunch of new clips
Audacity 3.7.4 was released on 10 Jun 2025
This is a patch release. It contains the following changes:
Added a new welcome/what's new screen.
OpenVINO effects are now available on macOS. More about that can be found in this blogpost.
OpenVINO effects can now be found via the Get Effects button. (NB, this is a slow rollout - you may not see it there just yet at the time of release)
OpenVINO effects have been recategorized into their own category in the Effect menu. This also goes for the transcription and music generator feature, previously found in the Generate and Analyze menus, respectively.
Fixed a crash when closing a large unsaved project.
Fixed a crash when using real-time effects that activate delay compensation.
Fixed issue where Studio Fade Out creates a new clip when applied at the end of a clip.
Fixed incorrect waveform rendering on clipped audio.
Fixed unintended deletion of a clip when joining two clips with pitch adjustment.
Effect preview now works when the track is muted.
Fixed possible incorrect calculations in the Hamming window derivative. (Thanks, witwald!)
Fixed compilation issues on legacy macOS (Thanks, barracuda156!)
Audacity 3.7.5 was released on 5 Aug 2025
This is a patch release. It contains the following changes:
Beta: #8942 Windows on ARM support. (Thanks, Vasanth K (@vask2108) and Linaro!)
#9121 FLAC importer now supports 32-bit PCM. (Thanks, Dr. K. D. Murray (@kdm9)!)
#8851 Fixed crash when rendering spectrum view. (Thanks, Hailey Somerville (@haileys)!)
Fixed lost focus when registration window was closed.
Fixed crash on wav import. (when audio file is up to 7 ms long)
Fixed crash when using Macro Wizard.
, Updated libopus to 1.5.2, updated libcurl to 8.12.1, updated libpng to 1.6.50
Due to a lack of devices, the Audacity team has not tested the WoA version extensively. We did however check that basic things work while using a Windows VM in Parallels (on an ARM Mac). Please let us know if you encounter any strangeness.
#7008 MP3 exports: Renamed "Insane" to "Excessive".
#7486 Renamed "Split cut/delete" to "Cut/delete and leave gap".
#7293 Pasting clips no longer moves clips on other tracks if "editing clips can move other clips" is enabled.
#6851 Improved startup speed on systems with many audio devices.
#7186 Multi view: Fixed the hitbox of the x being misaligned with the visuals. (Thanks, Kurtsley)
#7468 macOS: Fixed VST presets path.
#7571 Adding, removing, replacing and reordering of effects now is undoable.
#7573 Closing a project upon turning a realtime effect stack on and off doesn't crash Audacity anymore.
#7610 Canceling a stereo track mid-operation no longer crashes Audacity.
#7385 Importing Opus files using libopus no longer shifts the audio data.
Changed the login flow for cloud uploads.
Windows
Audacity 3.7 is tested on Windows 10 & 11
Windows Vista, 7 and 8.1 may still work, but are no longer tested. We are not actively supporting these versions anymore, but still accept patches which improve compatibility with these versions.
macOS / Mac OS X
Audacity 3.7 is tested on macOS 14
Older macOS versions down to OS X 10.9 may still work, but is no longer tested. We are not actively supporting OSX versions anymore, but still accept patches which improve compatibility with these versions.
The Universal Binary may not work on various OSX versions. Use the Intel (x86_64) installer instead.
Linux
Linux support is tested with AppImages on Ubuntu 24.04.
Other Linux distributions should work, but aren't tested by the Audacity team.
On some distributions, libfuse2 needs to be installed for AppImages to work. See https://github.com/AppImage/AppImageKit/wiki/FUSE for more information.
Community-maintained distro-specific versions and other repackages (such as Flatpak) are often available, too.
Audacity 3.7.2 was released on 10 Mar 2025
This is a patch release. It contains the following changes:
#8290 Fixed a crash when applying some effects across multiple tracks if one track is empty.
#7672 Returned the "Residue" option in noise reduction. (Thanks, Christopher Rooney!)
Modules are now allowed to stick around when patch releases like this one are published. This means you likely won't need to update the OpenVINO again during 3.7.x.
When adding a realtime effect to a track, the effect settings are now opened immediately.
Added an infobox when saving a project in a new version breaks compatibility with an old one.
Added a preference to turn off automatic tempo detection.
When duplicating tracks, the duplicated tracks now have independent realtime effect instances.
Fixed range-selection beyond the edge of a clip being destructive.
, , , , , , Improved stability of cloud saving.
Fixed pasting content from a clip at the beginning of itself being offset in time.
macOS: Fixed AUSoundIsolation.
Fixed audacity continuing to scroll after letting go of the scrollbar.
Fixed black stripes appearing when zooming in while in the envelope or multi-tool.
Added a new "get effects" button next to the Upload Audio button.
Added UUID instance support. See for further info.
Fixed label texts using the wrong color in dark themes. (Thanks, GovindaMadhava!)
Fixed tracks being incorrectly drawn on high zoom levels using high precision trackpads.
Linux: Fixed FFmpeg loading in the Ubuntu 22.04 AppImage.
Fixed crossfading tracks on stretched clips.
You no longer need to click OK twice to exit the label editor in some edit states. (Thanks, Kurtsley!)
Playback quality is now the same as rendering quality by default.
Audacity 3.6.4 was released on 19 Sep 2024
This is a patch release. It fixes the following bugs:
#7310 Fixed another crash when exiting Audacity. (Thanks, Joe Souza!)
#7312 Fixed projects not being compacted on close.
Audacity 3.6.3 was released on 9 Sep 2024
This is a patch release. It fixes the following bug:
#7266 Fixed a crash when exiting Audacity. (Thanks, Joe Souza!)
Audacity 3.2.1 was released on 05 Oct 2022
This is a patch release for Audacity 3.2. It fixes some bugs.
#3686 Fixed Audacity crashing on startup on some systems.
Fixed a crash when applying Waves Berzerk Distortion Mono to a mono track.
Fixed a freeze when very quickly starting and stopping playback.
macOS: Homebrew FFmpeg installs are now found automatically.
macOS: Fixed Melda VST Plugin UI.
Building with VST3 support is now possible without Conan.
A full list of changes can be found .
Windows
Audacity 3.2 supports Windows 10 & 11
Windows Vista, 7 and 8.1 should still work, but are no longer tested.
Downloads for older versions are available on the page on the Audacity Website.
macOS / Mac OS X
Audacity 3.2 supports OS X 10.9 and later, and macOS.
There are legacy versions for older OS X at .
Linux
In addition to the traditional update path via package managers, Audacity 3.0.3 and onwards are distributed as an AppImage. The AppImage gets updated at the same time as the Windows and macOS versions, so if you collaborate with users on those platforms, you may want to use the AppImage over your distribution's package manager.
Linux support is tested on Ubuntu 20.04.
Other Linux distributions should work, but aren't tested by the Audacity team.
Audacity 3.2.5 was released on 1 Mar 2023
This is a hotfix release. It fixes the following bug:
Windows
Audacity 3.2 supports Windows 10 & 11
Windows Vista, 7 and 8.1 should still work, but are no longer tested.
Downloads for older versions are available on the page on the Audacity Website.
macOS / Mac OS X
Audacity 3.2 supports OS X 10.9 and later, and macOS.
There are legacy versions for older OS X at .
Linux
In addition to the traditional update path via package managers, Audacity 3.0.3 and onwards are distributed as an AppImage. The AppImage gets updated at the same time as the Windows and macOS versions, so if you collaborate with users on those platforms, you may want to use the AppImage over your distribution's package manager.
Linux support is tested on Ubuntu 20.04.
Other Linux distributions should work, but aren't tested by the Audacity team.
Audacity 3.0.5 was released on 29 Sep 2021.
Audacity 3.0.5 replaces all previous macOS versions.
This is a hotfix release that fixes a bug on macOS that could corrupt project files when being opened via cmd+o on languages where the decimal separator wasn't a dot.
Other than that, this release is identical to Version 3.0.3.
Windows
Audacity 3.0.5 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 3.0.5 is for Intel Macs running OS X 10.7 and later and macOS.
There are legacy versions for older OS X at .
Linux
In addition to the traditional update path via package managers, Audacity 3.0.3 and onwards are distributed as an AppImage. The AppImage gets updated at the same time as the Windows and macOS versions, so if you collaborate with users on those platforms, you may want to use the AppImage over your distribution's package manager.
Linux support is tested on Ubuntu Linux.
Other Linux distributions should work, but aren't tested by the Audacity team.
This page is an overview of prominent new functionality that has been introduced in Audacity 3.0.4
Version 3.0.4 is a hotfix release.
Fixed a bug with envelope points, which could multiply uncontrollably and cause Audacity to crash. In particular:
: Envelope points are multiplied when using Filter Curve EQ or Graphic EQ
: Filter Curve EQ will crash if there is an envelope point outside of the selection
With the release of Audacity 3.0.0 the project file structure of Audacity was changed significantly with the entire project contained in a single unified database file.
If you have already updated to any 3.x version you should already be aware of this.
But if you are updating from any earlier 2.x Audacity version please read Updating from Audacity 2.x to Audacity 3.x.
Audacity 3.x can usually open AUP files created in older 2.x.x versions of Audacity, but saving the project in 3.x will prevent it opening again in Audacity versions prior to 3.0.0.
Note that this will leave behind the old AUP file and its associated _data folder which you will probably want to delete to recover disk space.
Audacity version 3.x should be able to open projects from Audacity 1.1 onwards - but not from 1.0
Audacity 3.5.1 was released on 24.04.2024.
This is a hotfix release. It fixes the following bugs:
#6322 Fixed a crash on launch on macOS 11 and older.
#6324 Fixed the update notification looking for alpha versions instead of release versions.
#6321 Fixed a freeze when using macros on multiple files.
Windows
Audacity 3.5 is tested on Windows 10 & 11
Windows Vista, 7 and 8.1 may still work, but are no longer tested.
macOS / Mac OS X
Audacity 3.5 is tested on macOS 14
Any macOS version since OS X 10.9 may still work, but is no longer tested.
Linux
Linux support is tested with AppImages on Ubuntu 22.04.
Other Linux distributions should work, but aren't tested by the Audacity team.
On some distributions, libfuse2 needs to be installed for AppImages to work. See for more information.
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 Audacity 2.4.1.
There were no new features in 2.4.1 - this was an emergency bug-fix release for a critical P1 bug.
P1 - Lost/corrupted audio data after pasting into empty project
- detailed release notes for this release of Audacity
Audacity 3.6.1 was released on 19 Jul 2024
This is a hotfix release. It fixes the following bugs:
#6889 Fixed a crash when exporting multichannel audio.
#6882 Fixed a crash when pasting mono clips into stereo tracks.
#4763 (Accessibility) Made more values available when using the plain UI of plugins. (Thanks, David Bailes!)
#Prevented incompatible versions from opening projects created in 3.6.x.
#Fixed the dark theme sometimes having white corners in buttons.
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 .
2.2.1 is a very light release, basically a maintenance release, with one new exciting feature added. Plus we wanted to experiment with shorter release cycles.
Audacity 3.3.3 was released on 08 Jun 2023.
This is a hotfix release. It fixes the following bugs:
Fixed EQ not scaling properly when resizing the window.
Fixed the upload flow.
Audacity 3.4.1 was released on 08 Nov 2023.
This is a hotfix release. It fixes the following bugs:
Fix 24-bit recording.
Fix a crash with .aup importing.
#1477: Filter Curve EQ will crash if there is an envelope point outside of the selection
This fix re-introduces an earlier, but way less destructive bug:
bugzilla 208 / #1500: Some effects delete Envelope Control Points, or do not move them when timeline changes
Other than that, this release is identical to Version 3.0.3.
Windows
Audacity 3.0.4 requires the CPU to support the SSE2 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 CPU-Z.
If your hardware only supports SSE, you may download Audacity 2.0.6 see the Legacy Windows page on the Audacity Website.
3.0.4 does not support Windows XP.
You may try 2.2.2 on XP, but it is unsupported.
macOS / Mac OS X
Audacity 3.0.4 is for Intel Macs running OS X 10.7 and later and macOS.
There are legacy versions for older OS X at http://audacityteam.org/download/legacy-mac/.
Linux
Linux support is tested on Ubuntu Linux.
Other Linux distributions should work, but aren't tested by the Audacity team.
Improved Audacity's performance when many clips are present
Fixed a crash with detach at silences #2072
Fixed clip name corruption when applying effects to adjacent clips #1889
Fixed a crash with the time shift commands #2061
Fixed custom themes not working #2043
Other than that, this release is identical to Version 3.1.0.
Windows
Audacity 3.1.x requires the CPU to support the SSE2 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 CPU-Z.
If your hardware only supports SSE, you may download Audacity 2.0.6 see the Legacy Windows page on the Audacity Website.
3.1.x does not support Windows XP.
You may try 2.2.2 on XP, but it is unsupported.
macOS / Mac OS X
Audacity 3.1.x is for Intel Macs running OS X 10.7 and later and macOS.
There are legacy versions for older OS X at http://audacityteam.org/download/legacy-mac/.
Linux
Linux support is tested on Ubuntu Linux.
Other Linux distributions should work, but aren't tested by the Audacity team.
Fixed data loss on joining clips #2123
Fixed a crash with exporting resampled tracks #2136
Fixed a crash when opening projects with very small double values #2128
Windows
Audacity 3.1.x requires the CPU to support the SSE2 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 CPU-Z.
If your hardware only supports SSE, you may download Audacity 2.0.6 see the Legacy Windows page on the Audacity Website.
3.1.x does not support Windows XP.
You may try 2.2.2 on XP, but it is unsupported.
macOS / Mac OS X
Audacity 3.1.x is for Intel Macs running OS X 10.7 and later and macOS.
There are legacy versions for older OS X at http://audacityteam.org/download/legacy-mac/.
Linux
Linux support is tested on Ubuntu Linux.
Other Linux distributions should work, but aren't tested by the Audacity team.
3.0.5 does not support Windows XP.
You may try 2.2.2 on XP, but it is unsupported.
#4040 fixed the screenshot tool
#4019 selecting audio no longer marks the project as changed
#3693 a new toolbar with cut/copy/paste buttons has been added
#3216 Plain UI for VST3 effects no longer show MIDI CC parameters
#2620 the effects sidebar no longer can fill the entire screen
A full list of changes can be found on Github.
Windows
Audacity 3.2 supports Windows 10 & 11
Windows Vista, 7 and 8.1 should still work, but are no longer tested.
Downloads for older versions are available on the Legacy Windows page on the Audacity Website.
macOS / Mac OS X
Audacity 3.2 supports OS X 10.9 and later, and macOS.
There are legacy versions for older OS X at http://audacityteam.org/download/legacy-mac/.
Linux
In addition to the traditional update path via package managers, Audacity 3.0.3 and onwards are distributed as an AppImage. The AppImage gets updated at the same time as the Windows and macOS versions, so if you collaborate with users on those platforms, you may want to use the AppImage over your distribution's package manager.
Linux support is tested on Ubuntu 20.04.
Other Linux distributions should work, but aren't tested by the Audacity team.
Windows
Audacity 3.3 is tested on Windows 10 & 11
Windows Vista, 7 and 8.1 should still work, but are no longer tested.
macOS / Mac OS X
Audacity 3.3 is tested on macOS 12 & 13
OS X 10.9 and onwards should still work, but are no longer tested.
Linux
In addition to the traditional update path via package managers, Audacity is distributed as an AppImage. The AppImage gets updated at the same time as the Windows and macOS versions, so if you collaborate with users on those platforms, you may want to use the AppImage over your distribution's package manager.
Linux support is tested with AppImages on Ubuntu 20.04 & 22.04.
Other Linux distributions should work, but aren't tested by the Audacity team.
Audacity is not yet compatible with Conan 2.
#4637 Issues with selection and time toolbars on Linux packages.
#4639 Missing duration input in generators on Linux packages.
#4646 Potentialy extreme memory usage with Jack host.
Windows
Audacity 3.3 is tested on Windows 10 & 11
Windows Vista, 7 and 8.1 should still work, but are no longer tested.
macOS / Mac OS X
Audacity 3.3 is tested on macOS 12 & 13
OS X 10.9 and onwards should still work, but are no longer tested.
Linux
In addition to the traditional update path via package managers, Audacity is distributed as an AppImage. The AppImage gets updated at the same time as the Windows and macOS versions, so if you collaborate with users on those platforms, you may want to use the AppImage over your distribution's package manager.
Linux support is tested with AppImages on Ubuntu 20.04 & 22.04.
Other Linux distributions should work, but aren't tested by the Audacity team.
Audacity is not yet compatible with Conan 2.
Windows
Audacity 3.2 supports Windows 10 & 11
Windows Vista, 7 and 8.1 should still work, but are no longer tested.
Downloads for older versions are available on the Legacy Windows page on the Audacity Website.
macOS / Mac OS X
Audacity 3.2 supports OS X 10.9 and later, and macOS.
There are legacy versions for older OS X at http://audacityteam.org/download/legacy-mac/.
Linux
In addition to the traditional update path via package managers, Audacity 3.0.3 and onwards are distributed as an AppImage. The AppImage gets updated at the same time as the Windows and macOS versions, so if you collaborate with users on those platforms, you may want to use the AppImage over your distribution's package manager.
Linux support is tested on Ubuntu 20.04.
Other Linux distributions should work, but aren't tested by the Audacity team.
#5473 Exporting multiple files honors sample rate settings again.
#5498 Ctrl+J is now a standard shortcut for joining clips.
#5389 Stereo tracks no longer randomly split into mono.
#5007 When exporting a file, the file extension is now always added (except for custom FFmpeg and external program exports).
#5516 Fix a crash when exporting Opus with older CPUs that don't support AVX.
Windows
Audacity 3.4 is tested on Windows 10 & 11
Windows Vista, 7 and 8.1 may still work, but are no longer tested.
macOS / Mac OS X
Audacity 3.4 is tested on macOS 12 - 14
Mac OS X 10.9 and onwards may still work, but are no longer tested.
Linux
In addition to the traditional update path via package managers, Audacity is distributed as an AppImage. The AppImage gets updated at the same time as the Windows and macOS versions, so if you collaborate with users on those platforms, you may want to use the AppImage over your distribution's package manager.
Linux support is tested with AppImages on Ubuntu 22.04.
Other Linux distributions should work, but aren't tested by the Audacity team.

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.
Release 2.2.1 is mainly a maintenance release. Soon after the release of 2.2.0 we discovered some problematical bugs in Audacity:
Bug #1767 - Opening a second project from Mac's Finder produces a second inaccessible instance of Audacity
Bug #1770 - Crash applying certain chain files
Bug #1783 - Preview fails when selection extends before zero
- Auto-scroll stopped working in 2.2.0
- Using File > Open to import audio gives wrong zoom level and no scroll bar slider
Audacity 2.2.1 - detailed release notes for this release of Audacity
#3696 Improved accessibility of the meters
#3769 Fixed a crash when editing some macro parameters
#3792 Fixed some play commands getting stuck in play mode
#3670 Audacity no longer quietly discards changes in realtime effects but instead asks if you want to save before quitting
#3838 Plugin scanning now lets you skip individual plugins if scanning gets stuck on them
#3980 Plugin scanning no longer produces "Audacity crashed" windows when a plugin fails validation, and no longer shows the plugins in the macOS dock during validation
#3883 Fixed an issue with labels losing focus on macOS Ventura
Fixed various plugin-specific issues
A full list of changes can be found on Github.
Windows
Audacity 3.2 supports Windows 10 & 11
Windows Vista, 7 and 8.1 should still work, but are no longer tested.
Downloads for older versions are available on the Legacy Windows page on the Audacity Website.
macOS / Mac OS X
Audacity 3.2 supports OS X 10.9 and later, and macOS.
There are legacy versions for older OS X at http://audacityteam.org/download/legacy-mac/.
Linux
In addition to the traditional update path via package managers, Audacity 3.0.3 and onwards are distributed as an AppImage. The AppImage gets updated at the same time as the Windows and macOS versions, so if you collaborate with users on those platforms, you may want to use the AppImage over your distribution's package manager.
Linux support is tested on Ubuntu 20.04.
Other Linux distributions should work, but aren't tested by the Audacity team.
This page is an appendix to New features in Audacity 2.2.0. 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 Audacity 2.2.0.
used to be a button in the edit toolbar. Now instead you enable or disable it from Tracks > Sync-Lock Tracks.
This should make it easier for users to avoid setting Sync-Lock on by accident by inadvertently nudging the button.
Left-clicking on a will delete the clip line, merging the two neighbouring clips.
Now if you hover over the Clip line and press and release the Esc key you can then click on the clip line and select from there by dragging, without deleting the clip line and merging the clips.
The cursors on Mac used to be 16x16 pixels. Now they are higher resolution and use 32x32 pixels.
Buttons in the track control panel now highlight when hovered over. The thumb on sliders now highlights when the mouse is over it.
The Esc key now cancels all click-and-drag actions. It also chooses among overlapping mouse click targets, which is especially useful in the Multi-Tool.
The default behavior now for and for edits requiring a selection is that if you click on them without a selection, a dialog now shows explaining that you need to make a selection. Here an attempt to apply Fade effect was made without first selecting some audio.
The colors of the are now customisable using custom . This can give greater clarity to the spectrograms. In the example below the high intensity greens stand out better than the reds in the standard spectrogram.
Previously created special 'Left' and 'Right' tracks. Now splitting creates mono tracks, panned left or panned right. Below is a screenshot of a stereo track split into two tracks, one panned left, one panned right.
Major overhaul of the Audacity manual, including more work on clickable images.
The in the manual have more extensive tooltips and more clickable areas.
Over 300 new or modified images for this edition of the manual.
- detailed release notes for this release of Audacity
Audacity 3.6.2 was released on 2 Sep 2024
This is a patch release. It adds a "Legacy" effects section containing the old Limiter, Compressor and Classic Filters.
It also fixes the following bugs:
#6995 Fixed a hang after undoing.
#6912 Fixed the zero line going missing.
#6927 Fixed envelope appearance for clips offset from 0.
Fixed Audacity turning white on some systems.
Fixed the pitch indicator disappearing on Linux when hitting double digits.
Fixed cutting not putting clips into the clipboard.
Fixed pasting sometimes resetting the clip name.
Fixed the track header UI breaking when resizing channels in a stereo track.
, Fixed LV2 plugin detection on macOS and Windows.
Fixed Labeled Audio operations.
, Fixed Cloud projects sometimes not opening.
Fixed a bug regarding stereo-to-mono splitting.
Fixed a bug causing tracks with master effects sometimes only exporting silence.
, Fixed multi-channel OGG and Wavpack import.
Fixed a crash after recording long sessions.
Fixed a crash when failing to load a cloud project.
Fixed Audacity maxing out the CPU when minimized.
Fixed the "editing clips can move other clips" preference desynchronizing multiple tracks.
Fixed Stereo tracks sometimes splitting into mono when opening a project.
Other changes:
The time track range now is a single dialog.
Reverted the behavior of selection change when importing a clip to the previous behavior.
Audacity 3.3.1 was released on 28. Apr 2023.
This is a hotfix release.
#4600 Fixed cut lines massively inflating project size.
Fixed custom project sample rates being uneditable.
Fixed crash reporting being disabled.
Audacity now shows an error if the upload to audio.com exceeds file size limits.
Fixed an error in calculating channels when uploading to audio.com.
Windows
Audacity 3.3 is tested on Windows 10 & 11
Windows Vista, 7 and 8.1 should still work, but are no longer tested.
macOS / Mac OS X
Audacity 3.3 is tested on macOS 12 & 13
OS X 10.9 and onwards should still work, but are no longer tested.
Linux
In addition to the traditional update path via package managers, Audacity is distributed as an AppImage. The AppImage gets updated at the same time as the Windows and macOS versions, so if you collaborate with users on those platforms, you may want to use the AppImage over your distribution's package manager.
Linux support is tested with AppImages on Ubuntu 20.04 & 22.04.
Other Linux distributions should work, but aren't tested by the Audacity team.
Audacity is not yet compatible with Conan 2.
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 .
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.










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.
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).
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.
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)
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 Bug #2009
Can't adjust Time Track envelope when Logarithmic scale selected - see Bug #1832
Mixer Board does not automatically update when tracks added or removed - see
Regular Interval Labels fails - see
Windows: Regular Interval Labels on multiple tracks produces multiple labels - see
Multiple problems with Change Pitch - see
Mac: Audacity crashes when right clicking in label after copying label text to ano app - see
Linux: Assert on recording or generating when main Window minimized - see
Windows: Macros - "ExportMP3 before" and "ExportMP3 after" overwrite causing non-critical data loss - see
Macros: Change Pitch in a Macro does not remember speed parameter setting - see
Audacity 2.3.1 - detailed release notes for this release of Audacity
A new command has been added to the Help menu: Help > Reset Configuration.
This resets your Audacity configuration, preferences (except Extended Import), export settings and toolbars, to default settings.
Be aware that this command acts immediately with no dialog and no choice of actions or chance to abort.
Undo is not available for this command.
User presets in Effects, Generators and Analyzers are left untouched, as are any Macros you may have created and plug-ins.
Audacity now supports LAME's gapless playback info, allowing MP3s to be exported and imported without additional padding.
Other applications that support the LAME tag, for example audio player applications, will be able to read MP3 files exported by Audacity without the padding.
In less than a month we have foxed a further 29 bugs in this maintenance release.
Here is a small selection of some of the most important.
P1 2442 - Windows: Crash when importing (or editing) to a disk with insufficient disk space available
P1 2449 - Mac: Attempting to export as M4A(AAC) yields an FFmpeg error message
P1 2457 - Windows: WAV Export runs 6 to 7 times slower than on 2.3.3
P1 - Macros with Nyquist effects don't apply saved parameters
P1 - Mix Stereo down to Mono fails if space at start of track.
P1 - Windows: with an empty rules list in "Extended Import" prefs - Tab or Home crashes Audacity
P1 - Mac: AudioUnit effects are not applied if you initially use the preview
P1 - Win/Linux: OPUS import fails
P2 2403 - Undocking meter toolbars while playing/recording results in a frozen meter
P2 2408 - A region label gets split on inserting audio when Sync-lock is turned on
P2 2418 - Time toolbar displays incorrect time if project rate isn't 44100
P2 - Time toolbar: Opening and closing preferences resets format to hh:mm:ss
P2 - Nyquist Effects do not display a Progress Dialog if run from a Macro.
P2 - Real-time effects - Enable checkbox has no effect
P2 - Mix and Render to New Track selects left channel of new stereo track
P2 - Mac/Linux: Old (PowerPC) projects open flat-lined or with corrupted display on Intel machines
P2 - audacity 2.3.3 config with Spectral Selection toolbar corrupts lower dock in 2.4.x and can crash
P2 - Possible crash when clearing text field in Gain dialog
Audacity 2.4.2 - detailed release notes for this release of Audacity
#4352 Added a new effect: Shelf Filter.
Added an initial (beta) version of Beats and Bars. See Aligning music to beats and bars for further info.
#4414 reworked the bottom toolbar dock:
Project Sample Rate is now found in Audio Setup -> Audio Settings (formerly known as Project Rate).
The Snapping Toolbar (formerly known as Snap-To) is now independent of the Selection Toolbar.
Added a new Time Signature Toolbar (beta). It is hidden by default. See for further info.
#4212 Improved Zooming behavior slightly (more to come in the future).
#4393 Added a new ruler, Linear (dB). This ruler goes from 0 dBFS to -∞ dBFS and better reflects the volume as shown in the recording/playback meters.
#3820 When copying clips between projects, you now can choose between whether to copy smart clips or just the visible portion.
#4133 added a delete button to the Cut/Copy/Paste toolbar.
FFmpeg 6 (avformat 60) is now supported.
Moved from Breakpad to Crashpad.
Extracted various libraries from within Audacity.
A full list of changes can be found on Github.
Windows
Audacity 3.3 is tested on Windows 10 & 11
Windows Vista, 7 and 8.1 should still work, but are no longer tested.
macOS / Mac OS X
Audacity 3.3 is tested on macOS 12 & 13
OS X 10.9 and onwards should still work, but are no longer tested.
Linux
In addition to the traditional update path via package managers, Audacity is distributed as an AppImage. The AppImage gets updated at the same time as the Windows and macOS versions, so if you collaborate with users on those platforms, you may want to use the AppImage over your distribution's package manager.
Linux support is tested with AppImages on Ubuntu 20.04 & 22.04.
Other Linux distributions should work, but aren't tested by the Audacity team.
Audacity is not yet compatible with Conan 2.
Audacity 3.4 was released on 02 Nov 2023
Audacity 3.4 adds a musical view, time stretching and a new exporter.
Audacity now features several music related features, such as switching between hh:mm:ss time and Beats & Measures, and time-stretching clips to align them to a song's tempo.
Details can be found in the following pages:
Hold Alt (macOS: Option) while hovering over the top third of a clip edge to stretch it.
More info:
Audacity now features a new export window with easier access to options such as sample rate and custom mapping (for 5.1 or 7.1 audio). Additionally, the "Browse" button uses the native file browser now!
And in very related news, Opus files are now natively supported.
For MP3, Audacity now always uses Joint Stereo mode, which always delivers the best possible quality.
The spectrogram colors are now perceptually uniform, and the colormap has gotten a name: Roseus. It also can be used for dataviz outside of Audacity, see for more info!
Simplified pasting logic
implements a time stretching algorithm originating in . It currently is one of the highest-quality time stretching algorithms for music on the market.
Audacity now uses Conan 2.
Continued extracting code into libraries and modules.
--nogap metadata no longer is ignored
fixed a crash with LV2 plugins (thanks jfroyall!)
fixed some crashes related to macros
A can be found on Github.
Windows
Audacity 3.4 is tested on Windows 10 & 11
Windows Vista, 7 and 8.1 may still work, but are no longer tested.
macOS / Mac OS X
Audacity 3.4 is tested on macOS 12 & 13, and should support macOS 14
OS X 10.9 and onwards may still work, but are no longer tested.
Linux
In addition to the traditional update path via package managers, Audacity is distributed as an AppImage. The AppImage gets updated at the same time as the Windows and macOS versions, so if you collaborate with users on those platforms, you may want to use the AppImage over your distribution's package manager.
Linux support is tested with AppImages on Ubuntu 22.04.
Other Linux distributions should work, but aren't tested by the Audacity team.
Audacity 3.0.0 was released on 17th Mar 2021.
Audacity 3.0.0 replaces all previous versions.
Over 150 bugs fixed since 2.4.2
Full details of new features in the visual guide to
Windows
Audacity 3.0.0 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 3.0.0 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.
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.2 that we have fixed for 3.0.0
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.
Below are listed what we believe are the most common and important issues with 3.0.0 for most users.
Accessibility
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 3.1.3 was released on 23. Dec 2021.
Audacity 3.1.3 is a patch release for Audacity 3.1.
It improves the following aspects:
Improved performance. Loading in projects especially should now be up to 50x faster compared to 3.1.0.
Added snap guides when resizing clips
Added new shortcuts for looping: Shift+L for "Set Loop to Selection", Shift+Alt+L for "Clear Looping Region"
Added a new selection region indicator in the timeline (identical in function as the one found pre-3.1, but with updated visuals)
Changed error messages to look less like a crash report
Re-added the Quick Play indicator (green triangle and line) that got lost during 3.1.0 development
Fixed Play-at-speed not updating the playback speed dynamically
Fixed looping regions being created unintentionally when attempting to use Timeline Quick Play
Fixed looping sometimes playing the wrong audio
Fixed a bug that could cause data-loss when joining multiple clips
Fixed scrub preview visibility
Fixed a bug when trying to locate FFMPEG manually
Fixed a glitch with Loop Playback
Fixed a crash and a macOS-specific bug when renaming sync-locked clips using a dialog box. ,
Fixed a crash when releasing a clip handle
Fixed a freeze when closing Audacity with the logging window open
Fixed a crash when loading a saved project using certain compilers
Fixed a crash on paste after running macros
Fixed a crash when cancelling a nyquist prompt
Windows
Audacity 3.1.x 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 3.1.x 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.
Other Linux distributions should work, but aren't tested by the Audacity team.
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.
There is a new Tracks Menu item "Type to Create a Label (on/off)" (turning it off prevents shortcuts accidentally creating labels in the focused label track). There is also an option in Tracks Preferences to make this setting.
When enabled (default), if there is already a label track that has the yellow focus border, you do not need to use "Add Label at Selection" or its CTRL + B shortcut to create a new label. Just type your required label text to create a new label at the position of the editing cursor or selection region. If the label track does not have focus, use the UP or DOWN arrow keys on your keyboard to move focus into the label track.
If you turn this option off, typing never creates a label in the focused label track. This lets you use shortcuts (for example, transport shortcuts to play audio related to the editing cursor or selection) without accidentally creating an unwanted label. When you want to create a new label, use "Add Label at Selection" or CTRL + B or "Add Label at Playback Position" CTRL + M.
There are new Recording Preferences settings to control the naming of recorded tracks:
Use Custom Track Name: Use this to replace Audacity's default name of Audio Track with one of your own choosing.
Add Track Number: Appends a track number to each new track name.
Add System Date: Appends the date to each new track name, in year-month-day format.
There is a new export option when exporting to MP3 "Force export to mono".
Enabling this checkbox always produces a mono (single channel) MP3 file, mixing down to mono if the Audacity content is stereo or would otherwise produce a stereo file. This is useful if stereo export is not required, because for variable or average bit rate or a Preset other than "Insane", the bit rate and hence the exported file size will be less than for stereo export, but with comparable quality to stereo. This is possible because fewer bits are needed for mono encoding than stereo.
If you are exporting only one mono Audacity track and that track is panned to center, Audacity will still automatically export as mono without the need to enable the new option.
Both Change Pitch and Change Tempo have a new option called "Use high quality stretching (slow)".
If this checkbox is enabled, the same high quality algorithm is used that is used in the Sliding_Time_Scale_-_Pitch_Shift|Sliding Time Scale / Pitch Shift effect. Change Tempo will process much more slowly if this checkbox is enabled, but will retain the complete content. For small to moderate tempo changes, the resulting quality will usually be higher, especially with percussive music (such as piano music).
The "Ratio" setting in Compressor effect now lets you use higher precision. "Ratio" now allows a setting between 1.1 and 10, with 0.1 precision (formerly, the minimum was 1.5, and the smallest increment was 0.5).
The Bass and Treble effect now supports Real-time preview - effect settings can be changed while playing and listening to the result in real-time. As with other real-time preview effects, the Enable checkbox acts like a live "Bypass" control, so that unchecking the checkbox Enable lets you hear the audio "dry" without the effect applied.
Bass and Treble also has a new checkbox item "Link Volume control to Tone controls". Enabling this automatically adjusts the Volume control for changes to Bass and Treble so as to lessen the change in the resulting output level.
Audacity now supports Mac Trackpad gestures for two-finger horizontal scroll and pinch/expand to zoom the waveform in or out at the pointer position. Previously a modifier key had to be used to perform these actions on a Trackpad.
Horizontal scrolling and pinch/expand should also work on most touchpads on Windows machines, but you may need to apply this or to install special drivers for your touchpad.
Back to: - detailed release notes for this release of Audacity
Audacity 3.4.2 was released on 16 Nov 2023.
This is a hotfix release. It fixes the following issues:
#5568 Fix a crash when opening projects with zero-length clips.
#5032 When exporting a file, the sample rate of the tracks is now considered, and last-used sample rate is remembered.
Copy-pasting behavior now pastes into clips again by default. This can be changed via Preferences -> Track Behavior -> Always paste audio as new clips.
#Mix and render now also resets the gain for the resulting track.
#Fix clips shifting to the right when effects are applied to them.
#Fix clicks occurring when overdubbing a project with muted tracks.
#Fix files being exported without a file extension in rare cases.
#Show all sample rates possible for MP2 exports.
#Fix pasting into labels.
#Fix a crash when clearing loops.
#Fix copying when "select all audio if selection required" is enabled.
##Fix GTK detection and compilation for wxWidgets 3.2.4.
Fix Nyquist-related crashes.
#Fix EQs in macros.
#Fix a crash when closing Audacity.
#Fix builds on arm64/armhf.
#Use dladdr when possible to setup modules paths
Windows
Audacity 3.4 is tested on Windows 10 & 11
Windows Vista, 7 and 8.1 may still work, but are no longer tested.
macOS / Mac OS X
Audacity 3.4 is tested on macOS 12 - 14
Mac OS X 10.9 and onwards may still work, but are no longer tested.
Linux
In addition to the traditional update path via package managers, Audacity is distributed as an AppImage. The AppImage gets updated at the same time as the Windows and macOS versions, so if you collaborate with users on those platforms, you may want to use the AppImage over your distribution's package manager.
Linux support is tested with AppImages on Ubuntu 22.04.
Other Linux distributions should work, but aren't tested by the Audacity team.
Audacity 3.6 was released on 16 July 2024, together with Muse Hub 2.0.
Audacity now features master effects. Master effects are effects which apply to the entire project at once. More information can be found at Using master effects & realtime effects.
A new compressor and limiter has been added, replacing the previous versions. A gain reduction history has been added to these effects when they're used as a .
Factory Presets suitable for a wide range of use cases for these effects have been provided by Vladislav Isaev and Marek Iwaszkiewicz, available via the Presets & Settings button.
Audacity now features new and improved dark and light themes. You can switch between themes via Preferences -> Interface. The theme previously used still is around as the Classic theme, and themes even older than that can be optionally from .
Updated instructions on creating custom themes can be found .
Audacity is now quite a bit snappier than before, especially when working on larger projects and on larger screens.
Added FFmpeg 7 support.
You now can paste audio files into Audacity using Ctrl+V.
Alternative waveform colors are now themeable by custom themes.
Removed the track name overlay preference and the "blend themes" preference.
When recording to a new track, the track is now scrolled back into view again.
The macro manager no longer shows parameterless actions as editable. (Thanks, Davi Nonnenmacher!)
Pressing Esc in some preference dialogs no longer saves them.
Fixed stray orange lines in the high contrast theme.
Windows
Audacity 3.6 is tested on Windows 10 & 11
Windows Vista, 7 and 8.1 may still work, but are no longer tested. We are not actively supporting these versions anymore, but still accept patches which improve compatibility with these versions.
macOS / Mac OS X
Audacity 3.6 is tested on macOS 14
Older macOS versions down to OS X 10.9 may still work, but is no longer tested. We are not actively supporting OSX versions anymore, but still accept patches which improve compatibility with these versions.
The Universal Binary may not work on various OSX versions. Use the Intel (x86_64) installer instead.
Linux
Linux support is tested with AppImages on Ubuntu 22.04.
Other Linux distributions should work, but aren't tested by the Audacity team.
On some distributions, libfuse2 needs to be installed for AppImages to work. See for more information.
audacity-win-3.0.0.exe (application/x-msdownload) - 29378296 bytes
SHA-256 6a0cfed327b00cf8fefef4bd5c8ba85b5364f3e56345772410572f2d821ca14d
audacity-macos-3.0.0.dmg (n/a) - 41328807 bytes
SHA-256 f769a9e8c0f2352171933339681616ddab43ca6d7b688918e5af8bd1382a0fad
audacity-minsrc-3.0.0.tar.xz (n/a) - 13308836 bytes
SHA-256 d3bb1358b930ea4ef935ed83cc5a0f47006565762c5667c2fb376c6535876a6a
audacity-win-3.0.0.zip (application/x-zip-compressed) - 12507745 bytes
SHA-256 63c23df0731d02327ca964f01e0bd2ff533fa189ef18402e29c3e3992038217d
audacity-manual-3.0.0.zip (application/x-zip-compressed) - 23118171 bytes
SHA-256 9e3ab6ae3455db8be98e26cc09d90a89901e37b8eca671949f9959bbc1c7c2e83.0.0 does not support Windows XP.
You may try 2.2.2 on XP, but it is unsupported.
Serious bugs and less serious bugs.
ID
P
Status
Summary
P3
RESOLVED
Plug-ins listed in reverse alphabetic order in Plug-ins Manager
3.1.x does not support Windows XP.
You may try 2.2.2 on XP, but it is unsupported.




#5014 Added cursors trimming and stretching left and right, and changed the I-beam cursor to be less similar to either
#4448 When importing audio, the project sample rate no longer changes
New defaults: The Time Signature toolbar now gets shown, the solo button is set to multi-track mode, time tracks have a wider starting range
#5291 Unsquished the Audacity logo found in some places of the app
#2330 Clicking on the border of two clips no longer merges them
#443 Built-in Opus support.
#4677 Accessibility: GUI can be disabled again for VST2 plugins (thanks, David Bailes!)
#4988 Accessibility: Restored window control IDs, improving NVDA compatibility (thanks again, David Bailes!)
#4872 fixed a crash on launch on OSX 10.9 (thanks, René Bertin!)
#2530 Overdubbing on Windows no longer fails with WASAPI with default Recording device.



Scripting: Added GetInfo: Type=Selection. (Thanks, Jonatã Bolzan Loss!)
Added an Extras > Export > Export Selected Audio option.
Import Raw: Added support for offsets larger than 2 GB.
Redesigned the "what's new" dialog.
Added an option to the View menu to show/hide RMS in waveforms.
OpenVINO AI effects can now be downloaded from audacityteam.org/download/openvino/
#5626 Fixed the quality slider for Ogg export on Linux. (Thanks, Devpriya Nalin!)
#6875 Fixed a bug which could open a project with the wrong sample rate.
Various compiler warning fixes and OpenBSD build fixes. (Thanks, Brad Smith!)
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 New features in Audacity 2.3.2
Windows
Audacity 2.3.2 requires the CPU to support the SSE2 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 CPU-Z.
If your hardware only supports SSE, you may download Audacity 2.0.6 see the Legacy Windows page on the Audacity Website.
2.3.2 does not support Windows XP.
You may try 2.2.2 on XP, but it is unsupported.
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 http://audacityteam.org/download/legacy-mac/.
Linux
Linux support is tested on Ubuntu Linux.
Audacity may compile on Gentoo, Debian, Mint.
Audacity does not currently compile on SuSE Linux.
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.
Serious bugs and less serious bugs.
You can choose various combinations of these. However, there are probably too many minor bugs and too much detail on that dynamic buglist page for most users.
We do use this detail in our own QA work.
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
ID
P
Status
Summary (2 tasks)
P3
NEW
Linux: PULSE-AUDIO issues. Freeze repeatedly starting/stopping streams
P3
RESOLVED
Windows: DirectSound Sound Activated Recording does not record correctly or pauses permanently after 12 seconds
Click on the bug numbers to see work done on these bugs.
Over 30 bugs fixed since 2.4.1
Full details of new features in the visual guide to New features in Audacity 2.4.2
Windows
Audacity 2.4.2 requires the CPU to support the SSE2 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 CPU-Z.
If your hardware only supports SSE, you may download Audacity 2.0.6 see the Legacy Windows page on the Audacity Website.
2.4.2 does not support Windows XP.
You may try 2.2.2 on XP, but it is unsupported.
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 https://audacityteam.org/download/legacy-mac/.
Linux
Linux support is tested on Ubuntu Linux.
Audacity may compile on Gentoo, Debian, Mint.
Audacity does not currently compile on SuSE Linux.
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.
Serious bugs and less serious bugs.
You can choose various combinations of these. However, there are probably too many minor bugs and too much detail on that dynamic buglist page for most users.
We do use this detail in our own QA work.
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
ID
P
Status
Summary (2 tasks)
P2
RESOLVED
Mac: Keyboard tabbing in Timer Record stuck in left hand panel.
P3
NEW
Linux: PULSE-AUDIO issues. Freeze repeatedly starting/stopping streams
Click on the bug numbers to see work done on these bugs.
(Note: 32-bit plugins will not work on 64-bit Audacity)
A 32-bit build of 3.0.3 remains available for download
Improved default spectrogram colors
We now provide an official binary for Linux in the form of an AppImage
Update checking: Audacity can now check to see if there is a newer version available
Error reporting: this is a new dialog where users can choose to send us the details of a serious error
Multiple bugs fixed
If you are a user of previous Audacity versions on Windows and had installed the optional FFmpeg library then you must now install the 64-bit versions of the FFmpeg library.
Otherwise your imports and exports that depend upon FFmpeg will no longer work.
See Installing FFmpeg for Windows for installation details.
Full details of new features in the visual guide to New features in Audacity 3.0.3
Audacity 3.0.3 replaces all previous versions.
Windows
Audacity 3.0.3 requires the CPU to support the SSE2 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 CPU-Z.
If your hardware only supports SSE, you may download Audacity 2.0.6 see the Legacy Windows page on the Audacity Website.
3.0.3 does not support Windows XP.
You may try 2.2.2 on XP, but it is unsupported.
macOS / Mac OS X
Audacity 3.0.3 is for Intel Macs running OS X 10.9 and later and macOS.
There are legacy versions for older OS X at http://audacityteam.org/download/legacy-mac/.
Linux
Linux support is tested on Ubuntu Linux.
Audacity may compile on Gentoo, Debian, Mint.
Audacity does not currently compile on SuSE Linux.
We probably track more bugs than you are interested in...
We used to have a separate page with a dynamic buglist for each version, but nowadays we recommend instead to visit our bugzilla instance for current bug status.
We do use this detail in our own QA work.
Below are listed what we believe are the most common and important issues with 3.0.3 for most users.
Accessibility
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
ID
P
Status
Summary (2 tasks)
P2
RESOLVED
If Temporary files directory is set to be unwritable then Audacity has a catalog of cryptic unhelpful errors
P2
RESOLVED
Audacity crashes with Macros on files when the macro-output folder is in an unwriteable location
Click on the bug numbers to see work done on these bugs.
In early October Apple released its latest operating system 10.15.x known as Catalina.
Audacity is not officially supported yet to run under Catalina. It appears to launch and run fine but it fails to record from the microphone (or external USB device) yielding only a flat-line silent recording. This is a permissions issue regarding access to the microphone (recording input) and something which we need to explore further.
Fortunately there is a workaround ...
if you have updated to Catalina and still need to use Audacity for recording as well as all its other functionality:
1) Go to Applications > Utilities
2) Launch Terminal.app
3) in the Terminal dialog type the following command following command:
open /Applications/Audacity.app/Contents/MacOS/Audacity
This will open Audacity and then Terminal will actually ask for the correct permissions.
this assume that Audacity is stored in your Applications folder. If it is somewhere else, you will need to change the path in the above command: open /*location of audacity*/Audacity.app/Contents/MacOS/Audacity When you first try to record, you will be asked to grant access to the microphone - similar happened in 1.14 Mojave - but microphone access permissions granted in Mojave do not pass through to Catalina. Once you have granted this access in Catalina you should not be asked for it again when relaunching Audacity with this workaround method.
If you leave Audacity active (black dot) in the bottom dock you can just relaunch from the Audacity logo.
If you totally quit Audacity you will need to relaunch from the Terminal app again every time.
Finally: credit for providing this useful workaround must go to Forum user noraa - very much appreciated, thanks Noraa.
Audacity 2.3.3 was released on ----- May 2019.
Audacity 2.3.3 replaces all previous versions.
Over 150 bugs fixed since 2.3.2.
Full details of new features in the visual guide to
Windows
Audacity 2.3.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.
macOS / Mac OS X
Audacity 2.3.3 is for Intel Macs running OS X 10.7 and later and macOS, but not Catalina.
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.
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.2 that we have fixed for 2.3.3
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.
Below are listed what we believe are the most common and important issues with 2.3.3 for most users.
macOS Catalina
We don't properly support mac Catalina yet. A workaround must be used to get recording to work at all.
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.
This page is an overview of the key new functionality that has been introduced in Audacity 2.1.3
Details of all the major changes since 2.1.2 can be found in Audacity 2.1.3.
We have implemented the long-standing and popular feature request of a fixed and centered play/record head (called the "pinned head"). When the pinned head is selected the waveform scrolls continuously past the fixed head while you are playing or recording.
The pinned head can be selected by using the new button at the left of the Timeline. By default this is the familiar green downwards-pointing triangle (like the playhead) and the default behavior is the old familiar scrolling play/record head. The pinned head can also be selected in Tracks Preferences.
When pinned playback or recording is chosen, the playhead displays as a green drawing-pin (as shown in the image below) and the recording head displays as a red drawing-pin.
Clicking the drawing-pin reverts to default unpinned playback and recording, and the button will change back to the green triangle.
For this release we have changed the way in which scrubbing works.
We have introduced a new which is on by default and sits just under the . You can turn it on or off from the right-click dropdown menu of the Timeline.
If you hover the mouse over the Scrub Ruler you will see the Scrub widget's green left- and right-pointing arrows appear (along with a tooltip if you continue to hover). Clicking anywhere in the Scrub Ruler, releasing the mouse button then moving the mouse left or right will start Scrubbing from there. Note that in this image the green scrub widget is to the right of the green triangle playhead, indicating that forwards scrubbing towards the pointer is taking place.
To stop scrub play and set the cursor at the current playback position, just click the Stop button (or its shortcut SPACE).
The shortcut for has changed from SHIFT + A to the simpler and easier to use X.
We have added some new features to improve Timer Record.
You can now specify optional actions on completion such as Save and/or Export, quit Audacity and, on Windows, shut down.
Audacity will now warn you in advance if it calculates that you have insufficient disk space for the length of your scheduled recording.
A big improvement you will notice is that all effects plus edits and other functionality can now be actioned from paused state - Audacity will stop the audio and do the action or open the dialog requested. This should remove a common cause of confusion for our users.
We have introduced a new effect (which supersedes the "Leveller" and "Hard Limiter" effects found in earlier Audacity versions). Technically this effect is a . The result of waveshaping is equivalent to applying non-linear amplification to the audio waveform. Preset shaping functions are provided, each of which produces a different type of distortion. Presets are provided which suggest typical settings for a wide range of uses.
The former Click Track generator has been updated and renamed to with improved sounds and a new "Swing amount" control for unequal beat duration.
We have added a new Generator for which reads numeric values from a file and creates a sample for each numeric value read.
There are two new keyboard shortcuts to navigate between labels: ALT + RIGHT to Move to Next Label and ALT + LEFT to Move to Previous Label. Use these shortcuts to move the editing position to the label, without opening the label for editing. If audio is already playing, playback jumps to the label requested, which is useful if you have using labels.
These new shortcuts also let screen readers for the blind read the label's name and its order in the labels in that track, a feature lacking in Audacity until now. There are no corresponding menu entries or buttons for these shortcuts.
There are two new commands to aid making selections:
Use Edit > Store Cursor Position to store the position of the editing cursor (or when there is active audio, to store the position of the playback or recording cursor).
Subsequently, use Edit > Select > Cursor to Stored Cursor Position to select from the editing cursor (or during active audio, from the position of the playback or recording cursor) to the stored cursor position.
In version 2.2.0 these commands were moved to the new .
Another new menu item is Tracks >Type to Create a Label (on/off). Previous Audacity already let you type to create a label in the focused label track, but this feature made it easy to accidentally create a label when you really wanted to use shortcuts to play or act on the audio. Uncheck this new menu item (or make the same change in Tracks Preferences) to avoid that risk.
In version 2.2.0 this command was moved to the Edit > Labels menu.
We have added to this Manual. It tells you about a few of the core Audacity features and about some of the more specialized features you might not know where to find.
This page gives an overview of further new functionality that has been introduced in Audacity 2.1.3
- detailed release notes for this release of Audacity
Audacity 2.3.1 will be released on 8th March 2019.
Audacity 2.3.1 replaces all previous versions.
Audacity now supports 64-bit Mac.
Over 20 bugs fixed since 2.3.0, including:
A crashing bug on Linux that made Audacity 2.3.0. unsuitable for Linux.
Full details of new features in the visual guide to
Windows
Audacity 2.3.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.
macOS / Mac OS X
Audacity 2.3.1 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.
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.0 that we have fixed for 2.3.1
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.
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.2.1 was released on 6 December 2017.
See the New features in Audacity 2.2.1 page for more information about improvements and other changes.
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.
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.
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.
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 support is tested on Ubuntu Linux.
Audacity may compile on Gentoo, Debian, Mint.
Audacity does not currently compile on SuSE Linux.
See our for much more detail of issues with Audacity 2.2.1.
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.
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.
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.
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
We track these and many other bugs in our 'bugzilla' database.
Click on the bug numbers to see work done on these bugs.
Audacity 3.1 was released on 27. October 2021
Audacity 3.1 replaces all previous versions.
The old Time Shift Tool has been replaced by Clip handles. Clip handles are the rounded corners above the clip which feature the clip title. You can move clips around by simply clicking and dragging the clip handle, and you can rename clips by double-clicking the clip handle.
Label tracks don't feature clip handles, but they can be moved around just the same: Simply click on the label (the bar for region labels, the circle for point labels) and drag them to their new place.
Audacity now can trim clips non-destructively by dragging the upper edge of a clip. This means that you can make clips shorter, then do some edits and then decide it should be longer anyway - the data will still be there. Copy-pasting the trimmed clip also will have that info available!
Audacity now features a new playback looping button. Enabling it will mark the current selection as a looping region, in which the playback will loop. You then can edit and select independently of the looping region. This feature replaces the previous Shift+Play behavior.
When looping is enabled, you can press Shift+Play to only play the looping region once.
Since it's conception in 2000, Audacity had cross-platform support of both Windows, macOS and Linux as it's goal. But macOS at the time didn't have a right-click, so to not hide features from mac users, Audacity didn't have any right-click context menus. The situation has changed since then, and there no longer is anything hindering right-click context menus, so they now have been added to a few places, such as in the waveform of clips and the empty (dark grey) space outside of tracks, providing relevant options right there.
In the preferences, is now disabled by default. This makes multi-track editing easier (even if you're not using Sync Lock). You may now see an error saying that there isn't enough space when pasting clips in-between other clips though, so if that happens to you too frequently, you may want to turn it back on.
The spectrogram defaults have been changed: scale type to Mel (was Linear), top of scale to 20000 Hz (was 8000 Hz), window size to 2048 (was 1024), and zero padding to 2 (was 1).
Since Audacity 3.0.3, there have been two hot-fix releases (3.0.4 and 3.0.5), both fixing a bug each which could lead to data corruption. Thanks to the automatic updates introduced in 3.0.3, we actually could make these hotfixes and be reasonably certain that they'd actually reach users and potentially avert data loss.
In addition, we fixed a number of bugs, from the very small (the play button had 1-2px cut off at the bottom) to some larger ones (especially crashes/bouncing balls of death). Some more details can be found below.
Context menus have been added in more places.
In the preferences, Tracks > Track behaviors > Editing a clip can move other clips is now disabled by default
The spectrogram defaults have been changed: scale type to Mel (was Linear), top of scale to 20000 Hz (was 8000 Hz), window size to 2048 (was 1024), and zero padding to 2 (was 1).
FFMPEG now supports avformat 55, 57 and 58.
PortAudio has been updated to version 19.7 and devendored (so it can be built against 19.6).
Several libraries (expat, libsndfile, ...) have been devendored. The lists which versions we build against.
There are some 50 issues closed labeled as bug. Among them:
AppImages support localization.
Progress bars for Nyquist generators have been made more accurate.
Rhythm tracks can no longer drift off-time by 2ms over 9 minutes; they're now sample-accurate.
Windows
Audacity 3.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.
macOS / Mac OS X
Audacity 3.1 is for Intel Macs running OS X 10.7 and later and macOS.
There are legacy versions for older OS X at .
Linux
In addition to the traditional update path via package managers, Audacity 3.0.3 and onwards are distributed as an AppImage. The AppImage gets updated at the same time as the Windows and macOS versions, so if you collaborate with users on those platforms, you may want to use the AppImage over your distribution's package manager.
Linux support is tested on Ubuntu Linux.
Other Linux distributions should work, but aren't tested by the Audacity team.
Audacity 3.2 was released on 22. Sep 2022
Added a new Effects button to the tracks menu, allowing you to place realtime effects.
Further information can be found on
Merged the mixer bar with the meter bars.
Added a new Audio Setup button, replacing the Device Toolbar by default. The device toolbar can be re-added via the View > Toolbars menu.
The Effects menu has gotten a new sorting. Other sorting and grouping options can be found in the Effects preferences.
Updated the icons
More info can be found on
VST3 effects are now supported.
VST3, LV2, Audio Units and LADSPA are now realtime capable
Plugins now automatically get scanned, tested and enabled when Audacity starts.
Apple Silicon (arm64) is now supported on macOS.
Note: When using an arm64 Audacity, you must use arm64 FFMPEG and plugins. Plugins for x86-64 (Intel macs) will not load.For the time being, Audacity will continue to offer x86-64 versions by default to avoid these incompatibilities, but you can download an arm64 version from .
FFMPEG 5.0 (avformat 59) is now supported, in addition to avformat 55, 57 and 58
Added support for
On Linux, Audacity can now be compiled without JACK present.
Audacity now uses XDG directories on Linux. Note: If you are upgrading from a previous version, Audacity will keep using the ~/.audacity-data and ~/.audacity folders until you delete them.
Audacity binaries are now licensed under the GNU General Public License, Version 3. Most code files remain GPLv2-or-later, but VST3 support required this license update. More information can be found in the .
Removed the Zoom Tool
The Audacity Manual HTML pages no longer are included in the installation.
If you require offline access of the manual, you can download it .You also can download PDFs of straight from its sidebar (or the three-dot button in the top-right corner on smaller/mobile devices).
Fixed Audacity sometimes not being able to import MP3 files (or reporting Huffman Data Overruns) by switching import library
Fixed rare data loss bug when placing labels during recording
Fixed clip titles being able to disappear off-screen when editing them
A full list of changes can be found .
Windows
Audacity 3.2 supports Windows 10 & 11
Windows Vista, 7 and 8.1 should still work, but are no longer tested.
Downloads for older versions are available on the page on the Audacity Website.
macOS / Mac OS X
Audacity 3.2 supports OS X 10.9 and later, and macOS.
There are legacy versions for older OS X at .
Linux
In addition to the traditional update path via package managers, Audacity 3.0.3 and onwards are distributed as an AppImage. The AppImage gets updated at the same time as the Windows and macOS versions, so if you collaborate with users on those platforms, you may want to use the AppImage over your distribution's package manager.
Linux support is tested on Ubuntu 20.04.
Other Linux distributions should work, but aren't tested by the Audacity team.
Audacity 3.5 was released on 22.04.2024. It adds cloud saving, automatic beat detection, and more.
audacity-win-2.3.2.exe application/x-msdownload)
SHA-256 351bbf5a30e65e2a77d28cf5384057bbc2b25880c682be755908307951e43b01
audacity-win-2.3.2.zip application/x-zip-compressed)
SHA-256 7edd522506274df9fff2839182988c210a7c2187295942b963eb81ea094cd4ad
audacity-macos-2.3.2.dmg (n/a)
SHA-256 0d2ea6de4f2cbd960abb6a6e020b51f6637423c072422596691960fcfae67206
audacity-minsrc-2.3.2.tar.xz (n/a)
SHA-256 df1f88984a6486094157e061024244b39c4a5875394ec9e5ae404c783cd8fee2
audacity-manual-2.3.2.zip (application/x-zip-compressed)
SHA-256 67717cf822e8f528da164f685175b181af99b59aa87941da8df46b8559ba5362
audacity-macosx-ub-2.1.1-screen-reader.dmg (n/a)
SHA-256 b1913d3362a9221609bae7fab848a5cae93d786d178234c6018e3c95ddfd9d62audacity-win-2.4.2.exe
SHA256 1f20cd153b2c322bf1ff9941e4e5204098abdc7da37250ce3fb38612b3e927ba
audacity-macos-2.4.2.dmg
SHA256 4730abe5b59d9c3dd000fde22d7037af6e6019a4305195a3e4e714f6c9f6380a
audacity-minsrc-2.4.2.tar.xz
SHA256 b3ea9b85f184cec4c1d0da50edb4a588132589d6d1709f6ef0147d52199d0b59
audacity-2.4.2.zip
SHA256 0c14f7c6850c93b9dacc14fe66876b8dc3397d92dbd849898783a21bad1fff55
audacity-manual-2.4.2.zip
SHA256 030b8da55738d80a181af212f6ce25205c4d047a90f21c15acd083c5a589a6c6
audacity-macosx-ub-2.1.1-screen-reader.dmg
SHA256 b1913d3362a9221609bae7fab848a5cae93d786d178234c6018e3c95ddfd9d62audacity-win-2.3.1.exe application/x-msdownload)
SHA-256 c3f35f2061473433cd545145d9018dab600ed6806a4a3de7e04cc5e8875b1966
audacity-win-2.3.1.zip application/x-zip-compressed)
SHA-256 6be81567fe97446eb591910f82d7a6c7a4469ef1e2926a7344cee74db44772af
audacity-macos-2.3.1.dmg (n/a)
SHA-256 cfce59cf73a8339c92d2246de7834df803a889563bd4c5b8bd4ef5fd3fd46553
audacity-minsrc-2.3.1.tar.xz (n/a)
SHA-256 f99f198a4d653aeee1f8967670f3edb4f74a81393bb14479d969f8aef9cdf923
audacity-manual-2.3.1.zip (application/x-zip-compressed)
SHA-256 235dc2cde337245d652033df46dce310aec3b3a213cc760764046d1b3afcf8a7Problems with Change Pitch, including not remembering parameter values.
Options and preferences:
Microfades are now an opt-in feature. They were always on in 2.3.0.
The advanced vertical zooming option is now available in the View->Zoom menu.
Regular interval labels now support range labels.
2.3.1 does not support Windows XP.
You may try 2.2.2 on XP, but it is unsupported.
Serious bugs and less serious bugs.
ID
P
Status
Summary (2 tasks) ⇒
P3
NEW
Linux: PULSE-AUDIO issues. Freeze repeatedly starting/stopping streams
P3
RESOLVED
Windows: DirectSound Sound Activated Recording does not record correctly or pauses permanently after 12 seconds
ID
Summary (3 tasks) ⇒
ID
Timer Record occasionally carries on recording past the scheduled end, requiring force quit
Linux: MIDI playback timing / synchronisation problems
Linux: PULSE-AUDIO issues. Freeze repeatedly starting/stopping streams




2.3.3 does not support Windows XP.
You may try 2.2.2 on XP, but it is unsupported.
Serious bugs and less serious bugs.
ID
P
Status
Summary (2 tasks) ⇒
ID
P1
RESOLVED
Mac: Audacity does not run properly on macOS 10.15 Catalina
P3
NEW
Linux: PULSE-AUDIO issues. Freeze repeatedly starting/stopping streams
Raw Import now will remember the previously used settings. Automatic detection of the format now is a button.
A journaling feature has been added for QA purposes.
Generate > Tone now supports triangle waves.
There now exist "What's new" screens for the update and welcome dialogs.
Timeline Quick Play for regions and locked regions have been replaced by playback looping.
The shortcut to rename labels and clip names has temporarily been hardcoded to Ctrl+F2.
This conflicts with the default xfce shortcut to change workspaces.
Auto Duck has been made way more accurate and should no longer miss sections above the threshold. #1389
The manual now only is included in the executable once #1917
Shift-clicking a menu item no longer opens the settings menu #1358
FFMPEG no longer segfaults ALSA #1170
Audacity no longer crashes when macros output directory is set to C:\ #1174
A bouncing ball of death problem has been fixed #1312
3.1 does not support Windows XP.
You may try 2.2.2 on XP, but it is unsupported.
Added a quick audio sharing feature.
Switched from mad to mpg123 as MP3 importer
Audacity has been added to the Windows Package manager (winget).
1889 Fixed clip titles changing name when applying some effects
1624 During batch processing, Audacity will no longer stop to ask for a sample rate when an unsupported one is chosen, but choose the nearest supported one instead.
2265 Fixed mod-script-pipe not being installed on Linux
3571 Fixed GTK packaging in Appimages. This fixes various issues with icons, dropdowns and similar things not appearing properly.
3634 Improved M4A/AAC support. Previously the target bitrate was not honored at all, now it can be set between 98 and 160 kbit/s (mono) or 196 and 320 kbit/s (stereo). The UI does not yet reflect these limits.
Over 100 bugs fixed since 2.3.3
Full details of new features in the visual guide to New features in Audacity 2.4.1
Windows
Audacity 2.4.1 requires the CPU to support the SSE2 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 CPU-Z.
If your hardware only supports SSE, you may download Audacity 2.0.6 see the Legacy Windows page on the Audacity Website.
2.4.1 does not support Windows XP.
You may try 2.2.2 on XP, but it is unsupported.
macOS / Mac OS X
Audacity 2.4.1 is for Intel Macs running OS X 10.7 and later and macOS including Catalina.
There are legacy versions for older OS X at http://audacityteam.org/download/legacy-mac/.
Linux
Linux support is tested on Ubuntu Linux. Use the CMake build. The Automake build is no longer reliable.
Audacity may compile on Gentoo, Debian, Mint.
Audacity does not currently compile on SuSE Linux.
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.3 that we have fixed for 2.4.1
Known bugs on the OS you use Mac, Windows or Linux.
Known bugs to do with accessibility or localization.
Workarounds for some bugs.
Serious bugs and less serious bugs.
You can choose various combinations of these. However, there are probably too many minor bugs and too much detail on that dynamic buglist page for most users.
We do use this detail in our own QA work.
Below are listed what we believe are the most common and important issues with 2.4.1 for most users.
Accessibility
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
ID
P
Status
Summary (5 tasks)
P1
RESOLVED
Mac: Zoomed in, playback meters slow to respond.
P2
RESOLVED
Linux: Unwanted messages in console.
Click on the bug numbers to see work done on these bugs.
Over 30 bugs fixed since 3.0.0
Full details of new features in the visual guide to New features in Audacity 3.0.2
Windows
Audacity 3.0.2 requires the CPU to support the SSE2 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 CPU-Z.
If your hardware only supports SSE, you may download Audacity 2.0.6 see the Legacy Windows page on the Audacity Website.
3.0.1 does not support Windows XP.
You may try 2.2.2 on XP, but it is unsupported.
macOS / Mac OS X
Audacity 3.0.2 is for Intel Macs running OS X 10.7 and later and macOS.
There are legacy versions for older OS X at http://audacityteam.org/download/legacy-mac/.
Linux
Linux support is tested on Ubuntu Linux.
Audacity may compile on Gentoo, Debian, Mint.
Audacity does not currently compile on SuSE Linux.
We probably track more bugs than you are interested in...
We used to have a separate page with a dynamic buglist for each version, but nowadays we recommend instead to visit our bugzilla instance for current bug status.
We do use this detail in our own QA work.
Below are listed what we believe are the most common and important issues with 3.0.2 for most users.
macOS Big Sur
Accessibility
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
ID
P
Status
Summary (3 tasks)
ID
P2
RESOLVED
"Failed to open the project database"
P3
NEW
Linux: High-dpi displays are not supported
Click on the bug numbers to see work done on these bugs.
Audacity can now automatically detect the tempo of imported loops, and adjust them to be in tempo.
Tempo detection is done via both audio analysis and metadata checking. If you want to prepare your loop for automatic tempo detection without relying on audio analysis, both acidizer tempo tags or simply writing "123 bpm" anywhere into the filename work.
Automatic tempo detection can be turned off via Preferences -> Import/Export.
You now can non-destructively change the pitch of a clip by holding Alt and pressing the Up and Down arrow keys. Alternatively, you can click on the overflow menu (...) and select "Pitch and speed...". When changing the pitch this way, an arrow in the UI indicates how much you've shifted it.
Additionally, the Pitch and speed dialog also features an option to optimize for voice which preserves formants.
Added an option to skip plugin scanning to Preferences -> Effects.
Added an overflow menu, as well as speed and pitch indicators to clips.
Added subtitle formats for labels. Export to WebVTT and SubRip and import of SubRip files is now supported. (Thanks, Pokechu22 and Larry Bordowitz!)
Reworked the plugin manager. It's now simplified and filterable, and also has a search box.
Improved accessibility. (Thanks, David Bailes!)
When zooming in vertically (Ctrl+scroll on the vertical scale), the zeroline now remains centered. Moving the vertical zoom off-center still is possible via Shift+scroll on the vertical scale.
Changed the look of the selection adjust cursors (previously pointing fingers on Windows and macOS, now look like >| everywhere).
Changed the timeline options button from a green triangle to a settings gear. From it, you can switch between Beats & Measures or hh:mm:ss timeline rulers, set various preferences regarding to looping, as well as playhead behaviors: "Scroll view to playhead" (previously: "Update display while playing") and "Continuous scrolling" (previously: Pinned Play Head).
Improved BSD support. (Thanks, Brad Smith!)
Changed the Audacity.app icon on macOS to fit new design guidelines. (Thanks, Filip Krawczyk!)
Reordered some menus.
Moved the OK/Cancel buttons of effects to the bottom.
There have been a number of removals of niche features to simplify the app. This should make Audacity a bit less overwhelming to use, and also will speed up future development as fewer things need to be considered.
Removed the read-only mouse preferences page.
Removed Printing options.
Removed Screenshot tool. To make a screenshot, use Win+Shift+S (Windows) or Cmd+Shift+4 (Mac) instead.
Removed Karaoke view.
Removed the "solo=none" preference.
Removed timeline tooltips preference.
Removed "dragging selection edges" preference.
Removed some warning dialogs and associated preferences.
Removed "scrolling left of zero" preference.
Replaced "Advanced Vertical Zooming" with new always-on behavior.
Removed some vertical zoom presets.
Removed EQ XML to TXT converter, which was needed for the Audacity 2.3 -> 2.4 transition. It is now a plugin instead, downloadable at .
Removed the "Vocal reduction and isolation" effect. As a replacement for Windows and Linux, the work better and on a wider array of content, including mono tracks. The old effect still can be downloaded from
Fixed a number of dialogs that were able to grow too large to fit on the screen.
#2133 Fixed the playback cursor sometimes desynchronizing with actual playback. (Thanks, David Bailes!)
#5283 Fixed "Reset configuration" command breaking modules preference page.
Fixed stereo tracks randomly splitting into mono.
The Export Audio -> (external program) option remembers the command line argument again.
Fixed the Compressor effect sometimes corrupting audio. (Thanks, David Bailes!)
Fixed Timer Record sometimes failing to export. (Thanks, David Bailes!)
Fixed incorrect level measurements for mono tracks in Noise Gate effect. (Thanks, Steve Daulton!)
When exporting multiple files, the mono/stereo setting is now honored properly.
Fixed some effects failing when language is set to German, Korean, Dutch, Slovenian, or Turkish.
Fixed 8 and 9 inputs not working on keyboard inputs which have AltGr+8/9 mean [ and ]. (Thanks, David Bailes!)
Fixed Audacity crashing when making a stereo track using keyboard. (Thanks, Joe Souza!)
Fixed the "Set default" button not working in the metadata editor. (Thanks, dg-no-9!)
Linux: Fixed a memory leak in Wayland by explicitly running on X11. (Thanks, Takahashi, Naoki!)
Fixed recording sometimes recording at the wrong sample rate, pitching things up in the process. (Thanks, David Bailes!)
Improved importing performance.
Filenames featuring a period mid-name are no longer cut off.
Fixed a crash when pasting 192k/24 bit audio.
Fixed a crash with AUMultibandCompressor.
Exporting stereo as mono now calculates volume correctly.
Exporting now can create folders within folders. (Thanks, Antonio!)
A full list of changes can be found on Github.
Windows
Audacity 3.5 is tested on Windows 10 & 11
Windows Vista, 7 and 8.1 may still work, but are no longer tested.
macOS / Mac OS X
Audacity 3.5 is tested on macOS 14
Any macOS version since OS X 10.9 may still work, but is no longer tested.
3.5.0 is incompatible with macOS 11 and earlier due to a bug on Apple's side. 3.5.1 will be made compatible again.
Linux
Linux support is tested with AppImages on Ubuntu 22.04.
Other Linux distributions should work, but aren't tested by the Audacity team.
On some distributions, libfuse2 needs to be installed for AppImages to work. See https://github.com/AppImage/AppImageKit/wiki/FUSE for more information.
Community-maintained distro-specific versions and other repackages (such as Flatpak) are often available, too.
This page is an overview of the key new functionality that has been introduced in Audacity 2.2.2
Details of all the major changes since 2.2.1 can be found in Audacity 2.2.2.
"Dropouts" are small fragments of missing audio on recording. They can sometimes be caused by very slow processing, especially slow writing to disk or USB key, when writing data cannot keep up with the recording.
We have added dropout detection for this release.
Dropout detection is controlled from a setting in Recording Preferences called "Detect dropouts".
When this setting is "on" (default setting) Audacity will detect dropouts (brief gaps in the recording) and will insert zeroes into the recording to keep the other good parts synchronized. These silent spans will make the dropouts more obvious, but keep the duration of the recording correct.
Dropouts may be caused by a disk drive that cannot keep up with the recording. This can happen, for example, with a slow USB or network drive, or if antivirus software is slowing writing to disk, or if other activity on the computer is slowing the computer down.
When recording stops, a Warning message box alerts the user and a label track, called "Dropouts", is added showing the lost parts, labeled with consecutive numbers.
For this release we have improved the way zooming using your mouse wheel works and provided a new Zoom Toggle function.
This is particularly for users who zoom in and out a lot, e.g. when using the Repair effect to do detailed work removing clicks in the audio.
We have changed mouse wheel zooming so that the focus for the zoom is:
With the mouse pointer outside the selection, the leftmost or rightmost edge of the current selection, (if a selection exists).
Mouse pointer position will be used as the zoom focus if the mouse position is inside the current selection, (if a selection exists).
If no selection is present, zoom focus is as it was before and is taken as the mouse pointer position.
We have introduced a new command, Zoom Toggle, accessed by a new button or by (shortcut Shift + Z).
Zoom Toggle toggles between two pre-defined zoom levels. These presets are user selectable in Tracks Preferences.
Defaults are normal Default Zoom level and 4 Pixels per Sample (which shows a fraction of a second of audio as samples)
Either of the two presets can be changed in Tracks Preferences using the dropdown menus.
Tracks Preferences showing Zoom Toggle selection dropdown for Preset 2
There have been some changes to Vertical Zooming.
We have introduced a context menu for the Vertical Scale. This is activated by right-clicking in the Vertical Scale - see for details.
Left-click, and drag, in the Vertical Scale remain available as a user-selectable option - see for details.
You can turn on advanced mode for vertical zooming from Edit > Preferences > Tracks Behaviors and selecting Advanced Vertical Zooming.
The Extra menu, created from consolidating Ext-Bar and Ext-Command menus that were introduced in the previous 2.2.1 release.
In dark theme, the change in appearance of sliders when you hover over them is greater than before.
In light and dark themes, buttons such as 'pause' and 'pin' now highlight when you hover over them and they are down. Previously there was no visible change.
The hover effect for buttons when they are up has been changed to work better in conjunction with this change.
In dark theme the microphone and speaker icons are now brighter and not dulled as they were before.
For menu commands that are enabled (not grayed-out) if you hold the Shift key and click on the sub-menu item, instead of executing the command the Keyboard Preferences pop open at the chosen command. You can then change that (or any other) shortcut binding.
Interface Preferences has been upgraded so when selecting languages the proper spelling of these languages is shown with accented and special characters.
The Index page in the Manual has been upgraded - so that now any item that can be clicked on/through in the front page imagemap now has a corresponding text entry in the index (this is primarily as an aid to VI (Visually Impaired) users)
Additionally the Index has been divided into alphabetic sections to aid readability.
Multiple use of "Save As" to the existing open project can result in data corruption/loss
Crash undoing during record, using Discard button of History window
Exporting audio in compressed formats to device with insufficient space produces inconsistent/truncated results
In Export Multiple, Cancel does not remove the file that is in progress when Cancel is chosen
- detailed release notes for this release of Audacity
Audacity 2.3.0 was released on 29 September 2018.
The 2.3.0 tarball is now marked as 'Experimental'.
After release we found it is not stable, and are investigating.
is one way to cause the problem.
Audacity 2.3.0 replaces all previous versions.
Over 90 bugs fixed since 2.2.2.
Includes fixes to Timer Record, and to 'Envelope Points'.
New feature - "Punch and Roll Recording".
Toolbars controlling volume and speed can now be resized for greater precision.
Full details of new features in the visual guide to
Windows
Audacity 2.3.0 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.0 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.
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.2.2 that we have fixed for 2.3.0
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.
Some of the bugs we fixed for Audacity 2.3.0:
Timer record continues recording and does not stop at the stated time. You may on low powered hardware still see slow updates to the timer, and we haven't fixed that entirely yet.
QM 1.7.1 plug-in crash, now fixed.
Envelope curves got badly confused when joining clips.
Below are listed what we believe are the most common and important issues with 2.3.0 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
Audacity 2.4.0 was released on 16th May 2020.
Audacity 2.4.0 replaces all previous versions.
Over 100 bugs fixed since 2.3.3
Full details of new features in the visual guide to
Windows
Audacity 2.4.0 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.0 is for Intel Macs running OS X 10.7 and later and macOS including Catalina.
There are legacy versions for older OS X at .
Linux
Linux support is tested on Ubuntu Linux. Use the CMake build. The Automake build is no longer reliable.
Audacity may compile on Gentoo, Debian, Mint.
Audacity does not currently compile on SuSE Linux.
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.3 that we have fixed for 2.4.0
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 dynamic buglist page for most users.
We do use this detail in our own QA work.
Below are listed what we believe are the most common and important issues with 2.4.0 for most users.
Accessibility
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-win-2.3.3.exe
SHA256 263cecf19ff27c7a2f0c04a4031f0e45cda5215eb0836a4e40e09605d83286e2
audacity-macos-2.3.3.dmg
SHA256 43db4d502086257ca377326f9621a343149faac6d3334424b20a3b5caceadda8
audacity-minsrc-2.3.3.tar.xz
SHA256 ca42f64d9e9b3d5ee007f5d00b438229f88c9016f30b3ad9f49076a14bce0b55
Audacity-2.3.3.zip
SHA256 0cb7d4e293ee6fd6955af2a4bc6cea8cf21b9db053b86274f3072e036d7204e3
audacity-manual-2.3.3.zip
SHA256 286ca5b865d53f960e45976bb22c6f0c1b863f2f43e8b7c0f633bf1c5ecb2790
audacity-macosx-ub-2.1.1-screen-reader.dmg
SHA256 b1913d3362a9221609bae7fab848a5cae93d786d178234c6018e3c95ddfd9d62audacity-win-2.4.1.exe - 28245064 bytes
SHA-256 dde069264974b3bf7a0b556ea3037bb424630e3112735f99129f3d84921e547f
audacity-macos-2.4.1.dmg - 39745448 bytes
SHA-256 5d340b025b80eb0c3ea41ae2487a77b86527bc8fb0e058d32e37762ac3d85575
audacity-minsrc-2.4.1.tar.xz - 11368524 bytes
SHA-256 d476e25129846108d8a57f818ea0c0b90912d3dd4127eb7365cac5fbe0458dc6
audacity-2.4.1.zip - 11636331 bytes
SHA-256 23f388b22974eb9ee05672e52d34971000e9c5656551bfe9b348e16ac1c5e495
audacity-manual-2.4.1.zip - 22600322 bytes
SHA-256 a18186de8788510a34298b857947b55e49029b622ce8e6119e53db4c427b60d5audacity-win-3.0.2.exe (application/x-msdownload) - 29534144 bytes
SHA-256 2fa8e586a339d9da8dcf49c21f4cd1cbaa24691b1dcc0d02f6c9f451ac8bea47
audacity-macos-3.0.2.dmg (n/a) - 41554455 bytes
SHA-256 57895aad20a5512aeb44d1ab5b7d01a68a5303d4225351528f377eb7686f281e
audacity-minsrc-3.0.2.tar.xz (n/a) - 13330160 bytes
SHA-256 728d6459931da006ed45a31e63b7fe6ca47a2547459a2aff3bf0880cef85c296
audacity-win-3.0.2.zip (application/x-zip-compressed) - 12588153 bytes
SHA-256 00b8f65fdffc6f213362bd01bb21e3c47f1b5cdf99b4fc5c8c0dd92a41e590e0
audacity-manual-3.0.2.zip (application/x-zip-compressed) - 23254582 bytes
SHA-256 5078ebf5c34af71abe60178b319cc6e6aae2e0d510bc400981e0899795ca362faudacity-win-2.3.0.exe (application/x-msdownload) - 26693160 bytes
SHA-256 3909676287cc0c44fe867bcc0e74a23891aeeeda42ebf11b3037c9b28dca43a1
audacity-win-2.3.0.zip (application/x-zip-compressed) - 12899377 bytes
SHA-256 f57b4074a544169311830bb428d1d8fefafceb6a3b0680ae23fa1c5321c05835
audacity-macos-2.3.0.dmg (n/a) - 35846075 bytes
SHA-256 16684a03a6e6aacac0962636735ce7d9bf11483f6d194b05729981136cced9eb
audacity-manual-2.3.0.zip (application/x-zip-compressed) - 20131123 bytes
SHA-256 4f48b3e5d8b8573442c087cbf853297cae46ce54754f7485b50e86e0b4326b98audacity-win-2.4.0.exe
SHA256 dc71fbfd4f6c1b921c6f8ec387125fb61f53a60abeeff30aa73e19ba675b2bec
audacity-macos-2.4.0.dmg
SHA256 42d08496569556d22f2f22c84b9f0196ef207af1311a9089ebbfcf2af9e21922
audacity-minsrc-2.4.0.tar.xz
SHA256 dcb85efe447e8c6fa815f5fa1c4a0678ec56fb4db52d767de2ecfb546f777878
audacity-manual-2.4.0.zip
SHA256 3800bff937de7e8695c27dce107e5779d6d84ad2c49ef8906eb7069824209472
audacity-2.4.0.zip
SHA256 b697958c49de95818f7322bca7a043cee1580c3ecab91d62bfb649457edd285aP2
RESOLVED
Crash importing malformed MP3 file using libmad
P2
RESOLVED
Mac: Keyboard tabbing in Timer Record stuck in left hand panel.
P3
NEW
Linux: PULSE-AUDIO issues. Freeze repeatedly starting/stopping streams
P3
RESOLVED
Faux recovery offered on launch (very moonphase)
Unicode page encodings fixed ( ͡° ͜ʖ ͡°)
Crash using SBSMS pitch change at low sample rate
(Mac) Equalization: "Telephone" curve displays a flat line, no sound on Preview
Toolbars: open undocked if previously not shown, unless Reset Toolbars first
Analysis effects that create labels should give focus to label track
Control value may be out of range when using FloatingPointValidator
Analysis effects produce false indication that a label is open for editing
Import Uncompressed File Dialog Incorrect Reference to Menu Item
Wave Color not grayed out in TCP dropdown menu when in Spectrogram view
Hover indication on note track channel toggle appears on all tracks (when they rerender)
Installer has old logo for 2.2.1 and 2.2.0
Un-muting with a single track unnecessarily activates the Solo button
Applying chain to file should zoom-to-fit







Play-at-Speed now can be adjusted whilst playing.
Macros (formerly 'Chains') substantially extended.
Pinned-play-head can now be repositioned by dragging.
2.3.0 does not support Windows XP.
You may try 2.2.2 on XP, but it is unsupported.
Serious bugs and less serious bugs.
P3
NEW
Linux: PULSE-AUDIO issues. Freeze repeatedly starting/stopping streams
P3
RESOLVED
Windows: DirectSound Sound Activated Recording does not record correctly or pauses permanently after 12 seconds
ID
P
Status
Summary (4 tasks) ⇒
ID
P1
RESOLVED
Mac: Audacity will not work with future versions of macOS
P1
RESOLVED
Linux: built-in real-time preview effects crash
2.4.0 does not support Windows XP.
You may try 2.2.2 on XP, but it is unsupported.
Serious bugs and less serious bugs.
RESOLVED
Crash importing malformed MP3 file using libmad
P2
RESOLVED
Mac: Keyboard tabbing in Timer Record stuck in left hand panel.
P3
NEW
Linux: PULSE-AUDIO issues. Freeze repeatedly starting/stopping streams
ID
P
Status
Summary (5 tasks) ⇒
P1
RESOLVED
Mac: Zoomed in, playback meters slow to respond.
P2
RESOLVED
Linux: Unwanted messages in console.
P2
For the first time, Audacity will now install as a 64-bit application on Windows devices. Due to this change, some processes and effects (e.g. certain sound generation processes & sliding stretch) will run much faster.
64-bit FFmpeg library: If you are a user of previous Audacity versions on Windows and had installed the optional FFmpeg library then you must now install the 64-bit versions of the FFmpeg library, otherwise your imports and exports that depend upon FFmpeg will no longer work. See Installing FFmpeg for Windows for installation details.
Installing the 64-bit FFmpeg library will not overwrite or delete your 32-bit FFmpeg library if you have one installed.
As Audacity is now a 64-bit application, 32-bit plug-ins will not work on Audacity 3.0.3 or later.
A new colorway has been introduced on Audacity 3.0.3 for Spectrograms.
The image below shows a sample track in Spectrogram view with a spectral selection:
If you wish to revert to the former colorway just go to and choose the Spectrograms tab and from there in the Scheme dropdown menu select Color (classic).
In addition to the Grayscale which was available as a choice for Spectrogram displays in earlier versions of Audacity there is now also an Inverse grayscale.
This too can be selected from the Scheme field in Spectrograms Preferences.
A new command has been added to the View menu, View > Track Name (on / off)
When this is enabled the audio track name is displayed superimposed translucently at top left of all audio tracks.
Note that the track name is always shown in the Track Control Panel but will be truncated if the name is too long to fit.
This has the same effect as the setting for Show track name as overlay in Tracks Preferences.
Audacity will now check for updates to see if a new update of Audacity is available. This is done on launch and then after every 12 hours while Audacity remains open.
The first time that you launch Audacity 3.0.3 you will see this dialog:
The dialog has a direct link to Application Preferences enabling you to turn update checking "off" in order to opt-out of update checking.
This is not an automatic update, update does not happen without you choosing to do so from the update checking dialog that appears when a new update is available.
This has long been one of the most-requested feature requests submitted by users to Audacity and it has finally been implemented.
You can opt-out of update checking by using a new preference in Application Preferences where you can turn this "off" or "on" at any time, the default setting is "on".
Now if and when Audacity crashes, or produces an error, there will be a dialog to enable you to optionally send error and crash reports back to the developers and Quality Assurance.
Not all error messages have the ability to automatically send back information to the developers and Quality Assurance.
We now provide an official binary for Linux in the form of an AppImage.
With the release of 3.0.3 Audacity has released the following Privacy Notice.
The Privacy Notice explains how Audacity collects and uses any information that, alone or in combination with other information, relates to you when you use the desktop application Audacity. We collect very limited Personal Data about you.
The Notice also sets out the rights that you have in relation to the Personal Data that we process about you and how you can exercise them.
In addition to the fixed bugs shown here, several changes have been made to increase the stability of the Unitary Project database structure.
P1 2754 - Change Tempo & Pitch and Sliding Stretch with selected audio in negative time crash Audacity on windows (error on Mac)
P1 2772 - Audacity crashes after failing to open corrupt project
P1 2793 - AUP3 projects fail to compact if project's path contains a single-quote
P1 - Audacity unresponsive after 'Fit to Height'
P1 - Audacity fails to export metadata with MP3 files
P2 2339 - On second run of Audacity "Filter Curve EQ" gets changed to "Filter Curve..." in the Effect menu
P2 2700 - "Failed to open the project database"
P2 2732 - Faux recovery offered on launch (very moonphase)
P2 - Audacity crashes with Macros on files when the macro-output folder is in an unwriteable location
P2 - If Temporary files directory is set to be unwritable then Audacity has a catalog of cryptic unhelpful errors
P2 - Linux: No support for Jack Audio System
P2 - Msgctxt feature of translation not working
P2 - The first use of the "window" command in LOF files is ignored by Audacity
P2 - The Macros output directory is in the top section in audacity.cfg
P2 - Open Project... under ScriptablesII can corrupt a project
P2 - Audio and MIDI files cannot be opened from FAT/FAT32 drives
P4 1309 - Paste with sync-lock can give error message but still do something
P4 1406 - Undoing envelope points by shortcut with mouse down creates spurious undo entries
P4 2466 - Linux: Filter Curve EQ GUI far too wide
P4 - Failed Macro command leaves empty undo item in history
P4 - Label Sounds fails when track sample rate is 22050 Hz
P5 1091 - Spectral Edit effects may have unpredictable results
With the release of Audacity 3.0.0 the project file structure of Audacity was changed significantly with the entire project contained in a single unified database file.
If you have already updated to 3.0.0 or 3.0.2 you should already be aware of this.
But if you are updating from any earlier 2.x Audacity version please read Updating from Audacity 2.x to Audacity 3.x.
Older Projects:
Audacity 3.x can usually open AUP files created in older 2.x.x versions of Audacity , but saving the project in 3.x will prevent it opening again in Audacity versions prior to 3.0.0.
Note that this will leave behind the old AUP file and its associated _data folder which you will probably want to delete to recover disk space.
Audacity version 3.x should be able to open projects from Audacity 1.1 onwards - but not from 1.0
Audacity Release Notes 3.0.3 - detailed release notes for this release of Audacity
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.
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.
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.
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.
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:
Macros 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 Scriptables submenus with many new commands.
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.
Macros are bindable to key presses.
New Nyquist Prompt in Tools with enhanced capabilities.
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 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.
These functions too are available from Macros.
Nyquist effects now support translation, and the ones shipped with Audacity are translated.
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. the Track Name overlay now has a background.
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.
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.
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.
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
Windows: Queen Mary 1.7.1 Vamp plug-ins crash Audacity on opening Plug-in Manager - see bug #1244
Inconsistent behavior when recording with a selection defined see bug #1839
Ctrl + M does not open label for editing - see bug #1852
Vertical Zoom in by clicking in the vertical Scale, or context menu, in waveform views is inconsistent see
Deletion of all tracks cannot be undone - see
Timer Record with a selection present can get a truncated recording with data loss - see
Duplicate shortcuts can be created - see
Labels longer than 260 characters are now supported - see
Using Spectrogram Settings in TCP or using Preferences causes Audacity to reset Project Rate to default rate in Quality Preferences - see
Cut Preview should play all selected/sync-locked tracks, respecting Mute/Solo during preview - see
Audacity 2.3.0 - detailed release notes for this release of Audacity

Audacity 2.2.0 was released on 02 November 2017.
See the New features in Audacity 2.2.0 page in the Manual for more information about improvements and other changes.
Four Selectable themes provided, with new 'Light' theme as default, plus option to customize
Many menu changes:
Menus Reorganized
Extended menu bar provided
Append-record is now the default (use Shift + Record for old behavior, to record on a new track)
The Esc key now cancels all click-and-drag actions. It also chooses among overlapping mouse click targets, which is especially useful in the Multi-Tool.
Sync-Lock button removed (use menu item or keyboard shortcut instead)
Major work on bug fixing. 198 bugs that were in 2.1.3 fixed for 2.2.0.
The most serious bug fixed this time round was which was about what happens when Audacity is recording and runs out of storage.
The problems of incomplete support for macOs Sierra have been resolved (including , , , and ).
For those who really have to know, the list of bugs fixed in 2.2.0 is .
Audacity 2.2.0 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.
Audacity 2.2.0 is for Intel Macs running OS X 10.6 and later and macOS. There are legacy versions for older OS X at .
Linux support is tested on Ubuntu Linux.
Audacity may compile on Gentoo, Debian, Mint.
Audacity does not currently compile on SuSE Linux.
See our for much more detail of issues with Audacity 2.2.0.
If you use File > Open to "open" an audio file (WAV file or MP3 file say) the file will import properly but only the first few seconds of it will be shown (the default zoom level), but more importantly the horizontal scroll slider will be missing from the scroll bar, meaning you can't access the remaining audio.
All you need to do do is press the Play button or any of the Zoom buttons in the Edit toolbar and the horizontal scroll slider will be restored.
The best way to avoid this happening is to use the File > Export command to import the file into an Audacity project. All that the File > Open does with an audio file is to
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.
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.
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.
With Sierra 10.12 and High Sierra 10.13 opening a second project from Mac's Finder produces a second inaccessible instance of Audacity. If you already have an Audacity project open, and attempt to open a second .AUP from within the Finder window (whether by double clicking, right-clicking for Open on the pop-up menu, or typing Cmd-O) or by right-clicking on the .AUP file and using Open With, the second project attempts to open in a new instance of Audacity, visible in Apple’s Dock bar at the bottom of the screen. This second instance of Audacity will not be accessible and you will need to Force Quit it.
Workaround: Use Audacity's File > Open command to open the second and successive projects.
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
We track these and many other bugs in our 'bugzilla' database.
Audacity 2.2.2 was released on 20 February 2018.
See the New features in Audacity 2.2.2 page in the Manual for more information about improvements and other changes.
New feature Dropout detection is controlled from a setting in Recording Preferences called "Detect dropouts".
When this setting is "on" (default setting) Audacity will detect dropouts (brief gaps in the recording) and will insert zeroes into the recording to keep the other good parts synchronized. These silent spans will make the dropouts more obvious, but keep the duration of the recording correct.
Dropouts may be caused by a disk drive that cannot keep up with the recording. This can happen, for example, with a slow USB or network drive, or if antivirus software is slowing writing to disk, or if other activity on the computer is slowing the computer down.
When recording stops, a Warning message is shown and a label track, called "Dropouts", is added showing the lost parts, labeled with consecutive numbers.
Zooming with the mouse wheel
Mouse wheel zooming has been changed so that the focus for the zoom is:
With the mouse pointer outside the selection, the leftmost or rightmost edge of the current selection, (if a selection exists).
Mouse pointer position will be used as the zoom focus if the mouse position is inside the current selection, (if a selection exists).
Zoom Toggle
A new command has been introduced, Zoom Toggle, accessed by a new button or by View > Zoom > Zoom Toggle (shortcut Shift + Z).
Zoom Toggle toggles between two pre-defined zoom levels. These presets are user selectable in Tracks Preferences.
Defaults are normal Default Zoom level and 4 Pixels per Sample (which shows a fraction of a second of audio as samples)
Simple Vertical Scrolling
A context menu has been introduced for the Vertical Scale. This is activated by right-clicking in the Vertical Scale.
Advanced Vertical Zooming
A new Extra menu has been created from consolidating the Ext-Bar and Ext-Command menus that were introduced in the previous 2.2.1 release.
Hover Appearance
In dark theme, the change in appearance of sliders when you hover over them is greater than before.
In light and dark themes, buttons such as 'pause' and 'pin' now highlight when you hover over them and they are down. Previously there was no visible change.
For menu commands that are enabled (not grayed-out) if you hold the Shift key and click on the sub-menu item, instead of executing the command the Keyboard Preferences pop open at the chosen command. You can then change that (or any other) shortcut binding.
Interface Preferences has been upgraded so when selecting languages the proper spelling of these languages is shown with accented and special characters.
The Index page in the Manual has been upgraded - so that now any item that can be clicked on/through in the front page imagemap now has a corresponding text entry in the index (this is primarily as an aid to VI (Visually Impaired) users)
For those who really have to know, the list of bugs fixed in 2.2.2 is .
Multiple use of "Save As" to the existing open project can result in data corruption/loss
Crash undoing during record, using Discard button of History window
Exporting audio in compressed formats to device with insufficient space produces inconsistent/truncated results
In Export Multiple, Cancel does not remove the file that is in progress when Cancel is chosen
Audacity 2.2.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.
2.2.2 does not officially support Windows XP.
Audacity 2.2.2 is for Intel Macs running OS X 10.6 and later and macOS. There are legacy versions for older OS X at .
Linux support is tested on Ubuntu Linux.
Audacity may compile on Gentoo, Debian, Mint.
Audacity does not currently compile on SuSE Linux.
See our for much more detail of issues with Audacity 2.2.2.
Below are listed what we believe are the most common and important issues with 2.2.2 for most users.
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
We track these and many other bugs in our 'bugzilla' database.
This page is an overview of the key new functionality that has been introduced in Audacity 2.3.2
Details of all the major changes since 2.3.1 can be found in Audacity 2.3.2.
The LAME library, which is needed for exporting MP3 audio files, is now built-in to Audacity on Windows and macOS as a part of the application.
With previous releases it was necessary to download and locate the LAME library as an optional extra.
If you go to Libraries Preferences you will see that the option to locate the library is no longer there and the dialog tells you what version of LAME is built-in.
LAME is not built into Audacity on Linux - you will still need to acquire an locate the optional LAME library.
There is now a Select button in the Track Control Panel.
The whole of an individual track can be selected by clicking this Select button.
Holding Ctrl (or ⌘ + A on a Mac) and clicking on the Select button toggles the selectedness of the track.
The new Nyquist Plug-in Installer is itself a Nyquist plug-in. It simplifies the installation of other Nyquist plug-ins. It is installed by default in Audacity and can be found in the Tools Menu. It can be accessed by: Tools > Nyquist Plug-in Installer...
This plug-in installer provides a file browser for selecting the plug-in '.NY' file (Nyquist plug-ins are plain text files that have the '.NY'), and then copies the file to the correct location.
Once the plug-in has been installed, in order to use it it must be enabled using the .
The folder that is created by Audacity when running a Macro on files, or when an Export command is used in a Macro that is run on the current project, has been renamed to "macro-output" to give it a more meaningful name.
The created folder used to be called "cleaned" (which was a hangover from functionality that used to be in Audacity, bit was removed many versions ago).
The experimental mod-script-pipe is now available with Audacity for Windows and Mac. You need to enable it in Modules Preferences.
The default setting for the "Type to create a label" in Tracks Behaviors Preferences has been changed from "on" to "off".
When enabled "on", if there is already a label track that has the yellow focus border, you do not need to use "Add Label at Selection" or its Ctrl + B shortcut to create a new label. Just type your required label text to create a new label at the position of the editing cursor or selection region.
The change was made as some users were confused by: a) shortcuts not working when the label track has focus b) labels not being created when the label track did not have focus.
This will not affect any previous setting that you have, or have made, for this Preference unless you chose to have your preferences reset as part of an upgrade installation.
WAV and AIFF audio files are size limited to a maximum of 4 GB. This is a general restriction and not an Audacity restriction.
In earlier versions of Audacity if you exported a WAV or AIFF file that would exceed those limits the file would be corrupted and truncated and this would happen without warning.
For 2.3.2 we have implemented an error trap to catch this and stop it happening. Now when attempting to export an oversized WAV or AIFF file Audacity will not do this and you will get the following error message:
Clicking on the ? Help button in the message will show the following table in the Manual
Click on the bug number for full details in the bug thread.
P1 - Append recording into a collapsed track causes a crash
P2 - Mac: misleading error message when importing M4A without FFmpeg installed
P2 - Expand function after Append Record to a collapsed track fails
P3 - NoteTrack: Hidden notes on importing MIDI
P4 - Note Track: Vertical Zoom Reset produces max. zoom out and not a reset
P4 - Note tracks don't save the pitch height, which may lead to hidden notes
- detailed release notes for this release of Audacity
audacity-minsrc-2.3.0.tar.xz (n/a) - 10431768 bytes
SHA-256 bc9c9e3c826e7e9c481ef3adcdf6277836c099ca26c34bd7071d0522917fecd8If no selection is present, zoom focus is as it was before and is taken as the mouse pointer position.
Either of the two presets can be changed in Tracks Preferences using the dropdown menus.
Left-click, and click&drag, in the Vertical Scale remain available as a user-selectable option. The default setting is "off",
You can turn on advanced mode for vertical zooming from Edit > Preferences > Tracks Behaviors and selecting Advanced Vertical Zooming.
Icon Appearance
In dark theme the microphone and speaker icons are now brighter and not dulled as they were before.
Crash using SBSMS pitch change at low sample rate
Installer has old logo for 2.2.1 and 2.2.0
(Mac) Equalization: "Telephone" curve displays a flat line, no sound on Preview
Toolbars: open undocked if previously not shown, unless Reset Toolbars first
Analysis effects that create labels should give focus to label track
Control value may be out of range when using FloatingPointValidator
Analysis effects produce false indication that a label is open for editing
Import Uncompressed File Dialog Incorrect Reference to Menu Item
Wave Color not grayed out in TCP dropdown menu when in Spectrogram view
Hover indication on note track channel toggle appears on all tracks (when they rerender)
Unicode page encodings fixed ( ͡° ͜ʖ ͡°)
Un-muting with a single track unnecessarily activates the Solo button
Applying chain to file should zoom-to-fit
ID
Summary (3 tasks) ⇒
ID
Timer Record occasionally carries on recording past the scheduled end, requiring force quit
Linux: PULSE-AUDIO issues. Freeze repeatedly starting/stopping streams
Using File > Open to import audio gives wrong zoom level and no scroll bar slider
P2 2096 - High quality stretching in Change Pitch/Tempo causes the Preview to malfunction and remove the selection
P2 723 - Recording does not stop at end of selection.
P2 1534 - Linux: Malformed tooltips/"Untitled window" in taskbar when clicking or hovering over toolbar sliders
P3 1899 - Windows: previously deleted folders are unnecessarily re-created on next Save
P3 2007 - Windows: Empty folder created on Import if last used import folder does not exist
P3 1762 - Importing keystrokes can fail to import keystrokes that are not in standard set
P4 2080 - Windows: Using WASAPI, after recording, playback can fail with "opening sound device error"
P5 2050 - Misleading LAME version error message
P4 2084 - Enh: Auto-select behaviour changed from previous version and not documented.
P4 1248 - Windows: TAB does not navigate out of mouse-created focus in sliders.
P4 2087 - Mixer Board gain control dialog is ridiculously over-long vertically
P4 2064 - Linux: ESC key does not work to abort drags in the Timeline Ruler
P4 1965 - Enh: Track name overlay display for all track types
P4 2051 - Shortcut for Edit>Clip>Boundaries>Split (Ctrl+i) should be in the Standard shortcut set
P5 2053 - Splitting or joining collapsed stereo tracks causes broken scroll bar behavior
Graphic EQ
Sample Format
Stereo
Mono
16-bit (default)
6h:45m
13h:31m
24-bit
4h:30m
9h:01m
32-bit
3h:22m
6h:45m















New keyboard commands for working with clips
Help buttons ? in Preferences, Effects, Generators and Analyzers - and other places
Non-Greying out of effects when no selection (and explanatory dialog with help button)
Playback of MIDI (and Allegro) files imported into Note Tracks is now available.
'Center' option in Selection Toolbar
Stem plots
Major overhaul to documentation/manual including many new images and streamlined text on landing pages for in-program help.
Overhaul of much code:
Overhaul of envelope handling code to deal with some anomalies
Overhaul of exception handling for greater safety
New Logo
Most of the bugs fixed were more minor, such as bug 463 which was about a case in which the numbering on the timeline could display incorrect times.
Using File > Open to import audio gives wrong zoom level and no scroll bar slider
ID
Summary (5 tasks) ⇒
ID
Timer Record occasionally carries on recording past the scheduled end, requiring force quit
Linux: MIDI playback timing / synchronisation problems
Opening a second project from Mac's Finder produces a second inaccessible instance of Audacity
Linux: PULSE-AUDIO issues. Freeze repeatedly starting/stopping streams
Audacity now comes supplied with four pre-configured, user-selectable, themes. This enables you to choose the look and feel you prefer for Audacity's interface. see the Themes page for details.
Light theme: this is a light theme loosely based on the look and feel of earlier Audacity versions, but given a contemporary twist with more modern-looking buttons and icons.
Dark theme: created by the Dark Audacity project. This is similar to the Light theme, with the same buttons and icons, but given a dark twist.
Classic theme: The one you know and loved. This theme is a re-creation of the look and feel of earlier Audacity versions.
High Contrast theme: some users with poor eyesight benefit from a high contrast that is 'eye-popping' for most people.
The theme to use can be chosen at Edit > Preferences > Interface
Playback of MIDI (and Allegro) files imported into Note Tracks is now available. Please see the Note Tracks page for more details.
This should just work on Windows but for playback on Mac and Linux additional software may be required, see this section on the Playing and Recording page.
But note that there will no use of the Playback meter while Note tracks are played.
There is a new entry in the Tracks Preferences for Display samples. This setting changes how Waveform and Waveform dB views are displayed. It only affects the appearance of the waveform when you are so far zoomed in that you can see the individual sample dots. At lower zoom levels it makes no difference.
Stem plot: This is the default setting which draws a vertical line from the track center line to the sample dot, giving a clearer impression of the relative amplitude of the samples. As seen in the images below, when zoomed out close to the minimum for a stem plot, the horizontal distance between sample dots may be more uneven than seen with the connect dots default.
Connect dots: This is alternative setting yields a waveform where each sample dot is connected to the next sample by a line drawn between them.
Uneven spacing is due to "aliasing", but zooming in further will equalize the spacing whether choosing Connect dots or Stem plot.
We have made the Menus shorter and clearer than in previous Audacity versions. The menus have been simplified without losing functionality. The most commonly used functions are found in the top levels of the menus. The functions moved down into lower submenus are better organized.
This is not just a rearrangement. We also added new menu items to make the layout more logical. There are new menu items for exporting as MP3 or WAV. Previously you had to export audio, and then choose the format. You still can do that, but these new items are there for convenience.
There are two new additional menus that are hidden by default. They can be turned on at View > Extra Menus (on/off) or the Interface pane of Edit > Preferences.
These extra menus have many extra less frequently used commands. They are particularly useful to VI users, but normally-sighted users may find them useful too.
Image of the Extended Menu bar as it appears on Windows
The Ext-Bar menu provides access to operations that are not available in the default Audacity menus. These will be of most interest to visually impaired users or those who have difficulty using the mouse.
can be assigned to these commands if required.
The Ext-Command menu provides access to extra commands for and movement of the editing or playback cursor that are not available in the default Audacity menus. These will be of most interest to visually impaired users or those who have difficulty using the mouse.
can be assigned to these commands if required.
From Audacity 2.2.0 onward the default recording mode has changed so that when you click the Record button on Transport Toolbar, or use the R, Audacity will record at the end of the currently selected (or only) track.
If you hold the Shift key down the Record button in Transport Toolbar will temporarily change to . Then clicking on this modified Record button, or using the shortcut Shift + R will cause Audacity to create a new track and begin recording on that track from the current cursor position (or from the left edge of a region on the Timeline).
Many places in the user interface have had a help button ? added. Examples are all the Preferences dialog panes, all the Effects, Generators and Analyzers and some error messages.
Clicking on that button in the dialog will link you to the appropriate page in the Manual.
Example: the Amplify effect. Try clicking on the "?" at the bottom right of this image.
For Audacity 2.2.0 we have reduced the number of preset shortcuts in the application to a "Standard" set. We did this to simplify the set of shortcuts somewhat and to provide greater flexibility for users who want to set their own custom shortcuts.
You can choose to revert to the full set of shortcuts that were in 2.1.3 and earlier by selecting "Full" from the dropdown menu accessed from the Defaults button in the Keyboard Preferences dialog.
You can use the Defaults button to switch between the two provided default sets of shortcuts at any time.
See Commands and Keyboard Shortcut Reference for more details.
There are now four available settings in the Selection and Audio Position Boxes in Selection Toolbar for the manner in which the details of your selection are displayed:
Start and End of selection: the start time and the end time of your selection (default setting)
Start and Length of selection: the start time and the length of your selection
Length and End of selection: the length and the end time of your selection
Length and Center of selection: the length and the time at the center of your selection
New commands, all of which interact with the clips on the focused track. As yet, there are no default shortcuts:
Transport > Cursor to > Previous clip boundary
Transport > Cursor to > Next clip boundary
Select > Clip Boundaries > Previous clip boundary to cursor
Select > Clip Boundaries > Cursor to next clip boundary
Select > Clip Boundaries >
Select > Clip Boundaries >
We have now provided an error trap for situations where you are running out of available disk space.
You will now see the error message: "Audacity failed to write to a file in <device>"
This is particularly useful when recording as Audacity will stop recording when the error is trapped, preserving your recording up to that point.
This page New features in Audacity 2.2.0 - appendix gives an overview of further new functionality that has been introduced in this release of Audacity.
Audacity 2.2.0 - detailed release notes for this release of Audacity
One cluster of bugs we fixed relate to Unicode. Unicode is a system for representing many non-English letters and symbols. We, Microsoft and Apple all have made mistakes with Unicode that affected Audacity 3.0.0. One problem we tracked during 3.0.0 turned out to be a Windows update issue with Unicode input, which was resolved by a later Windows update. Disappearing checkmarks in macOS Big Sur release turned out to be a Unicode issue, believed to be in Apple code, which we now work around in 3.0.2. A mistake we made with Unicode prevented Audacity working in Korean and Japanese.
Some of our bug-fixes are small changes in areas where the previous Audacity behaviour was not as we wanted. 3.0.2 may only be a 'point' release, but we think it's one most people using 3.0.0 will want.
After 3.0.0 was launched a few users discovered a couple of mysterious bugs which we had not encountered in our extensive QA testing of alpha and Release Candidate builds. These two important bugs that 3.0.0 users saw were hard for us to track down as we could not replicate them. We added extra diagnostic information to help us do that:
Error: Failed to open database file
There was an error which only occurred occasionally for a few users but had us mystified. Usually this seemed to occur when trying to import an audio file, but there may have been other ways it could happen. It did not appear to be causing users to experience data loss or damaged projects. It was this bug: Bug 2700 - "Failed to open the project database"
We added a Show Log to this error message so we could gather more information about this to aid the developers in analyzing the issue. This led to what's probably a solution, as Jack L, with this extra logging, was able to get the problem sufficiently often for us to get a handle on it. This extra information told us that in some circumstances we were trying to access the disk before it was ready again, with back to back requests too quickly. Paul then changed the logic of opening a database so that two important requests were always one after the after. This should address the opening issue. Leland added a retry, so that if SQLite can't yet read the database, it tries again, but fractionally later. The retry timeout should benefit all code in Audacity that reads the database, not just at the time of opening. Jack L then ran his torture tests workload and the problem he experienced was gone.
Even so, because the original error was only occasional, we can't know for sure that it, or similar issues, are gone! We still have the extra logging in Audacity. If you do encounter the dialog indicating a problem, please click on the Show Log chevron to generate the log and send us a copy of the screenshot to the Audacity Forum. You may see a variant of the message, "The project's database failed to reopen"
False recovery offered on launch
This is another mysterious issue which only occurred very occasionally and was foxing us.
Sometimes after exiting Audacity without saving the project when offered, on the next relaunch a false recovery can be offered when there is really nothing to be recovered as no crash has occurred to cause this. We think this error had the same underlying cause, but we don't know for sure.
This bug is Bug 2732 Faux recovery offered on launch (very moonphase). If you encounter this and accept this recovery it "recovers" an empty project and no damage is done.
If you do see this error, please let us know what you can of how it happened.
With the release of Audacity 3.0.0 the project file structure of Audacity was changed significantly with the entire project contained in a single unified database file.
If you have already updated to 3.0.0 you should already be aware of this.
But if you are updating from any earlier 2.x Audacity version please read Updating from Audacity 2.x to Audacity 3.x.
The Manage Macros dialog has been improved for this release:
The Cancel button has been removed
It is replaced with a Close button
A new Save button has been added to enable you to save the results of editing a Macro.
The Save button is grayed-out until you edit a Macro.
We have extended the options in Directories Preferences to include a new entry for Macro output.
If you leave the entry for Macro output blank then Audacity will default to creating a folder called "macro-output" in:
Windows: C:\Users\<your username>\Documents\Audacity
Mac: /Users/<your username>/Documents
2708 Nyquist effects fail silently with One hour plus stereo
2706 Win: Vocal Reduction and Isolation most options fail
2698 Noise Gate fails silently if "hold" is non-zero
Cannot open project that's in a read only folder - error message vague
Compressor with audio before T=0 crashes Audacity
Mac: EGAT preview dialog is hidden behind the EGAT dialog
Opened projects not being removed from "audacity.cfg"
Linux: AUP3 projects use incorrect char size on "differently" configured wxWidgets
Failed to execute a project file command (on server)
2701 Progress dialog interferes with scripting
2714 (Japanese & Korean) "Unable to parse project information"
2722 Noise Gate fails on a one hour stereo selection
Cleared "Recent Files" are restored on next launch
Mac: Missing sub-menu check marks in French
Metadata Editor: changed size is not remembered/restored on next use
Windows: Cannot edit labels with emoji in them correctly
Mac: Stop button in EGATs with Preview does nor stop the preview
Export: Incorrect handling over 0 dB
Coloring of tracks in Mixer Board are awry
Mac: VI users get trapped in radio buttons of Keyboard Preferences
Apply macro may not create the macro-output folder in the source directory
2723 VST_PATH environment variable fails for non-standard locations
2209 Nyquist: Audacity crashes when running seq-write-smf
2522 In Macros, Record New Track and Play with a selection do not wait for completion.
Plug-ins listed in reverse alphabetic order in Plug-ins Manager
Mac: keyboard navigation problem in Libraries preferences dialog
Audacity may suggest installing FFmpeg even when FFmpeg is installed
2733 Noise Gate 'Level Reduction' has a minimum of -60 dB
2726 Enh: Some preference changes are not written until Audacity exits
2717 Linux: Internal Error at DBConnection.cpp line 275
Allegro (.gro files) cause crash with undo/redo
Bitrot for Docimage script
Move the actual build information to the top of the build information tab
Import>Audio failure error message is misleading
Enh: Remove the "Variable Speed: Fast / Standard" option from MP3 dialog
Recent files list can be replaced by ExportCL commands
Audacity 3.0.2 - detailed release notes for this release of Audacity









This page is an overview of prominent new functionality that has been introduced in Audacity 3.0.0
Version 3.0.0 is primarily a release for a unitary, single self-contained, project file.
Details of all the major changes since 2.4.2 can be found in Audacity 3.0.
Audacity 3.0.0 introduces the new AUP3 project format. Project files saved with this version will have an aup3 extension, for example My-Project.aup3. We believe that this new project format will make life easier for Audacity users, as it replaces the previous project storage format - which used an AUP file and its associated _data folder full of little audio clips - with a single project file that integrates those two parts.
The old structure caused too many users to lose or damage their projects by moving or deleting the project components. The new single project file structure precludes that happening.
Once you have saved the project in the new AUP3 format they can then no longer be opened in previous versions of Audacity.
The workaround is to Export as WAV files, exporting individual tracks using and then Importing those into older Audacity versions.
Active projects cannot be saved to a FAT/FAT32 formatted drive as FAT is subject to a maximum file size of 4GB which can easily be temporarily exceeded when editing.
Saved Projects with the new unified file structure should not be larger than similar projects with the old multiple files structure.
As you work on a project, Audacity will consume additional temporary disk space. This is normally released on closing the project. This is not new with Unitary Project File, previous versions of Audacity also used to do this.
Extensive speed testing has shown that for most work in Audacity the new project file can be a little faster than the old project structure.
This is especially true of using the Effects and Generators which run faster with the new project file.
Automatic Recovery (following a crash) is different in Audacity 3.0.0. It is simpler with no orphan block-files or missing block-files to worry about
When Audacity is launched following a crash it will offer to recover the crashed projects.
You can choose to either accept the recovery or to discard the projects.
You can select projects for either action by clicking on their checkbox, or you can select all by clicking on Select.
In addition to the single database project file the database also creates two temporary work files WAL & SHM files. For example My-Project.aup3-wal and My-Project.aup3-shm. On Mac there is only the WAL file.
These are deleted on closure of the project or on exit from Audacity.
Do not delete them or move these temporary files while the project is open as this will destroy the project.
Windows blocks you from doing this but macOS and Linux do not.
There is a new backup command for projects: File > Save Project > Backup Project.
This saves a copy of the current project as an AUP3 file, but with a new name. It is 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 Project As..." using this command will leave your current project open enabling you to continue working on it.
You are strongly advised to make backup versions of your project at key stages in your project so you can return to that stage if you mess up.
Corsican language has been added for 3.0.0, thanks to Patriccollu.
Marathi language has been added for 3.0.0, thanks to Mukul Kulkarni.
Thanks also to all our regular translators who brought translations up to date for 3.0.0.
A new analyzer has been introduced called Label Sounds. It supersedes and replaces the old Sound Finder and Silence Finder analyzers.
Label Sounds is a tool which can useful to label the different songs or sections (or silences) in a long recording, such as the tracks from an LP or cassette.
This analyzer is an upgrade of the old Sound Finder from previous versions of Audacity. It is more accurate, and more versatile than previous versions, supporting both region labels and point labels.
Accessed by: Analyze > Label Sounds...
It detects the audio level in the selected track(s). When the track level exceeds a specified threshold level, the audio is considered to be "sound", and when below the level it is considered to be "silence".
There are options to add point labels before or after each detected sound, region labels around each sound, or region labels between each sound (effectively labeling the silences).
You can still continue to use this Sound Finder if it is present in your Audacity app as a result of an earlier Audacity version download.
Default folder locations have been added enabling you to specify the folders to be used for each of the Audacity actions: Open, Save, Import and Export.
If you set a default folder for any of those actions Audacity will always offer that folder location when you invoke that action.
If a particular action's default folder is left blank (default setting) then Audacity will offer the last-used location for that action.
The default setting is for all to be blank.
See Directories Preferences for more details.
Import and Export of Macros has been added to the Manage Macros dialog.
Only one Macro can be imported or exported at a time.
Comments can now be added to Macros to enable you to document what is happening in the Macro.
There is a new command "Comment" in the Macro command set. Editing its parameters enables you to type the text of your comment.
The Noise Gate effect has been improved for version 3.0.0 of Audacity. It now supports faster Attack times (down to 1ms), and provides separate controls for Attack, Hold and Decay. The effect can also process much longer selections in one pass (up to 13.5 hours at a sample rate of 44,100 Hz.)
In Tracks preferences you can now set Multi-view as your preferred user-default view for tracks.
We realized that we had a couple of settings in Tracks Behaviors Preferences that affect the operation of the Cut, Paste, and Delete editing commands in perhaps unexpected ways:
Editing a clip can move other clips
Enable Cut lines
So a new page was added to the Manual to explain the subtleties of these behaviors. See .
We have changed Mixer Board so that its window always remains on top when it is in use.
Many users have requested this and the original developer always wanted to do this but could not at the time because of issues with the libraries used for this feature.
These libraries have been updated by the provider and we can now make Mixer Board a top window on all three platforms.
A Repeat last used command has been added for Generators, Analyzers and Tools. These are not in the menus but are "ghost" commands that you can assign custom shortcuts to.
This enables you to simply repeat the last generator, analyzer or tool that you used, with the last settings that you used.
Nyquist has been updated to the latest Nyquist Version 3.16
This has enabled us to clear a lot of long-standing Nyquist-related Audacity bugs.
A large number of bugs were fixed for this release.
Here is a small selection of some of the most important.
P1 - Some effects (including equalization effects) delete Envelope Control Points, or do not move them when timeline changes
P1 - Change Pitch effect may create spurious clip at end
P1 - Linux: Crash when applying or previewing Sliding Stretch effect on stereo track
P2 - Mac: COMMAND + V paste limitations in standard file save dialogs
P2 - Mac: Cut/Copy from file save dialogs using shortcuts does not work
P2 - No error/warning message when using a missing aliased audio file
P3 - Noise Reduction preview failure when track rate is different from project rate
P3 - Sound Activated Recording fails when recording meter disabled
P3 - Equalization effects ignore and remove any amplitude envelope
- detailed release notes for this release of Audacity
Relaunch Audacity
File > Open...
But note carefully that this will remove your Undo History and the contents of your Audacity clipboard.
P1 2630 - A project saved with an imported MP3 with Unicode metadata cannot be opened
P1 2656 - Cannot horizontal scroll when paused in Play-at-Speed
P1 2669 - Win: Save As can be used to overwrite the existing project without warning
P2 2464 - Cannot drag just the selected audio and label with Time Shift Tool
P2 2437 - Mac: "Open with" fails when Audacity is running
P2 2473 - Linux: Numbers on meters have opaque backgrounds
P2 2487 - Playback meters do not respond during preview of non-real-time effects
P2 2491 - Reset Configuration does not reset Extended Import preferences
P2 2509 - Filter curve and Graphic EQ help links are broken in release version
P2 2527 - Reset Configuration does not reset Project rate or selection timers
P2 2573 - High / Low Pass filters limited to ~94 mins stereo at 44100 Hz
P2 2581 - Inconsistent behavior when pasting and not enough room
P2 2593 - Play-at-Speed does not play unless you have used normal Play first
P2 2616 - Labelled Audio Cut and Delete disabled by Sync-Lock
P3 2366 - Macros: Run does "Select All" ignoring setting in Tracks Behaviors Preferences
P3 2460 - Enh: Can't select "Multi-view" as default view mode in Tracks preferences
P3 2510 - Mac: Drag&Drop of a project file onto Audacity in Apps bar or Finder fails if Audacity is active in the Apps bar
P3 2534 - Change Speed merges selected clip with adjacent clips - residual fix to be tested
P3 2564 - Metadata: Artist and Year tags missing on M4A(AAC) exports
P3 2611 - Mixer Board does not stay on top of main window







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.
As this Toolbar is read-only you cannot use it to reset the audio position, to do that you need to use the Selection Toolbar.
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.
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.
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.
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 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.
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.
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 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.
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 Multi-view display.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
P1 2227 - Mac: Audacity does not run properly on macOS 10.15 Catalina
P1 2237 - Equalization effects have no Import or Export for curves
P1 2261 - Graphic EQ sliders have no frequency labels
P1 - Track heights are reset to default on project re-opening
P1 - Playback does not start at the saved cursor position on reopening a saved project.
P1 - Zoom in fail when playing
P2 2062 - Export as WAV does not remember the previously used setting
P2 2214 - Rendering a single track unnecessarily moves the track to project bottom
P2 2218 - Rendering a single track unnecessarily strips it of its properties
P2 - "Ignore blank space" Preference fails on Export Multiple based on "Tracks"
P2 - Loop Quick-Play does not scroll when playing
P2 - Timer record: if a labels are present recording starts at last label position - not cursor position
Audacity 2.4.0 - detailed release notes for this release of Audacity
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 .
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 this table in the Audacity Wiki.
Two bugs we fixed which noticeably change behavior are:
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 P2 Bug 344 - M4A Quality slider has no control of bitrate setting or AAC quality
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.
This was P3 Bug 1904 - Audio offset not honored in Export/Export Multiple/Export Selection
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 P2 Bug 2213 - When Solo button is "Multi-track" Export is not accurate - can lead to data loss
The former Equalization effect has now been split into two separate effects. We did this as part of fixing some bugs with the effect:
For this maintenance release we have decided to withdraw some pieces of functionality which are considered to be no longer useful or relevant.
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 Nyquist IDE. A lot of the important functionality is already built into the Nyquist prompt in Audacity.
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.
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.
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.
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 2077 - Mac - FFmpeg Custom options dialog opens behind Export Audio dialog
P1 2112 - Crash when opening Equalization settings in a Macro
P1 2119 - Linux: Incorrect behaviors in "Manage Macro"
P1 - Track deletion while in Record/Pause state crashes Audacity
P1 - Silence Audio deletes MIDI notes
P1 - Tabbing between labels now only works if the label track is selected
P1 - Crash when attempting to time shift multiple tracks
P1 - Linux: Many effects (Repair, Paulstretch, Reverb) much slower
P1 - Audacity throws warning dialog on opening project if it contains silent blockfile(s)
P1 - Uncompressed exports in formats that have no (realistic) size restriction fail the 4GB trap for WAV & AIFF - regression on 2.3.1
P1 - Mac: Cannot use Enter to effect an Effect after entering numeric data in a field - regression on 2.1.3
P1 - Punch&Roll record inserts a squelch/screech noise at start of re-recording
P2 - FFmpeg: M4A Quality slider has no control of bitrate setting or AAC quality
P2 - Mac: ENTER does not close/apply effects unless user has turned on Full Keyboard Access
P2 - Moving tracks or swapping stereo channels during playback does not work correctly.
P2 - Mac: Modal dialogs cause 100% Audacity CPU when open with any AU or graphical VST/LV2 effect
P2 - Tracks menu error messages do not have "?" help buttons to link to the Manual
P2 - crash after attempting to export as OGG at very high sample rate
P2 - When Solo button is "Multi-track" Export is not accurate - can lead to data loss
P3 - GSM 6.10 files cannot be exported - failure messages are unhelpful un-illuminating
P3 - No error reported to user and crash when FFmpeg attempts invalid custom export of WAV with mp2 codec
P3 - Mac/Linux: Text export for Contrast and Plot Spectrum does not supply extension if omitted
P3 - MIDI or Allegro export filter does not enforce output format cross-platform
P3 - Custom FFmpeg Export: an empty presets list can be Exported
P3 - Windows: Plug-in manager does not properly disable SC4
P3 - Mac: Sticky Tooltips
P3 - Windows: DirectSound Sound Activated Recording does not record correctly or pauses permanently after 12 seconds
P3 - TXT and XML exports are not to Documents and may require elevation to save
P3 - Cryptic error message when existing project cannot be saved
P3 - Keyboard Preferences: Closing subtrees can leave highlight on wrong item.
P3 - Preview fails (with Error Opening Sound Device) for built-in Generate effects when no selection
P3 - Audio offset not honored in Export/Export Multiple/Export Selection
P3 - 24-bit WAV (and AIFF) export is wrongly limited to 3GB
P3 - Label editor: After it closes, no control is the focus
P3 - "Q" shortcut for "Toggle Spectral Selection is not in the Standard set
P3 - Screenshot tool: no way to exit using the keyboard
P3 - Spectral Selection Toolbar can be truncated when undocked
P3 - Windows: Modules page of preferences is not read by NVDA screen reader
P3 - Updating Audacity can cause messed up toolbar layout
P3 - Import2: Incorrect error message if file not found
P3 - Bugs that won't be fixed relating to on-demand loading of aliased external audio files
P3 - No error message when trying to delete with no selection
P4 - Welcome Message: Local links to "Quick Help" and "Manual" do nothing if help is not installed.
P4 - Time track selected by itself cannot be removed with Tracks>Remove Tracks
P4 - Metadata Editor: Tags without values can't be added
P4 - Modifier keys ignored when focus is on time box in the Selection Toolbar
P4 - Win/Linux: Audacity crashes with LADSPA blop plug-ins
P4 - Mis-handling of envelopes when split-deleting, or when cutting with cut lines enabled
P4 - Windows: Strange cursor changes Works for me on 2.3.2
P4 - Linux: Mixer Board meters do not update when Meter Preferences are updated
P4 - "backslash percent" not saved in effect presets
P4 - Multiple non-modal "Help from the Internet" windows
P4 - Incorrect level shown in Mixer Board meter when track has positive gain
P4 - Numeric control units are not translated
P4 - Built-in Macro name "MP3 Conversion" does not translate
P4 - Access keys not shown (Japanese)
P4 - ENH: Noise Reduction error message for no selection is unhelpful
P4 - Mac Accessibility: if a text box is the focus, pressing enter does not press the default button
P4 - GetInfo: localization creates invalid JSON
P4 - Nyquist: Assert when receiving multibyte characters
P4 - Crossfade Tracks effect may desynchronize tracks
P4 - AUD-GET-INFO command fails if data contains backslash
P4 - selected audio: timeline and track show different selected time range
P4 - Shipped macros are not protected against edits. Edits can be made, but there is a Restore button
P4 - Sample Rate dialog does not appear when track has custom sample rate
P5 - "Undo Recover" does not undo.
P5 - Incorrect pointer (cursor) when rearranging tracks
P5 - Unwanted duplicate .mo files on Mac.
P5 - AIFF exports GT 4GB are trapped but error message is only "WAV" - German translation also OK now - was not so before
P1 1750 - Equalization: EQ control points can disappear if the points are at the same frequency
P1 2031 - Equalization: presets under the Manage button do not save custom EQ curves
P1 2088 - Graphic EQ ( and Filter Curve): Manage button does not work
P2 - Equalization effect: possible crash when using Manage > User Presets
P2 - Filter Curve (and Graphic EQ) corrupt saved curves (on the right)
P2 - Filter Curve and Graphic EQ have no factory presets (available in 2.3.2 and earlier)
Audacity 2.3.3 - detailed release notes for this release of Audacity


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.
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.
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.
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.
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.
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.
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.
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.
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
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.==
(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.
(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.
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.
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.
(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:
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 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.
(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.
(Linux) When configuring effect parameters in "Edit Chains", the "Preview" button is not intended to be functional. Pressing it may cause a crash.
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.
(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) 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.
(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
(Linux) Extended Import: Clicking "Move rule up" when there are no rules or filters causes a crash.==
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.==
(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.
(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.
You may see the error Application configuration incorrect when launching Audacity after installation. This mainly affects some Windows XP or 2000 machines. This can be fixed by downloading and installing the appropriate Microsoft "Redistributable Package" as follows:
Microsoft Visual C++ 2008 SP1 Redistributable Package (x86) for 32-bit Windows
Microsoft Visual C++ 2008 SP1 Redistributable Package (x64) for 64-bit Windows.
Be sure to get the correct package according to whether you have 32-bit or 64-bit Windows. To check, right-click over and choose . If 64-bit is not mentioned, you have 32-bit.
(Linux) Fixed Audacity could not be compiled against FFmpeg 0.7.x and 0.8.x.
(Linux) Playing existing tracks while recording in mono could cause recordings to be distorted or low-pitched.
Automatic Crash Recovery in the event of abnormal program termination.
Fast "On-Demand" import of WAV/AIFF files if read directly from source.
FLAC now fully supported. Added support for optional FFmpeg library for import/export of AC3/M4A/WMA and import of audio from video files.
Unexplained crashes or corrupted audio occurs (note this can happen if the computer is low on memory or disk space).
For problems that occur when reopening or working in a project, the log file at Help > Show Log....
(Windows and OS X) VST/Audio Units Plug-ins: On first use and otherwise when requested, Audacity scans for and loads VST effects before the main interface appears. On OS X, Audio Unit effects are always loaded, which can lead to a very slow launch if there are multiple plug-ins. Occasionally, an incompatible or badly written plug-in may lead to a crash or freeze on launch. Known plug-ins affected:
Waves Version 7 Audio Units on OS X
Native Instruments Guitar Rig v3 and v4 on OS X (v5 does not have this issue).
(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.
Album art and lyrics in imported metadata are lost when exporting.
Exported "Comments" ID3 tags are not recognized by Windows Media Player or Explorer.
Genre WAV info tag (IGNR) not supported due to limitation in libsndfile.
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.
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 FFmpeg 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.
Muting specific time-shifted mono tracks when exporting produces audio at wrong point on timeline in exported file if muted tracks are to left of unmuted.
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.
Dither noise is incorrectly applied by default if exporting to most formats where the bit depth is the same as (or higher 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.
(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 (;).
On-Demand WAV/AIFF import not available if using the optional FFmpeg importer (that is, if "FFmpeg-compatible files" set in the import dialog).
Export Multiple can export invalid files (despite reporting that export was successful) if the track is muted or empty (it is intentional that muted tracks are not exported).
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".
(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).
WAV or AIFF exports may either generate a "Libsndfile says" error or be low volume, distorted or unplayable if you import a file having metadata following the data, or there are other issues with the metadata content. Workaround: Click File > Open Metadata Editor, press "Clear" to empty the metadata, then export. If you are on Linux and see "Libsndfile says", you could try updating to libsndfile 1.0.25 then recompile Audacity against that.
When importing a MIDI track, the channel selection buttons to left of the track are not currently available.
(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.
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.
(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.
(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) Tracks that were selected on project save are deselected when re-opening the project.
(OS X and Linux) In some locales, Preferences text may be truncated or overlapped, or dropdown boxes truncated.
(OS X) The "Cmd - Wheel - Rotate" mouse binding does not zoom in unless you uncheck "Zoom using scroll ball while holding Command" at "Mouse and Keyboard" in the Mac System Preferences.
(Windows) The "Files Missing" warning always restores maximised windows to smaller size.
(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.
After changing language in Preferences, a few parts of the interface don't change until Audacity is restarted.
Audacity has several weaknesses in preserving the context of the audio being worked with:
If playback scrolls, pressing Stop leaves the waveform where it stopped and the cursor invisible. Pressing Play to resume then scrolls the waveform to start at the left edge, hiding the previously visible context before the cursor position
Current scrolling behaviour makes it too hard to watch the waveform progress, with a single shift of cursor and waveform position when cursor reaches the right edge
Zoom to Selection shows none of the surrounding context
By default, all audio in the project is selected if an action requiring a selection is requested when there is no selection (this behavior can be turned off in the Tracks Preferences). If enabled:
You can always apply effects to the whole project in one step, but you can also delete audio in all tracks if you press Delete when there is no selection. That is easy to Undo, but we aim to tweak this behavior and make it more customizable in a future Audacity.
A few items in Edit menu are incorrectly grayed out if no track is selected.
If Sync-Lock Tracks is enabled, there is no indication of the cursor in the Sync-Locked tracks.
If you save a region with Edit > Save Region then click OK in Preferences, the saved region cannot be restored.
Mouse Bindings are not currently configurable by the user.
Snap To state and Selection Format when Snap To is on are global. Therefore changing these in one project will make them show incorrectly in any other projects.
Snap-To does not move the cursor when first enabled or when the selection format is changed.
We're aware that some error messages in Audacity are not as helpful as we would like them to be. If you see a cryptic error message from Audacity, try a search (or ask) on https://forum.audacityteam.org/
A track or clip whose whole length is selected cannot be dragged up or down into an adjacent track. Workaround: Before dragging, click in the waveform to remove the selection, hit ENTER to deselect the track, or hover over an unselected part of the track or clip.
(Linux) If Audacity is left open but without focus, its CPU use will rise slowly until all available system CPU is consumed. This is a bug in wxGTK 2.8.10 (not previous versions) - see http://trac.wxwidgets.org/ticket/11315 . This issue can be fixed by updating to wxGTK 2.8.11 or 2.8.12.
(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.
(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 some other unique name.
In projects containing an hour or more of total audio, there may be a delay compared to previous versions of Audacity when:
Creating a label or label track
Dragging selections with the keyboard (Workaround: Hold SHIFT then press left or right arrow a few times per second instead of holding the arrow key)
Dragging sample points with Draw Tool
Using Cut, Copy, Paste, Delete or Silence Audio.
The delay may be more evident on slower computers. In addition, label text may not be recovered if there is a crash.
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.
On Mac, Audacity may freeze if JACK is launched by QjackCtl then Audacity is launched. Workaround: Use JackPilot to launch JACK, or launch QJackCtrl after Audacity and JACK are running.
(OS X and Linux) PortAudio's default latency values which are used when recording with software playthrough are much lower than Audacity's default "Audio to buffer" setting. This may cause playthrough or recording glitches when recording with software playthrough enabled, especially when using pulse on Linux. Workaround for Linux: record from an (hw) device instead if software playthrough is required.
(OS X) Playback to Bluetooth headsets gives an error. Workaround: Revert to Audacity 1.3.3 (this may only work with stereo headsets), or use Soundflower to send the Audacity output to an audio application that works with the headset.
(Windows) When a USB device is connected, the Mixer Toolbar input slider for that device (and sometimes for any device) may wrongly appear active even though it has no control over the device's input level. Sometimes the Audacity slider will apply a software gain to the level (which is dangerous as it will only make the same clipped input quieter rather than stopping the clipping). Sometimes the Audacity slider will not affect the input volume at all. Workaround: use the slider in the Windows Control Panel where available, or any gain control on the device, or reduce the output being sent to the device.
(Windows) Recording at 24-bit quality or higher isn't possible even with devices that support it due to current limitations in PortAudio.
(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.
Adding or removing an external audio device while Audacity is open will not be automatically reflected in Device Toolbar or Devices Preferences. Workaround: Use Transport > Rescan Audio Devices.
Calculation of "disk space remains for recording (time)" incorrect when recording in 24 bit quality.
Play-at-Speed slider: Change of playback speed is no longer automatic after you move the play-at-speed slider. To change speed, move the slider, then click the green button to left of the slider to play at the new speed.
Timer Record cannot maintain scheduled duration if system clock changes
The Transport menu lacks the combined "Play/Stop" command, but it has a shortcut which is set to "Space" by default. To change this shortcut, or to add a shortcut for the separate "Play" and "Stop" commands shown in the Transport Menu, go to the Keyboard Preferences.
(OS X) The "Hardware Playthrough" option in Recording Preferences is currently unsupported on all known Mac hardware. Try the "Software Playthrough" preference instead. If that does not work, the third-party LineIn application also provides software playthrough.
(Windows) Audacity is incompatible (or not fully compatible) with some professional soundcards or audio devices, and may crash or have limited or faulty functionality. Occasionally, this may be true of some AC97 devices built into the motherboard. Workaround: make a different soundcard your default when using Audacity, but please e-mail us the following details to our feedback address:
Your version of Windows and Service Pack
Name, model number and driver version number of the soundcard or device.
Note: Multichannel Recording in Audacity is often not possible with professional devices unless you compile Audacity with ASIO support.
Nyquist effects: in locales where comma acts as the decimal separator, entering a comma in a text box to left of a slider only produces the whole number before the comma. Workaround: use a dot (period) as the decimal separator
The following effects remove envelope control points: Change Speed/Pitch/Tempo; Equalization; Noise Removal; Sliding Time Scale/Pitch Shift; any Nyquist effect in the Effect menu. Workaround: Use Tracks > Mix and Render to apply the envelope to the waveform before applying the effect. Reverse retains the control points, but does not move them.
Truncate Silence does not adjust clip boundaries inside the selection being truncated.
Truncate Silence doesn't work intuitively if run on multiple tracks. It may be preferable to run it on each track at a time.
Truncate Silence: The resultant silence after the effect is 1 ms less than that expected, unless the result was expected to be 1 ms.
Truncate Silence may not truncate a silence that is exactly the same length as the specified "min silence duration".
(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 .
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). Also note that projects containing more than 2^31 samples of total audio cannot be correctly saved.
Projects created by Audacity 1.1.x or earlier are no longer supported. Workaround: Export each project track as WAV using the appropriate legacy version of Audacity, then import the WAV files into current Audacity.
Projects created by Audacity 1.2.x are partially supported - there is a possibility Audacity could corrupt them. Please make a backup copy of the project's .aup file and _data folder to a new folder before opening the project in this version of Audacity. Once you save the project in this version, it cannot be opened in 1.2.
Projects created by previous versions of Audacity may contain audio "block files" longer than the project format allows. Reopening such projects in previous versions might or might not result in deletion of the overlong audio. Audacity has been provisionally fixed so that it can no longer create or delete overlong files, but it cannot read any such files it encounters. If overlong files are found, a "Problems Reading Sequence Tags" message will display .
If you continue with the offered repair then choose "Continue without deleting" in the Orphan Block File(s) dialog, the overlong files will be retained as "orphans" in the project's _data folder but will appear as silence in the track(s).
As long as you choose "Close project immediately" in the Orphan Block File(s) dialog, the project will quit and will not be changed in any way.
If you encounter the "Problems Reading Sequence Tags" message, please write to our feedback address with a copy of the .aup file and the log as found at Help > Show Log.
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.==
Some interface text or markings remain in black when using High Contrast light-on-dark themes, so cannot be read properly
The yellow track focus border remains "on" even when toolbars or dialogs have focus.
(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)
(Windows and OS X) Some USB or Firewire recording devices only record silence, or only offer mono recording for a stereo device, or only mono or stereo for a device that previously supported multi-channel recording. Workaround: You can try 1.3.10 Beta or earlier (including 1.2.5/6), but these versions may have other bugs or limitations.
Please report make and model number of devices that exhibit the issue.
Importing WAV or AIFF files (possibly those created by Audacity) may cause a freeze or a crash. After this occurs, Audacity may become destabilized and crash again even without importing further files. It is believed to mostly affect Intel Mac machines and to be caused by memory corruption. Workaround: Reboot the computer.
(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, Linux) Timer Record may carry on recording past the scheduled end time resulting in Audacity having to be force quit.
(Windows Vista,7) On upgrading to the current Beta from 1.3.12 or earlier, "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.
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.
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.
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.
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).
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.
Including fix to prevent zooming with mouse wheel or ball scrolling the content off-screen.
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.
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.
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
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.
(Linux) When configuring effect parameters in "Edit Chains", the "Preview" button is not intended to be functional. Pressing it may cause a crash.
(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.
(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
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
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.
(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.
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
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) 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.
(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.
(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.
(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:
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.
(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.
"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.
(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.
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.
(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.
(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 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
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.
You may see the error Application configuration incorrect when launching Audacity after installation. This mainly affects some Windows XP or 2000 machines. This can be fixed by downloading and installing the appropriate Microsoft "Redistributable Package" as follows:
Microsoft Visual C++ 2008 SP1 Redistributable Package (x86) for 32-bit Windows
Microsoft Visual C++ 2008 SP1 Redistributable Package (x64) for 64-bit Windows.
Be sure to get the correct package according to whether you have 32-bit or 64-bit Windows. To check, right-click over and choose . If 64-bit is not mentioned, you have 32-bit.
New Preference (off by default) to import files On-Demand (without seek ability) when using the optional FFmpeg library.
New Preference (off by default) to retain labels when deleting a selection that snaps to the label without extending past it.
(Windows installer) New option to reset Preferences on next launch.
(Mac) Audacity now has excellent compatibility with the VoiceOver screen reader. For details, please see https://manual.audacityteam.org/help/manual/man/accessibility.html#mac.
CleanSpeech Mode (no longer supported) will not now be enabled even if it was enabled by an earlier version of Audacity.
Added Serbian (Latin and Cyrillic) translations.
Unexplained crashes or corrupted audio occurs (note this can happen if the computer is low on memory or disk space).
For problems that occur when reopening or working in a project, the log file at Help > Show Log....
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.
Some interface text or markings remain in black when using High Contrast light-on-dark themes, so cannot be read properly
(OS X) Issues with VoiceOver:
If you use arrow keys to navigate the Timetext controls in Selection Toolbar, VoiceOver stops reading. Workaround: Use Control-Option-W
Mixer Toolbar input/output sliders are not read, just described as "multiple indicators". The "Graphic EQ" sliders in Equalization *are* read.
Metadata Editor table not read.
Edit Labels dialog not read.
(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.
Nyquist effects add spurious split lines if applied over clip boundaries.
Nyquist effects: in locales where comma acts as the decimal separator, entering a comma in a text box to left of a slider only produces the whole number before the comma. Workaround: use a dot (period) as the decimal separator
The following effects remove envelope control points: Change Speed/Pitch/Tempo; Equalization; Noise Removal; Sliding Time Scale/Pitch Shift; any Nyquist effect in the Effect menu. Workaround: Use Tracks > Mix and Render to apply the envelope to the waveform before applying the effect. Reverse retains the control points, but does not move them.
Truncate Silence does not adjust clip boundaries inside the selection being truncated.
Truncate Silence doesn't work intuitively if run on multiple tracks. It may be preferable to run it on each track at a time.
Truncate Silence may not truncate a silence that is exactly the same length as the specified "min silence duration".
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). Also note that projects containing more than 2^31 samples of total audio cannot be correctly saved.
Workaround: Edit > Undo if necessary then drag from outside the selection region or single-click in the clip to remove the selection.
Exporting or using Tracks > Mix and Render on a track where split lines exist may create clicks at the split lines. Workaround: Use Edit > Clip Boundaries > Join before exporting or rendering.
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.
When pasting audio into tracks with envelope points, the envelope points may move in unexpected ways, so causing unwanted amplitude adjustments.
(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.
Album art and lyrics in imported metadata are lost when exporting.
Exported "Comments" ID3 tags are not recognized by Windows Media Player or Explorer.
Genre WAV info tag (IGNR) not supported due to limitation in libsndfile.
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.
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 FFmpeg 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.
Dither noise is incorrectly applied by default if exporting to most formats where the bit depth is the same as (or higher 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.
(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 (;).
(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.
(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).
(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.
"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 FFmpeg 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 Extended Import Preferences. 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 can export invalid files (despite reporting that export was successful) if the track is muted or empty (it is intentional that muted tracks are not exported).
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".
(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 initialized Preferences, 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) 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) Tracks that were selected on project save are deselected when re-opening the project.
(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.
(OS X) The "Cmd - Wheel - Rotate" mouse binding does not zoom in unless you modify the default System Preferences. ** On OS X 10.6 or later, go to Universal Access / Seeing / Zoom / Options and uncheck "Use scroll wheel with modifier keys to zoom".
Prior to OS X 10.6, go to "Mouse and Keyboard" and uncheck "Zoom using scroll ball while holding Command".
(Windows) The "Files Missing" warning always restores maximised windows to smaller size.
(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.
After changing language in Preferences, a few parts of the interface don't change until Audacity is restarted.
Audacity has several weaknesses in preserving the context of the audio being worked with:
If playback scrolls, pressing Stop leaves the waveform where it stopped and the cursor invisible. Pressing Play to resume then scrolls the waveform to start at the left edge, hiding the previously visible context before the cursor position
Current scrolling behaviour makes it too hard to watch the waveform progress, with a single shift of cursor and waveform position when cursor reaches the right edge
Zoom to Selection shows none of the surrounding context
By default, all audio in the project is selected if an action requiring a selection is requested when there is no selection (this behavior can be turned off in the Tracks Preferences). If enabled:
You can always apply effects to the whole project in one step, but you can also delete audio in all tracks if you press Delete when there is no selection. That is easy to Undo, but we aim to tweak this behavior and make it more customizable in a future Audacity.
A few items in Edit menu are incorrectly grayed out if no track is selected.
If Sync-Lock Tracks is enabled, there is no indication of the cursor in the Sync-Locked tracks.
If you save a region with Edit > Save Region then click OK in Preferences, the saved region cannot be restored.
In projects containing an hour or more of total audio, there may be a delay compared to previous versions of Audacity when:
Creating a label or label track
Dragging selections with the keyboard (Workaround: Hold SHIFT then press left or right arrow a few times per second instead of holding the arrow key)
Dragging sample points with Draw Tool
Using Cut, Copy, Paste, Delete or Silence Audio.
The delay may be more evident on slower computers. In addition, label text may not be recovered if there is a crash.
Mouse Bindings are not currently configurable by the user.
Snap To state and Selection Format when Snap To is on are global. Therefore changing these in one project will make them show incorrectly in any other projects.
Snap-To does not move the cursor when first enabled or when the selection format is changed.
We're aware that some error messages in Audacity are not as helpful as we would like them to be. If you see a cryptic error message from Audacity, try a search (or ask) on https://forum.audacityteam.org/
(Linux) If Audacity is left open but without focus, its CPU use will rise slowly until all available system CPU is consumed. This is a bug in wxGTK 2.8.10 (not previous versions) - see http://trac.wxwidgets.org/ticket/11315 . This issue can be fixed by updating to wxGTK 2.8.11 or 2.8.12.
(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.
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".
On Mac, Audacity may freeze if JACK is launched by QjackCtl then Audacity is launched. Workaround: Use JackPilot to launch JACK, or launch QJackCtrl after Audacity and JACK are running.
(OS X and Linux) PortAudio's default latency values which are used when recording with software playthrough are much lower than Audacity's default "Audio to buffer" setting. This may cause playthrough or recording glitches when recording with software playthrough enabled, especially when using pulse on Linux. Workaround for Linux: record from an (hw) device instead if software playthrough is required.
(OS X) Playback to Bluetooth headsets gives an error. Workaround: Revert to Audacity 1.3.3 (this may only work with stereo headsets), or use Soundflower to send the Audacity output to an audio application that works with the headset.
(OS X) The "Hardware Playthrough" option in Recording Preferences is currently unsupported on all known Mac hardware. Try the "Software Playthrough" preference instead. If that does not work, the third-party LineIn application also provides software playthrough.
(Windows) When a USB device is connected, the Mixer Toolbar input slider for that device (and sometimes for any device) may wrongly appear active even though it has no control over the device's input level. Sometimes the Audacity slider will apply a software gain to the level (which is dangerous as it will only make the same clipped input quieter rather than stopping the clipping). Sometimes the Audacity slider will not affect the input volume at all. Workaround: use the slider in the Windows Control Panel where available, or any gain control on the device, or reduce the output being sent to the device.
(Windows) Audacity is incompatible (or not fully compatible) with some professional soundcards or audio devices, and may crash or have limited or faulty functionality. Occasionally, this may be true of some AC97 devices built into the motherboard. Workaround: make a different soundcard your default when using Audacity, but please e-mail us the following details to https://web.audacityteam.org/contact/#feedback :
Your version of Windows and Service Pack
Name, model number and driver version number of the soundcard or device.
Note: Multichannel Recording in Audacity is often not possible with professional devices unless you compile Audacity with ASIO support.
(Windows) Recording at 24-bit quality or higher isn't possible even with devices that support it due to current limitations in PortAudio.
Adding or removing an external audio device while Audacity is open will not be automatically reflected in Device Toolbar or Devices Preferences. Workaround: Use Transport > Rescan Audio Devices.
Calculation of "disk space remains for recording (time)" incorrect when recording in 24 bit quality.
Play-at-Speed slider: Change of playback speed is no longer automatic after you move the play-at-speed slider. To change speed, move the slider, then click the green button to left of the slider to play at the new speed.
Timer Record cannot maintain scheduled duration if system clock changes
(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.
The Transport menu lacks the combined "Play/Stop" command, but it has a shortcut which is set to "Space" by default. To change this shortcut, or to add a shortcut for the separate "Play" and "Stop" commands shown in the Transport Menu, go to the Keyboard Preferences.
(Windows and OS X) VST/Audio Units Plug-ins: On first use and otherwise when requested, Audacity scans for and loads VST effects before the main interface appears. On OS X, Audio Unit effects are always loaded, which can lead to a very slow launch if there are multiple plug-ins. Occasionally, an incompatible or badly written plug-in may lead to a crash or freeze on launch. Known plug-ins affected:
Waves Version 7 and 8 Audio Units on OS X
Native Instruments Guitar Rig v3 and v4 on OS X (v5 does not have this issue)
PredatorFX
AURoundTripAAC from "Apple audio mastering tools".
Projects created by Audacity 1.1.x or earlier are no longer supported. Workaround: Export each project track as WAV using the appropriate legacy version of Audacity, then import the WAV files into current Audacity.
Projects created by Audacity 1.2.x are partially supported - there is a possibility Audacity could corrupt them. Please make a backup copy of the project's .aup file and _data folder to a new folder before opening the project in this version of Audacity. Once you save the project in this version, it cannot be opened in 1.2.
Projects created by previous versions of Audacity may contain audio "block files" longer than the project format allows. Reopening such projects in previous versions might or might not result in deletion of the overlong audio. Audacity has been provisionally fixed so that it can no longer create or delete overlong files, but it cannot read any such files it encounters. If overlong files are found, a "Problems Reading Sequence Tags" message will display .
If you continue with the offered repair then choose "Continue without deleting" in the Orphan Block File(s) dialog, the overlong files will be retained as "orphans" in the project's _data folder but will appear as silence in the track(s).
As long as you choose "Close project immediately" in the Orphan Block File(s) dialog, the project will quit and will not be changed in any way.
If you encounter the "Problems Reading Sequence Tags" message, please write to our feedback address with a copy of the .aup file and the log as found at Help > Show Log.
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.
(Windows Vista,7) On upgrading to the current Beta from 1.3.12 or earlier, "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.
(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.
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)
(Windows and OS X) Some USB or Firewire recording devices only record silence, or only offer mono recording for a stereo device, or only mono or stereo for a device that previously supported multi-channel recording. Workaround: You can try 1.3.10 Beta or earlier (including 1.2.5/6), but these versions may have other bugs or limitations.
Please report make and model number of devices that exhibit the issue.
(Windows, Linux) Timer Record may carry on recording past the scheduled end time resulting in Audacity having to be force quit.
Importing WAV or AIFF files (possibly those created by Audacity) may cause a freeze or a crash. After this occurs, Audacity may become destabilized and crash again even without importing further files. It is believed to mostly affect Intel Mac machines and to be caused by memory corruption. Workaround: Reboot the computer.
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.
"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.
Exporting (or any render operation) on a track containing split lines could create clicks at the split lines.
Normalize could crash if the track name contained "%".
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
Device Toolbar tooltips now display the selected device
Increased default width of Device Toolbar and Meter Toolbar.
Improvements and some bug fixes to Nyquist effects, including:
Delay (new option to prevent duration change)
Sample Data Export (new "L-R on Same Line" layout option)
Risset Drum (new "Amplitude" slider).
Importing a labels file writes the file name to the name of the Label Track, and exporting a labels file offers the name of the last Label Track in the project.
Removed the "Audio cache" option from Directories Preferences due to frequent crash reports. All data operations will now be written to disk and not to RAM.
Removed the FFmpeg "On-Demand" option from Libraries Preferences (this fixes Audacity not building if configured --without-ffmpeg).
Compilation: Progress on making the Modules feature mainstream. Modules can now be individually enabled and disabled in Preferences.
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.
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 feedback address 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.
"Missing Audio Data Block File(s)", "Problems Reading Sequence Tags" or "Orphan Block File(s)" errors are reported. If you see these errors, please choose the options to "Treat missing audio as silence" or "Continue without deleting" the orphans.
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.
Multiple or duplicated .aup files or project folders appear within the same project.
Unexplained crashes or corrupted audio occurs (note this can happen if the computer is low on memory or disk space).
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 .
For problems that occur when reopening or working in a project, the log file at Help > Show Log....
(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 https://manual.audacityteam.org/o/man/accessibility.html
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.
(OS X) Issues with VoiceOver:
If you use arrow keys to navigate the Timetext controls in Selection Toolbar, VoiceOver stops reading. Workaround: Use Control-Option-W
Mixer Toolbar input/output sliders are not read, just described as "multiple indicators". The "Graphic EQ" sliders in Equalization *are* read.
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.
(Windows) Compilation with Visual Studio 2010 is not supported or recommended. See the Wiki page Developing on Windows 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)
(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
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.
Nyquist effects add spurious split lines if applied over clip boundaries.
Nyquist effects: in locales where comma acts as the decimal separator, entering a comma in a text box to left of a slider only produces the whole number before the comma. Workaround: use a dot (period) as the decimal separator
The following effects remove envelope control points: Change Speed/Pitch/Tempo; Equalization; Noise Removal; Sliding Time Scale/Pitch Shift; any Nyquist effect in the Effect menu. Workaround: Use Tracks > Mix and Render to apply the envelope to the waveform before applying the effect. Reverse retains the control points, but does not move them.
Truncate Silence does not adjust clip boundaries inside the selection being truncated.
Truncate Silence doesn't work intuitively if run on multiple tracks. It may be preferable to run it on each track at a time.
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.
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). Also note that projects containing more than 2^31 samples of total audio cannot be correctly saved.
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
faint, specious clip lines could occur if the clip is dragged back to its original track.
Workaround: Edit > Undo if necessary then drag from outside the selection region or single-click in the clip to remove the selection.
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.
When pasting audio into tracks with envelope points, the envelope points may move in unexpected ways, so causing unwanted amplitude adjustments.
(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.
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.
Dither noise is incorrectly applied by default if exporting to most formats where the bit depth is the same as (or higher 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 .
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.
(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 (;).
(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.
Exported "Comments" ID3 tags are not recognized by Windows Media Player or Explorer.
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 can export invalid files (despite reporting that export was successful) if the track is muted or empty (it is intentional that muted tracks are not exported).
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.
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".
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.
(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 download site and extract the files to your own preferred location.
Selections locked to/only possible to click at whole seconds: We know that it is easy to check the "Snap To" box in Toolbar 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) 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.
(OS X) The "Cmd - Wheel - Rotate" mouse binding does not zoom in unless you modify the default System Preferences. ** On OS X 10.6 or later, go to Universal Access / Seeing / Zoom / Options and uncheck "Use scroll wheel with modifier keys to zoom".
Prior to OS X 10.6, go to "Mouse and Keyboard" and uncheck "Zoom using scroll ball while holding Command".
(Windows) The "Files Missing" warning always restores maximised windows to smaller size.
After changing language in Preferences, a few parts of the interface don't change until Audacity is restarted.
Audacity has several weaknesses in preserving the context of the audio being worked with:
If playback scrolls, pressing Stop leaves the waveform where it stopped and the cursor invisible. Pressing Play to resume then scrolls the waveform to start at the left edge, hiding the previously visible context before the cursor position
Current scrolling behaviour makes it too hard to watch the waveform progress, with a single shift of cursor and waveform position when cursor reaches the right edge
By default, all audio in the project is selected if an action requiring a selection is requested when there is no selection (this behavior can be turned off in the Tracks Preferences). If enabled:
You can always apply effects to the whole project in one step, but you can also delete audio in all tracks if you press Delete when there is no selection. That is easy to Undo, but we aim to tweak this behavior and make it more customizable in a future Audacity.
A few items in Edit menu are incorrectly grayed out if no track is selected.
If Sync-Lock Tracks is enabled, there is no indication of the cursor in the Sync-Locked tracks.
If you save a region with Edit > Save Region then click OK in Preferences, the saved region cannot be restored.
In projects containing an hour or more of total audio, there may be a delay compared to previous versions of Audacity when:
Creating a label or label track
Dragging selections with the keyboard (Workaround: Hold SHIFT then press left or right arrow a few times per second instead of holding the arrow key)
The delay may be more evident on slower computers. In addition, label text may not be recovered if there is a crash.
Mouse Bindings are not currently configurable by the user.
Snap To state and Selection Format when Snap To is on are global. Therefore changing these in one project will make them show incorrectly in any other projects.
Snap To does not move the cursor when first enabled or when the selection format is changed.
We're aware that some error messages in Audacity are not as helpful as we would like them to be. If you see a cryptic error message from Audacity, try a search (or ask) on
(Linux) If Audacity is left open but without focus, its CPU use will rise slowly until all available system CPU is consumed. This is a bug in wxGTK 2.8.10 (not previous versions) - see . This issue can be fixed by updating to wxGTK 2.8.11 or 2.8.12.
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 http://trac.wxwidgets.org/changeset/62397?format=diff&new=62397, 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) 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.
(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.
(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.
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.
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".
(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: http://audacityteam.org/forum/viewtopic.php?f=17&t=5064
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.
(OS X and Linux) Audacity now works very well with JACK, 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.
On Mac, Audacity may freeze if JACK is launched by QjackCtl then Audacity is launched. Workaround: Use JackPilot to launch JACK, or launch QJackCtrl after Audacity and JACK are running.
(OS X and Linux) PortAudio's default latency values which are used when recording with software playthrough are much lower than Audacity's default "Audio to buffer" setting. This may cause playthrough or recording glitches when recording with software playthrough enabled, especially when using pulse on Linux. Workaround for Linux: record from an (hw) device instead if software playthrough is required.
(OS X) Playback to Bluetooth headsets gives an error. Workaround: Revert to Audacity 1.3.3 (this may only work with stereo headsets), or use to send the Audacity output to an audio application that works with the headset.
(OS X) The "Hardware Playthrough" option in Recording Preferences is currently unsupported on all known Mac hardware. Try the "Software Playthrough" preference instead. If that does not work, the third-party application also provides software playthrough.
(Windows) When a USB device is connected, the Mixer Toolbar input slider for that device (and sometimes for any device) may wrongly appear active even though it has no control over the device's input level. Sometimes the Audacity slider will apply a software gain to the level (which is dangerous as it will only make the same clipped input quieter rather than stopping the clipping). Sometimes the Audacity slider will not affect the input volume at all. Workaround: use the slider in the Windows Control Panel where available, or any gain control on the device, or reduce the output being sent to the device.
(Windows) Audacity is incompatible (or not fully compatible) with some professional soundcards or audio devices, and may crash or have limited or faulty functionality. Occasionally, this may be true of some AC97 devices built into the motherboard. Workaround: make a different soundcard your default when using Audacity, but please e-mail the following details to our :
Your version of Windows and Service Pack
Name, model number and driver version number of the soundcard or device.
Note: Multichannel Recording in Audacity is often not possible with professional devices unless you compile Audacity with ASIO support.
(Windows) Recording at 24-bit quality or higher isn't possible even with devices that support it due to current limitations in PortAudio.
Adding or removing an external audio device while Audacity is open will not be automatically reflected in the list in Device Toolbar or Devices Preferences. On Mac, unplugging then replugging an external device will give "error while opening sound device" (on Linux, pressing "Record" a second time will remove the error). Workaround: Use Transport > Rescan Audio Devices.
Calculation of "disk space remains for recording (time)" incorrect when recording in 24 bit quality.
Play-at-Speed slider: Change of playback speed is no longer automatic after you move the play-at-speed slider. To change speed, move the slider, then click the green button to left of the slider to play at the new speed.
Timer Record cannot maintain scheduled duration if system clock changes
(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.
The Transport menu lacks the combined "Play/Stop" command, but it has a shortcut which is set to "Space" by default. To change this shortcut, or to add a shortcut for the separate "Play" and "Stop" commands shown in the Transport Menu, go to the Keyboard 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 (http://trac.wxwidgets.org/ticket/13280) and fixed in changeset 67929 (http://trac.wxwidgets.org/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 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.
(Windows and OS X) VST/Audio Units Plug-ins: On first use and otherwise when requested, Audacity scans for and loads VST effects before the main interface appears. On OS X, Audio Unit effects are always loaded, which can lead to a very slow launch if there are many plug-ins. Occasionally, an incompatible or badly written plug-in may lead to a crash or freeze on launch. Known plug-ins affected:
Waves Version 7, 8 and 9 Audio Units on OS X
Native Instruments Guitar Rig v3 and v4 on OS X (v5 does not have this issue)
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 folder for application data. 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.
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.
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.
Projects created by Audacity 1.1.x or earlier are no longer supported. Workaround: Export each project track as WAV using the appropriate legacy version of Audacity, then import the WAV files into current Audacity.
Projects created by Audacity 1.2.x are partially supported - there is a possibility Audacity could corrupt them. Please make a backup copy of the project's .aup file and _data folder to a new folder before opening the project in this version of Audacity. Once you save the project in this version, it cannot be opened in 1.2.
Projects created by previous versions of Audacity may contain audio "block files" longer than the project format allows. Reopening such projects in previous versions might or might not result in deletion of the overlong audio. Audacity has been provisionally fixed so that it can no longer create or delete overlong files, but it cannot read any such files it encounters. If overlong files are found, a "Problems Reading Sequence Tags" message will display .
If you continue with the offered repair then choose "Continue without deleting" in the Orphan Block File(s) dialog, the overlong files will be retained as "orphans" in the project's _data folder but will appear as silence in the track(s).
As long as you choose "Close project immediately" in the Orphan Block File(s) dialog, the project will quit and will not be changed in any way.
If you encounter the "Problems Reading Sequence Tags" message, please write to our with a copy of the .aup file and the log as found at Help > Show Log.
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.
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 keyboard shortcut alternatives for the buttons instead.
(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:
opening saved projects that were fitted to the window
fitting an already zoomed in project to the window or zooming in on a fitted project
progress dialog remains white for a long time after the progress bars complete for a file import or effect.
(Windows Vista,7) On upgrading to the current Beta from 1.3.12 or earlier, "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.
(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.
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)
(Windows and OS X) Some USB or Firewire recording devices only record silence, or only offer mono recording for a stereo device, or only mono or stereo for a device that previously supported multi-channel recording. Workaround: You can try 1.3.10 Beta or earlier (including 1.2.5/6), but these versions may have other bugs or limitations.
Please report make and model number of devices that exhibit the issue.
(Windows, Linux) Timer Record may carry on recording past the scheduled end time resulting in Audacity having to be force quit.
Importing WAV or AIFF files (possibly those created by Audacity) may cause a freeze or a crash. After this occurs, Audacity may become destabilized and crash again even without importing further files. It is believed to mostly affect Intel Mac machines and to be caused by memory corruption. Workaround: Reboot the computer.
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.
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 instructions.
You may see the error Application configuration incorrect when launching Audacity after installation. This mainly affects some Windows XP or 2000 machines. This can be fixed by downloading and installing the appropriate Microsoft "Redistributable Package" as follows:
for 32-bit Windows
for 64-bit Windows.
Be sure to get the correct package according to whether you have 32-bit or 64-bit Windows. To check, right-click over and choose . If 64-bit is not mentioned, you have 32-bit.
On first use of Audacity you need to confirm the new dialog for detected effects before you can start the Audacity program.
Users upgrading to 2.0.x versions from 1.3.6 or earlier must download the of the LAME MP3 encoder.
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:
Text boxes with slider in Nyquist effects only produced whole numbers when using comma to enter a fractional number. Text boxes without slider still have this problem.
Built-in generators produced silence after running a Nyquist effect.
(Windows) When first changing to Windows WASAPI host, the input volume slider in Mixer Toolbar was enabled when it should have been permanently disabled.
(Windows) On some machines, launching Audacity then recording from the current Device Toolbar input would not record until the input was reselected.
(OS X) Frequent crashes occurred on importing audio files on some machines.
(OS X) Files did not open using Finder "Open with", double-clicking the file or dragging the file to the Audacity icon.
(Linux 64-bit) Fixed a crash when using Equalization.
(Linux) It was not possible to open an effect or other dialog then navigate through the dialog using TAB.
(Linux) The Play shortcut did not play a read-directly WAV, AIFF or FLAC import if the warning for importing uncompressed files appeared.
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:
Labels Editor now allows empty labels to be saved on closing the editor.
TAB and SHIFT+TAB when the label track has focus now always move forwards or backwards respectively to the nearest label.
(Windows) On a very few machines, the Windows WDM-KS low latency audio host introduced in Audacity 2.0.4 caused Audacity to hang or the computer to crash. WDM-KS has been removed from 2.0.5 until it can be safely enabled.
(Windows and OS X) Screen reader improvements for Install VST Effects dialog.
(OS X) Audio Unit plug-ins detected by Audacity on launch are now not loaded until chosen from the Effect menu. This should speed up launch and avoid crashes at launch due to misbehaving Audio Units.
(Linux) Update to PortAudio r1910 fixes memory and other bugs under ALSA.
(Linux) Applied fix for wxGTK 2.8.12 bug which resulted in loss of Audacity's menu bar (or visual corruption under Unity) on Debian-based systems.
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.
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 feedback address 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.
"Missing Audio Data Block File(s)", "Problems Reading Sequence Tags" or "Orphan Block File(s)" errors are reported. If you see these errors, please choose the options to "Treat missing audio as silence" or "Continue without deleting" the orphans.
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.
Multiple or duplicated .aup files or project folders appear within the same project.
Unexplained crashes or corrupted audio occurs (note this can happen if the computer is low on memory or disk space).
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.
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 feedback address.
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 https://manual.audacityteam.org/o/man/accessibility.html
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.
Some interface text or markings remain in black when using High Contrast light-on-dark themes, so cannot be read properly
Install VST Effects dialog. The list view of plug-ins is a check box list view, and all the plug-ins are checked initially. Unfortunately Jaws and Window-Eyes do not read whether or not a check box is checked, but you can still press SPACEBAR to change this.
(OS X) Issues with VoiceOver:
If you use arrow keys to navigate the Timetext controls in Selection Toolbar, VoiceOver stops reading. Workaround: Use Control-Option-W
When you TAB forwards from "Audio Position" in Selection Toolbar, the "Selection End" or "Selection Length" radio button is read as "Selection Start". When you use COMMAND + F6 or COMMAND + SHIFT + F6 to move directly into "Selection End" from another toolbar, the button is read as "Selection Start".
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) New libsoxr resampling library: Default ./configure will enable a new library libsoxr for resampling and disable libresample and libsamplerate (the previous resampling libraries). Cmake 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.
To enable libresample, your configure must include --without-libsoxr as well as --with-libresample.
(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)
(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).
AU
Digitech RP250 (effects pedal)
MNoiseGenerator AU and others in crash if you preview them
Native Instruments B4 and Native Instruments Guitar Rig v3 and v4 (v5 does not have this issue)
PredatorFX
Waves Version 7, 8 and 9 AU
Workaround: If Audio Units are not needed in Audacity, restart Audacity then open Audacity > Preferences and choose "Effect". Under "Enable Effects", uncheck "Audio Unit", press OK and restart Audacity. Alternatively, look in the Mac Crash Report for the AU plug-in that crashed, move it from <Your Home>/Library/Audio/Plug-Ins/Components or /Library/Audio/Plug-Ins/Components then restart Audacity. See this page for more help.
(Windows) The following VST plug-in may cause Audacity to hang if you select it in the "Install VST Effects" dialog then click OK.
Waves v5
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". 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 .
(Windows and Linux) Some LADSPA "Blop" plug-ins ( ) are reported to crash in Audacity on Linux Debian. On Windows, the Blop plug-ins included in can also crash, but this can be avoided if you ensure the "blop_files" folder contains the necessary "_data.dll" files for the plug-ins and that this folder is present in the Audacity "Plug-Ins" folder.
(Windows) LADSPA Multiband EQ may not be visible in Effect menu (occurs on Windows XP), and crashes soon after opening
Applying Equalization to a track that has a different sample rate to the first track will affect different frequencies than those requested in the Equalization curve. Workaround: Use Tracks > Resample... to resample all tracks to the same sample rate before using Equalization. If different sample rates are required, use a separate project window for each track.
Cut Preview only plays the upper track of multiple selected or Sync-Locked tracks.
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.
Nyquist effects add spurious split lines if applied over clip boundaries.
Preview is not supported in Nyquist plug-ins. "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.
The following effects remove envelope control points: Change Speed/Pitch/Tempo; Equalization; Noise Removal; Sliding Time Scale/Pitch Shift; any Nyquist effect in the Effect menu. Workaround: Use Tracks > Mix and Render to apply the envelope to the waveform before applying the effect. Reverse retains the control points, but does not move them.
Truncate Silence does not adjust clip boundaries inside the selection being truncated.
Truncate Silence doesn't work intuitively if run on multiple tracks. It may be preferable to run it on each track at a time.
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). Also note that projects containing more than 2^31 samples of total audio cannot be correctly saved.
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
faint, specious clip lines could occur if the clip is dragged back to its original track.
Workaround: Edit > Undo if necessary then drag from outside the selection region or single-click in the clip to remove the selection.
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.
When pasting audio into tracks with envelope points, the envelope points may move in unexpected ways, so causing unwanted amplitude adjustments.
(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.
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.
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.
(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.
(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.
(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 download site and extract the files to your own preferred location.
(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.
(OS X) Images captured with Help > Screenshot Tools are completely black.
(OS X) The "Cmd - Wheel - Rotate" mouse binding does not zoom in unless you modify the default System Preferences. ** On OS X 10.6 or later, go to Universal Access / Seeing / Zoom / Options and uncheck "Use scroll wheel with modifier keys to zoom".
Prior to OS X 10.6, go to "Mouse and Keyboard" and uncheck "Zoom using scroll ball while holding Command".
(Windows) The "Files Missing" warning always restores maximised windows to smaller size.
(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.
After changing language in Preferences, a few parts of the interface don't change until Audacity is restarted.
Audacity has several weaknesses in preserving the context of the audio being worked with:
If playback scrolls, pressing Stop leaves the waveform where it stopped and the cursor invisible. Pressing Play to resume then scrolls the waveform to start at the left edge, hiding the previously visible context before the cursor position. Workaround: If you had a selection and a special playback command like Cut Preview or Quick-Play caused the waveform to scroll, use View > Go to Selection Start or View > Go to Selection End to move the selection back into view.
Current scrolling behaviour makes it too hard to watch the waveform progress, with a single shift of cursor and waveform position when cursor reaches the right edge
By default, all audio in the project is selected if an action requiring a selection is requested when there is no selection (this behavior can be turned off in the Tracks Preferences). If enabled:
You can always apply effects to the whole project in one step, but you can also delete audio in all tracks if you press Delete when there is no selection. That is easy to Undo, but we aim to tweak this behavior and make it more customizable in a future Audacity.
A few items in Edit menu are incorrectly grayed out if no track is selected.
If Sync-Lock Tracks is enabled, there is no indication of the cursor in the Sync-Locked tracks.
If you save a region with Edit > Save Region then click OK in Preferences, the saved region cannot be restored.
In projects containing an hour or more of total audio, there may be a delay compared to previous versions of Audacity when:
Creating a label or label track
Dragging selections with the keyboard (Workaround: Hold SHIFT then press left or right arrow a few times per second instead of holding the arrow key)
The delay may be more evident on slower computers. In addition, label text may not be recovered if there is a crash.
Mouse Bindings are not currently configurable by the user.
Snap To state and Selection Format when Snap To is on are global. Therefore changing these in one project will make them show incorrectly in any other projects.
Snap-To does not move the cursor when first enabled or when the selection format is changed.
We're aware that some error messages in Audacity are not as helpful as we would like them to be. If you see a cryptic error message from Audacity, try a search (or ask) on
(Linux) If Audacity is left open but without focus, its CPU use will rise slowly until all available system CPU is consumed. This is a bug in wxGTK 2.8.10 (not previous versions) - see . This issue can be fixed by updating to wxGTK 2.8.11 or 2.8.12.
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 http://trac.wxwidgets.org/changeset/62397?format=diff&new=62397, 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).
(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.
(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.
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.
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".
(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:
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.
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 JACK, 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.
On Mac, Audacity may freeze if JACK is launched by QjackCtl then Audacity is launched. Workaround: Use JackPilot to launch JACK, or launch QJackCtrl after Audacity and JACK are running.
(OS X and Linux) PortAudio's default latency values which are used when recording with software playthrough are much lower than Audacity's default "Audio to buffer" setting. This may cause playthrough or recording glitches when recording with software playthrough enabled, especially when using pulse on Linux. Workaround for Linux: record from an (hw) device instead if software playthrough is required.
(OS X) Playback to Bluetooth headsets gives an error. Workaround: Revert to Audacity 1.3.3 (this may only work with stereo headsets), or use to send the Audacity output to an audio application that works with the headset.
(OS X) The "Hardware Playthrough" option in Recording Preferences is currently unsupported on all known Mac hardware. Try the "Software Playthrough" preference instead. If that does not work, the third-party application also provides software playthrough.
The input slider in is disabled for all or most inputs. Please use the Windows system input slider instead.
Recording from the stereo mix input may not produce an adequate input level unless you turn the system audio output up very high. On Windows Vista and later you can choose the "Windows WASAPI" host and a "loopback" input instead for recording computer playback.
(Windows) When a USB device is connected, the Mixer Toolbar input slider for that device (and sometimes for any device) may wrongly appear active even though it has no control over the device's input level. Sometimes the Audacity slider will apply a software gain to the level (which is dangerous as it will only make the same clipped input quieter rather than stopping the clipping). Sometimes the Audacity slider will not affect the input volume at all. Workaround: use the slider in the Windows Control Panel where available, or any gain control on the device, or reduce the output being sent to the device.
(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.
(Windows) Audacity is incompatible (or not fully compatible) with some professional soundcards or audio devices, and may crash or have limited or faulty functionality. Occasionally, this may be true of some AC97 devices built into the motherboard. Workaround: make a different soundcard your default when using Audacity, but please e-mail the following details to our :
Your version of Windows and Service Pack
Name, model number and driver version number of the soundcard or device.
Note: Multichannel Recording in Audacity is often not possible with professional devices unless you compile Audacity with ASIO support.
(Windows) The "Windows WASAPI" host currently has the following limitations:
The only available inputs are "loopback" inputs for .
The input slider in is disabled.
Adding or removing an external audio device while Audacity is open will not be automatically reflected in the list in Device Toolbar or Devices Preferences. On Mac, unplugging then replugging an external device will give "error while opening sound device" (on Linux, pressing "Record" a second time will remove the error). Workaround: Use Transport > Rescan Audio Devices.
Calculation of "disk space remains for recording (time)" incorrect when recording in 24 bit quality.
Play-at-Speed slider: Change of playback speed is no longer automatic after you move the play-at-speed slider. To change speed, move the slider, then click the green button to left of the slider to play at the new speed.
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.
"Play/Stop and Set Cursor": Use SHIFT + A. This also starts or stops playback, but when stopped, sets the cursor to the stop position.
To change these shortcuts, or to add a shortcut for the separate "Play" and "Stop" commands shown in the Transport Menu, go to the Keyboard Preferences.
Timer Record cannot maintain scheduled duration if system clock changes
(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.
(Linux) Extended Import: Clicking "Move rule up" when there are no rules or filters causes a crash.
(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.
(Windows and OS X) "Install VST Effects" dialog:
The dialog lists more than VST effects: On first use, Audacity scans for then (before launching Audacity) presents a dialog where you can choose which VST effects to load into the Audacity Effect menu. Remove the checkmark from any VST effects you do not want to load then click OK to load the checkmarked effects. If you click Cancel the dialog will reappear on next Audacity launch.
VST instruments will appear in the list but are not supported, so will not load even if checkmarked.
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.
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.
Projects created by Audacity 1.1.x or earlier are no longer supported. Workaround: Export each project track as WAV using the appropriate legacy version of Audacity, then import the WAV files into current Audacity.
Projects created by Audacity 1.2.x are partially supported - there is a possibility Audacity could corrupt them. Please make a backup copy of the project's .aup file and _data folder to a new folder before opening the project in this version of Audacity. Once you save the project in this version, it cannot be opened in 1.2.
Projects created by previous versions of Audacity may contain audio "block files" longer than the project format allows. Reopening such projects in previous versions might or might not result in deletion of the overlong audio. Audacity has been provisionally fixed so that it can no longer create or delete overlong files, but it cannot read any such files it encounters. If overlong files are found, a "Problems Reading Sequence Tags" message will display .
If you continue with the offered repair then choose "Continue without deleting" in the Orphan Block File(s) dialog, the overlong files will be retained as "orphans" in the project's _data folder but will appear as silence in the track(s).
As long as you choose "Close project immediately" in the Orphan Block File(s) dialog, the project will quit and will not be changed in any way.
If you encounter the "Problems Reading Sequence Tags" message, please write to our with a copy of the .aup file and the log as found at Help > Show Log.
Time Track warp points saved in a 2.0.3 or later project will be preserved if opened in previous Audacity versions, but playback and display will be incorrect.
Projects containing 2^31 samples or more (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.
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.
(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.
(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.
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).
(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.
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)
(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 Vista,7) On upgrading to the current Beta from 1.3.12 or earlier, "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 and OS X) Some USB or Firewire recording devices only record silence, or only offer mono recording for a stereo device, or only mono or stereo for a device that previously supported multi-channel recording. Workaround: You can try 1.3.10 Beta or earlier (including 1.2.5/6), but these versions may have other bugs or limitations.
Please report make and model number of devices that exhibit the issue, and your operating system details (for example, Windows 7 Service Pack 1).
(Windows) There may be substantial delays drawing the waveform in longer projects. These include:
opening saved projects that were fitted to the window
fitting an already zoomed in project to the window or zooming in on a fitted project
progress dialog remains white for a long time after the progress bars complete for a file import or effect.
Some interface text or markings remain in black when using High Contrast light-on-dark themes, so cannot be read properly
Edit Labels dialog not read.
Genre WAV info tag (IGNR) not supported due to limitation in libsndfile.
ID3 v2.4 tags in imported MP3 files are not seen and will be removed on export.
Audacity writes both ID3 v2.3 (TYER) and v2.4 (TDRC) tags for "Year", but any applications that require the older TYER on its own (without TDRC) will not see "Year" in Audacity-exported files. The id3 command-line application on Linux is one example.
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.
Using Cut, Copy, Paste, Delete or Silence Audio.
PredatorFX
AURoundTripAAC from "Apple audio mastering tools".
Mixer Toolbar input/output sliders are not read, just described as "multiple indicators". The "Graphic EQ" sliders in Equalization *are* read.
Metadata Editor table not read.
Edit Labels dialog not read.
Audacity writes both ID3 v2.3 (TYER) and v2.4 (TDRC) tags for "Year", but any applications that require the older TYER on its own (without TDRC) will not see "Year" in Audacity-exported files. The id3 command-line application on Linux is one example.
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.
Zoom to Selection shows none of the surrounding context
Using Cut, Copy, Paste, Delete or Silence Audio.
Loopback recordings should only be made with the Audacity Project Rate set to 44100 Hz . Setting other project rates will cause Audacity to resample the input to the project rate any may cause glitches in the recorded audio.
"Audio to buffer" in Recording Preferences cannot be used to adjust recording latency.
The dialog is on top of other windows, so could hide any prompts that VST effects show when effects are loaded after pressing OK. This would be evident by the "loading progress" arrow in the check boxes coming to a halt and the VST dialog losing focus. To continue loading the effects in this case, press ENTER on your keyboard to OK the hidden prompt, or drag the VST dialog away to reveal the prompt then click OK on the prompt.
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.
Notes for Windows:
Users upgrading to 2.0.x versions from 1.3.6 or earlier must download the latest version 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.
You may see the error Application configuration incorrect when launching Audacity after installation. This mainly affects some Windows XP or 2000 machines. This can be fixed by downloading and installing the appropriate Microsoft "Redistributable Package" as follows:
for 32-bit Windows
for 64-bit Windows.
Be sure to get the correct package according to whether you have 32-bit or 64-bit Windows. To check, right-click over and choose . If 64-bit is not mentioned, you have 32-bit.
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
Other interface bug fixes.
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.
Warp points saved in a 2.0.3 project will be preserved if opened in previous versions but playback and display will be incorrect.
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.
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 feedback address 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.
"Missing Audio Data Block File(s)", "Problems Reading Sequence Tags" or "Orphan Block File(s)" errors are reported. If you see these errors, please choose the options to "Treat missing audio as silence" or "Continue without deleting" the orphans.
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.
Multiple or duplicated .aup files or project folders appear within the same project.
Unexplained crashes or corrupted audio occurs (note this can happen if the computer is low on memory or disk space).
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 .
For problems that occur when reopening or working in a project, the log file at Help > Show Log....
(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 https://manual.audacityteam.org/o/man/accessibility.html
There are some accessibility bugs in the parts of Audacity that are accessible:
Some interface text or markings remain in black when using High Contrast light-on-dark themes, so cannot be read properly
(OS X) Issues with VoiceOver:
If you use arrow keys to navigate the Timetext controls in Selection Toolbar, VoiceOver stops reading. Workaround: Use Control-Option-W
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.
(Linux) New libsoxr resampling library: Default ./configure will enable a new library libsoxr for resampling and disable libresample and libsamplerate (the previous resampling libraries). Cmake 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.
To enable libresample, your configure must include --without-libsoxr as well as --with-libresample.
(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)
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 .
(Windows and Linux) Some LADSPA "Blop" plug-ins ( ) are reported to crash in Audacity on Linux Debian. On Windows, the Blop plug-ins included in can also crash, but this can be avoided if you ensure the "blop_files" folder contains the necessary "_data.dll" files for the plug-ins and that this folder is present in the Audacity "Plug-Ins" folder.
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.
Nyquist effects add spurious split lines if applied over clip boundaries.
Nyquist effects: in locales where comma acts as the decimal separator, entering a comma in a text box to left of a slider only produces the whole number before the comma. Workaround: use a dot (period) as the decimal separator
The following effects remove envelope control points: Change Speed/Pitch/Tempo; Equalization; Noise Removal; Sliding Time Scale/Pitch Shift; any Nyquist effect in the Effect menu. Workaround: Use Tracks > Mix and Render to apply the envelope to the waveform before applying the effect. Reverse retains the control points, but does not move them.
Truncate Silence does not adjust clip boundaries inside the selection being truncated.
Truncate Silence doesn't work intuitively if run on multiple tracks. It may be preferable to run it on each track at a time.
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). Also note that projects containing more than 2^31 samples of total audio cannot be correctly saved.
(Linux) Equalization: If EQCurves.xml or EQDefaultCurves.xml have corrupt XML syntax (for example, a missing closing ">"), Equalization will crash either on opening or after OK'ing a "Not well formed" error message.
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
faint, specious clip lines could occur if the clip is dragged back to its original track.
Workaround: Edit > Undo if necessary then drag from outside the selection region or single-click in the clip to remove the selection.
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.
When pasting audio into tracks with envelope points, the envelope points may move in unexpected ways, so causing unwanted amplitude adjustments.
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.
(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 (;).
(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.
(Windows and OS X) If you import a file then use "End Task" in the "Applications" tab of Windows Task Manager or "Quit" from the Dock on Mac, Audacity crashes instead of asking if you want to save changes.
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.
Exported "Comments" ID3 tags are not recognized by Windows Media Player or Explorer.
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.
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".
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 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.
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.
Dither noise is incorrectly applied by default if exporting to most formats where the bit depth is the same as (or higher 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 .
(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 download site 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.
Selections locked to/only possible to click at whole seconds: We know that it is easy to check the "Snap To" box in Toolbar 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) 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.
(OS X) The "Cmd - Wheel - Rotate" mouse binding does not zoom in unless you modify the default System Preferences. ** On OS X 10.6 or later, go to Universal Access / Seeing / Zoom / Options and uncheck "Use scroll wheel with modifier keys to zoom".
Prior to OS X 10.6, go to "Mouse and Keyboard" and uncheck "Zoom using scroll ball while holding Command".
(Windows) The "Files Missing" warning always restores maximised windows to smaller size.
(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.
After changing language in Preferences, a few parts of the interface don't change until Audacity is restarted.
Audacity has several weaknesses in preserving the context of the audio being worked with:
If playback scrolls, pressing Stop leaves the waveform where it stopped and the cursor invisible. Pressing Play to resume then scrolls the waveform to start at the left edge, hiding the previously visible context before the cursor position
Current scrolling behaviour makes it too hard to watch the waveform progress, with a single shift of cursor and waveform position when cursor reaches the right edge
By default, all audio in the project is selected if an action requiring a selection is requested when there is no selection (this behavior can be turned off in the Tracks Preferences). If enabled:
You can always apply effects to the whole project in one step, but you can also delete audio in all tracks if you press Delete when there is no selection. That is easy to Undo, but we aim to tweak this behavior and make it more customizable in a future Audacity.
A few items in Edit menu are incorrectly grayed out if no track is selected.
If Sync-Lock Tracks is enabled, there is no indication of the cursor in the Sync-Locked tracks.
If you save a region with Edit > Save Region then click OK in Preferences, the saved region cannot be restored.
In projects containing an hour or more of total audio, there may be a delay compared to previous versions of Audacity when:
Creating a label or label track
Dragging selections with the keyboard (Workaround: Hold SHIFT then press left or right arrow a few times per second instead of holding the arrow key)
The delay may be more evident on slower computers. In addition, label text may not be recovered if there is a crash.
Mouse Bindings are not currently configurable by the user.
Snap To state and Selection Format when Snap To is on are global. Therefore changing these in one project will make them show incorrectly in any other projects.
Snap To does not move the cursor when first enabled or when the selection format is changed.
We're aware that some error messages in Audacity are not as helpful as we would like them to be. If you see a cryptic error message from Audacity, try a search (or ask) on
(Linux) If Audacity is left open but without focus, its CPU use will rise slowly until all available system CPU is consumed. This is a bug in wxGTK 2.8.10 (not previous versions) - see . This issue can be fixed by updating to wxGTK 2.8.11 or 2.8.12.
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 http://trac.wxwidgets.org/changeset/62397?format=diff&new=62397, 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) 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.
(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.
(Linux) Complete or partial loss of Audacity menu bar
32-bit systems using wxGTK 2.8.12: If not using the Unity shell, closing Preferences may lead to loss of the Audacity Menu Bar (only "Fi" from "Files" will be visible). If using Unity, a small black square will appear, but the Audacity menu in the Global Menu is unaffected. Workaround for one session: Resize (or maximize/unmaximize) the Audacity window after closing Preferences.
64-bit systems using wx GTK 2.8.12 without Unity: Audacity may launch with no menu bar. Workaround for one session: Open and OK Preferences or open a new Audacity window.
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.
(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.
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.
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".
(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: http://audacityteam.org/forum/viewtopic.php?f=17&t=5064
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.
(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 Device Toolbar 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.
"Play/Stop and Set Cursor": Use SHIFT + A. This also starts or stops playback, but when stopped, sets the cursor to the stop position.
To change these shortcuts, or to add a shortcut for the separate "Play" and "Stop" commands shown in the Transport Menu, go to the Keyboard Preferences.
(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.
(OS X and Linux) PortAudio's default latency values which are used when recording with software playthrough are much lower than Audacity's default "Audio to buffer" setting. This may cause playthrough or recording glitches when recording with software playthrough enabled, especially when using pulse on Linux. Workaround for Linux: record from an (hw) device instead if software playthrough is required.
(OS X) Playback to Bluetooth headsets gives an error. Workaround: Revert to Audacity 1.3.3 (this may only work with stereo headsets), or use to send the Audacity output to an audio application that works with the headset.
(OS X) The "Hardware Playthrough" option in Recording Preferences is currently unsupported on all known Mac hardware. Try the "Software Playthrough" preference instead. If that does not work, the third-party application also provides software playthrough.
(Windows) When a USB device is connected, the Mixer Toolbar input slider for that device (and sometimes for any device) may wrongly appear active even though it has no control over the device's input level. Sometimes the Audacity slider will apply a software gain to the level (which is dangerous as it will only make the same clipped input quieter rather than stopping the clipping). Sometimes the Audacity slider will not affect the input volume at all. Workaround: use the slider in the Windows Control Panel where available, or any gain control on the device, or reduce the output being sent to the device.
(Windows) Audacity is incompatible (or not fully compatible) with some professional soundcards or audio devices, and may crash or have limited or faulty functionality. Occasionally, this may be true of some AC97 devices built into the motherboard. Workaround: make a different soundcard your default when using Audacity, but please e-mail the following details to our :
Your version of Windows and Service Pack
Name, model number and driver version number of the soundcard or device.
Note: Multichannel Recording in Audacity is often not possible with professional devices unless you compile Audacity with ASIO support.
(Windows) Recording at 24-bit quality or higher isn't possible even with devices that support it due to current limitations in PortAudio.
Adding or removing an external audio device while Audacity is open will not be automatically reflected in the list in Device Toolbar or Devices Preferences. On Mac, unplugging then replugging an external device will give "error while opening sound device" (on Linux, pressing "Record" a second time will remove the error). Workaround: Use Transport > Rescan Audio Devices.
Calculation of "disk space remains for recording (time)" incorrect when recording in 24 bit quality.
Play-at-Speed slider: Change of playback speed is no longer automatic after you move the play-at-speed slider. To change speed, move the slider, then click the green button to left of the slider to play at the new speed.
Timer Record cannot maintain scheduled duration if system clock changes
(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.
(Linux) Extended Import: Clicking "Move rule up" when there are no rules or filters causes a crash.
(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.
(Windows and OS X) VST/Audio Units Plug-ins: On first use and otherwise when requested, Audacity scans for and loads VST effects before the main interface appears. On OS X, Audio Unit effects are always loaded, which can lead to a very slow launch if there are many plug-ins. Occasionally, an incompatible or badly written plug-in may lead to a crash or freeze on launch. Known plug-ins affected:
Waves Version 7, 8 and 9 Audio Units on OS X, Waves Version 5 on Windows
Native Instruments Guitar Rig v3 and v4 on OS X (v5 does not have this issue)
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 folder for application data. 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.
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.
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.
Time Track warp points saved in a 2.0.3 or later project will be preserved if opened in previous Audacity versions, but playback and display will be incorrect.
Projects created by Audacity 1.1.x or earlier are no longer supported. Workaround: Export each project track as WAV using the appropriate legacy version of Audacity, then import the WAV files into current Audacity.
Projects created by Audacity 1.2.x are partially supported - there is a possibility Audacity could corrupt them. Please make a backup copy of the project's .aup file and _data folder to a new folder before opening the project in this version of Audacity. Once you save the project in this version, it cannot be opened in 1.2.
Projects created by previous versions of Audacity may contain audio "block files" longer than the project format allows. Reopening such projects in previous versions might or might not result in deletion of the overlong audio. Audacity has been provisionally fixed so that it can no longer create or delete overlong files, but it cannot read any such files it encounters. If overlong files are found, a "Problems Reading Sequence Tags" message will display .
If you continue with the offered repair then choose "Continue without deleting" in the Orphan Block File(s) dialog, the overlong files will be retained as "orphans" in the project's _data folder but will appear as silence in the track(s).
As long as you choose "Close project immediately" in the Orphan Block File(s) dialog, the project will quit and will not be changed in any way.
If you encounter the "Problems Reading Sequence Tags" message, please write to our with a copy of the .aup file and the log as found at Help > Show Log.
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.
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.
(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 keyboard shortcut alternatives for the buttons instead.
(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.
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)
(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 Vista,7) On upgrading to the current Beta from 1.3.12 or earlier, "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 and OS X) Some USB or Firewire recording devices only record silence, or only offer mono recording for a stereo device, or only mono or stereo for a device that previously supported multi-channel recording. Workaround: You can try 1.3.10 Beta or earlier (including 1.2.5/6), but these versions may have other bugs or limitations.
Please report make and model number of devices that exhibit the issue, and your operating system details (for example, Windows 7 Service Pack 1).
(Windows) There may be substantial delays drawing the waveform in longer projects. These include:
opening saved projects that were fitted to the window
fitting an already zoomed in project to the window or zooming in on a fitted project
progress dialog remains white for a long time after the progress bars complete for a file import or effect.
(Windows, Linux) Timer Record may carry on recording past the scheduled end time resulting in Audacity having to be force quit.
Importing WAV or AIFF files (possibly those created by Audacity) may cause a freeze or a crash. After this occurs, Audacity may become destabilized and crash again even without importing further files. It is believed to mostly affect Intel Mac machines and to be caused by memory corruption. Workaround: Reboot the computer.
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.
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
Release Notes 2.0.0
Bug Lists - Search the complete Audacity Bugzilla database
Audacity 2.0.4 was available from 06 September 2013 to 20 October 2013. 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.
Mixer Toolbar input/output sliders are not read, just described as "multiple indicators". The "Graphic EQ" sliders in Equalization *are* read.
Metadata Editor table not read.
Edit Labels dialog not read.
Genre WAV info tag (IGNR) not supported due to limitation in libsndfile.
ID3 v2.4 tags in imported MP3 files are not seen and will be removed on export.
Audacity writes both ID3 v2.3 (TYER) and v2.4 (TDRC) tags for "Year", but any applications that require the older TYER on its own (without TDRC) will not see "Year" in Audacity-exported files. The id3 command-line application on Linux is one example.
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.
Using Cut, Copy, Paste, Delete or Silence Audio.
On Mac, Audacity may freeze if JACK is launched by QjackCtl then Audacity is launched. Workaround: Use JackPilot to launch JACK, or launch QJackCtrl after Audacity and JACK are running.
PredatorFX
AURoundTripAAC from "Apple audio mastering tools".
Notes for Windows:
Users upgrading to 2.0.x versions from 1.3.6 or earlier must download the latest version 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.
On first use of Audacity you need to confirm the new dialog for detected effects before you can start the Audacity program.
You may see the error Application configuration incorrect when launching Audacity after installation. This mainly affects some Windows XP or 2000 machines. This can be fixed by downloading and installing the appropriate Microsoft "Redistributable Package" as follows:
for 32-bit Windows
for 64-bit Windows.
Be sure to get the correct package according to whether you have 32-bit or 64-bit Windows. To check, right-click over and choose . If 64-bit is not mentioned, you have 32-bit.
Keyboard Preferences: Shortcuts for Generators, Effects and Analyzers were not exported. All imported shortcut changes were discarded.
Equalization curves were corrupted in Graphic EQ mode after switching to/from Draw Curves or after running the effect then reopening it.
Change Pitch displayed corrupted values when reducing pitch or editing "from" Frequency. Detection was very inaccurate at high sample rates.
Bass Boost no longer clips if the track contains 32-bit audio.
Auto Duck was excessively slow on older machines.
(Windows) Exported MP3 comments tags were not seen by Windows programs.
(Windows and OS X) Audacity crashed if you used system quit before file import was complete.
(Linux) Equalization crashed Audacity if the XML file was corrupted.
(Linux) When configuring effect parameters in "Edit Chains", "Preview" (not intended to be functional) caused a crash.
(Linux) LICENSE.txt and README.txt were wrongly installed in /usr/local/share/doc instead of /usr/local/share/doc/audacity/ .
Accessibility: ENTER did not toggle selectedness of a label track unless a label was selected.
Numerous other interface fixes.
New "Reverb" effect to replace GVerb, based on the original "Freeverb".
New View > Go to Selection Start and Go to Selection End commands.
New Tracks > Align End to End command to append existing tracks to each other.
Change Tempo now supports fractional BPM.
Plot Spectrum now supports FFT sizes up to 65536.
WAV files now support "Album Title", "Track Number" and "Genre" LIST INFO tags and also support ID3 tags.
Handle a bug in older iPods or some OS X applications that cause them to refuse AIFF files whose metadata contains an uneven number of characters,
(Windows) Added support for "Windows WDM-KS" host which can provide very low latencies if you reduce "Audio to Buffer" in Recording Preferences.
(Windows Vista and later) You can now record computer playback by choosing the new "Windows WASAPI" host in Device Toolbar then a "loopback" input.
(Windows and Mac OS X): VST scanning dialog now replaced with a dialog for choosing which VST effects to load.
(Linux) CTRL + ALT can now be used to smooth samples in Draw Tool.
Modules Preferences replaced with a dialog on launch of Audacity enabling you to choose which modules to load.
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.
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 feedback address 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.
"Missing Audio Data Block File(s)", "Problems Reading Sequence Tags" or "Orphan Block File(s)" errors are reported. If you see these errors, please choose the options to "Treat missing audio as silence" or "Continue without deleting" the orphans.
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.
Multiple or duplicated .aup files or project folders appear within the same project.
Unexplained crashes or corrupted audio occurs (note this can happen if the computer is low on memory or disk space).
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.
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 feedback address.
(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 https://manual.audacityteam.org/o/man/accessibility.html
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.
Some interface text or markings remain in black when using High Contrast light-on-dark themes, so cannot be read properly
Install VST Effects dialog. To install all the plug-ins, TAB to the OK button and press it. The list view of plug-ins is a check box list view, and all the plug-ins are checked initially, despite what screen readers say. Pressing SPACEBAR changes whether or not an item is checked, even though screen readers do not read this information. In addition, the focused item is not selected, which is not standard practice in a check box list view, and screen readers correctly read this information. These accessibility problems are due to the Audacity software, and not screen readers.
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) New libsoxr resampling library: Default ./configure will enable a new library libsoxr for resampling and disable libresample and libsamplerate (the previous resampling libraries). Cmake 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.
To enable libresample, your configure must include --without-libsoxr as well as --with-libresample.
(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)
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 .
(Windows and Linux) Some LADSPA "Blop" plug-ins ( ) are reported to crash in Audacity on Linux Debian. On Windows, the Blop plug-ins included in can also crash, but this can be avoided if you ensure the "blop_files" folder contains the necessary "_data.dll" files for the plug-ins and that this folder is present in the Audacity "Plug-Ins" folder.
(Windows and Linux, where system locale uses comma as decimal separator) may produce silence if used on audio that has had a effect applied to it. Workaround: Run Audacity in English , or change the system locale to English and run Audacity in the local language.
(Windows) LADSPA Multiband EQ may not be visible in Effect menu (occurs on Windows XP), and crashes soon after opening
Cut Preview only plays the upper track of multiple selected or Sync-Locked tracks.
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.
Nyquist effects add spurious split lines if applied over clip boundaries.
Nyquist effects: in locales where comma acts as the decimal separator, entering a comma in a text box to left of a slider only produces the whole number before the comma. Workaround: use a dot (period) as the decimal separator
Preview is not supported in Nyquist plug-ins. "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.
The following effects remove envelope control points: Change Speed/Pitch/Tempo; Equalization; Noise Removal; Sliding Time Scale/Pitch Shift; any Nyquist effect in the Effect menu. Workaround: Use Tracks > Mix and Render to apply the envelope to the waveform before applying the effect. Reverse retains the control points, but does not move them.
Truncate Silence does not adjust clip boundaries inside the selection being truncated.
Truncate Silence doesn't work intuitively if run on multiple tracks. It may be preferable to run it on each track at a time.
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). Also note that projects containing more than 2^31 samples of total audio cannot be correctly saved.
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
faint, specious clip lines could occur if the clip is dragged back to its original track.
Workaround: Edit > Undo if necessary then drag from outside the selection region or single-click in the clip to remove the selection.
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.
When pasting audio into tracks with envelope points, the envelope points may move in unexpected ways, so causing unwanted amplitude adjustments.
(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.
(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 download site and extract the files to your own preferred location.
(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) If the warning for importing uncompressed audio files appears before import of a WAV, AIFF or FLAC file and you choose the "Read the files directly"... radio button, 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.
(Linux) It is not possible to open an effect or other dialog then navigate through the dialog using TAB. It is only possible to use ENTER to accept the defaults. 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.
(OS X and Linux) In some locales, Preferences text may be truncated or overlapped, or dropdown boxes truncated.
(OS X) Images captured with Help > Screenshot Tools are completely black.
(OS X) The "Cmd - Wheel - Rotate" mouse binding does not zoom in unless you modify the default System Preferences. ** On OS X 10.6 or later, go to Universal Access / Seeing / Zoom / Options and uncheck "Use scroll wheel with modifier keys to zoom".
Prior to OS X 10.6, go to "Mouse and Keyboard" and uncheck "Zoom using scroll ball while holding Command".
(Windows) The "Files Missing" warning always restores maximised windows to smaller size.
(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.
After changing language in Preferences, a few parts of the interface don't change until Audacity is restarted.
Audacity has several weaknesses in preserving the context of the audio being worked with:
If playback scrolls, pressing Stop leaves the waveform where it stopped and the cursor invisible. Pressing Play to resume then scrolls the waveform to start at the left edge, hiding the previously visible context before the cursor position. Workaround: If you had a selection and a special playback command like Cut Preview or Quick-Play caused the waveform to scroll, use View > Go to Selection Start or View > Go to Selection End to move the selection back into view.
Current scrolling behaviour makes it too hard to watch the waveform progress, with a single shift of cursor and waveform position when cursor reaches the right edge
By default, all audio in the project is selected if an action requiring a selection is requested when there is no selection (this behavior can be turned off in the Tracks Preferences). If enabled:
You can always apply effects to the whole project in one step, but you can also delete audio in all tracks if you press Delete when there is no selection. That is easy to Undo, but we aim to tweak this behavior and make it more customizable in a future Audacity.
A few items in Edit menu are incorrectly grayed out if no track is selected.
If Sync-Lock Tracks is enabled, there is no indication of the cursor in the Sync-Locked tracks.
If you save a region with Edit > Save Region then click OK in Preferences, the saved region cannot be restored.
In projects containing an hour or more of total audio, there may be a delay compared to previous versions of Audacity when:
Creating a label or label track
Dragging selections with the keyboard (Workaround: Hold SHIFT then press left or right arrow a few times per second instead of holding the arrow key)
The delay may be more evident on slower computers. In addition, label text may not be recovered if there is a crash.
Mouse Bindings are not currently configurable by the user.
Snap To state and Selection Format when Snap To is on are global. Therefore changing these in one project will make them show incorrectly in any other projects.
Snap-To does not move the cursor when first enabled or when the selection format is changed.
We're aware that some error messages in Audacity are not as helpful as we would like them to be. If you see a cryptic error message from Audacity, try a search (or ask) on
(Linux) If Audacity is left open but without focus, its CPU use will rise slowly until all available system CPU is consumed. This is a bug in wxGTK 2.8.10 (not previous versions) - see . This issue can be fixed by updating to wxGTK 2.8.11 or 2.8.12.
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 http://trac.wxwidgets.org/changeset/62397?format=diff&new=62397, 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).
(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.
(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.
(Linux) Complete or partial loss of Audacity menu bar
32-bit systems using wxGTK 2.8.12: If not using the Unity shell, closing Preferences may lead to loss of the Audacity Menu Bar (only "Fi" from "Files" will be visible). If using Unity, a small black square will appear, but the Audacity menu in the Global Menu is unaffected. Workaround for one session: Resize (or maximize/unmaximize) the Audacity window after closing Preferences.
64-bit systems using wx GTK 2.8.12 without Unity: Audacity may launch with no menu bar. Workaround for one session: Open and OK Preferences or open a new Audacity window.
Solution: This is a wxGTK bug, as reported here (
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.
(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.
A few commands with identical names in different sub-menus are not distinguishable by name in Keyboard Preferences.
In the "Edit" category of Keyboard Preferences, shortcuts for "Remove Audio or Labels" are listed above the same commands for "Labeled Audio".
In the "Tracks" category, shortcuts for "Align Tracks" are listed above those for "Align and Move Cursor".
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.
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".
(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:
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.
(Windows) The "Windows WASAPI" host currently has the following limitations:
The only available inputs are "loopback" inputs for recording computer playback.
The input slider in Device Toolbar is disabled (but appears to be enabled on switching to Windows WASAPI host until you select or change the loopback input).
The Audacity output slider may also be grayed out, or may affect the system output level but not the achieved recording level.
If you adjust the system output level and/or the output level of the application playing the audio this will also adjust the recording level.
Loopback recordings should only be made with the Audacity set to 44100 Hz . Setting other project rates will cause Audacity to resample the input to the project rate and may cause glitches in the recorded audio.
"Audio to buffer" in Recording Preferences cannot be used to adjust recording latency.
(Windows) "Windows WDM-KS" host is currently the least compatible of the four hosts, and may produce "error opening sound device" on some machines or have other quirks (such as some inputs not being available under this host). Please report detailed problems to and state your exact version of Windows.
The input slider in is disabled for all or most inputs (but appears to be enabled on switching to WDM-KS host until you switch to a different WDM-KS input). Please use the Windows system input slider instead.
Recording from the stereo mix input may not produce an adequate input level unless you turn the system audio output up very high. On Windows Vista and later you can choose the "Windows WASAPI" host and a "loopback" input instead for recording computer playback.
Adding or removing an external audio device while Audacity is open will not be automatically reflected in the list in Device Toolbar or Devices Preferences. On Mac, unplugging then replugging an external device will give "error while opening sound device" (on Linux, pressing "Record" a second time will remove the error). Workaround: Use Transport > Rescan Audio Devices.
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.
Recordings stopped with the "Stop and Set Cursor" shortcut (by default, SHIFT + A) cannot be removed by Undo.
(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.
(OS X and Linux) PortAudio's default latency values which are used when recording with software playthrough are much lower than Audacity's default "Audio to buffer" setting. This may cause playthrough or recording glitches when recording with software playthrough enabled, especially when using pulse on Linux. Workaround for Linux: record from an (hw) device instead if software playthrough is required.
(OS X) Playback to Bluetooth headsets gives an error. Workaround: Revert to Audacity 1.3.3 (this may only work with stereo headsets), or use to send the Audacity output to an audio application that works with the headset.
(OS X) The "Hardware Playthrough" option in Recording Preferences is currently unsupported on all known Mac hardware. Try the "Software Playthrough" preference instead. If that does not work, the third-party application also provides software playthrough.
(Windows) When a USB device is connected, the Mixer Toolbar input slider for that device (and sometimes for any device) may wrongly appear active even though it has no control over the device's input level. Sometimes the Audacity slider will apply a software gain to the level (which is dangerous as it will only make the same clipped input quieter rather than stopping the clipping). Sometimes the Audacity slider will not affect the input volume at all. Workaround: use the slider in the Windows Control Panel where available, or any gain control on the device, or reduce the output being sent to the device.
(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.
(Windows) Audacity is incompatible (or not fully compatible) with some professional soundcards or audio devices, and may crash or have limited or faulty functionality. Occasionally, this may be true of some AC97 devices built into the motherboard. Workaround: make a different soundcard your default when using Audacity, but please e-mail the following details to our :
Your version of Windows and Service Pack
Name, model number and driver version number of the soundcard or device.
Note: Multichannel Recording in Audacity is often not possible with professional devices unless you compile Audacity with ASIO support.
Calculation of "disk space remains for recording (time)" incorrect when recording in 24 bit quality.
Play-at-Speed slider: Change of playback speed is no longer automatic after you move the play-at-speed slider. To change speed, move the slider, then click the green button to left of the slider to play at the new speed.
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.
"Play/Stop and Set Cursor": Use SHIFT + A. This also starts or stops playback, but when stopped, sets the cursor to the stop position.
To change these shortcuts, or to add a shortcut for the separate "Play" and "Stop" commands shown in the Transport Menu, go to the Keyboard Preferences.
Timer Record cannot maintain scheduled duration if system clock changes
(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.
(Linux) Extended Import: Clicking "Move rule up" when there are no rules or filters causes a crash.
(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.
(OS X) Audio Units Plug-ins: Audacity scans for and loads Audio Unit (AU) effects on each launch before the main interface appears. This can lead to a very slow launch if there are many plug-ins. Occasionally, an incompatible or badly written plug-in may lead to a crash or freeze on launch. Known plug-ins affected are listed below.
Mac OS X:
AURoundTripAAC from "Apple audio mastering tools".
In a future version of Audacity we aim to defer loading of AU plug-ins until they are requested in the Effect menu, as we already do for VST effects. Workaround: If AudioUnit effects are not needed in Audacity, force quit Audacity, then open Audacity's folder for application data. 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
If AU plug-ins were the problem, Audacity should now launch.
For more detailed help with editing audacity.cfg or with identifying or moving AU plug-ins, please follow the Audio Unit instructions on this page.
(Windows and OS X) "Install VST Effects" dialog lists more than VST effects: On first use, Audacity scans for VST effects then (before launching Audacity) presents a dialog where you can choose which VST effects to load into the Audacity Effect menu. Remove the checkmark from any VST effects you do not want to load then click OK to load the checkmarked effects. If you click Cancel the dialog will reappear on next Audacity launch.
Note that VST instruments will appear in the list but are not supported, so will not load even if checkmarked.
On Windows the dialog will appear even if you have no VST effects, because Audacity detects the two shipped LADPSA plug-ins (hard_limiter_1413.dll and sc4_1882.dll) and also any optional LADSPA DLL plug-ins you may have installed. These LADSPA plug-ins will load whether you enable them in the dialog or not. Therefore you should just click OK on the dialog if you have no VST effects.
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.
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.
Projects created by Audacity 1.1.x or earlier are no longer supported. Workaround: Export each project track as WAV using the appropriate legacy version of Audacity, then import the WAV files into current Audacity.
Projects created by Audacity 1.2.x are partially supported - there is a possibility Audacity could corrupt them. Please make a backup copy of the project's .aup file and _data folder to a new folder before opening the project in this version of Audacity. Once you save the project in this version, it cannot be opened in 1.2.
Projects created by previous versions of Audacity may contain audio "block files" longer than the project format allows. Reopening such projects in previous versions might or might not result in deletion of the overlong audio. Audacity has been provisionally fixed so that it can no longer create or delete overlong files, but it cannot read any such files it encounters. If overlong files are found, a "Problems Reading Sequence Tags" message will display .
If you continue with the offered repair then choose "Continue without deleting" in the Orphan Block File(s) dialog, the overlong files will be retained as "orphans" in the project's _data folder but will appear as silence in the track(s).
As long as you choose "Close project immediately" in the Orphan Block File(s) dialog, the project will quit and will not be changed in any way.
If you encounter the "Problems Reading Sequence Tags" message, please write to our with a copy of the .aup file and the log as found at Help > Show Log.
Time Track warp points saved in a 2.0.3 or later project will be preserved if opened in previous Audacity versions, but playback and display will be incorrect.
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.
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.
(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.
(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.
If you change the Mute/Solo button state on any track(s) before applying an effect or edit, Undo also undoes the Mute/Solo changes. Workaround: Select the audio to be edited after changing the Mute/Solo state (other than by using ENTER to select the focused track).
(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.
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)
(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 Vista,7) On upgrading to the current Beta from 1.3.12 or earlier, "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 and OS X) Some USB or Firewire recording devices only record silence, or only offer mono recording for a stereo device, or only mono or stereo for a device that previously supported multi-channel recording. Workaround: You can try 1.3.10 Beta or earlier (including 1.2.5/6), but these versions may have other bugs or limitations.
Please report make and model number of devices that exhibit the issue, and your operating system details (for example, Windows 7 Service Pack 1).
(Windows) There may be substantial delays drawing the waveform in longer projects. These include:
opening saved projects that were fitted to the window
fitting an already zoomed in project to the window or zooming in on a fitted project
progress dialog remains white for a long time after the progress bars complete for a file import or effect.
Audacity 2.0.6 was available from 29 September 2014 until 28 March 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.
FFmpeg updated for 2.0.6:
(OS X) Issues with VoiceOver:
If you use arrow keys to navigate the Timetext controls in Selection Toolbar, VoiceOver stops reading. Workaround: Use Control-Option-W
When you TAB forwards from "Audio Position" in Selection Toolbar, the "Selection End" or "Selection Length" radio button is read as "Selection Start". When you use COMMAND + F6 or COMMAND + SHIFT + F6 to move directly into "Selection End" from another toolbar, the button is read as "Selection Start".
Mixer Toolbar input/output sliders are not read, just described as "multiple indicators". The "Graphic EQ" sliders in Equalization *are* read.
Metadata Editor table not read.
Edit Labels dialog not read.
Audacity writes both ID3 v2.3 (TYER) and v2.4 (TDRC) tags for "Year", but any applications that require the older TYER on its own (without TDRC) will not see "Year" in Audacity-exported files. The id3 command-line application on Linux is one example.
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.
Zoom to Selection shows none of the surrounding context
Using Cut, Copy, Paste, Delete or Silence Audio.
On Mac, Audacity may freeze if JACK is launched by QjackCtl then Audacity is launched. Workaround: Use JackPilot to launch JACK, or launch QJackCtrl after Audacity and JACK are running.
MNoiseGenerator AU in MFreeEffectsBundle
Native Instruments B4
Native Instruments Guitar Rig v3 and v4 (v5 does not have this issue)
PredatorFX
Waves Version 7, 8 and 9 AU
OS X 10.10 Yosemite: Audacity 2.0.6 will not officially support OS X 10.10 Yosemite when released (in particular, Apple Audio Units may not open in Audacity).
Extra 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 .
You may see the error Application configuration incorrect when launching Audacity after installation. This mainly affects some Windows XP or 2000 machines. This can be fixed by downloading and installing the appropriate Microsoft "Redistributable Package" as follows:
for 32-bit Windows
for 64-bit Windows.
Be sure to get the correct package according to whether you have 32-bit or 64-bit Windows. To check, right-click over and choose . If 64-bit is not mentioned, you have 32-bit.
On first use of Audacity you need to confirm the new dialog for detected effects before you can start the Audacity program.
Users upgrading to 2.0.x versions from 1.3.6 or earlier must download the of the LAME MP3 encoder.
Interface:
Redesigned, searchable Keyboard Preferences with Tree, Name and Key views.
Edit Menu: "Cut" and "Delete" are now in the top level of the menu.
Transport Menu now includes "Play/Stop" and "Play/Stop and Set Cursor" (use Keyboard Preferences to create shortcuts for "Play" and "Stop").
Tracks Menu now includes "Mix and Render to New Track".
Track Dropdown Menu now has Move Track To Top and Move Track To Bottom.
New right-click menu choice "Delete Label" to remove single labels.
"Snap To" now offers choice of snap to the "closest" or "prior" position. Note: the previous "Snap To On" keyboard shortcut will no longer work.
"Snap To" settings are now independent for each project.
Effects:
Truncate Silence: redesigned with simpler option "Truncate Detected Silence" to shorten to the specified length without compressing silence.
VST effects: New "Settings" dialog lets you specify buffer size (for faster processing) and enable buffer delay compensation (to prevent inserted silence). Compensation may cause a crash in a few plug-ins.
Import or export using FFmpeg now requires FFmpeg 1.2 or later (or libav 0.8 or later). For recommended downloads of recent FFmpeg please visit .
New Tamil translation (largely complete).
(Windows) FLAC exports can now exceed 2 GB in size.
(OS X) Easier Audacity installation using the DMG: drag the Audacity folder to the /Applications shortcut.
(Linux) Self-compiled builds of Audacity now search for system LADSPA effects in /usr/lib/ladspa.
Interface:
Region Restore did not restore the region after using Preferences.
Dragging selections with the keyboard or Selection Toolbar digits was very slow.
(Windows) Help > About Audacity crashed when run in Magyar language.
(OS X) Some full and reduced Menu Bar items were not translated.
(OS X and Linux) Fixed various interface crashes.
Effects:
Reverb and Paulstretch were missing from Chains.
Analyze > Contrast could report very inaccurate RMS levels.
Noise Removal: Attack and decay times were half as long as set.
Click or drag on the Timeline after Loop Play continued to loop.
Transcription Toolbar did not play slower than 0.1x speed.
(Linux) Audacity did not build if python 2 was not available.
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 https://manual.audacityteam.org/o/man/accessibility.html
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.
Install VST Effects dialog: The list view of plug-ins is a check box list view, and all the plug-ins are checked initially. Unfortunately Jaws and Window-Eyes do not read whether or not a check box is checked, but you can still press SPACE to change this.
Keyboard Preferences: Window-Eyes doesn't read the key bindings when View by Tree is selected, and may not always read the bindings in other views.
(OS X) It is not possible to TAB through Keyboard Preferences.
(OS X) Issues with VoiceOver:
(reported on OS X 10.9.x) After exporting, the black accessibility area is trapped in the Tooldock area, so there is no way to read the tracks. Workaround: Save as a project, close the project then reopen it. You can then navigate the tracks with VoiceOver.
If you use arrow keys to navigate the Timetext controls in Selection Toolbar, VoiceOver stops reading. Workaround: Use Control-Option-W
(Linux) Using the Unity shell, most or all keyboard shortcuts are not listed in the Audacity menus. Gnome Fallback is not affected. Workaround: You can view shortcuts at or online at .
(Linux) SPACE cannot be used to change context menu items that have a checkbox (such as Selection Format in the context menu of TimeText digits, or Mono/Left/Right and Set Rate and Set Sample Format in the Track Dropdown Menu). Using SPACE in these menus could crash Audacity. Workaround: Use ENTER instead of SPACE to select the new choice.
(Linux) Issues with Orca:
Audacity tracks are not read.
Not all toolbar controls are read, examples being Timetext controls, Project Rate and controls in Device Toolbar.
Not all controls in Preferences are read.
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) New libsoxr resampling library: Default ./configure will enable a new library libsoxr for resampling and disable libresample and libsamplerate (the previous resampling libraries). Cmake 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.
To enable libresample, your configure must include --without-libsoxr as well as --with-libresample.
(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 may not always compile against supported versions of libav or FFmpeg. Audacity 2.0.6 supports FFmpeg 1.2 or higher (FFmpeg 2.2.3 is known to work) or libav 0.8 or higher.
Dynamic loading (as in default Audacity ./configure) requires building against the FFmpeg project - it will not build against the libav* headers from the libav project. Workarounds: Configure Audacity with --disable-dynamic-loading. If dynamic loading is required, build against FFmpeg instead of libav, or you can build against libav if you remove the "#define IS_FFMPEG_PROJECT 1" line in src/FFmpeg.h.
Audacity may still build against no-longer-supported FFmpeg versions (such as FFmpeg 0.8 which is system-installed on Debian Wheezy), but configuring with --disable-dynamic-loading will be necessary. FFmpeg 0.8 has at least one known issue in Audacity 2.0.6 or later: mono WMA files export with no audio data. This issue will not be fixed given FFmpeg 0.8 is no longer supported by Audacity 2.0.6.
(Windows and Mac OS X) When running VST effects in graphical mode the controls of many plug-ins do not visibly respond when loading a preset file from the "Load" button. The new settings are however loaded internally, will apply when running the effect and will be visible if you reopen the effect after running it. Controls do respond to loading a preset file if you turn off graphical mode.
(OS X) When saving 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" dropdown 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).
AU
Workaround: If Audio Units are not needed in Audacity, restart Audacity then open Audacity > Preferences and choose "Effect". Under "Enable Effects", uncheck "Audio Unit", press OK and restart Audacity. Alternatively, look in the Mac Crash Report for the AU plug-in that crashed, move it from <Your Home>/Library/Audio/Plug-Ins/Components or /Library/Audio/Plug-Ins/Components then restart Audacity. See this page for more help.
(Windows)
DISTRHO Mini Series VST's from crash Audacity in graphic mode but will run in text mode (open the Effects Preferences and uncheck "Display VST effects in graphical mode").
Waves v5 may cause Audacity to hang if you select it in the "Install VST Effects" dialog then click OK.
(OS X) Some VST plug-ins no longer allow text input in the presets dropdown, either by typing or pasting. Examples are Sound Hack "Delay Trio / Freesound Bundle" and Blue Cat.
(OS X) Blue Cat plug-ins: Opening the dialog to save a preset will hide the plug-in interface and lock out the main Audacity window. Workaround: Right-click or CONTROL-click over Audacity's Dock icon, choose "Quit" then choose to save changes or not. Other plug-ins that use JUCE (such as GRM Tools) are also likely to be affected.
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. This may occur for example in the Ubuntu package of Audacity 2.0.5 on Ubuntu 14.04. Workaround: Build Audacity configured --with-sbsms="local", or use the Audacity package in Ubuntu 14.10 which uses libsbsms 2.0.2-1.
(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 .
(Windows and Linux) Some LADSPA "Blop" plug-ins ( ) are reported to crash in Audacity on Linux Debian. On Windows, the Blop plug-ins included in can also crash, but this can be avoided if you ensure the "blop_files" folder contains the necessary "_data.dll" files for the plug-ins and that this folder is present in the Audacity "Plug-Ins" folder.
(Windows) LADSPA Multiband EQ may not be visible in Effect menu (occurs on Windows XP), and crashes soon after opening
Cut Preview only plays the upper track of multiple selected or Sync-Locked tracks.
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.
Nyquist effects add spurious split lines if applied over clip boundaries.
Preview is not supported in Nyquist plug-ins. "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.
The following effects remove envelope control points: Change Speed/Pitch/Tempo; Equalization; Noise Removal; Sliding Time Scale/Pitch Shift; any Nyquist effect in the Effect menu. Workaround: Use Tracks > Mix and Render to apply the envelope to the waveform before applying the effect.
The Reverse effect retains the control points, but does not move them.
Truncate Silence doesn't work intuitively if run on multiple tracks. It may be preferable to run it on each track at a time.
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). Also note that projects containing more than 2^31 samples of total audio cannot be correctly saved.
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
faint, specious clip lines could occur if the clip is dragged back to its original track.
Workaround: Edit > Undo if necessary then drag from outside the selection region or single-click in the clip to remove the selection.
Undo may fail silently after applying an effect or edit across one or more split lines. Workaround: Effect > Repeat the effect from the top of the Effect Menu then undo both applications of the effect, or open View > History... and click on the step above the currently indicated line.
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.
When pasting audio into tracks with envelope points, the envelope points may move in unexpected ways, so causing unwanted amplitude adjustments.
(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.
In the "Custom FFmpeg Export" dialog, deleting a preset crashes Audacity. Importing a preset crashes Audacity unless the "ffmpeg_presets" 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: Given the alternative AAC encoders for FFmpeg have other problems as described in these notes, you can instead export as WAV and convert to AAC in iTunes on Windows and Mac.
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.
AAC: Artist and Year metadata is not exported or imported due to a bug in FFmpeg 2.2.2.
WMA and APE (Monkeys Audio): "Artist Name" is not seen on importing the file (Audacity bug)
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.
(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 download site and extract the files to your own preferred location.
In projects containing an hour or more of total audio, there may be a delay compared to previous versions of Audacity when:
Dragging sample points with Draw Tool
Using Cut, Copy, Paste, Delete or Silence Audio.
The delay may be more evident on slower computers. In addition, label text may not be recovered if there is a crash.
(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.
(OS X) Images captured with Help > Screenshot Tools are completely black.
(OS X) The "Cmd - Wheel - Rotate" mouse binding does not zoom in unless you modify the default System Preferences. ** On OS X 10.6 or later, go to Universal Access / Seeing / Zoom / Options and uncheck "Use scroll wheel with modifier keys to zoom".
Prior to OS X 10.6, go to "Mouse and Keyboard" and uncheck "Zoom using scroll ball while holding Command".
(Windows) The "Files Missing" warning always restores maximised windows to smaller size.
(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.
After changing language in Preferences, a few parts of the interface don't change until Audacity is restarted.
Audacity has several weaknesses in preserving the context of the audio being worked with:
If playback scrolls, pressing Stop leaves the waveform where it stopped and the cursor invisible. Pressing Play to resume then scrolls the waveform to start at the left edge, hiding the previously visible context before the cursor position. Workaround: If you had a selection and a special playback command like Cut Preview or Quick-Play caused the waveform to scroll, use View > Go to Selection Start or View > Go to Selection End to move the selection back into view.
Current scrolling behaviour makes it too hard to watch the waveform progress, with a single shift of cursor and waveform position when cursor reaches the right edge
By default, all audio in the project is selected if an action requiring a selection is requested when there is no selection (this behavior can be turned off in the Tracks Preferences). If enabled:
You can always apply effects to the whole project in one step, but you can also delete audio in all tracks if you press Delete when there is no selection. That is easy to Undo, but we aim to tweak this behavior and make it more customizable in a future Audacity.
A few items in Edit menu are incorrectly grayed out if no track is selected.
If Sync-Lock Tracks is enabled, there is no indication of the cursor in the Sync-Locked tracks.
Mouse Bindings are not currently configurable by the user.
Snap-To does not move the cursor when first enabled or when the selection format is changed.
We're aware that some error messages in Audacity are not as helpful as we would like them to be. If you see a cryptic error message from Audacity, try a search (or ask) on
(Linux) If Audacity is left open but without focus, its CPU use will rise slowly until all available system CPU is consumed. This is a bug in wxGTK 2.8.10 (not previous versions) - see . This issue can be fixed by updating to wxGTK 2.8.11 or 2.8.12.
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 http://trac.wxwidgets.org/changeset/62397?format=diff&new=62397, 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).
(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.
(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.
(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.
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.
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".
(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). Workarounds: Try launching Audacity from the terminal with the pulse latency set in an environment variable, for example:
env PULSE_LATENCY_MSEC=30 audacity
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"
(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:
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.
(Linux) Meters may not respond immediately to playback which could cause them to report incorrect peak level or not display clipping.
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 JACK, 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.
On Mac, Audacity may freeze if JACK is launched by QjackCtl then Audacity is launched. Workaround: Use JackPilot to launch JACK, or launch QJackCtrl after Audacity and JACK are running.
(OS X and Linux) PortAudio's default latency values which are used when recording with software playthrough are much lower than Audacity's default "Audio to buffer" setting. This may cause playthrough or recording glitches when recording with software playthrough enabled, especially when using pulse on Linux. Workaround for Linux: record from an (hw) device instead if software playthrough is required.
(OS X) Playback to Bluetooth headsets gives an error. Workaround: Revert to Audacity 1.3.3 (this may only work with stereo headsets), or use to send the Audacity output to an audio application that works with the headset.
(OS X) The "Hardware Playthrough" option in Recording Preferences is currently unsupported on all known Mac hardware. Try the "Software Playthrough" preference instead. If that does not work, the third-party application also provides software playthrough.
(Windows) The input slider in is disabled for all or most inputs. Please use the Windows system input slider instead.
(Windows) Recording from the stereo mix input may not produce an adequate input level unless you turn the system audio output up very high. On Windows Vista and later you can choose the "Windows WASAPI" host and a "loopback" input instead for recording computer playback.
(Windows) When a USB device is connected, the Mixer Toolbar input slider for that device (and sometimes for any device) may wrongly appear active even though it has no control over the device's input level. Sometimes the Audacity slider will apply a software gain to the level (which is dangerous as it will only make the same clipped input quieter rather than stopping the clipping). Sometimes the Audacity slider will not affect the input volume at all. Workaround: use the slider in the Windows Control Panel where available, or any gain control on the device, or reduce the output being sent to the device.
(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.
(Windows) Audacity is incompatible (or not fully compatible) with some professional soundcards or audio devices, and may crash or have limited or faulty functionality. Occasionally, this may be true of some AC97 devices built into the motherboard. Workaround: make a different soundcard your default when using Audacity, but please email the following details to our :
Your version of Windows and Service Pack
Name, model number and driver version number of the soundcard or device.
Note: Multichannel Recording in Audacity is often not possible with professional devices unless you compile Audacity with ASIO support.
(Windows) The "Windows WASAPI" host currently has the following limitations:
The only available inputs are "loopback" inputs for .
The input slider in is disabled.
Adding or removing an external audio device while Audacity is open will not be automatically reflected in the list in Device Toolbar or Devices Preferences. On Mac, unplugging then replugging an external device will give "error while opening sound device" (on Linux, pressing "Record" a second time will remove the error). Workaround: Use Transport > Rescan Audio Devices.
Calculation of "disk space remains for recording (time)" incorrect when recording in 24 bit quality.
Play-at-Speed slider: Change of playback speed is no longer automatic after you move the play-at-speed slider. To change speed, move the slider, then click the green button to left of the slider to play at the new speed.
Timer Record cannot maintain scheduled duration if system clock changes
(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.
(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.
(Windows and OS X) "Install VST Effects" dialog:
The dialog lists more than VST effects: On first use, Audacity scans for then (before launching Audacity) presents a dialog where you can choose which VST effects to load into the Audacity Effect menu. Remove the checkmark from any VST effects you do not want to load then click OK to load the checkmarked effects. If you click Cancel the dialog will reappear on next Audacity launch.
VST instruments will appear in the list but are not supported, so will not load even if checkmarked.
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.
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.
Projects created by Audacity 1.1.x or earlier are no longer supported. Workaround: Export each project track as WAV using the appropriate legacy version of Audacity, then import the WAV files into current Audacity.
Projects created by Audacity 1.2.x are partially supported - there is a possibility Audacity could corrupt them. Please make a backup copy of the project's .aup file and _data folder to a new folder before opening the project in this version of Audacity. Once you save the project in this version, it cannot be opened in 1.2.
Projects created by previous versions of Audacity may contain audio "block files" longer than the project format allows. Reopening such projects in previous versions might or might not result in deletion of the overlong audio. Audacity has been provisionally fixed so that it can no longer create or delete overlong files, but it cannot read any such files it encounters. If overlong files are found, a "Problems Reading Sequence Tags" message will display .
If you continue with the offered repair then choose "Continue without deleting" in the Orphan Block File(s) dialog, the overlong files will be retained as "orphans" in the project's _data folder but will appear as silence in the track(s).
As long as you choose "Close project immediately" in the Orphan Block File(s) dialog, the project will quit and will not be changed in any way.
If you encounter the "Problems Reading Sequence Tags" message, please write to our with a copy of the .aup file and the log as found at Help > Show Log.
Time Track warp points saved in a 2.0.3 or later project will be preserved if opened in previous Audacity versions, but playback and display will be incorrect.
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.
(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 keyboard shortcut alternatives for the buttons instead.
(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)
(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 Vista,7) On upgrading to the current Beta from 1.3.12 or earlier, "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 and OS X) Some USB or Firewire recording devices only record silence, or only offer mono recording for a stereo device, or only mono or stereo for a device that previously supported multi-channel recording. Workaround: You can try 1.3.10 Beta or earlier (including 1.2.5/6), but these versions may have other bugs or limitations.
Please report make and model number of devices that exhibit the issue, and your operating system details (for example, Windows 7 Service Pack 1).
(Windows) There may be substantial delays drawing the waveform in longer projects. These include:
opening saved projects that were fitted to the window
fitting an already zoomed in project to the window or zooming in on a fitted project
progress dialog remains white for a long time after the progress bars complete for a file import or effect.
LV2 effects are now supported on all platforms (textual interface only).
(OS X and Linux) Nyquist effects ran much more slowly than on Windows.
When you TAB forwards from "Audio Position" in Selection Toolbar, the "Selection End" or "Selection Length" radio button is read as "Selection Start". When you use COMMAND + F6 or COMMAND + SHIFT + F6 to move directly into "Selection End" from another toolbar, the button is read as "Selection Start".
Mixer Toolbar input/output sliders are not read, but just described as "multiple indicators". The "Graphic EQ" and vertical sliders in Equalization *are* read.
Metadata Editor table not read.
Edit Labels dialog not read.
In the "Edit Chains" window, only the first command in the "Chain" list is read, and it is only read when first accessed. In the "Select Command" window for inserting a new command in a Chain, commands in the table are not read.
"Manage Curves" table in Equalization not read.
Building against self-compiled FFmpeg 2.2.2 with --disable-dynamic-loading the only argument fails on Ubuntu 13.10 with "undefined reference to 'av_codec_is_encoder'". Workaround: Configuring with --disable-dynamic-loading and --with-lib-preference="local" (or at least --with-ffmpeg="local") may build successfully, but may not disable Libraries Preferences. The best solution may be not to disable dynamic loading.
MNoiseGenerator AU and others in MFreeEffectsBundle crash if you preview them
Native Instruments B4 and Native Instruments Guitar Rig v3 and v4 (v5 does not have this issue)
PredatorFX
Waves Version 7, 8 and 9 AU
ID3 v2.4 tags in imported MP3 files are not seen and will be removed on export.
Audacity writes both ID3 v2.3 (TYER) and v2.4 (TDRC) tags for "Year", but any applications that require the older TYER on its own (without TDRC) will not see "Year" in Audacity-exported files. The id3 command-line application on Linux is one example.
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.
Zoom to Selection shows none of the surrounding context
Loopback recordings should only be made with the Audacity Project Rate set to 44100 Hz . Setting other project rates will cause Audacity to resample the input to the project rate any may cause glitches in the recorded audio.
"Audio to buffer" in Recording Preferences cannot be used to adjust recording latency.
The dialog is on top of other windows, so could hide any prompts that VST effects show when effects are loaded after pressing OK. This would be evident by the "loading progress" arrow in the check boxes coming to a halt and the VST dialog losing focus. To continue loading the effects in this case, press ENTER on your keyboard to OK the hidden prompt, or drag the VST dialog away to reveal the prompt then click OK on the prompt.
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.
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.
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).
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
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.
(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.
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.
(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).
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.
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.
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
(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.
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.
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.
(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.
(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).
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).
(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.
(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.
(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".
(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"
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.
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.
(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.
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.
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.
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.
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.
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.
(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.2 was available from 20th January 2016 until 16 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.
On first use of Audacity you need to confirm or cancel the Register Effects dialog for detected effects before you can launch Audacity.
MP3 Encoding: Users upgrading to Audacity 2.0.x versions from 1.3.6 or earlier must download the latest version of the LAME MP3 encoder.
Users on Windows XP: You may see "Entry Point Not Found" when first launching Audacity after installation. This error occurs if you are running less than the latest "Service Pack" of updates for your Windows XP system. Please see https://manual.audacityteam.org/o/man/faq_installation_and_plug_ins.html#entry_point for how to install the latest Service Pack and for advice about the potential security risks of running XP now that Microsoft no longer supports it.
All Effect Menu items (built-in or plug-in) can now be used in a Chain.
Items in the Effect, Generate or Analyze Menus can be sorted or grouped by name, publisher or class of effect.
Noise Removal is improved and renamed to "Noise Reduction".
Change Speed has new time controls for current and new length. You can now enter the speed change as a multiplier e.g. "2" is twice as fast.
New "Crossfade Tracks" effect can be used for crossfading two tracks. This replaces Cross Fade In and Cross Fade Out.
Nyquist Prompt and most shipped Nyquist effects now have Preview button.
Interface:
Redesigned Meter Toolbars: The default shows separate Record and Playback Meters, half-height so they can be wider while docked, in gradient style.
A frequency selection can now be made (and spectral edit effects applied to those frequencies) when in a spectrogram view. You can also create or adjust frequency selections in a new "Spectral Selection Toolbar" (available at View > Toolbars).
Transcription Toolbar (Play-at-speed) can now loop play and cut-preview.
Timer Record now saves recordings automatically into an existing project.
New Armenian translation.
Operating system and sound device support:
(Windows) Audacity 2.1.0 requires Windows XP SP3 (32-bit) or XP SP2 (64-bit), Vista, Windows 7, Windows 8 or 8.1.
(Windows) Audacity is now compiled using Visual Studio 2013.
(Windows) Recording with WASAPI host now includes experimental support for physical inputs (up to 24-bit depth) as well as loopback recording.
(OS X) 10.10 (Yosemite) is now supported including Apple Audio Units.
Please report any issues with WASAPI recording/playback or Yosemite to .
(Linux Ubuntu) Under Unity, keyboard shortcuts are not visible in the Audacity menus. Keyboard shortcuts are visible if you install the classic GNOME Flashback interface or under Unity if you open Audacity with the UBUNTU_MENUPROXY=0 environment variable. Audacity compiled from source will ship with src/audacity.desktop.in set to UBUNTU_MENUPROXY=0 but it will remain up to distributions to use this desktop file.
Selections made with Selection Toolbar were not restored after Undo.
Undo could fail silently if a selection included/touched a clip boundary.
Imports and Exports:
If there were invalid FFmpeg libs in system PATH this prevented Audacity recognising the installed FFmpeg or the FFmpeg specified in audacity.cfg.
Mac OS X:
Fix uninitialized buffer - this should correct playback buzz or crackle where the upper of multiple tracks started with or contained white space.
Device names were corrupted when using system language other than English.
Fixed crashes using (external program).
Waves v9 Audio Units should now work correctly.
GNU/Linux:
Fix "Audacity already running" error when using the command-line or context menu to open multiple or further files.
Fix segfault exporting an FFmpeg format to an unwritable folder.
Fix silent failure exporting FFmpeg, MP2 or OGG to an unwritable folder.
Fix ENTER activated an effect when OK button was greyed out.
Some interface text or markings remain in black when using High Contrast light-on-dark themes, so cannot be read properly.
Spectral Selection Toolbar: Typing a 0 (zero) in the High Frequency box when its digits are dashed (undefined) resets existing Low Frequency values to zero. Typing or incrementing digits in either box may require the wanted digit to be typed or incremented twice and may increment digits in the other box. It is usually best to enter the high frequency first and then TAB through both Low and High Frequency boxes to ensure that they contain correct values.
Analyze > Contrast: Once you use ALT + F6 or ALT + SHIFT + F6 to switch focus from this dialog, you can't return to it using the keyboard. You can switch to and from Contrast on Mac OS X by using the Window Menu.
(Windows only) Plot Spectrum: Changing the values loses focus on the dialog. Use ALT + F6 to return focus to Plot Spectrum.
Register Effects dialog: The list view of plug-ins is a check box list view, and all the plug-ins are checked initially. Unfortunately Jaws and Window-Eyes do not read whether or not a check box is checked, but you can still press SPACE to change this.
Keyboard Preferences: Window-Eyes doesn't read the key bindings when View by Tree is selected, and may not always read the bindings in other views.
(OS X) It is not possible to TAB through Keyboard Preferences.
(OS X) It is not possible to move through docked toolbars using the ALT + F6 or ALT + SHIFT + F6 shortcuts.
(OS X) It is not possible to move between the main Audacity window and some VST and Audio Unit effects using the ALT + F6 or ALT + SHIFT + F6 shortcuts when the effect is in Graphical Mode. You can use the "Manage" menu then Options... to change the effect to textual mode.
(OS X) Issues with VoiceOver:
(reported on OS X 10.9.x) After exporting, the black accessibility area is trapped in the Tooldock area, so there is no way to read the tracks. Workaround: Save as a project, close the project then reopen it. You can then navigate the tracks with VoiceOver.
If you use arrow keys to navigate the Timetext controls in Selection Toolbar, VoiceOver stops reading. Workaround: Use Control-Option-W
When you TAB forwards from "Audio Position" in Selection Toolbar, the "Selection End" or "Selection Length" radio button is read as "Selection Start". When you use COMMAND + F6 or COMMAND + SHIFT + F6 to move directly into "Selection End" from another toolbar, the button is read as "Selection Start".
Mixer Toolbar input/output sliders are not read, but just described as "multiple indicators". The "Graphic EQ" and vertical sliders in Equalization *are* read.
Metadata Editor table not read.
Edit Labels dialog not read.
In the "Edit Chains" window, only the first command in the "Chain" list is read, and it is only read when first accessed. In the "Select Command" window for inserting a new command in a Chain, commands in the table are not read.
"Manage Curves" table in Equalization not read.
(Linux Ubuntu) Under Unity, keyboard shortcuts are not visible in the Audacity menus. Keyboard shortcuts are visible if you install the classic GNOME Flashback interface or under Unity if you open Audacity from the termimal with
env UBUNTU_MENUPROXY=0 audacity
Audacity will now ship with src/audacity.desktop.in set to UBUNTU_MENUPROXY=0 so Audacity compiled from source will show shortcuts in the menus and will have its own menu bar in the application. It will remain up to Ubuntu whether they use this desktop file in packaged versions of Audacity.
(Linux) SPACE cannot be used to change context menu items (such as Selection Format in the context menu of TimeText digits, or Mono/Left/Right and Set Rate and Set Sample Format in the Audio Track DropDown Menu). Workaround: Use ENTER instead of SPACE.
(Linux) Issues with Orca:
Audacity tracks are not read.
Not all toolbar controls are read, examples being Timetext controls, Project Rate and controls in Device Toolbar.
Not all controls in Preferences are read.
Control labels for VAMP and VST plug-ins are not read.
Control labels for Nyquist plug-ins are read inconsistently in older version 3 or earlier plug-ins (Version 4 seems to read more consistently).
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.
(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 supports FFmpeg 1.2 or higher (FFmpeg 2.2.3 is known to work) or libav 0.8 or higher.
Dynamic loading (as in default Audacity ./configure) requires building against the FFmpeg project - it will not build against the libav* headers from the libav project. Workarounds: Configure Audacity with --disable-dynamic-loading. If dynamic loading is required, build against FFmpeg instead of libav, or you can build against libav if you remove the "#define IS_FFMPEG_PROJECT 1" line in src/FFmpeg.h.
Audacity may still build against no-longer-supported FFmpeg versions (such as FFmpeg 0.8 which is system-installed on Debian Wheezy), but configuring with --disable-dynamic-loading will be necessary. FFmpeg 0.8 has at least one known issue in Audacity 2.0.6 or later: mono WMA files export with no audio data. This issue will not be fixed given FFmpeg 0.8 is no longer supported by Audacity 2.0.6.
Building against self-compiled FFmpeg 2.2.2 with --disable-dynamic-loading the only argument fails on Ubuntu 13.10 with "undefined reference to 'av_codec_is_encoder'". Workaround: Configuring with --disable-dynamic-loading and --with-lib-preference="local" (or at least --with-ffmpeg="local") may build successfully, but may not disable Libraries Preferences. The best solution may be not to disable dynamic loading.
When you import a preset into an Apple Audio Unit, that preset's settings are applied by the effect without the effect controls updating to the new settings. Other AU effects may ignore presets when you import them. To be sure the imported preset you want to use is loaded into the effect, select it from "User Presets".
Digitech RP250 (effects pedal)
MNoiseGenerator AU and others in MFreeEffectsBundle crash if you preview them
Native Instruments B4 and Native Instruments Guitar Rig v3 and v4 (v5 does not have this issue)
PredatorFX
Waves Version 7 and 8 AU: These effects may crash Audacity on quit, after project data has been saved. Waves Version 9 AU should now work correctly.
Workaround: If Audio Units are not needed in Audacity, restart Audacity then open Audacity > Preferences and choose "Effect". Under "Enable Effects", uncheck "Audio Unit", press OK and restart Audacity. Alternatively, look in the Mac Crash Report for the AU plug-in that crashed, move it from <Your Home>/Library/Audio/Plug-Ins/Components or /Library/Audio/Plug-Ins/Components then restart Audacity. See this page for more help.
(Windows)
DISTRHO Mini Series VST's from http://distrho.sourceforge.net/plugins.php crash Audacity in graphic mode but will run in text mode (open the Effects Preferences and uncheck "Display VST effects in graphical mode").
Waves v5 may cause Audacity to hang if you select it in the "Register Effects" dialog then click OK.
iZotope Vinyl that has not yet been registered cannot be used in Audacity 2.1.0 because it causes the "Register Effects" dialog to freeze. You can register it in a previous version of Audacity.
(Linux)
If a TAL VST is open when a built-in effect is previewed, Audacity will crash.
(Windows and Mac OS X) When running VST effects in graphical mode the controls of many plug-ins do not visibly respond when loading a preset file from the "Load" button. The new settings are however loaded internally, will apply when running the effect and will be visible if you reopen the effect after running it. Controls do respond to loading a preset file if you turn off graphical mode.
(OS X) Some VST plug-ins no longer allow text input in the presets drop-down, either by typing or pasting. Examples are Sound Hack "Delay Trio / Freesound Bundle" and Blue Cat.
(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 .
(Windows and Linux) Some LADSPA "Blop" plug-ins ( http://blop.sourceforge.net/index.html ) are reported to crash in Audacity on Linux Debian. On Windows, the Blop plug-ins included in http://opensourcepack.blogspot.co.uk/p/ladspa-for-win32.html can also crash, but this can be avoided if you ensure the "blop_files" folder contains the necessary "_data.dll" files for the plug-ins and that this folder is present in the Audacity "Plug-Ins" folder.
(Windows and Mac OS X) The SC4 compressor shipped with Audacity crashes if used in a Chain.
(Windows) If you open a Real-Time Preview (RTP) effect then preview in a built-in effect, the Play/Stop button in the RTP effect will display Stop and cannot be used until you press Play in the main project window.
(Windows) LADSPA Multiband EQ may not be visible in Effect menu (occurs on Windows XP), and crashes soon after opening
Cut Preview only plays the upper track of multiple selected or Sync-Locked tracks.
Nyquist effects render the space between clips as silence. Workarounds: Edit > Clip Boundaries > Detach at Silences (this may also remove parts of the original audio if any of it was totally silent).
"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.
The following effects remove envelope control points: Change Speed/Pitch/Tempo; Equalization; Noise Removal; Sliding Time Scale/Pitch Shift; any Nyquist effect in the Effect menu. Workaround: Use Tracks > Mix and Render to apply the envelope to the waveform before applying the effect.
The Reverse effect retains the control points, but does not move them.
Truncate Silence when run on multiple selected tracks only looks for and truncates "silence" regions which are common to all those tracks. If you want to truncate silence independently for each track it is currently necessary to run the effect on one selected track at a time.
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).
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.
Workaround: Edit > Undo if necessary then drag from outside the selection region or single-click in the clip to remove the selection.
Set Rate in the Audio Track Dropdown Menu does not work correctly when there is a separate clip in the track or when there are envelope points. Clips will cause Set Rate to shorten the audio too much or insert white space into it. Envelope points will not move in response to Set Rate.
Vertical-dragging a clip into a track at a different sample rate where the clip contains a selection that transgresses into another clip will corrupt the project if you drag from within the selection. Playback, export and project saving will be at the wrong position or speed. Workaround: Vertical drag without or outside a selection. If you need to retain the selection when vertical dragging, use Edit > Region Save, remove the selection before drag then Edit > Region Restore. If the problem occurs, Edit > Undo to where playback is correct (dragging the track back where it came from will not resolve the issue).
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 Drop-Down Menu to make two mono tracks into stereo. Workaround: Select over the split line and Edit > Clip Boundaries > Join.
When pasting audio into tracks with envelope points, the envelope points may move in unexpected ways, so causing unwanted amplitude adjustments.
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 FFmpeg 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.
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) 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) 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 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 here.
(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 IDTE (or use Windows Media Player 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 Metadata Editor 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".
ID3 v2.4 tags in imported MP3 files are not seen and will be removed on export.
Audacity writes both ID3 v2.3 (TYER) and v2.4 (TDRC) tags for "Year", but any applications that require the older TYER on its own (without TDRC) will not see "Year" in Audacity-exported files. The id3 command-line application on Linux is one example.
AAC: Artist and Year metadata is not exported or imported due to a bug in FFmpeg 2.2.2.
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.
"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 FFmpeg 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 Extended Import Preferences. 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 reading it directly, 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 Quality Preferences. To fix any files that have already been affected, see this Forum topic.
On a fresh installation of Audacity or initialized Preferences, 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.
(OS X and Linux) In some locales, Preferences text may be truncated or overlapped, or dropdown boxes truncated.
(OS X) The "Cmd - Wheel - Rotate" mouse binding does not zoom in unless you modify the default System Preferences. ** On OS X 10.6 or later, go to Universal Access / Seeing / Zoom / Options and uncheck "Use scroll wheel with modifier keys to zoom".
Prior to OS X 10.6, go to "Mouse and Keyboard" and uncheck "Zoom using scroll ball while holding Command".
(Windows) The "Files Missing" warning always restores maximised windows to smaller size.
(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.
After changing language in Preferences, a few parts of the interface don't change until Audacity is restarted.
Audacity has several weaknesses in preserving the context of the audio being worked with:
If playback scrolls, pressing Stop leaves the waveform where it stopped and the cursor invisible. Pressing Play to resume then scrolls the waveform to start at the left edge, hiding the previously visible context before the cursor position. Workaround: If you had a selection and a special playback command like Cut Preview or Quick-Play caused the waveform to scroll, use or to move the selection back into view.
Current scrolling behaviour makes it too hard to watch the waveform progress, with a single shift of cursor and waveform position when cursor reaches the right edge
Zoom to Selection shows none of the surrounding context
By default, all audio in the project is selected if an action requiring a selection is requested when there is no selection (this behavior can be turned off in the Tracks Preferences). If enabled:
You can always apply effects to the whole project in one step, but you can also delete audio in all tracks if you press Delete when there is no selection. That is easy to Undo, but we aim to tweak this behavior and make it more customizable in a future Audacity.
A few items in Edit menu are incorrectly grayed out if no track is selected.
If Sync-Lock Tracks is enabled, there is no indication of the cursor in the Sync-Locked tracks.
In projects containing an hour or more of total audio, there may be a delay compared to previous versions of Audacity when:
Dragging sample points with Draw Tool
Using Cut, Copy, Paste, Delete or Silence Audio.
The delay may be more evident on slower computers. In addition, label text may not be recovered if there is a crash.
Mouse Bindings are not currently configurable by the user.
Snap-To does not move the cursor when first enabled or when the selection format is changed.
We're aware that some error messages in Audacity are not as helpful as we would like them to be. If you see a cryptic error message from Audacity, try a search (or ask) on https://forum.audacityteam.org/
When using TAB to move into a TimeText control (for example, in a Generator, Change Speed or Selection Toolbar) the first character is highlighted instead of the first non-zero character.
(Linux) If Audacity is left open but without focus, its CPU use will rise slowly until all available system CPU is consumed. This is a bug in wxGTK 2.8.10 (not previous versions) - see http://trac.wxwidgets.org/ticket/11315 . This issue can be fixed by updating to wxGTK 2.8.11 or 2.8.12.
(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.
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.
(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: http://audacityteam.org/forum/viewtopic.php?f=17&t=5064
(Linux) Meters may not respond immediately to playback which could cause them to report incorrect peak level or not display clipping.
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.
On Mac, Audacity may freeze if JACK is launched by QjackCtl then Audacity is launched. Workaround: Use JackPilot to launch JACK, or launch QJackCtrl after Audacity and JACK are running.
(OS X and Linux) PortAudio's default latency values which are used when recording with software playthrough are much lower than Audacity's default "Audio to buffer" setting. This may cause playthrough or recording glitches when recording with software playthrough enabled, especially when using pulse on Linux. Workaround for Linux: record from an (hw) device instead if software playthrough is required.
(OS X) Playback to Bluetooth headsets gives an error. Workaround: Revert to Audacity 1.3.3 (this may only work with stereo headsets), or use Soundflower to send the Audacity output to an audio application that works with the headset.
(OS X) The "Hardware Playthrough" option in Recording Preferences is currently unsupported on all known Mac hardware. Try the "Software Playthrough" preference instead. If that does not work, the third-party LineIn application also provides software playthrough.
(Windows Vista and later) The "Windows WASAPI" host supplies playback, plus a "loopback" device for recording computer playback and as of Audacity 2.1.0, experimental support for physical inputs.
Not everyone will necessarily experience all or any of the issues noted below, but please report any WASAPI issues not covered below to our feedback address.
Although volume slider support for WASAPI is implemented, on some devices the Mixer Toolbar recording volume slider will be grayed out when selecting the Windows WASAPI host. Even if the Audacity recording slider is available, the sound device may not support Audacity adjusting its system playback or recording sliders. To control loopback recording on those systems, try adjusting the playback level of the audio player.
On many other devices, the Audacity recording and playback volume sliders will be "linked" together when loopback recording with playback and recording device set to the same device. Adjusting either slider will often adjust the sound you hear without affecting the achieved recording level, enabling you to record without listening. If "silent" recording does not work, mute the "Device" slider at far left of the Windows "Volume Mixer" or plug in speakers or headphones and turn off their volume.
If the achieved loopback recording level is too low, try turning up the volume in the application playing the audio.
Adjusting linked sliders during loopback recording may cause audio breakup or recording glitches.
Loopback recording may fail "error opening" when Audacity is set to record in mono.
You will normally need to start playing the loopback stream (or to have previously played some other audio in the application you are using for playback) before starting loopback recording in Audacity.
Changing Default Format or Exclusive Mode settings in Windows "Sound" while Audacity is open may cause "error opening" when starting to play or record. Try Transport > Rescan Audio Devices or restarting Audacity.
If you receive dropouts or poor quality when recording, try setting the Audacity to 44100 Hz and setting Default Format in Windows sound to 44100 Hz. Setting the same higher or lower rate in both places may also work.
Physical inputs may fail "error opening", especially when overdub recording. Try setting Audacity project rate to 44100 Hz with Exclusive Mode enabled for the device in Windows Sound for both playback and recording, or set project rate to the same as Windows "Default Format" with Exclusive Mode off.
Latency when overdubbing may substantially increase shortly after starting the recording.
"Audio to buffer" in Recording Preferences cannot be used to adjust recording latency.
Non-looped playback plays the selection minus the "Audio to buffer" (for example, standard playback will fail to play the buffered length at the end of the selection). The buffer setting may be set to zero when using WASAPI host.
(Windows) When a USB device is connected, the Mixer Toolbar input slider for that device (and sometimes for any device) may wrongly appear active even though it has no control over the device's input level. Sometimes the Audacity slider will apply a software gain to the level (which is dangerous as it will only make the same clipped input quieter rather than stopping the clipping). Sometimes the Audacity slider will not affect the input volume at all. Workaround: use the slider in the Windows Control Panel where available, or any gain control on the device, or reduce the output being sent to the device.
(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 Device Toolbar to change the devices as needed, then Audacity will remember them.
(Windows) Audacity is incompatible (or not fully compatible) with some professional sound cards or audio devices, and may crash or have limited or faulty functionality. Occasionally, this may be true of some AC97 devices built into the motherboard. Workaround: make a different sound card your default when using Audacity, but please e-mail the following details to our feedback address:
Your version of Windows and Service Pack
Name, model number and driver version number of the sound card or device.
Note: Multichannel Recording in Audacity is often not possible with professional devices unless you compile Audacity with ASIO support.
Adding or removing an external audio device while Audacity is open will not be automatically reflected in the list in Device Toolbar or Devices Preferences. On Mac, unplugging then replugging an external device will give "error while opening sound device" (on Linux, pressing "Record" a second time will remove the error). Workaround: Use Transport > Rescan Audio Devices.
Calculation of "disk space remains for recording (time)" incorrect when recording in 24 bit quality.
Play-at-Speed slider: Change of playback speed is no longer automatic after you move the play-at-speed slider. To change speed, move the slider, then click the green button to left of the slider to play at the new speed.
Timer Record cannot maintain scheduled duration if system clock changes
(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.
"Register Effects" dialog:
When you use Audacity for the first time, Audacity will scan for supported plug-ins of all types. The Register Effects dialogue lists all LADSPA, VST and Audio Unit (Mac OS X) plug-ins that are detected, with checkboxes to enable each plug-in or not. On Windows and Mac, this first time dialog will list a minimum of hard_limiter_1413 and sc4_1882. Those two plug-ins are shipped with Audacity and you will usually want to enable them. Therefore you should just click OK on the dialog if you have no third-party effects.
VST instruments will appear in the list but are not supported, so will not load even if checkmarked.
The dialog is on top of other windows, so could hide any prompts that VST effects show when effects are loaded after pressing OK. This would be evident by the "loading progress" arrow in the check boxes coming to a halt and the VST dialog losing focus. To continue loading the effects in this case, press ENTER on your keyboard to OK the hidden prompt, or drag the VST dialog away to reveal the prompt then click OK on the prompt.
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.
Projects created by Audacity 1.1.x or earlier are no longer supported. Workaround: Export each project track as WAV using the appropriate legacy version of Audacity, then import the WAV files into current Audacity.
Projects created by Audacity 1.2.x are partially supported - there is a possibility Audacity could corrupt them. Please make a backup copy of the project's .aup file and _data folder to a new folder before opening the project in this version of Audacity. Once you save the project in this version, it cannot be opened in 1.2.
Projects created by previous versions of Audacity may contain audio "block files" longer than the project format allows. Reopening such projects in previous versions might or might not result in deletion of the overlong audio. Audacity has been provisionally fixed so that it can no longer create or delete overlong files, but it cannot read any such files it encounters. If overlong files are found, a "Problems Reading Sequence Tags" message will display .
If you continue with the offered repair then choose "Continue without deleting" in the Orphan Block File(s) dialogue, the overlong files will be retained as "orphans" in the project's _data folder but will appear as silence in the track(s).
As long as you choose "Close project immediately" in the Orphan Block File(s) dialogue, the project will quit and will not be changed in any way.
If you encounter the "Problems Reading Sequence Tags" message, please write to our feedback address with a copy of the .aup file and the log as found at Help > Show Log.
Time Track warp points saved in a 2.0.3 or later project will be preserved if opened in previous Audacity versions, but playback and display will be incorrect.
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 keyboard shortcut alternatives for the buttons instead.
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....
(Windows Vista or later) 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 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 and OS X) Some USB or Firewire recording devices only record silence, or only offer mono recording for a stereo device, or only mono or stereo for a device that previously supported multi-channel recording. Workaround: You can try 1.3.10 Beta or earlier (including 1.2.5/6), but these versions may have other bugs or limitations.
Please report make and model number of devices that exhibit the issue, and your operating system details (for example, Windows 7 Service Pack 1).
(Windows) There may be substantial delays drawing the waveform in longer projects. These include:
opening saved projects that were fitted to the window
fitting an already zoomed in project to the window or zooming in on a fitted project
progress dialog remains white for a long time after the progress bars complete for a file import or effect.
Using the red close button top left of an effect window removes access to the main Audacity window, requiring force quit. See Bug 1318.
Effects
Noise Reduction defaults changed.
Interface
We’ve made several improvements to the spectrogram view of tracks which are particularly valuable for vocal work.
New option ‘Spectral Reassignment’. This algorithm deduces a ‘finer’ spectrogram for vocal work.
Four new Spectrogram scales.
Improvement to the Pitch (EAC) algorithm – cleaner (sharper) display.
Spectrogram Settings are now available per-track.
Other Changes
Upgraded from wxWidgets 2.8.12 to wxWidgets 3.0.2.
Restructuring of the Preferences Menu
Restructuring of the Track Dropdown Menu (for the Spectrograms)
Crashes
Crashes on reading .wav files with many channels (CVE-2016-2540) and corrupt .mp2 files (CVE-2016-2541) have been fixed. Thanks to Chris Navarrete from Fortinet’s FortiGuard Labs for notifying us of these bugs and associated security risk.
Interface
Mac OS X
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 https://bugzilla.audacityteam.org/query.cgi?format=specific or view the complete list of open bugs.
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 https://manual.audacityteam.org/o/man/accessibility.html
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.
Edit Labels Dialog: After closing the labels editor, the editing cursor is always set at the label that was selected when Edit Labels was opened. If you closed the labels editor with some other label selected, you can navigate to that label using TAB or SHIFT + TAB with focus in the label track.
Keyboard Preferences: Window-Eyes doesn't read the key bindings when View by Tree is selected, and may not always read the bindings in other views. VoiceOver and Orca do not read the key bindings at all. You could export the bindings, modify them in a text editor then import the modified list.
Spectral Selection Toolbar:
Typing a 0 (zero) in the High Frequency box when its digits are dashed (undefined) resets existing Low Frequency values to zero. Typing or incrementing digits in either box may require the wanted digit to be typed or incremented twice and may increment digits in the other box. It is usually best to enter the high frequency first and then TAB through both Low and High Frequency boxes to ensure that they contain correct values.
It is not possible to use the keyboard to move the cursor or selection region to an arbitrary position when playing or recording. However you can use the [ or ] shortcuts respectively to set the left or right boundary of the selection at the playback or recording position ( ). The Status Bar messages that you can CTRL + drag to select audio during scrubbing are incorrect.
(Windows) In certain parts of the main window, NVDA does not speak typed characters (JAWS and Window-Eyes are not affected):
Typing numbers into the time controls in Selection Toolbar or Analyze > Contrast...
In the main window, not speaking a character if it is a command for example, j,k,[ or ]
(OS X) Audacity is not Retina-ready. If is applied to Audacity as a workaround, the export format cannot be changed.
(OS X) COMMAND + F6 and SHIFT + COMMAND + F6 may not cycle correctly between tracks and tooldock areas, especially on El Capitan and with VoiceOver off. Focus may get trapped in Project Rate unless a mouse click first places focus elsewhere in Selection Toolbar. Using the cycle shortcut for the opposite direction can sometimes escape out of trappage.
(OS X and Linux) Focus can get trapped in dialogues when using ALT + F6 or ALT + SHIFT + F6 to move between modeless windows and the main project window. If you want both Plot Spectrum and Contrast open you can avoid getting trapped on Linux by opening Plot Spectrum before Contrast.
(OS X) It is not possible to TAB through Keyboard Preferences.
(OS X) It is not possible to move through docked toolbars using the ALT + F6 or ALT + SHIFT + F6 shortcuts.
(OS X) It is not possible to move between the main Audacity window and some VST and Audio Unit effects using the ALT + F6 or ALT + SHIFT + F6 shortcuts when the effect is in Graphical Mode. You can use the "Manage" menu then Options... to change the effect to textual mode.
(OS X) The Timeline text numbers are very large, but the text labels or dropdown contents in Selection Toolbar and Spectral Selection Toolbar are small and hard to read.
(OS X) Issues with VoiceOver:
(reported on OS X 10.9.x) After exporting, the black accessibility area is trapped in the Tooldock area, so there is no way to read the tracks. Workaround: Save as a project, close the project then reopen it. You can then navigate the tracks with VoiceOver.
If you use arrow keys to navigate the Timetext controls in Selection Toolbar, VoiceOver stops reading. Workaround: Use Control-Option-W
(Linux Ubuntu) Under Unity, keyboard shortcuts are not visible in the Audacity menus. Keyboard shortcuts are visible if you install the classic interface or under Unity if you open Audacity from the termimal with
env UBUNTU_MENUPROXY=0 audacity
Audacity will now ship with src/audacity.desktop.in set to UBUNTU_MENUPROXY=0 so Audacity compiled from source will show shortcuts in the menus and will have its own menu bar in the application. It will remain up to Ubuntu whether they use this desktop file in packaged versions of Audacity.
TAB unexpectedly navigates out of the current tooldock area instead of staying inside it, and CTRL + F6 from Selection Toolbar and SHIFT + CTRL + F6 from the Tracks table do not navigate to the upper tooldock area but leave focus in the previous toolbar. However you can use the TAB navigation behavior described above to access the upper tooldock area.
(Linux) Issues with Orca:
Audacity tracks are not read.
Not all toolbar controls are read, examples being Timetext controls, Project Rate and controls in Device Toolbar.
Not all controls in Preferences are read.
Unfortunately, Audacity 2.1.2 is not accessible for users of VoiceOver, and this was also the case for the Audacity 2.1.1 release. However, an accessible version of Audacity 2.1.1 is available on our Mac OS X downloads page. The name of this accessible version is "2.1.1-screen-reader" (DMG and ZIP downloads are available). It is hoped that future versions of Audacity will be accessible for users of VoiceOver.
(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. 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)
(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) Some devices that used to offer multiple recording channels in Audacity without ASIO may now only offer mono or stereo recording instead of the expected number of channels. Usually the multi or similar device only has 2 channels instead of the expected number. Occasionally the multi device is missing, leaving only two-channel devices to choose from. These devices have been reported:
Alesis Multimix-8 USB
DSP2000-CPort
M-Audio Delta 66
Motu 896 AD/DA FW
Tascam US 1641 and US 1800
If you experience this issue please report make and model number of the device, your operating system (for example, Windows 7 Service Pack 1) and the device driver version number you are using. It is possible that more than stereo recording may be possible if you can find earlier drivers that are still compatible with your version of Windows, or if you try the Windows WASAPI host in . See for a list of devices reported to record multi-channels into Audacity without ASIO.
(Windows) There may be substantial delays drawing the waveform in longer projects of an hour or more. The main problems are with opening saved projects that were fitted to the window, and fitting already zoomed in projects to the window, such as a new recording. Additionally, import or effect progress dialogs may stall "whited out" for a few seconds after the progress bars complete before the waveform is drawn.
Audacity's built-in generators don't yet work with Chains. Plugin 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.
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.
Noise Reduction" does not yet support storing its parameters in a Chain. Noise Reduction will run at its last used settings if used in a Chain.
(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).
Dynamic loading (as in default Audacity ./configure) requires building against the FFmpeg project - it will not build against the libav* headers from the libav project. Workarounds: Configure Audacity with --disable-dynamic-loading. If dynamic loading is required, build against FFmpeg instead of libav, or you can build against libav if you remove the "#define IS_FFMPEG_PROJECT 1" line in src/FFmpeg.h.
Audacity may still build against no-longer-supported FFmpeg versions (such as FFmpeg 0.8 which is system-installed on Debian Wheezy), but configuring with --disable-dynamic-loading will be necessary. FFmpeg 0.8 has at least one known issue in Audacity 2.0.6 or later: mono WMA files export with no audio data. This issue will not be fixed given FFmpeg 0.8 is no longer supported by Audacity 2.0.6.
Building against self-compiled FFmpeg 2.2.2 with --disable-dynamic-loading the only argument fails on Ubuntu 13.10 with "undefined reference to 'av_codec_is_encoder'". Workaround: Configuring with --disable-dynamic-loading and --with-lib-preference="local" (or at least --with-ffmpeg="local") may build successfully, but may not disable Libraries Preferences. The best solution may be not to disable dynamic loading.
"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.
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.
When you import a preset into an Apple Audio Unit, that preset's settings are applied by the effect without the effect controls updating to the new settings. Other AU effects may ignore presets when you import them. To be sure the imported preset you want to use is loaded into the effect, select it from "User Presets".
(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.
(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.
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).
(Windows) Installing the latest 1.7.1 "Queen Mary" Vamp plugins to any of the supported locations 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 https://code.soundsoftware.ac.uk/projects/qm-vamp-plugins/files instead.
(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 graphical mode the controls of many plug-ins do not visibly respond when loading a preset file from the "Load" button. The new settings are however loaded internally, will apply when running the effect and will be visible if you reopen the effect after running it. Controls do respond to loading a preset file if you turn off graphical mode.
(Windows)
Playing audio while Ambience VST plug-in is open (including previewing any non-real-time preview effect) causes Audacity to crash.
Amplio 2 is likely to crash after being enabled at Add / Remove Plugins or when previewing the effect in real-time. If enabling Amplio2 crashes, try enabling it again. Then make sure audio is not playing, open Amplio2 and press "Apply", without pressing the Play button in the effect.
Audiocation Phase crashes if closed and reopened.
(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).
Workaround: If Audio Units are not needed in Audacity, restart Audacity then open Audacity > Preferences and choose "Effect". Under "Enable Effects", uncheck "Audio Unit", press OK and restart Audacity. Alternatively, look in the Mac Crash Report for the AU plug-in that crashed, move it from <Your Home>/Library/Audio/Plug-Ins/Components or /Library/Audio/Plug-Ins/Components then restart Audacity. See this page for more help.
(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.
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 all those tracks. If you want to truncate silence independently for each track it is currently necessary to run the effect on one selected track at a time.
(Linux) On Ubuntu with the Unity interface enabled in audacity.desktop, previewing a built-in or Nyquist effect or generator in one project then opening the same effect or generator in another project will cause a crash. There may sometimes be a crash if opening any built-in or Nyquist effect or generator in another project when such an effect is already previewing.
(Linux) Sliding Time Scale / Pitch Shift may crash randomly in Audacity built with pre-2.0.2 versions of libsbsms. This may occur for example in the Ubuntu package of Audacity 2.0.5 on Ubuntu 14.04. Workaround: Build Audacity configured --with-sbsms="local", or use the Audacity package in Ubuntu 14.10 which uses libsbsms 2.0.2-1.
(Windows and Linux) Some LADSPA "Blop" plug-ins ( ) are reported to crash in Audacity on Linux Debian. On Windows, the Blop plug-ins included in can also crash, but this can be avoided if you ensure the "blop_files" folder contains the necessary "_data.dll" files for the plug-ins and that this folder is present in the Audacity "Plug-Ins" folder.
(Windows and Mac OS X) The SC4 compressor shipped with Audacity crashes if used in a Chain.
(Windows) LADSPA Multiband EQ may not be visible in Effect menu (occurs on Windows XP), and crashes soon after opening
Cut Preview only plays the upper track of multiple selected or Sync-Locked tracks.
Nyquist effects render the space between clips as silence. Workarounds: Edit > Clip Boundaries > Detach at Silences (this may also remove parts of the original audio if any of it was totally silent).
The following effects remove envelope control points: Change Speed/Pitch/Tempo; Equalization; Noise Removal; Sliding Time Scale/Pitch Shift; any Nyquist effect in the Effect menu. Workaround: Use Tracks > Mix and Render to apply the envelope to the waveform before applying the effect.
The Reverse effect retains the control points, but does not move them.
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).
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
faint, specious clip lines could occur if the clip is dragged back to its original track.
Workaround: Edit > Undo if necessary then drag from outside the selection region or single-click in the clip to remove the selection.
If audio is created at other than time zero, a selection made in that clip could include the sample before the first selected sample but exclude the last 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.
Set Rate in the Audio Track Dropdown Menu does not work correctly when there is a separate clip in the track or when there are envelope points. Clips will cause Set Rate to shorten the audio too much or insert white space into it. Envelope points will not move in response to Set Rate.
Vertical-dragging a clip into a track at a different sample rate where the clip contains a selection that transgresses into another clip will corrupt the project if you drag from within the selection. Playback, export and project saving will be at the wrong position or speed. Workaround: Vertical drag without or outside a selection. If you need to retain the selection when vertical dragging, use Edit > Region Save, remove the selection before drag then Edit > Region Restore. If the problem occurs, Edit > Undo to where playback is correct (dragging the track back where it came from will not resolve the issue).
often do not appear when snapping to Split Lines created with enabled at hh:mm:ss + milliseconds or higher resolution. You could label the split lines or turn Snap To off to see the guides.
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 Drop-Down Menu to make two mono tracks into stereo. Workaround: Select over the split line and Edit > Clip Boundaries > Join.
When pasting audio into tracks with envelope points, the envelope points may move in unexpected ways, so causing unwanted amplitude adjustments.
When exporting or rendering a longer mix and one or more tracks are much shorter than the others, the progress bar will appear to show no progress and "remaining time" will increase continually. However the mix or export will complete normally in reasonable time if you wait for the progress dialogue to close.
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: 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.
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.
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.
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.
(Mac OS X) When exporting using Custom FFmpeg Export, you must agree to create and replace an unwanted "NoOverwritePrompt" file before you can export. The exported audio file is correct.
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.
(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 download site 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.
Audacity crashes after quit if quit from the Task Manager (Windows) or Taskbar (Linux) while "About Audacity" is open. Audacity always crashes after quit if quit from the Dock on Mac OS X. On Linux, any quit by any method produces "OS_IS_BAR (bar)" and "GTK_IS_WIDGET" (widget) assertion errors in the terminal if Audacity is launched from there. Any unsaved audio is saved correctly before the 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.
(Mac OS X) When zooming in to maximum level (or close to maximum) in tracks exceeding about 6 minutes in length, the view position might move. This might un-center or remove the cursor from view, or cause the COMMAND + [ or COMMAND + ] shortcuts to not center or display the selection edge.
(OS X Yosemite or later) 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 /Applications/Utilities/Console.app.
(OS X and Linux) In some locales, Preferences text may be truncated or overlapped, or dropdown boxes truncated.
(OS X) The "Window" menu is not currently available.
(OS X) If the Audacity window buttons get trapped under the menu bar, there is no way to minimize Audacity because the COMMAND + M / COMMAND + OPTION + M shortcuts do not currently work. You can use COMMAND + H to hide Audacity instead.
(OS X) In projects that have a vertical scrollbar you cannot mouse-drag a track up or down beyond the visible vertical area because the drag does not vertically scroll the project. You can drag the vertical scrollbar then drag the track again, or use the to move the track.
(OS X) Period must be used as the decimal separator in effects even when the system language is French, German or other language that specifies comma separator.
(OS X) The "Cmd - Wheel - Rotate" mouse binding does not zoom in unless you modify the default System Preferences. ** On OS X 10.6 or later, go to Universal Access / Seeing / Zoom / Options and uncheck "Use scroll wheel with modifier keys to zoom".
Prior to OS X 10.6, go to "Mouse and Keyboard" and uncheck "Zoom using scroll ball while holding Command".
(Windows) The "Files Missing" warning always restores maximised windows to smaller size.
After changing language in Preferences, a few parts of the interface don't change until Audacity is restarted.
Audacity has several weaknesses in preserving the context of the audio being worked with:
If playback scrolls, pressing Stop leaves the waveform where it stopped and the cursor invisible. Pressing Play to resume then scrolls the waveform to start at the left edge, hiding the previously visible context before the cursor position. Workaround: If you had a selection and a special playback command like Cut Preview or Quick-Play caused the waveform to scroll, use View > Go to Selection Start or View > Go to Selection End to move the selection back into view.
Current scrolling behaviour makes it too hard to watch the waveform progress, with a single shift of cursor and waveform position when cursor reaches the right edge
By default, all audio in the project is selected if an action requiring a selection is requested when there is no selection (this behavior can be turned off in the Tracks Preferences). If enabled:
You can always apply effects to the whole project in one step, but you can also delete audio in all tracks if you press Delete when there is no selection. That is easy to Undo, but we aim to tweak this behavior and make it more customizable in a future Audacity.
A few items in Edit menu are incorrectly grayed out if no track is selected.
If Sync-Lock Tracks is enabled, there is no indication of the cursor in the Sync-Locked tracks.
Mouse Bindings are not currently configurable by the user.
Snap-To does not move the cursor when first enabled or when the selection format is changed.
We're aware that some error messages in Audacity are not as helpful as we would like them to be. If you see a cryptic error message from Audacity, try a search (or ask) on
When using TAB to move into a TimeText control (for example, in a Generator, Change Speed or Selection Toolbar) the first character is highlighted instead of the first non-zero character.
While in Pause mode, editing and effects functions are not available while playback is paused, nor is Save or Export. You must press the Stop button for these commands to become available.
(Linux) If Audacity is left open but without focus, its CPU use will rise slowly until all available system CPU is consumed. This is a bug in wxGTK 2.8.10 (not previous versions) - see . This issue can be fixed by updating to wxGTK 2.8.11 or 2.8.12.
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 http://trac.wxwidgets.org/changeset/62397?format=diff&new=62397, 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).
(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.
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.
(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.
Export multiple by labels may add unwanted silence to exported files if multiple tracks are present that don't all start at time zero. You can workaround this by using Edit > Select > All then Tracks > Mix and Render to render the audio to one track, or by generating a short amount of silence at the start of each track that is offset from zero.
(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".
(Linux) If system locale is set to Valencian and Audacity language in Interface Preferences is set to "System", Audacity will be in Catalan. You can change to Valencian language in Interface Preferences.
(OS X) Audacity set to "System" language in Interface Preferences as in a new installation or after preferences reset will always be in English language irrespective of the Mac system locale. Workaround: Follow the steps at https://manual.audacityteam.org/o/man/faq_about_audacity.html#language to change the Audacity language in Interface Preferences.
(Windows) Audacity must be explicitly set to use Galician or Valencian in Interface Preferences to display those languages. Setting the Windows Region and Language format to Galician or Valencian and Audacity to "System" language will only display Audacity in English.
(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: http://audacityteam.org/forum/viewtopic.php?f=17&t=5064
(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. More help with this can be found here.
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.
(Linux) Meters may not respond immediately to playback which could cause them to report incorrect peak level or not display clipping.
(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.
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 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 .
For problems that occur when reopening or working in a project, the log file at Help > Show Log....
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. 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/ (~/Library/Logs/DiagnosticReports on Mavericks).
(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.
(OS X and Linux) PortAudio's default latency values which are used when recording with software playthrough are much lower than Audacity's default "Audio to buffer" setting. This may cause playthrough or recording glitches when recording with software playthrough enabled, especially when using pulse on Linux. Workaround for Linux: record from an (hw) device instead if software playthrough is required.
(OS X) Playback to Bluetooth headsets gives an error. Workaround: Revert to Audacity 1.3.3 (this may only work with stereo headsets), or use to send the Audacity output to an audio application that works with the headset.
(OS X) The "Hardware Playthrough" option in Recording Preferences is currently unsupported on all known Mac hardware. Try the "Software Playthrough" preference instead. If that does not work, the third-party application also provides software playthrough.
(Windows) When a USB device is connected, the Mixer Toolbar input slider for that device (and sometimes for any device) may wrongly appear active even though it has no control over the device's input level. Sometimes the Audacity slider will apply a software gain to the level (which is dangerous as it will only make the same clipped input quieter rather than stopping the clipping). Sometimes the Audacity slider will not affect the input volume at all. Workaround: use the slider in the Windows Control Panel where available, or any gain control on the device, or reduce the output being sent to the device.
(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.
(Windows) Audacity is incompatible (or not fully compatible) with some professional sound cards or audio devices, and may crash or have limited or faulty functionality. Occasionally, this may be true of some AC97 devices built into the motherboard. Workaround: make a different sound card your default when using Audacity, but please e-mail the following details to our :
Your version of Windows and Service Pack
Name, model number and driver version number of the sound card or device.
Note: Multichannel Recording in Audacity is often not possible with professional devices unless you compile Audacity with ASIO support.
Adding or removing an external audio device while Audacity is open will not be automatically reflected in the list in Device Toolbar or Devices Preferences. On Mac, unplugging then replugging an external device will give "error while opening sound device" (on Linux, pressing "Record" a second time will remove the error). Workaround: Use Transport > Rescan Audio Devices.
Calculation of "disk space remains for recording (time)" incorrect when recording in 24 bit quality.
Play-at-Speed slider: Change of playback speed is no longer automatic after you move the play-at-speed slider. To change speed, move the slider, then click the green button to left of the slider to play at the new speed.
Timer Record cannot maintain scheduled duration if system clock changes
(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.
(Windows Vista and later) The "Windows WASAPI" host supplies playback, plus a "loopback" device for and experimental support for physical inputs.
Not everyone will necessarily experience all or any of the issues noted below, but please report any WASAPI issues not covered below to .
Although volume slider support for WASAPI is implemented, on some devices the Mixer Toolbar recording volume slider will be grayed out when selecting the Windows WASAPI host. Even if the Audacity recording slider is available, the sound device may not support Audacity adjusting its system playback or recording sliders. To control loopback recording on those systems, try adjusting the playback level of the audio player.
(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.
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.
(OS X) If Audacity crashes in a project that has not yet been saved, you must recover the project before restarting the computer because the default Audacity temporary directory is cleared out when the computer restarts. You can change the default temporary directory at Audacity > Preferences: "Directories" section.
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.
Projects created by Audacity 1.1.x or earlier are no longer supported. Workaround: Export each project track as WAV using the appropriate legacy version of Audacity, then import the WAV files into current Audacity.
Projects created by Audacity 1.2.x are partially supported - there is a possibility Audacity could corrupt them. Please make a backup copy of the project's .aup file and _data folder to a new folder before opening the project in this version of Audacity. Once you save the project in this version, it cannot be opened in 1.2.
Projects created by previous versions of Audacity may contain audio "block files" longer than the project format allows. Reopening such projects in previous versions might or might not result in deletion of the overlong audio. Audacity has been provisionally fixed so that it can no longer create or delete overlong files, but it cannot read any such files it encounters. If overlong files are found, a "Problems Reading Sequence Tags" message will display .
If you continue with the offered repair then choose "Continue without deleting" in the Orphan Block File(s) dialogue, the overlong files will be retained as "orphans" in the project's _data folder but will appear as silence in the track(s).
As long as you choose "Close project immediately" in the Orphan Block File(s) dialogue, the project will quit and will not be changed in any way.
If you encounter the "Problems Reading Sequence Tags" message, please write to our with a copy of the .aup file and the log as found at Help > Show Log.
Time Track warp points saved in a 2.0.3 or later project will be preserved if opened in previous Audacity versions, but playback and display will be incorrect.
In order to forwards scroll-scrub at normal 1x speed without using the scroll wheel it is always necessary to move the mouse to the end of the window, even if the project is shorter than the window width. However if you try to forwards scroll-scrub in a less than half-width project by reducing the backwards-only speed, moving the pointer to the end of the window will not achieve 1x speed - it will be necessary to advance the scroll wheel once the pointer is at the end of the window. Enabling "scrolling left of zero" in Tracks Preferences may be more convenient if you scroll scrub with short tracks.
There is no button or menu command yet to enter Scrubbing and Seeking, only the CTRL (COMMAND on Mac) with left-click or double-left-click gesture.
When you hold CTRL (COMMAND on Mac) then left-click to start scrub or left-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.
While scrubbing if you click on any of the tools in the Tools toolbar, apart from the already active Select tool, then scrubbing will stop.
Frequency range cannot be changed in the session for scales other than "Linear". This applies to both the track's "Spectrograms Settings" amd to Spectrograms Preferences. Workaround: Restart Audacity after changing frequency for non-linear scales.
A Spectral Selection created in Spectrogram view currently only works with the three specific spectral edit effects. 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.
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.
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.
(Linux with XFCE desktop) Toolbars are not tall enough when undocked. Single height toolbars are reduced to an unmanageably small height. Resizeable toolbars, such as meter toolbars, may be restored to the desired height if you can see the resize handle bottom right.
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 keyboard shortcut alternatives for the buttons instead.
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.
The Noise Reduction "Frequency smoothing" default has been increased to 3 to help avoid metallic artifacts. Resetting Preferences or deleting audacity.cfg will set the new default.
(Windows) The location of Audacity's work-in-progress folder has been changed, to avoid problems where certain disk cleaners treated them as deletable temporary files.
When you TAB forwards from "Audio Position" in Selection Toolbar, the "Selection End" or "Selection Length" radio button is read as "Selection Start". When you use COMMAND + F6 or COMMAND + SHIFT + F6 to move directly into "Selection End" from another toolbar, the button is read as "Selection Start".
Mixer Toolbar input/output sliders are not read, but just described as "multiple indicators". The "Graphic EQ" and vertical sliders in Equalization *are* read.
Metadata Editor table not read.
Edit Labels dialog not read.
In the "Edit Chains" window, only the first command in the "Chain" list is read, and it is only read when first accessed. In the "Select Command" window for inserting a new command in a Chain, commands in the table are not read.
"Manage Curves" table in Equalization not read.
Control labels for Vamp and VST plugins are not read.
Control labels for Nyquist plugins are read inconsistently in older version 3 or earlier plugins (Version 4 seems to read more consistently).
DISTRHO Mini Series VST's from http://distrho.sourceforge.net/plugins.php crash Audacity in graphic mode but will run in text mode (open the Effects Preferences and uncheck "Display VST effects in graphical mode").
MDA Tracker may crash if the effect is applied while playing audio. For all the MDA VST's, the sliders have no effect and only the default effect settings can be applied.
Waves v5 may cause Audacity to hang if you select it in the "Register Effects" dialog then click OK.
Digitech RP250 (effects pedal)
MNoiseGenerator AU and others in MFreeEffectsBundle crash if you preview them
Native Instruments B4 and Native Instruments Guitar Rig v3 and v4 (v5 does not have this issue)
PredatorFX
Waves Version 7 and 8 AU: These effects may crash Audacity on quit, after project data has been saved. Waves Version 9 AU should now work correctly.
ID3 v2.4 tags in imported MP3 files are not seen and will be removed on export.
Audacity writes both ID3 v2.3 (TYER) and v2.4 (TDRC) tags for "Year", but any applications that require the older TYER on its own (without TDRC) will not see "Year" in Audacity-exported files. The id3 command-line application on Linux is one example.
Zoom to Selection shows none of the surrounding context
On Mac, Audacity may freeze if JACK is launched by QjackCtl then Audacity is launched. Workaround: Use JackPilot to launch JACK, or launch QJackCtrl after Audacity and JACK are running.
If the achieved loopback recording level is too low, try turning up the volume in the application playing the audio.
Adjusting linked sliders during loopback recording may cause audio breakup or recording glitches.
Loopback recording may fail "error opening" when Audacity is set to record in mono.
You will normally need to start playing the loopback stream (or to have previously played some other audio in the application you are using for playback) before starting loopback recording in Audacity.
Changing Default Format or Exclusive Mode settings in Windows Sound while Audacity is open may cause "error opening" when starting to play or record. Try Transport > Rescan Audio Devices or restarting Audacity.
If you receive dropouts or poor quality when recording, try setting the Audacity Project Rate to 44100 Hz and setting Default Format in Windows Sound to 44100 Hz, with both "Exclusive Mode" boxes unchecked. Other rates may work, providing the same rate is set in both places. The most likely place for a dropout is within the first second or two of recording.
Physical inputs may fail "error opening", especially when overdub recording. Try setting Audacity project rate to 44100 Hz then for both the playback and the recording device in Windows Sound, ensure both "Exclusive Mode" are checked (enabled). You can also try setting Audacity Project Rate to the same as Windows "Default Format" with both Exclusive Mode boxes unchecked.
Latency when overdubbing may substantially increase shortly after starting the recording.
"Audio to buffer" in Recording Preferences cannot be used to adjust recording latency.
Non-looped playback plays the selection minus the "Audio to buffer" (for example, standard playback will fail to play the buffered length at the end of the selection). The buffer setting may be set to zero when using WASAPI host.
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.
Can now add/remove effects from Generate and Effects menus.
New version of Vocal Removal Effect.
Classic Filters now included as an opt-in effect.
Interface
Much faster editing with larger projects, thanks to a faster method for storing the autosave recovery file.
Performance improvements for Draw Tool and zooming of Spectrogram views.
Zero-padding Spectrograms Preference smooths the image for short window sizes.
Other Changes
Upgraded to Nyquist 3.0.9 and libflac 1.3.1.
Upgraded LV2 libs, LV2 GUIs on Linux, LV2 factory Presets.
Crash report integration.
Crashes
Crash using Undo while dragging sample points
Crash using File > Close on project window when Screenshot Tools was open.
FFmpeg Custom Export: Crashes importing presets.
(OS X) Crash closing Track Gain or Pan adjustment box.
(OS X) Crash closing project window between save project dialogues
(Linux) TAL VST (but not other VST's) crashed if previewing built-in effect
(Linux) SPACE could not be used/could crash in context menus that have a checkbox.
Interface
LV2 effects did not use parameters when using Chains.
Built in Generators were not usable in Chains.
Plot Spectrum could not change values without losing focus.
Mac OS X
Confusing behaviour importing / exporting AU presets. In particular, Apple Audio Units silently applied an imported preset.
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 https://manual.audacityteam.org/o/man/accessibility.html
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.
Spectral Selection Toolbar:
This toolbar is tied to the project rate so it does not accept entered frequencies above half the project rate even if those frequencies are valid for a track that is at a higher rate.
It is not possible to enter an undefined frequency into this toolbar using the keyboard, and thus not currently possible to run a high pass or low pass filter on the spectral selection using Spectral edit multi tool. A high or low shelving filer may be applied to the spectral selection using Spectral edit shelves.
Typing a 0 (zero) in the High Frequency box when its digits are dashed (undefined) resets existing Low Frequency values to zero. Typing or incrementing digits in either box may require the wanted digit to be typed or incremented twice and may increment digits in the other box. It is usually best to enter the high frequency first and then TAB through both Low and High Frequency boxes to ensure that they contain correct values.
Analyze > Contrast: Once you use ALT + F6 or ALT + SHIFT + F6 to switch focus from this dialog, you can't return to it using the keyboard. You can switch to and from Contrast on Mac OS X by using the Window Menu.
It is not possible to use the keyboard to move the cursor or selection region to an arbitrary position when playing or recording. However you can use the [ or ] shortcuts respectively to set the left or right boundary of the selection at the playback or recording position ( ). The Status Bar messages that you can CTRL + drag to select audio during scrubbing are incorrect.
Keyboard Preferences: Window-Eyes doesn't read the key bindings when View by Tree is selected, and may not always read the bindings in other views.
(OS X) Audacity is not Retina-ready. If is applied to Audacity as a workaround, the export format cannot be changed.
(OS X) It is not possible to TAB through Keyboard Preferences.
(OS X) It is not possible to move through docked toolbars using the ALT + F6 or ALT + SHIFT + F6 shortcuts.
(OS X) It is not possible to move between the main Audacity window and some VST and Audio Unit effects using the ALT + F6 or ALT + SHIFT + F6 shortcuts when the effect is in Graphical Mode. You can use the "Manage" menu then Options... to change the effect to textual mode.
(OS X) Issues with VoiceOver:
(reported on OS X 10.9.x) After exporting, the black accessibility area is trapped in the Tooldock area, so there is no way to read the tracks. Workaround: Save as a project, close the project then reopen it. You can then navigate the tracks with VoiceOver.
If you use arrow keys to navigate the Timetext controls in Selection Toolbar, VoiceOver stops reading. Workaround: Use Control-Option-W
(Linux Ubuntu) Under Unity, keyboard shortcuts are not visible in the Audacity menus. Keyboard shortcuts are visible if you install the classic interface or under Unity if you open Audacity from the termimal with
env UBUNTU_MENUPROXY=0 audacity
Audacity will now ship with src/audacity.desktop.in set to UBUNTU_MENUPROXY=0 so Audacity compiled from source will show shortcuts in the menus and will have its own menu bar in the application. It will remain up to Ubuntu whether they use this desktop file in packaged versions of Audacity.
(Linux) SPACE cannot be used to change context menu items (such as Selection Format in the context menu of TimeText digits, or Mono/Left/Right and Set Rate and Set Sample Format in the Audio Track DropDown Menu). Workaround: Use ENTER instead of SPACE.
(Linux) Issues with Orca:
Audacity tracks are not read.
Not all toolbar controls are read, examples being Timetext controls, Project Rate and controls in Device Toolbar.
Not all controls in Preferences are read.
(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. 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)
(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 and OS X) Some USB or Firewire recording devices only record silence, or only offer mono recording for a stereo device, or only mono or stereo for a device that previously supported multi-channel recording. Workaround: You can try 1.3.10 Beta or earlier (including 1.2.5/6), but these versions may have other bugs or limitations.
Please report make and model number of devices that exhibit the issue, and your operating system details (for example, Windows 7 Service Pack 1).
(Windows) There may be substantial delays drawing the waveform in longer projects of an hour or more. The main problems are with opening saved projects that were fitted to the window, and fitting already zoomed in projects to the window, such as a new recording. Additionally, import or effect progress dialogs may stall "whited out" for a few seconds after the progress bars complete before the waveform is drawn.
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.
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.
Noise Reduction" does not yet support storing its parameters in a Chain. Noise Reduction will run at its last used settings if used in a Chain.
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).
Dynamic loading (as in default Audacity ./configure) requires building against the FFmpeg project - it will not build against the libav* headers from the libav project. Workarounds: Configure Audacity with --disable-dynamic-loading. If dynamic loading is required, build against FFmpeg instead of libav, or you can build against libav if you remove the "#define IS_FFMPEG_PROJECT 1" line in src/FFmpeg.h.
Audacity may still build against no-longer-supported FFmpeg versions (such as FFmpeg 0.8 which is system-installed on Debian Wheezy), but configuring with --disable-dynamic-loading will be necessary. FFmpeg 0.8 has at least one known issue in Audacity 2.0.6 or later: mono WMA files export with no audio data. This issue will not be fixed given FFmpeg 0.8 is no longer supported by Audacity 2.0.6.
Building against self-compiled FFmpeg 2.2.2 with --disable-dynamic-loading the only argument fails on Ubuntu 13.10 with "undefined reference to 'av_codec_is_encoder'". Workaround: Configuring with --disable-dynamic-loading and --with-lib-preference="local" (or at least --with-ffmpeg="local") may build successfully, but may not disable Libraries Preferences. The best solution may be not to disable dynamic loading.
"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.
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.
When you import a preset into an Apple Audio Unit, that preset's settings are applied by the effect without the effect controls updating to the new settings. Other AU effects may ignore presets when you import them. To be sure the imported preset you want to use is loaded into the effect, select it from "User Presets".
(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.
(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.
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).
Input cannot be made using the text boxes. Use the slider instead to adjust values.
(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 graphical mode the controls of many plug-ins do not visibly respond when loading a preset file from the "Load" button. The new settings are however loaded internally, will apply when running the effect and will be visible if you reopen the effect after running it. Controls do respond to loading a preset file if you turn off graphical mode.
(Windows)
DFX Geometer from may crash Audacity when loading the effect from the Effect Menu. This usually happens only once or twice when the effect is first loaded in the operating system session. Once the effect is open in Audacity it should work properly.
DISTRHO Mini Series VST's from crash Audacity in graphic mode but will run in text mode (open the Effects Preferences and uncheck "Display VST effects in graphical mode").
(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).
Workaround: If Audio Units are not needed in Audacity, restart Audacity then open Audacity > Preferences and choose "Effect". Under "Enable Effects", uncheck "Audio Unit", press OK and restart Audacity. Alternatively, look in the Mac Crash Report for the AU plug-in that crashed, move it from <Your Home>/Library/Audio/Plug-Ins/Components or /Library/Audio/Plug-Ins/Components then restart Audacity. See this page for more help.
(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.
Equalization does not retain settings, so always opens with a "flat" curve. Nether the last used settings or user presets are retained. Workaround: To retain the current settings:
Click the "Save / Manage Curves..." button
Select the "unnamed" item
Click the "Rename" button
Type a name for the curve
Click the "OK" button. If the name already exists, click "Yes" to overwrite or "No" to enter a new name.
Click the "OK" button.
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 all those tracks. If you want to truncate silence independently for each track it is currently necessary to run the effect on one selected track at a time.
(Linux) On Ubuntu with the Unity interface enabled in audacity.desktop, previewing a built-in or Nyquist effect or generator in one project then opening the same effect or generator in another project will cause a crash. There may sometimes be a crash if opening any built-in or Nyquist effect or generator in another project when such an effect is already previewing.
(Linux) Sliding Time Scale / Pitch Shift may crash randomly in Audacity built with pre-2.0.2 versions of libsbsms. This may occur for example in the Ubuntu package of Audacity 2.0.5 on Ubuntu 14.04. Workaround: Build Audacity configured --with-sbsms="local", or use the Audacity package in Ubuntu 14.10 which uses libsbsms 2.0.2-1.
(Windows and Linux) Some LADSPA "Blop" plug-ins ( ) are reported to crash in Audacity on Linux Debian. On Windows, the Blop plug-ins included in can also crash, but this can be avoided if you ensure the "blop_files" folder contains the necessary "_data.dll" files for the plug-ins and that this folder is present in the Audacity "Plug-Ins" folder.
(Windows and Mac OS X) The SC4 compressor shipped with Audacity crashes if used in a Chain.
(Windows) If you open a Real-Time Preview (RTP) effect then preview in a built-in effect, the Play/Stop button in the RTP effect will display Stop and cannot be used until you press Play in the main project window.
(Windows) LADSPA Multiband EQ may not be visible in Effect menu (occurs on Windows XP), and crashes soon after opening
Cut Preview only plays the upper track of multiple selected or Sync-Locked tracks.
Nyquist effects render the space between clips as silence. Workarounds: Edit > Clip Boundaries > Detach at Silences (this may also remove parts of the original audio if any of it was totally silent).
The following effects remove envelope control points: Change Speed/Pitch/Tempo; Equalization; Noise Removal; Sliding Time Scale/Pitch Shift; any Nyquist effect in the Effect menu. Workaround: Use Tracks > Mix and Render to apply the envelope to the waveform before applying the effect.
The Reverse effect retains the control points, but does not move them.
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).
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
faint, specious clip lines could occur if the clip is dragged back to its original track.
Workaround: Edit > Undo if necessary then drag from outside the selection region or single-click in the clip to remove the selection.
Set Rate in the Audio Track Dropdown Menu does not work correctly when there is a separate clip in the track or when there are envelope points. Clips will cause Set Rate to shorten the audio too much or insert white space into it. Envelope points will not move in response to Set Rate.
Vertical-dragging a clip into a track at a different sample rate where the clip contains a selection that transgresses into another clip will corrupt the project if you drag from within the selection. Playback, export and project saving will be at the wrong position or speed. Workaround: Vertical drag without or outside a selection. If you need to retain the selection when vertical dragging, use Edit > Region Save, remove the selection before drag then Edit > Region Restore. If the problem occurs, Edit > Undo to where playback is correct (dragging the track back where it came from will not resolve the issue).
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 Drop-Down Menu to make two mono tracks into stereo. Workaround: Select over the split line and Edit > Clip Boundaries > Join.
When pasting audio into tracks with envelope points, the envelope points may move in unexpected ways, so causing unwanted amplitude adjustments.
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: 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.
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.
(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.
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.
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) 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.
(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.
"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.
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.
(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 download site 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.
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 Audio Track Dropdown Menu 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.
(OS X and Linux) In some locales, Preferences text may be truncated or overlapped, or dropdown boxes truncated.
(OS X) Period must be used as the decimal separator in effects even when the system language is French, German or other language that specifies comma separator.
(OS X) The "Cmd - Wheel - Rotate" mouse binding does not zoom in unless you modify the default System Preferences. ** On OS X 10.6 or later, go to Universal Access / Seeing / Zoom / Options and uncheck "Use scroll wheel with modifier keys to zoom".
Prior to OS X 10.6, go to "Mouse and Keyboard" and uncheck "Zoom using scroll ball while holding Command".
(Windows) The "Files Missing" warning always restores maximised windows to smaller size.
After changing language in Preferences, a few parts of the interface don't change until Audacity is restarted.
Audacity has several weaknesses in preserving the context of the audio being worked with:
If playback scrolls, pressing Stop leaves the waveform where it stopped and the cursor invisible. Pressing Play to resume then scrolls the waveform to start at the left edge, hiding the previously visible context before the cursor position. Workaround: If you had a selection and a special playback command like Cut Preview or Quick-Play caused the waveform to scroll, use or to move the selection back into view.
Current scrolling behaviour makes it too hard to watch the waveform progress, with a single shift of cursor and waveform position when cursor reaches the right edge
By default, all audio in the project is selected if an action requiring a selection is requested when there is no selection (this behavior can be turned off in the Tracks Preferences). If enabled:
You can always apply effects to the whole project in one step, but you can also delete audio in all tracks if you press Delete when there is no selection. That is easy to Undo, but we aim to tweak this behavior and make it more customizable in a future Audacity.
A few items in Edit menu are incorrectly grayed out if no track is selected.
If Sync-Lock Tracks is enabled, there is no indication of the cursor in the Sync-Locked tracks.
Mouse Bindings are not currently configurable by the user.
Snap-To does not move the cursor when first enabled or when the selection format is changed.
We're aware that some error messages in Audacity are not as helpful as we would like them to be. If you see a cryptic error message from Audacity, try a search (or ask) on
When using TAB to move into a TimeText control (for example, in a Generator, Change Speed or Selection Toolbar) the first character is highlighted instead of the first non-zero character.
(Linux) If Audacity is left open but without focus, its CPU use will rise slowly until all available system CPU is consumed. This is a bug in wxGTK 2.8.10 (not previous versions) - see . This issue can be fixed by updating to wxGTK 2.8.11 or 2.8.12.
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 http://trac.wxwidgets.org/changeset/62397?format=diff&new=62397, 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).
(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: 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.
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.
(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.
(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".
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 https://manual.audacityteam.org/o/man/languages.html.
(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: http://audacityteam.org/forum/viewtopic.php?f=17&t=5064
(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.
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.
(Linux) Meters may not respond immediately to playback which could cause them to report incorrect peak level or not display clipping.
(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.
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 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 .
For problems that occur when reopening or working in a project, the log file at Help > Show Log....
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. 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/ (~/Library/Logs/DiagnosticReports on Mavericks).
(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.
(OS X and Linux) PortAudio's default latency values which are used when recording with software playthrough are much lower than Audacity's default "Audio to buffer" setting. This may cause playthrough or recording glitches when recording with software playthrough enabled, especially when using pulse on Linux. Workaround for Linux: record from an (hw) device instead if software playthrough is required.
(OS X) Playback to Bluetooth headsets gives an error. Workaround: Revert to Audacity 1.3.3 (this may only work with stereo headsets), or use to send the Audacity output to an audio application that works with the headset.
(OS X) The "Hardware Playthrough" option in Recording Preferences is currently unsupported on all known Mac hardware. Try the "Software Playthrough" preference instead. If that does not work, the third-party application also provides software playthrough.
(Windows Vista and later) The "Windows WASAPI" host supplies playback, plus a "loopback" device for and experimental support for physical inputs.
Not everyone will necessarily experience all or any of the issues noted below, but please report any WASAPI issues not covered below to .
Although volume slider support for WASAPI is implemented, on some devices the Mixer Toolbar recording volume slider will be grayed out when selecting the Windows WASAPI host. Even if the Audacity recording slider is available, the sound device may not support Audacity adjusting its system playback or recording sliders. To control loopback recording on those systems, try adjusting the playback level of the audio player.
(Windows) When a USB device is connected, the Mixer Toolbar input slider for that device (and sometimes for any device) may wrongly appear active even though it has no control over the device's input level. Sometimes the Audacity slider will apply a software gain to the level (which is dangerous as it will only make the same clipped input quieter rather than stopping the clipping). Sometimes the Audacity slider will not affect the input volume at all. Workaround: use the slider in the Windows Control Panel where available, or any gain control on the device, or reduce the output being sent to the device.
(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.
(Windows) Audacity is incompatible (or not fully compatible) with some professional sound cards or audio devices, and may crash or have limited or faulty functionality. Occasionally, this may be true of some AC97 devices built into the motherboard. Workaround: make a different sound card your default when using Audacity, but please e-mail the following details to our :
Your version of Windows and Service Pack
Name, model number and driver version number of the sound card or device.
Note: Multichannel Recording in Audacity is often not possible with professional devices unless you compile Audacity with ASIO support.
Adding or removing an external audio device while Audacity is open will not be automatically reflected in the list in Device Toolbar or Devices Preferences. On Mac, unplugging then replugging an external device will give "error while opening sound device" (on Linux, pressing "Record" a second time will remove the error). Workaround: Use Transport > Rescan Audio Devices.
Calculation of "disk space remains for recording (time)" incorrect when recording in 24 bit quality.
Play-at-Speed slider: Change of playback speed is no longer automatic after you move the play-at-speed slider. To change speed, move the slider, then click the green button to left of the slider to play at the new speed.
Timer Record cannot maintain scheduled duration if system clock changes
(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.
(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.
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.
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.
Projects created by Audacity 1.1.x or earlier are no longer supported. Workaround: Export each project track as WAV using the appropriate legacy version of Audacity, then import the WAV files into current Audacity.
Projects created by Audacity 1.2.x are partially supported - there is a possibility Audacity could corrupt them. Please make a backup copy of the project's .aup file and _data folder to a new folder before opening the project in this version of Audacity. Once you save the project in this version, it cannot be opened in 1.2.
Projects created by previous versions of Audacity may contain audio "block files" longer than the project format allows. Reopening such projects in previous versions might or might not result in deletion of the overlong audio. Audacity has been provisionally fixed so that it can no longer create or delete overlong files, but it cannot read any such files it encounters. If overlong files are found, a "Problems Reading Sequence Tags" message will display .
If you continue with the offered repair then choose "Continue without deleting" in the Orphan Block File(s) dialog, the overlong files will be retained as "orphans" in the project's _data folder but will appear as silence in the track(s).
As long as you choose "Close project immediately" in the Orphan Block File(s) dialog, the project will quit and will not be changed in any way.
If you encounter the "Problems Reading Sequence Tags" message, please write to our with a copy of the .aup file and the log as found at Help > Show Log.
Time Track warp points saved in a 2.0.3 or later project will be preserved if opened in previous Audacity versions, but playback and display will be incorrect.
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.
While scrubbing if you click on any of the tools in the Tools toolbar, apart from the already active Select tool, then scrubbing will stop.
In order to forwards scroll-scrub at normal 1x speed without using the scroll wheel it is always necessary to move the mouse to the end of the window, even if the project is shorter than the window width. However if you try to forwards scroll-scrub in a less than half-width project by reducing the backwards-only speed, moving the pointer to the end of the window will not achieve 1x speed - it will be necessary to advance the scroll wheel once the pointer is at the end of the window. Enabling "scrolling left of zero" in may be more convenient if you scroll-scrub with short tracks.
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 Spectral Selection created in either Spectral Selection view currently only works with the three specific spectral edit effects 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.
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.
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.
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 keyboard shortcut alternatives for the buttons instead.
(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 our feedback address with details and include the crash report from /Library/Logs/DiagnosticReports/.
Historic changelogs
These are the changelogs down to the very beginning.
Normalize: Faster processing and improved interface. Left-right balance in unsplit stereo tracks is now preserved by default, with a checkbox option provided to process stereo channels independently.
Spectrograms now allow window sizes up to 32768 and frequencies up to half the sample rate (the maximum possible).
Mix and Render now preserves clip length by not rendering white space between time zero and first audio, and preserves audio before time zero. To retain silence before the audio starts, generate silence after render.
Grouped some Edit Menu items into "Remove Audio" and "Clip Boundaries".
CleanSpeech Mode removed from Interface Preferences (it still runs if it was enabled in a previous Audacity but can only be turned off there).
(OS X) Added support for AudioUnit MusicEffects (but no MIDI support).
(Linux) Set the per-user files directory per the program name set in configure.
(Linux) Changed the default location of the Audacity temporary directory to be in /var/tmp not /tmp, so preserving the directory between reboots.
Bug fixes:
Interface:
Excessive delay occurred when typing into labels in long projects.
Last digit of TimeText controls could not be manipulated in some formats.
Control Toolbar renamed to Transport Toolbar.
Device Toolbar (on by default) now contains all input and output device choices, including host and recording channels. Input/output choices are no longer in Mixer Toolbar on Windows XP or some older operating systems. New Transport > Rescan Audio Devices menu item to refresh the device list.
New "Sync-Lock Tracks" feature (turned on in the Tracks menu) to allow groups of audio and/or label tracks to retain synchronisation when the track length changes.
Bug fixes:
Interface:
Cutting or copying from a track at a given sample rate into a track at another rate resulted in speed-changed audio.
Generating inside a clip could modify the clip length or create spurious clips.
A hover tooltip is now provided if the Mixer Toolbar input selector cannot control the system slider for the selected input.
More intuitive behavior when moving and resizing labels by dragging
Support added for importing lists of files (LOF) containing relative paths
Export Multiple: new option to use a numerical prefix before existing label or track names; "Success" dialog now resizable
Bug fixes:
Imports and Exports:
AAC files could not be exported at 48000 Hz
When importing multiple native file formats using FFmpeg, all files after the first reverted to using the native importer
(Windows) Better icon file with higher resolution and transparency
New SoundFinder plug-in to label regions of audio between silences, so allowing silences between tracks to be excluded when exporting multiple
Bug fixes:
Imports and Exports:
Bug when exporting partial selections caused too much audio to be exported is fixed.
Fix corrupt files exported through FFmpeg when metadata included, (metadata is now exported correctly in M4A files)
Linked audio and label tracks disabled until a future Beta version so they can be bug fixed
Input volume slider will be disabled if it doesn't have proper control of system slider; use the system slider instead
Proper support for copying/pasting label-with-audio including label text; new Edit > Paste Text to New Label menu item to paste system clipboard
Bug fixes:
Imports and Exports:
Freeze importing audio files when Default View Mode set to Pitch (EAC)
Simultaneous On-Demand imports sorted incorrectly
Bug fixes:
* Crash, slow launch or excessive CPU/memory use arising from automatic VST support:
* VST instrument plug-ins should now be correctly ignored
* VST effects now scanned only at start of first session that detects them, then cached; effects are now not loaded or opened until needed
* New "Effects" tab in Preferences to enable/disable VST effects and enable VST rescan on next launch * Default View Mode now works
* Chains now always apply their stored parameters rather than those last used in Effect menu * Non-MP3 files imported via drag or Recent Files caused crash if filter in file open window set to MP3
* AAC exports (using the optional FFmpeg library) were silenced
* Generating audio always fitted the project in the window; fit now done only if generating in new track
* View menu items/shortcuts incorrectly disabled when playing or recording
* DTMF generator defaulted to zero duration on open
* Unwanted interactions between linked audio and label tracks
* Noise Removal shifted clips if the selection region included white space
* (Windows XP) Failure to launch on some machines due to "incorrect configuration" issue
* (Windows) Crash importing a stereo file while a screen reader such as JAWS is running
* (Mac OS X):
* Audio Units effects applied to all tracks in project even if not selected
* QuickTime importer now handles files greater than 16-bit or 64000 Hz
* Various other interface bugs
New Features:
* Effects and Analysis:
* VST Effects now display GUI by default
* Faster Equalization and Noise Removal; improved Truncate Silence and Click Track
* Chains applied to files now clear temporary data after processing each file
* Updated Nyquist implementation with support for SAL syntax and improved memory management
* Plot Spectrum now analyzes up to 237.8 seconds of audio, with separate windows for each project and improved display; new preferences for Spectrograms
* Contrast Analysis tool now modeless for easier use
* Interface:
* Draft Manual/Quick Help included in Windows and Mac installers
* New "Mixer Board" view with per-track VU meters
* Mute, solo, gain, pan and track height saved in projects
* More compact Preferences window with easier-to-use Keyboard tab and new toolbars shortcuts
* New Screenshot Tools and improved screen reader support
* Other:
* Record more than 16 channels (hardware/drivers permitting)
* Improved support for non-mmap ALSA devices such as PulseAudio
* 32-bit float data over 0 dB now handled without clipping
* "Stop" option when importing preserves already imported data
* AMR NB import/export now supported if the optional FFmpeg library is installed
* Faster waveform drawing and better response in multi-track projects
Bug fixes:
* Export Multiple: failed with no export or warning if empty label encountered; silenced project and exported files if overwriting imported WAV files without copying the data in
* Metadata Editor hidden if it was on a now unavailable second monitor
* Misaligned audio after "Split New" or Noise Removal effect
* Incorrect label movement and paste with linked audio and label tracks
* Equalization, Cut Preview and Advanced Mixing Options dialog
* (Linux) Mixer Toolbar should now adjust levels and select input sources properly
* "Audio cache" preference caused crashes - data is now only cached in memory if available RAM is above a level defined in preferences
* Various other crashes
New Features:
F11 Full Screen mode
High-quality "Sliding Time Scale/Pitch Shift" effect
Audio Contrast Analyzer for testing audio on the internet for WCAG2 accessibility compliance.
Windows: sound devices can now be opened using the more efficient DirectSound API
Other changes:
* Latency correction should be improved for many users by employing a fixed rather than variable correction
* Grouping of Effects into categories turned off until a way is added for users to do so themselves
* Numerous minor interface improvements such as Metadata Editor navigation, new "hh:mm:ss + hundredths" selection format
* Note: Windows users wanting to export MP3 files will require the latest version of the LAME encoder from http://lame.buanzo.com.ar/
Cross-platform Bug Fixes:
* Muting/soloing caused incorrect channel results in exported stereo files
* Noise Removal and all Nyquist effects pasted the original unmodified audio at the end of the modified region
* Noise Removal inserted a tail of low level noise at the end of the modified region
* Nyquist and Compressor plug-ins did not display moving bars in progress dialog and over-estimated "Remaining Time"
* Cancelling Nyquist effects deleted unprocessed audio
* Change Speed and Change Tempo failed to modify the original selection length
* Cut lines invisible * Fixed various bugs importing multi-stream files via FFmpeg
* File > Export as WAV could be corrupted if overwriting an imported WAV read direct from the file
* Export multiple "Other uncompressed files" choice always produced 16-bit PCM audio irrespective of chosen options.
* MP3 export usually produced a 128 kbps constant bit rate file irrespective of chosen options; reported length often incorrect
* MP3 ID3 Genre tag misread on import if the genre list in Metadata Editor was opened and saved
* Exported metadata tags in MP3, OGG and FLAC often not seen by player software - now substantially improved
* WMA exports (via FFmpeg)corrupted if metadata tags included
* Some multi-channel recording devices that previously recorded more than two channels no longer did so
* Generated audio did not fit in window
* No warning was given when saving an empty project
* Beep on completing longer process did not work on many systems
* fixed crashes importing lists of files (.LOF), in Meter Toolbar and Change Speed
Platform-specific Bug Fixes:
* Windows Vista: crash opening Preferences with no sound devices enabled and connected * Mac OS X and Linux:
* Spurious clipping at start of playback
* Labels did not accept certain legal characters
* Shortcuts did not work after running effects
* Project Rate did not change to respect rate of first imported file if that rate was unsupported * Mac OS X only:
* Crash resizing project window
* Menu items became inactive or visibly corrupted
* File > Open dialog did not always work on OS X 10.4
* Impossible to set independent Command and Control shortcuts that shared the same key
* Freeze importing uncompressed files via On-Demand (please report any remaining instances of this to: [email protected])
* Portable settings were not picked up, instead settings were taken from the default location
* Fixed unavailability of FFmpeg installer
Interface:
* "Save Compressed Copy of Project" saves in much smaller .OGG format to facilitate online transmission of projects
* Improved MIDI import and export routines, and clearer color for selection region
* Default temporary directory on Mac now accessible in Finder
Import / Export:
* Stability improvements in on-demand loading
* FFmpeg: support for latest version of library, improved version checks and error messages, stability improvements in custom exporter
Bug Fixes:
* Crash in "Get Noise Profile" step of Noise Removal at project rates below 20480 Hz.
* Underestimation of peak level in tracks with a small number of different peaks
* Truncate Silence could result in repeated or lost audio if applied to the whole of a track * Other interface, generating, exporting and platform-specific fixes
Compilation:
* Added autoconf macro archive to CVS, enabling *.nix users without this archive to build --with -MIDI
Interface:
* Note Track now supports export as a MIDI file
* Linked audio and label tracks: improved support when source and target number of tracks differ and when cross-pasting different track types
Import / Export:
* On-demand now supports project saving during summarising; reverts to stripey background; fixed some crashes due to threading issues
* Exports: Single AAC filter (M4A LC profile) with quality settings slider; removed FFmpeg formats already supported by Audacity; added explicit GSM 6.10 (WAV) filter; current project rate now used for all exports, with check for format-invalid rates; improvements to metadata support
Effects:
* LV2 plug-ins: added support (OS X and Linux only) for using synths as tone generators, scale point labels, grouped controls and i18n translations
Interface:
* Note Track now builds on Windows
* Fixes/improvements for linked audio and label tracks (one desynchronisation bug remains when pasting audio into a greater number of tracks than were copied); now supports label shifting when changing pitch and tempo
* Added full label pasting support: now possible to paste multiple labels, region labels and labels with audio, and correct label text is now pasted
Import / Export:
* Added full "on-demand" support (now with minimum file length of 30 seconds): clicking moves summary calculation point; supports split and merge of stereo tracks; incompletely summarised tracks resume summary calculation automatically; text-based Status Bar progress indication and animated dummy waveform instead of embedded progress bar
Effects:
* Fixed a bug where previewing Equalization curves more than once previewed the unmodified audio
* Improvements to DTMF generator
Miscellaneous:
* Improved support for working with audio in excess of 2^31 samples (about 13.5 hours at 44100 Hz); some accessibility improvements
Interface:
* New Preference: Default View Mode, to choose type of waveform, spectrum or pitch view for new tracks
* Note Track: experimental support is now enabled by defining USE_MIDI in config*, but does not build out-of-the-box on Windows
* Bug fixes for linked audio and label tracks; now supports label shifting when changing speed and generating tones
Import / Export:
* Improvements/fixes for AAC exports including new M4A filter for compatibility with iTunes; RealAudio export support removed - FFmpeg does not support this properly
* Improved refresh of on-demand loading; fixed a phantom on-demand progress bar when time-shifting clips
Effects:
* Experimental support for LV2 plug-in architecture on Linux and Mac, but operation may be buggy; no LV2 support yet on Windows, because the required slv2 library currently does not build
Import / Export:
* Experimental support for exporting a much wider range of proprietary audio formats via FFmpeg
* "On-demand" immediate loading of imported PCM WAV or AIFF files now has experimental "progress bar" embedded in the waveform until fully loaded
Interface:
* Note Track: experimental support for cut, copy and paste using Edit Toolbar; currently not available for Linux, where EXPERIMENTAL_NOTE_TRACK must be undefined in order to build
* New Transport menu for alternative access to play and record commands and some recording preferences
* Audio tracks are now linked to label tracks by being positioned above a label track, if linkage is enabled in the Tracks menu
Import / Export:
* Experimental support for importing a much wider range of audio formats via FFmpeg: support has to be enabled in *config when building and requires FFmpeg libraries
* Experimental support for "on-demand" immediate loading of imported PCM WAV or AIFF files (full waveform continues to load while you play or edit).
Effects:
* Built-in plug-ins now grouped into related hierarchical categories
Interface:
* New Debug Log window available in all builds
* Experimental support for linking a label track with any number of audio tracks so that labels shift with cuts and inserts in the audio track
* Default theme now reverted to that of 1.3.5
* Recording channels preference now defaults to stereo
Miscellaneous:
* Bug fixes for shortcut availability/tab order in Selection Bar, and for window focus issues when previewing effects
* Improvements in escaping and navigating fields in dialogs, and in stability when screen readers are used
Interface: *
Further improvements to menu navigation and wordings.
All file dialogs are now resizable, and support "Places" sidebar on Windows 2000 or later.
Preferences:
Compilation:
Simplified modular builds for Windows, removing static-linked configurations.
New shared configurations on Mac to support modular builds, and all builds are now Unicode.
Miscellaneous:
Default auto save interval reduced to 2 minutes.
Bug fixes to correct project rate initialisation on Linux, and file importing issues on PPC Macs.
Recording / Playback:
Several bugs fixed so that latency correction should be better, and more devices work correctly. Problems with invalid sample rates under Linux should be much rarer.
Newer version of Portaudio library.
New feature to record onto the end of an existing track (hold Shift while clicking Record).
Import / Export:
Updated versions of Libogg, Libvorbis, Libflac, Libsndfile and Twolame libraries.
Handling of unsupported file formats more informative.
Handling of file names with slashes on OS X improved. New dialog allows replacement of illegal file name characters on all platforms.
Interface:
Improved scaling and layout for rulers and VU meters.
Envelope fixes/improvements including full control of undo/redo.
New keyboard shortcuts and improved menu navigation.
Preferences: More intuitive tab arrangement. New options for mute/solo and Metadata Editor behavior. Language can now be changed without restart.
Effects:
New Vocal Remover plug-in, improvements for Generate effects.
Compilation:
Fixes when building Audacity with libraries disabled.
Improvements to make Mac and Solaris builds easier.
Security:
Full fix for issue CVE-2007-6061 on systems where temporary directories can be changed by other users (thanks to Michael Schwendt).
Miscellaneous:
Updated translations for many locales.
Several stability improvements.
New Features
New Welcome Screen with introduction to Audacity
Enhanced Windows Shell integration, so Audacity shows up in lots of Windows places such as "Open With".
New keyboard command: 'Mix and Render to New Track' (bound to Ctrl+Shift+M).
New keyboard shortcut: "Shift-A" starts playback when stopped, or performs "Stop and Select" when playing.
Interface:
Keyboard shortcuts for making short/long jumps along the timeline.
Added 'Snap To' in the Selection Bar.
Made keyboard navigation easier when multiple menu items with the same first letter exist.
Enhanced interface for label editing.
Opening/saving formats:
Metadata editor added for OGG, FLAC and WAV/AIFF exports, and general improvements in this area.
Import of metadata improved.
Muted tracks are no longer audible in the exported mix.
Effects:
Truncate Silence: support for multiple and stereo tracks.
Dtmf Generator:
added support for keypad letters
added an amplitude control.
Recording / Playback:
Improvements to latency correction.
Updated version of portaudio-v19 library.
Note that Help is no longer built in, but accessible on the Web via links in Audacity.
Opening/saving formats:
Import
Import of audio from QuickTime (mov, aac, m4a) files is now supported on OS X.
Broadcast Wave Format (BWF) wave files can now be imported.
Effects:
EQ effect
Responsiveness improved.
Several enhancements added.
Batch support added.
Other features:
Major speed improvement in Spectrogram rendering
Increased support for drag and drop on OS X
Support added for building against wxWidgets 2.8
Support opening multiple Audacity Projects at once from Explorer on Windows
Also:
Many improvements to language specific translations
Numerous stability improvements
Improved accessibility for the visually impaired + Improvements for screen readers, accessibility of tracks, and hot keys
Usability improvements + New selection bar + New features for label tracks + Improved toolbar docking flexibility + Menu renaming and reorganization + Selection, ruler, and playback control improvements
Auto-save and automatic crash recovery
New features The new features in Audacity 1.3 have been grouped into the following six major categories.
Collapse/Expand Tracks In Audacity 1.3, every track has an upward-pointing triangle at the bottom of the label area on the left side of the track.
Multiple clips per track In Audacity 1.2, there is one audio 'clip' per track. There is no easy way to time-shift part of a track without moving the rest. In Audacity 1.3, you can split a single track into multiple clips. You can move these clips around between different tracks, making it easy to construct complex compositions out of hundreds of smaller audio samples.
Selection Bar In Audacity 1.2, the current selection is contained in a status bar at the bottom of the window. In Audacity 1.3, this is replaced by a fully functional Selection Bar, which displays and controls the current selection (your choice of Start and End, or Start and Length), and the current audio position. The selection bar is fully editable - just click in any field and type to change the current selection precisely. In addition, many formatting options allow you to view times in different units, such as samples, CD frames, or NTSC video frames.
The File menu now includes a list of recent files.
The "Generate Silence" effect now prompts for a length.
Audacity is now built with Vorbis 1.1, which features better encoding quality and file compression.
Dragging sound files into the Audacity window now works on Mac OS X and Linux, as well as Windows. (Before, it worked only on Windows.)
Fixed a bug that caused recording to stop or display incorrectly after about 50 minutes on some Windows systems. (This was partly fixed in Audacity 1.2.2, but still didn't work on some systems.)
The Change Pitch and Change Tempo effects have been upgraded to use a new version of the SoundTouch library by Olli Parviainen, with better speed and higher quality.
libsndfile has been upgraded to version 1.0.11.
VU Meters added for both playback and recording. Click on the recording meter to monitor the input without recording.
Export Multiple - new feature that lets you export multiple files at once, either by track, or split based on labels.
Attempt to automatically correct latency in full-duplex recordings. (This does not work perfectly, and is not yet supported on all systems. It will improve in future versions.)
The following translations have been added or updated: Finnish, French, Hungarian, Italian, Japanese, Norwegian, Polish, Russian.
Fix a bug that could cause data to be lost when pasting audio from one project into another, after the first project has been saved and closed.
Fix a possible crash when opening or resizing the Equalization window, especially when using large system fonts.
New cross-fade effects.
Fix problem where samples were drawn in the wrong position when zoomed all the way in. This caused the drawing tool to move a different sample than the one under the cursor.
Don't use id3v2.4 tags, which are not yet supported by most players. (This was fixed in 1.2.0-pre2, but appeared again by accident in 1.2.0-pre3.)
Fixed problems that could occur when importing certain non-seekable PCM audio files, such as GSM610.
Fixed bug that was causing the samples to shift off-screen horizontally when zoomed in very far and the track had a time-shift offset.
Fixed bugs in the new resampler that added noise to resampled audio on some systems. If you experienced noise when exporting to a WAV, MP3 or OGG file you may have been bitten by this bug.
Fixed bug where Export is grayed out when nothing is selected.
Fixed crash caused by opening Audacity on a computer with a high-end sound card with no mixer support.
Fixed crash in Import Raw.
Fixed New Stereo Track.
Online help completed. The full manual is nearly complete and will be posted to the web site for online browsing shortly.
Audacity will no longer let you do unsafe editing operations while playing or recording. This eliminates many potential crashes.
Fixed ability to cancel Quit button.
New resampling library, with no restrictions on the maximum or minimum rate of resampling.
User Interface
Vertical zooming of tracks.
Improved look and placement of toolbars.
New custom mouse cursors.
User Interface
New Mixer toolbar allows you to control the output volume, input volume, and input source directly from Audacity.
Every track now has its own gain and pan controls.
User Interface
Fixed bug in Windows version, for track menu commands "Name..." and "Split Stereo Track"/"Make Stereo Track".
Effects
User Interface
Tooltips appear in Status Bar.
Vertical cursor follows play/record
Pause button
Core audio processing:
Support for 24-bit and 32-bit sample formats
Automatic real-time resampling (using linear interpolation)
Effects:
libmad for fast MP3 importing
libid3tag for editing MP3 file information
libsndfile to read and write more audio file formats
PortAudio for cross-platform audio playing and recording
Scrubbing and Seeking, including backwards play.
Quick-Play from Timeline enhancements, particularly for looping.
(Windows) Language of Audacity user interface is now set in installer.
More VI usability enhancements for track focus & navigation.
Modules can be enabled in Preferences. Mod-nyq-bench available as an experimental module (but not in the default download).
Track dropdown menu settings could affect other tracks.
Slight mismatch of vertical scale with linear spectrogram view.
RTP effect Play/Stop button remained deactivated after built-in preview ended.
Contrast: "Move forward or backward through active windows" did not refocus Contrast.
LADSPA and LV2 generate plug-ins failed when white space selected.
When you TAB forwards from "Audio Position" in Selection Toolbar, the "Selection End" or "Selection Length" radio button is read as "Selection Start". When you use COMMAND + F6 or COMMAND + SHIFT + F6 to move directly into "Selection End" from another toolbar, the button is read as "Selection Start".
Mixer Toolbar input/output sliders are not read, but just described as "multiple indicators". The "Graphic EQ" and vertical sliders in Equalization *are* read.
Metadata Editor table not read.
Edit Labels dialog not read.
In the "Edit Chains" window, only the first command in the "Chain" list is read, and it is only read when first accessed. In the "Select Command" window for inserting a new command in a Chain, commands in the table are not read.
"Manage Curves" table in Equalization not read.
Control labels for Vamp and VST plug-ins are not read.
Control labels for Nyquist plug-ins are read inconsistently in older version 3 or earlier plug-ins (Version 4 seems to read more consistently).
MDA Tracker may crash if the effect is applied while playing audio. For all the MDA VST's, the sliders have no effect and only the default effect settings can be applied.
Waves v5 may cause Audacity to hang if you select it in the "Register Effects" dialog then click OK.
Digitech RP250 (effects pedal)
MNoiseGenerator AU and others in MFreeEffectsBundle crash if you preview them
Native Instruments B4 and Native Instruments Guitar Rig v3 and v4 (v5 does not have this issue)
PredatorFX
Waves Version 7 and 8 AU: These effects may crash Audacity on quit, after project data has been saved. Waves Version 9 AU should now work correctly.
ID3 v2.4 tags in imported MP3 files are not seen and will be removed on export.
Audacity writes both ID3 v2.3 (TYER) and v2.4 (TDRC) tags for "Year", but any applications that require the older TYER on its own (without TDRC) will not see "Year" in Audacity-exported files. The id3 command-line application on Linux is one example.
AAC: Artist and Year metadata is not exported or imported due to a bug in FFmpeg 2.2.2.
Zoom to Selection shows none of the surrounding context
On Mac, Audacity may freeze if JACK is launched by QjackCtl then Audacity is launched. Workaround: Use JackPilot to launch JACK, or launch QJackCtrl after Audacity and JACK are running.
If the achieved loopback recording level is too low, try turning up the volume in the application playing the audio.
Adjusting linked sliders during loopback recording may cause audio breakup or recording glitches.
Loopback recording may fail "error opening" when Audacity is set to record in mono.
You will normally need to start playing the loopback stream (or to have previously played some other audio in the application you are using for playback) before starting loopback recording in Audacity.
Changing Default Format or Exclusive Mode settings in Windows Sound while Audacity is open may cause "error opening" when starting to play or record. Try Transport > Rescan Audio Devices or restarting Audacity.
If you receive dropouts or poor quality when recording, try setting the Audacity Project Rate to 44100 Hz and setting Default Format in Windows Sound to 44100 Hz, with both "Exclusive Mode" boxes unchecked. Other rates may work, providing the same rate is set in both places. The most likely place for a dropout is within the first second or two of recording.
Physical inputs may fail "error opening", especially when overdub recording. Try setting Audacity project rate to 44100 Hz then for both the playback and the recording device in Windows Sound, ensure both "Exclusive Mode" are checked (enabled). You can also try setting Audacity Project Rate to the same as Windows "Default Format" with both Exclusive Mode boxes unchecked.
Latency when overdubbing may substantially increase shortly after starting the recording.
"Audio to buffer" in Recording Preferences cannot be used to adjust recording latency.
Non-looped playback plays the selection minus the "Audio to buffer" (for example, standard playback will fail to play the buffered length at the end of the selection). The buffer setting may be set to zero when using WASAPI host.
(OS X, Linux) Crash occurred if Toolbars were reset during playback or recording.
Imports and Exports:
MP2 files were not importable without FFmpeg library or an import rule.
Files that could only be imported using FFmpeg imported as noise with no error message if FFmpeg was not available.
Files containing PCM audio but an incorrect extension (such as MP3) caused a freeze.
Effects and Analysis:
An empty command could be added to a Chain which then displayed a Nyquist error message when run.
Plot Spectrum didn't preserve signal level if multiple tracks were analyzed.
Other bug fixes:
Audacity has been provisionally fixed so that it can no longer create block files longer than the sample format or project format allows, and can no longer delete these, which led to data loss. Any overlong blocks found are preserved but "orphaned", so will appear as silence.
Orphan block files were wrongly reported if cutting or copying to the clipboard then reopening the project in the same session.
Fixed some crashes and incorrect movement of audio when dragging tracks.
(Windows) Data loss is now prevented when encountering a corrupted .aup file created in ANSI builds.
(Linux) Restore building if USE_PORTMIXER is not defined.
Noise Removal: New "Sensitivity" slider to adjust the noise threshold, and new option to isolate noise.
New "Extended Import" Preferences for specifying different importers to open specific file extensions.
Improved Automatic Crash Recovery with all project changes autosaved.
MIDI tracks can be vertically zoomed, time shifted and display bar lines. Note: the channel selection buttons are not available in 1.3.13.
(Windows and Linux) The window Close button and other system close or shutdown commands now quit on closing the last window. File > Close now always clears to a new, empty project.
(OS X) Simpler installer with top-level "Audacity" folder.
Edit > Region Save did not save the cursor position.
(Windows) Projects crashed when clicking rapidly inside the interface or when applying repeated effects towards the end of audio tracks.
(Windows) Some Unicode characters could not be typed into labels, or caused a freeze using some input methods.
(OS X) Crash when quitting an empty project window, or when closing the main project window while a progress dialog was on screen.
Numerous other interface fixes including Dependencies dialog, Keyboard Preferences and spurious lines drawn on waveform.
Imports and Exports:
Support added for later versions of the optional FFmpeg library up to current FFmpeg HEAD. This should significantly improve FFmpeg support on Linux. FFmpeg downloads for Windows and Mac updated to v0.6. This fixes mono AAC files importing as stereo, though current 0.5 versions of FFmpeg will still work.
Both FFmpeg and LAME should now be properly detected even when other versions of those libraries exist on the system.
New warning (on by default) for importing uncompressed audio files. Better error messages when read-directly uncompressed files are missing.
Imported ID3v2 metadata tags were removed when exporting without the Metadata Editor appearing (for example, when using an export command in Chains). Note: As a result of this fix, ID3v1 tags must now be written by exporting using (external program) and an installed LAME.
U-Law/A-Law files with WAV headers now use the standard 18 byte fmt chunk, so should now be recognised by most telephony applications.
Variable bit rate MP3s exported using "MP3 Files" were larger than necessary because using the bit reservoir was disabled.
(OS X) Files imported from iTunes could create invalid characters in the .aup project file, causing an error when re-opening the project. Note: An error "reference to invalid character number" will still occur if re-opening a project created in previous Betas that contains such characters. To fix the issue, 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 (;).
Other bug fixes:
Nyquist effects: fixes for crashes, incorrect slider behaviour and better support for backslashes, double quotes and Unicode characters.
(Windows and OS X) Processing of VST effects was substantially slower than in previous versions of Audacity.
(OS X 10.5 PPC) A first-time installation of Audacity Beta would hang on launch if VST effects were detected.
(Linux) Recordings made with the pulse device crashed or stalled when using overdub and/or software playthrough.
(Linux) Play-at-Speed crashed at 0.08 speed or lower if Audacity was configured with libsamplerate.
New Equalization preset "Inverse RIAA", with new button to invert other curves
Timer Record now remembers last scheduled duration
Meter Toolbar can now be made much narrower, and so more suitable for vertical orientation
New Preferences choice for "System" language which is used on first run instead of asking user to choose language
Warning now provided if WAV/AIFF exports are not successfully completed
(Linux) Improved icon set in compliance with freedesktop.org Icon Theme Specification 0.6
Projects froze if files imported via On-Demand were no longer available
(Linux) WAV/AIFF exports were corrupted if overwriting an aliased file which had been imported using the command line
Labels:
Cutting or deleting a region in the waveform and label track did not move the labels in advance of the cut
Incorrect behavior snapping to labels and boundaries when Snep To was enabled
Labels can now be reversed if included with the audio selection
Other bug fixes:
When using non-English languages, Generate effects truncated the selected region
Mice with high-precision scroll-wheels could cause a crash
Changing recording preferences using the Transport menu did not update the menu in other open projects
(Windows 7) Clicking in a file open or save dialog caused files or folders to disappear from the list, and file filtering was broken
Improved help for files that cannot be imported because the relevant optional library is missing.
Effects:
Allow effects which change the length of the audio they work on to also be applied to selected label tracks, thus keeping them synchronized.
Fixed inability in Nyquist plug-ins to add labels to an existing label track
(Mac) Equalization window was corrupted after Preview
(Linux 64-bit) Fixed crash Generating Click Track
Audio Devices:
Fixed bug causing recording to stop short when the recording sample rate is not supported by the sound device and libsamplerate is used for resampling.
Fix crash when opening Preferences on a machine where there are no available audio devices.
Fixes for bugs using Timer Record and Sound Activated Recording
User Interface:
Sizes of some dialogs adjusted to ensure they fit on the screen.
Fix for supposedly "hidden" items appearing on screen with large monitors.
Various keyboard shortcut and translation fixes.
Other bug fixes:
Several timing-dependent crashes and minor incorrect behaviors have been fixed
Windows installer now installs correctly over previous versions of Audacity
WMA exports corrupted if they contained metadata
Metadata Editor appeared before the Export window when exporting to any format
Effects:
Crash or hang using Equalization on longer tracks
Reverse did not reverse clip boundaries
Nyquist:
Excessive memory consumption led to slow processing or crashes
Values appearing in Nyquist effects text boxes were not always the default or previously entered values
Errors running Nyquist effects in European locales where comma used as decimal separator
VST effects remained in Effect menu even when re-scanned and no longer available
Truncate Silence produced incorrect results if silences spanned a block boundary
Other bug fixes:
Spurious "not writable/disk full" errors when saving projects
Playing, rendering or exporting multiple tracks led to desynchronised playback or loss of audio data
Crash opening Preferences when no recording and/or playback devices enabled or connected
Preferences window: OK button did not respond to ENTER when a tab selected in left-hand panel
Mixer Board solo button handling
(Windows) After a period launching correctly, Audacity sometimes did not come up on top at launch
(Mac OS X) Correctly installed Help folder could not be found
(Mac OS X and Linux) Output slider could affect VU playback meter which then did not reflect actual waveform volume level
(Linux) Undoing or redoing a label edit could cause a crash
New "Smart Recording" preference automatically pauses recordings that fall below a pre-defined input level.
Expanded Build Information tab.
Added support for VAMP audio analysis plug-ins.
Solo button solos only one track at a time, and a track cannot be both mute and solo.
Layout of OK/Cancel buttons consistency improved.
Preferences:
"Select all audio in project, if none selected" (on by default)
"Beep on completion of longer activities" (system bell, not main output).
Other preferences cleaned up and explanations improved.
Envelopes: Many fixes when copying / pasting / repeating.
Many translation updates.
Track height fixed in several cases.
CleanSpeech mode switching without closing and re-opening fixed.
Compressor: variable decay time added.
Equalization:
Clicks at start / end prevented
Improvements to saved curves being found
Preview works correctly
'Merge' command appears in Undo history.
Clipping detected more reliably.
Nyquist plug-ins reviewed and enhanced.
Better (and more) progress bars.
Cancelling effect always restores previous audio.
Several improvement to effects in batch mode.
Metadata can be added to OGG files
Improved export option selection
Additional export options added to MP3 and FLAC file formats
Command line exporter now supported on Windows and OS X
New Auto Duck effect
Added previewing to AudioUnit effects
Much improved Noise Removal effect
Effects previewing can now be canceled
New DTMF Tone Generator effect
Additional options available in Noise effect
Improved the Tone Generation effects
Improved main window sliders
New support for snapping while selecting and sliding
Improved track focus handling and visual feedback
Speed improvements and handling of resizing/zooming in tracks
Spectrum view can now be zoomed.
New internal file cache to improve handling of project files over networks
Major improvements to some built-in effects (Repair, Equalization) and fixes to others
New features and bug fixes for Nyquist
Restructured Preferences dialog
Improved batch processing
File format export improvements
Timer recording
Intel Mac support
Improved Label Tracks Label Tracks are Audacity's way for you to create markings 3 and annotations within your project. In Audacity 1.3, Label Tracks are much improved, with support for overlapping labels, and support for modifying both the left and right edge of the label region just by clicking and dragging.
QuickTime and Audio Units on Mac OS X On Mac OS X, Audacity can now import and audio file supported by Apple's QuickTime technology. This includes .MOV and .MP4 (AAC) files. Unfortunately encrypted audio files (such as those from the iTunes Music Store) cannot be imported directly into Audacity - Apple does not allow this to be done easily because it would be too easy to circumvent the encryption this way.
Also on Mac OS X, Audacity now supports Audio Unit plug-ins. Audacity searches for Audio Units in the usual location, in the system or user's Library folder.
Other features Better performance with large projects
Project integrity check on open
Transcription toolbar
Upload
Batch
Cut lines
CleanSpeech
The "View History" window can now discard old undo levels to save disk space on Windows. (This previously worked only on Linux and Mac.)
"Preferences" command is now in Edit menu.
"Plot Spectrum" command is now in Analyze menu.
Opening a project file saved by a later version of Audacity displays an intelligent error message. Also, trying to import a project file (instead of open it) displays an intelligent error message.
Audacity now compiles in Visual C++ .NET 2003.
Other minor bug fixes.
New or updated translations: Arabic (ar), Czech (cs), Finnish (fi), Hungarian (hu), Japanese (ja), Norwegian (nb), Slovenian (sl), Simplified Chinese (zh_CN), Traditional Chinese (zh_TW).
Shift-clicking on a mute or solo button now un-mutes (or un-solos) all other tracks.
Nyquist plug-ins can now accept strings as input. Also, a "Debug" button has been added to Nyquist effect dialogs, which allows you to see all of the output produced by Nyquist, for aid in debugging.
When the audio file referenced ("aliased") by an Audacity project is missing, Audacity will now always play silence. Before, Audacity would sometimes repeat the most recent audio that was played previously.
VU Meters will now always reset when audio I/O has stopped.
Fixed a major Mac-only bug that was causing Audacity to crash at seemingly random times, but especially during audio playback and recording.
New or updated translations: Italian (it), Hungarian (hu), Ukrainian (uk), Spanish (es). Polish (pl), Simplified Chinese (zh), Norsk-Bokmal (nb), French (fr).
MP3 tags dialog will only pop up the first time you export as MP3; after that it will not pop up again as long as you have filled in at least one tag.
You can now add a label at the current playback position - in the Project menu, with a shortcut of Ctrl+M.
Clicking on a label now selects all of the tracks, making it easier to use the label track to recall selections.
Windows: Fixed a crash in the Time Track "Set Rate" command.
Fixed a bug that caused problems with recordings over 45 minutes on some Windows systems.
Mac OS X: Improved support for the Griffin iMic by fixing a bug that was causing it to always record in mono instead of stereo.
Added support for Software Playthrough (listen to what you're recording while recording it, or while monitoring using a VU meter) - this makes it possible, for example, to record using one audio device while listening to it play through a separate device.
Unix/Linux: Fixed freeze caused by captured mouse when audio device hangs. (Audacity may not respond, but it will no longer freeze all of X.)
Fixed a cosmetic bug that caused improper waveform display if you tried to open an Audacity project saved on a different platform (e.g., copying a project from a Mac to a PC).
Fixed bug that could cause instability when pasting, splitting, or duplicating a label track.
You can now change the font of a label track by choosing "Font..." from the label track's pop-up menu.
Basic printing support has been added. Currently it scales the entire project to fit exactly on one page. Try printing in landscape orientation for best results.
Mac OS X and Windows: Audacity ships with a newer version (1.0.1) of the Ogg Vorbis encoder. Vorbis compression will now have higher quality and smaller file sizes.
Fix a bug that occasionally caused crashes when applying effects to split tracks.
Zoom In / Zoom Out now properly disable when they're not available.
Fixed disk memory leak in Preview
Other minor bug fixes and performance improvements.
Fix a crash when the temporary directory is not available on startup.
Correctly load ID3 tags saved in Audacity project files.
On Linux and OS X, store lockfiles in the temp directory instead of the user's home directory. This fixes problems in lab environments where users have restricted or network-mounted home directories.
Fix a bug that prevented Nyquist effects from running when certain regional settings were activated.
Fix a bug in the Quick Mix command that could cause old temporary files to not be deleted.
Linux: Fix endianness problems in playback on PowerPC.
Linux: Fix compilation problem in Nyquist on MIPS.
Linux: Include a more recent PortAudio v19 snapshot (fixes compilation problems when building with the --with-portaudio=v19 option).
Two new Nyquist plug-ins: "Cross Fade In" and "Cross Fade Out."
Other minor bug-fixes.
When the cursor is on-screen, the Zoom In button now zooms to the area around the cursor.
Mac OS X: Fixed audio problems on the Apple PowerMac G5.
Linux/ALSA: Work around a bug in ALSA's OSS emulation that caused Audacity's playback cursor to move too quickly.
Microsoft Windows: The Audacity source code should now compile out of the box on Windows.
Many new/updated translations.
Dithering is now only applied on export when it is really necessary (e.g. when converting float samples to 16-bit).
Files that only contain mono tracks are now automatically exported to stereo files when they contain tracks which are panned to the left or the right.
The Delete key can now be used to delete the current selection, in addition to the Backspace key.
Fixed bug where Audacity didn't ask whether to save changes if you close the project or exit while recording.
Mac OS X: Supports Playthrough (listen to what you're recording while recording it) if your hardware device supports it.
Mac OS X: Audacity is now a package (you can right-click on Audacity.app and select 'Show Package Contents'). Launch time has improved significantly.
MS Windows: Fixed problem that caused Windows XP to use the short name of a file ("TESTFI~1.AUP"), which led to problems when the file was later opened again using the long file name.
MS Windows: Fixed bug that caused file exports to fail if the destination directory was the root folder of a Windows drive.
MS Windows: Audacity's application information which is written to the Windows registry now always contains the full path to the executable.
MS Windows: Fixed problems in trying to set the Windows registry as non-admin user, for file-type associations.
Make sure the "Save" command is enabled after changing gain and pan sliders.
Updated translations. Added translator credits to the "About" window in localized versions.
Cosmetic fixes for Mac OS X.
Support for the VST Enabler on Windows added.
Fixed crash if you close Audacity while the Preferences dialog is open.
Fixed duplicate-character bug in Mac OS X Label Tracks.
The recording level control on Linux now adjusts the IGAIN, rather than the playthrough level of the recording source.
Fixed bug that caused corruption to 16-bit stereo recordings.
Fixed bug that caused data loss if you deleted all tracks in a saved project and then open a new file into the same window.
Added support for alternate audio button order (in Interface preferences)
Added preliminary support for wxX11
Added fully transparent Windows XP icon
Fixed crash if you try to record (or play) and no audio devices exist, or if the audio device doesn't support the mode you selected.
Audacity no longer sets the process priority to high while recording on Windows. Users can still do this manually using the Task Manager.
Fixed bug that caused last ~100 ms of the selection to get cut off on Windows.
Fixed FFT Filter and Equalization effects dialogs.
Fixed bugs in Unix build system (DESTDIR in locale directory, choosing libsamplerate instead of libresample)
Support for LADSPA plug-ins on Windows added, and three open source LADSPA plug-ins ported to Windows (GVerb reverb, SC4 compressor, and Hard Limiter)
Audacity now supports LADSPA plug-ins on all platforms, and supports VST plug-ins through an optional LADSPA plug-in called the "VST Enabler", which you can download separately. Because of licensing issues, Audacity cannot be distributed with VST support built-in.
Mac OS X keyboard shortcut problems have been fixed.
Mac OS X audio muting problems have been fixed.
Mac OS X playback/recording cursor sync problems have been fixed.
Silence now displays a straight line again, instead of nothing.
Added a vertical ruler to the Waveform dB display.
Fixed crash in Change Pitch.
You can now Paste if nothing is selected.
Canceling an Import operation doesn't cause an extra error dialog to appear.
Audacity now handles filenames with international characters correctly.
Now outputs ID3v2.3 tags (instead of ID3v2.4), to be compatible with more MP3 players.
Minor improvements to build system on Unix systems.
Complete implementation of editable keyboard shortcuts.
Find zero-crossings.
Mouse wheel can be used to zoom in and out.
Multi-Tool mode.
Amplify using envelope.
Labels can store selections (like Audacity 1.0.0).
Effects
Repeat Last Effect command
Improved VST plug-in support
Most effects now have a Preview button
Compressor (Dynamic Range Compressor)
Change Pitch (without changing tempo)
Change Tempo (without changing pitch)
Change Speed (changing both pitch and tempo)
Repeat (useful for creating loops)
Normalize (adjust volume and DC bias)
Audio I/O
1-second preview command.
Looped play.
File I/O
Audacity 1.2.0 opens project files from all previous versions of Audacity from 0.98 through 1.1.3.
Open multiple files from the same dialog.
Use a text file to specify a list of audio files to open with offsets.
Updated user manual
Bug fixes
Project files with special characters are no longer invalid.
"Scratchy" noises caused by bad clipping are fixed.
Audacity no longer exports invalid Ogg files, and does not cut off the last few seconds of exported Ogg files.
Mono MP3 files now export at the correct speed.
Many incorrect results from the Envelope tool have been fixed.
The "Export Labels" command now overwrites existing files correctly.
The "Plot Spectrum" window displays the correct octave numbers for notes.
Several memory leaks are fixed.
Uses improved project file format. (Unfortunately reading previous formats, including 1.1.1, is not supported.)
Block files (stored in Audacity project directories) now use the standard AU format. Though some Audacity meta-information is in these files, they can now be read by many other popular audio programs as well.
Fixed some bugs relating to reading/writing audio files with more than 16 bits per sample.
Import RAW is functional again, with a simpler GUI but support for far more file formats. The autodetection algorithms are much more accurate than in 1.0.
Audio I/O
Completely rewritten audio I/O, with lower latency and minimal chance of buffer underruns while recording.
Resampling
Using high quality resampling algorithms, with the option of better quality for mixing than for real-time playback
Preliminary support for Time Tracks, for changing playback speed over time.
Many more bug fixes and new features
Drawing tool (with three different modes)
Vertical Resizing of stereo tracks is more fun.
Adjust selection by click-dragging selection boundary
Toolbar button context-sensitive enabling/disabling
Better zooming functionality (centers region)
Multiple ways to display the cursor position and selection
Snap-to selection mode
Drag tracks up and down
Align and group align functions
Cursor save/restore
Working history window
Effects
Effects broken down into three menus: Generate, Effect, and Analyze
Generate menu lets you generate silence, noise, or a tone
Nyquist support (supports plug-ins written in Nyquist, an interpreted functional language based on Lisp)
Localization
Improved localization support
More languages available
Language selection dialog on startup
Mac OS X
Support for more audio hardware
Support for full-duplex (play while recording)
Support for MP3 exporting using LameLib Carbon
Unix
Audacity now has a man page (it describes command-line options and how to set the search path)
File Formats
Uses libsndfile 1.0, which fixes some bugs and improves performance
Searching for Files:
On Windows and Mac OS, Audacity now looks for translations in the "Languages" folder and all plug-ins in the "Plug-ins" folder, relative to the program.
On Unix, Audacity looks for translations in /share/locale and looks for everything else in /share/audacity and also in any paths in the AUDACITY_PATH environment variable
Support LADSPA plug-ins on Linux / Unix
File formats:
New XML-based Audacity project format
Full Ogg Vorbis support now (importing and exporting)
Export to any command-line programs on Unix
Support for reading and writing many more types of uncompressed audio files, including ADPCM WAV files.
Toolbars
New toolbar drawing code; automatically adopts your operating system's colors
New toolbar buttons (Skip to Start, Skip to End)
New Edit toolbar
Toolbar buttons disable when they're not available
User Interface
Fully customizable keyboard commands
Autoscroll while playing or recording
New Ruler, used in main view and in FFT Filter effect
The waveform now displays the average value in a lighter color inside the peak values
Localization
Audacity can now be localized to different foreign languages.


* Compressor: new option to compress based on peaks, improved
attack and decay time support
* Mixer Board: improved design, more responsive meters and
now interacts fully with Track Panel in main windowAudacity 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.
(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.
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.
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 .
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.
(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.
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.
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.
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.
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).
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.
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.
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.
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.
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.
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.
(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.
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
(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.
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.
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.
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.
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.
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.
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.
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).
(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.
(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.
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.
(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
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.
(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:
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.
(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.
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
(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.
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.
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.
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.
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.
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.
(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 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.
2.1.3 is the last version of Audacity that will officially support Windows XP.
Pinned (fixed and centered) play/record head for playing and recording
New scrubbing features
Scrub Ruler
Scrub Toolbar (off by default, enable it at View > Toolbars)
Effects and Generators:
Effects, edits and other functionality are now not grayed-out when paused during playback or recording and thus the editing functions can be selected and performed
New Distortion effect (replaces Leveller)
Change Tempo and Change Pitch have new options to use the higher quality but slower SBSMS algorithm, which ensures the selection length does not change and no content is lost.
Click Track generator updated and renamed to "Rhythm Track" with improved sounds and new "Swing amount" control for unequal beat duration.
New Generator for
New and changed 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.
The shortcut for Play/Stop and Set Cursor has changed from SHIFT + A to the more easy to use X.
New and changed menu items
New Edit Menu items "Store Cursor Position" and "Select > Cursor to Stored Cursor Position" (during transport, the position of the playback or recording cursor is stored)
Edit > "Region Save" and "Region Restore" renamed to "Store Region" and "Retrieve Region" respectively
New Tracks Menu item "Type to Create a Label (on/off)" (turning it off prevents shortcuts accidentally creating labels in the focused label track)
New options and preferences
New option when exporting MP3 to mix to mono
New recording preferences for naming of recorded tracks
New Timer Record features:
Options on completion e.g. Save and/or Export, quit Audacity, shut down (on Windows).
More informative dialogs, including warnings on disk space.
Protection against accidental canceling.
(Linux) On Linux only, Audacity now supports FFmpeg/libav up to avformat/avcodec 57.x.x, which is compatible with current FFmpeg 3.x.x releases.
(Mac) On Mac, audacity.app is now added to /Applications/ directly rather than adding a folder there.
Audacity is now digitally signed on Mac and Windows (but not Windows XP).
After mouse down to drag a docked toolbar to a new docked or undocked position, the track focus is removed and the selected control loses its focus border even though that toolbar still has focus. When dragging or resizing an already undocked toolbar, the selected control similarly loses its focus border.
Some interface text or markings remain in black when using High Contrast light-on-dark themes, so cannot be read properly.
Keyboard Preferences: Window-Eyes doesn't read the key bindings when View by Tree is selected, and may not always read the bindings in other views. VoiceOver and Orca do not read the key bindings at all. You could export the bindings, modify them in a text editor then import the modified list.
Spectral Selection Toolbar:
You can't enter a new low frequency first if it is above the current high frequency - in that case, you must enter the new high frequency first.
If you change low and high frequencies to kHz, then typing or incrementing values in the High Frequencies box has unpredictable results.
It is not possible to use the keyboard to move the cursor or selection region to an arbitrary position when playing or recording. However you can use the [ or ] shortcuts respectively to set the left or right boundary of the selection at the playback or recording position ( https://manual.audacityteam.org/man/edit_menu_select.html#left ). Different Scrubbing modes may also be started using shortcuts or the Transport Menu, but there is no keyboard interface yet to control scrubbing. Scrubbing may be started by shortcut even if the pointer is in the waveform, although the Status Bar messages don't refer to moving the pointer to Scrub.
(Windows):
In certain parts of the main window, NVDA does not speak typed characters (JAWS and Window-Eyes are not affected):
In the main window, not speaking a character if it is a command for example, j,k,[ or ]
In a label track, not speaking characters typed into a label.
(OS X/macOS):
Audacity is not yet fully Retina-ready. It is known that the Track Control Panel appears fuzzy. Please let us know of any other issues. Retinizer can no longer be applied to Audacity. If Retinizer is applied to previous Audacity this will prevent the export format being changed.
Selection is not in the first control of Generators, Effects or Analyzers. In most effects the selection is invisible and one TAB puts selection in the Manage Button. In Change Speed the selection is "Current Length" and in Change Pitch the selection is the first octave.
If you apply a real-time preview effect while focus has remained in Audacity, the effect loses focus. If you apply a real-time preview effect after task switching away from and back to Audacity, the effect will go behind the project window. The effect may be brought back to focus in both cases with ALT + F6.
It is not possible to move between the main Audacity window and some VST and Audio Unit effects using the ALT + F6 or ALT + SHIFT + F6 shortcuts when the effect is in Graphical Mode. You can use the "Manage" menu then Options... to change the effect to textual mode.
(OS X/macOS) Issues with VoiceOver: Unfortunately, current Audacity is not accessible for users of VoiceOver for the reasons given below. This was also the case for releases starting from Audacity 2.1.1. However, an accessible version of Audacity 2.1.1 is available on our Mac OS X downloads page. The name of this accessible version is "2.1.1-screen-reader" (DMG and ZIP downloads are available). It is hoped that future versions of Audacity will be accessible for users of VoiceOver.
(reported on OS X 10.9.x) After exporting, the black accessibility area is trapped in the Tooldock area, so there is no way to read the tracks. Workaround: Save as a project, close the project then reopen it. You can then navigate the tracks with VoiceOver.
If you use arrow keys to navigate the Timetext controls in Selection Toolbar, VoiceOver stops reading. Workaround: Use Control-Option-W
When you TAB forwards from "Audio Position" in Selection Toolbar, the "Selection End" or "Selection Length" radio button is read as "Selection Start". When you use COMMAND + F6 or COMMAND + SHIFT + F6 to move directly into "Selection End" from another toolbar, the button is read as "Selection Start".
Mixer Toolbar input/output sliders are not read, but just described as "multiple indicators". The "Graphic EQ" and vertical sliders in Equalization *are* read.
Metadata Editor table not read.
Edit Labels dialog not read.
In the "Edit Chains" window, only the first command in the "Chain" list is read, and it is only read when first accessed. In the "Select Command" window for inserting a new command in a Chain, commands in the table are not read.
"Manage Curves" table in Equalization not read.
GNU/Linux:
(Linux Ubuntu) Under Unity, keyboard shortcuts are not visible in the Audacity menus. Keyboard shortcuts are visible if you install the classic GNOME Flashback interface or under Unity if you open Audacity from the terminal with
env UBUNTU_MENUPROXY=0 audacity
Audacity will now ship with src/audacity.desktop.in set to UBUNTU_MENUPROXY=0 so Audacity compiled from source will show shortcuts in the menus and will have its own menu bar in the application. It will remain up to Ubuntu whether they use this desktop file in packaged versions of Audacity.
Access keys mostly do not work except for radio buttons and checkboxes.
(Linux with Xfce desktop) It is not possible to move forward through modeless windows, undocked Toolbars and the main project window using ALT + F6. You may move backward using ALT + SHIFT + F6, but focus may get trapped in windows or undocked toolbars.
(Linux) It is not possible to TAB through the search box in Keyboard Preferences. However, as long as the "Tree" or "Name" button is selected, you can use DOWN arrow to move out of the Search box into the list, then TAB into the lower controls.
(Linux) Playing or recording then stopping causes the currently focused track or tooldock area to lose focus. Some shortcuts for example those for Tools Toolbar will then not work until focus is restored. Workaround: To restore focus, deliver a mouse click in the interface or create a shortcut for Reset Toolbars and use that shortcut.
(Linux) TAB unexpectedly navigates out of the current tooldock area instead of staying inside it, and CTRL + F6 from Selection Toolbar and SHIFT + CTRL + F6 from the Tracks table do not navigate to the upper tooldock area but leave focus in the previous toolbar. However you can use the TAB navigation behavior described above to access the upper tooldock area.
(Linux) The shortcut to "Move backward from toolbars to tracks" does not cycle from the audio track to upper tooldock, only to Selection Toolbar. The shortcut to "Move forward from toolbars to tracks" does not cycle from Selection Toolbar to upper tooldock, only to the audio track.
(Linux) Issues with Orca:
Audacity tracks are not read.
Not all toolbar controls are read, examples being Timetext controls, Project Rate and controls in Device Toolbar.
Not all controls in Preferences are read.
Control labels for Vamp and VST plugins are not read.
Control labels for Nyquist plugins are read inconsistently in older version 3 or earlier plugins (Version 4 seems to read more consistently).
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.
(Mac and Linux) Audacity will not launch if the temporary directory is set to a USB or hard drive formatted with FAT16, FAT32 or exFAT. To make Audacity launch again, open the audacity.cfg settings file. Underneath the [Directories] line, change TempDir to any drive or partition formatted with the operating system's native file system (MacOS Extended (HFS+) on Mac, or ext3/ext4 on Linux).
If you launch Audacity by COMMAND + Space (Spotlight Search) then ENTER (or double-click the search result), a false error prompt appears "The application "Audacity.app" can't be opened" when in fact it will open anyway.
(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)
(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 and MacOS) On a few machines, Timer Record may not respond to a request to stop the recording or may carry on recording past the scheduled end time. 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.
(Windows) Some devices that used to offer multiple recording channels in Audacity without ASIO may now only offer mono or stereo recording instead of the expected number of channels. Usually the multi or similar device only has 2 channels instead of the expected number. Occasionally the multi device is missing, leaving only two-channel devices to choose from. These devices have been reported:
Alesis Multimix-8 USB
DSP2000-CPort
M-Audio Delta 66
Motu 896 AD/DA FW
Tascam US 1641 and US 1800
If you experience this issue please report make and model number of the device, your operating system (for example, Windows 7 Service Pack 1) and the device driver version number you are using. It is possible that more than stereo recording may be possible if you can find earlier drivers that are still compatible with your version of Windows, or if you try the Windows WASAPI host in Device Toolbar. See Multichannel Recording for a list of devices reported to record multi-channels into Audacity without ASIO.
(Windows) There may be substantial delays drawing the waveform in longer projects of an hour or more. The main problems are with opening saved projects that were fitted to the window, and fitting already zoomed in projects to the window, such as a new recording. Additionally:
Opening and closing large projects one after the other may eventually cause project opening to slow significantly
Import or effect progress dialogs may stall "whited out" for a few seconds after the progress bars complete before the waveform is drawn.
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.
(Windows) LV2 effects can only be used in a Chain at their default settings.
Noise Reduction" does not yet support storing its parameters in a Chain. Noise Reduction will run at its last used settings if used in a Chain.
Dynamic loading (as in default Audacity ./configure) requires building against the FFmpeg project - it will not build against the libav* headers from the libav project. Workarounds: Configure Audacity with --disable-dynamic-loading. If dynamic loading is required, build against FFmpeg instead of libav, or you can build against libav if you remove the "#define IS_FFMPEG_PROJECT 1" line in src/FFmpeg.h.
Audacity may still build against no-longer-supported FFmpeg versions (such as FFmpeg 0.8 which is system-installed on Debian Wheezy), but configuring with --disable-dynamic-loading will be necessary. FFmpeg 0.8 has at least one known issue in Audacity 2.0.6 or later: mono WMA files export with no audio data. This issue will not be fixed given FFmpeg 0.8 is no longer supported by Audacity 2.0.6.
Building against self-compiled FFmpeg 2.2.2 with --disable-dynamic-loading the only argument fails on Ubuntu 13.10 with "undefined reference to 'av_codec_is_encoder'". Workaround: Configuring with --disable-dynamic-loading and --with-lib-preference="local" (or at least --with-ffmpeg="local") may build successfully, but may not disable Libraries Preferences. The best solution may be not to disable dynamic loading.
You can remove any duplicates that don't run by using Effect > Add / Remove Plug-ins... then click OK. This does not remove the duplicates from the Plug-in Manager's list. Alternatively you can remove all unwanted duplicates, whether you have deleted the old Audacity installation folder or not, by deleting the file pluginregistry.cfg in ~/Library/Application Support/audacity/.
If you delete the Audacity folder from a previous installation, remember to move any optional plug-ins you added to its plug-ins folder to the new Audacity Plug-Ins folder at ~/Library/Application Support/audacity/Plug-Ins.
Effects, Generators or Analyzers plug-ins (except Nyquist) that are no longer available remain listed in the menus until you open the Plug-in Manager. The plugins will then be removed from the menus after restarting Audacity. This also applies to previously shipped plug-ins that are no longer available in current Audacity, such as Hard Limiter.
(Windows) The Plug-in Manager does not properly disable the SC4 effect. It will remain disabled during your current Audacity session but the next time you re-open Audacity the SC4 effect will be shown as enabled and will be available for use.
When you import a preset into an Apple Audio Unit, that preset's settings are applied by the effect without the effect controls updating to the new settings. Other AU effects may ignore presets when you import them. To be sure the imported preset you want to use is loaded into the effect, select it from "User Presets".
LV2 plug-ins cannot be added to Chains if the corresponding LADSPA version of the same plug-in is also enabled. Audacity will in this case show two copies of the LADSPA plugin in Select Command.
(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.
(Windows)
Betabugs PhaseBug and PhaseBug Mono hang the Add/Remove Plug-ins dialogue on high CPU usage after Enable and OK. Try Audiocation Phase instead, or use Audacity 2.0.6 from Legacy Windows on the Audacity Website if you need to use these Betabugs plugins.
DFX Geometer from http://destroyfx.smartelectronix.com/ may crash Audacity when loading the effect from the Effect Menu. This usually happens only once or twice when the effect is first loaded in the operating system session. Once the effect is open in Audacity it should work properly.
DISTRHO Mini Series VST's from crash Audacity in graphic mode but will run in text mode (open the Effects Preferences and uncheck "Display VST effects in graphical mode").
MDA Tracker may crash if the effect is applied while playing audio or if stopping and starting playback.
ReaPlugs plugins do not see user presets which were saved in Audacity 2.1.0 or 2.1.1.
You must restart playback to hear the result of enabling or disabling ReaEQ tabs. "Enable" or "Active" checkboxes work correctly while playing in other ReaPlug effects.
SimulAnalog Guitar suite plugins may crash Audacity at the default Buffer Size of 8192. For the most stable results, use the Manage button in the effect, then Options... and change Buffer Size to 8000. If crashes persist, use the effect by just applying it, without playing audio while the effect is open.
Waves v5 may cause Audacity to hang if you select it in the "Register Effects" dialog then click OK.
(OS X)
The following plug-ins may cause Audacity to crash if they are used after starting Audacity.
AUNBandEQ
AURoundTripAAC from "Apple audio mastering tools" (this requires OS X 10.6 or later so may crash on 10.4 or 10.5).
AU
Digitech RP250 (effects pedal)
Native Instruments B4 and Native Instruments Guitar Rig v3 and v4 (v5 does not have this issue)
PredatorFX
Waves Version 7 and 8 AU: These effects may crash Audacity on quit, after project data has been saved. Waves Version 9 AU should now work correctly.
Workaround: If Audio Units are not needed in Audacity, restart Audacity then open Audacity > Preferences... and choose "Effect". Under "Enable Effects", uncheck "Audio Unit", snd press OK. If Audacity won't launch you can instead add lines: to the audacity.cfg settings file. Alternatively, look in the Mac Crash Report for the AU plug-in that crashed, move it from <Your Home>/Library/Audio/Plug-Ins/Components or /Library/Audio/Plug-Ins/Components then restart Audacity.
AUPeakLimiter when opened only shows its title bar or shows a visually corrupted title bar containing black pieces from the interface. To correct the interface it may be possible to click on the plugin controls or to click the Apply button then undo the effect.
Plot Spectrum and Contrast cannot currently be removed from the Analyze Menu.
(Linux) On Ubuntu with the Unity interface enabled in audacity.desktop, previewing a built-in or Nyquist effect or generator in one project then opening the same effect or generator in another project will cause a crash. There may sometimes be a crash if opening any built-in or Nyquist effect or generator in another project when such an effect is already previewing.
(Linux) Opening the "Help on the Internet" dialog from the Help menu or from Contrast... creates an additional empty and unclosable dialog, and the real help dialog asserts when closed. Be sure to press "Continue" in the assertion error dialog. If you press "Stop", Audacity will force quit.
(Linux) Sliding Time Scale / Pitch Shift may crash randomly in Audacity built with pre-2.0.2 versions of libsbsms. This may occur for example in the Ubuntu package of Audacity 2.0.5 on Ubuntu 14.04. Workaround: Build Audacity configured --with-sbsms="local", or use the Audacity package in Ubuntu 14.10 which uses libsbsms 2.0.2-1.
(Mac) Typing or pasting values in the parameter boxes will either not change the parameter applied or set it to zero, as shown by the slider positions. Workaround: User the sliders to set effect parameters. To do so using the keyboard, CTRL + F7 if necessary to enable Full Keyboard Access, then TAB into the slider and use arrow keys or Page Up/Down.
(OS X/macOS) Many items in the Generate, Effect and Analyze menus (except for example Plot Spectrum) cannot by default be applied/closed by ENTER on the keyboard unless you first press TAB once. An alternative which avoids having to use TAB is to CTRL + F7 once to enable Full Keyboard Access for all applications. In any case, without this setting enabled, it will be impossible to navigate dialog buttons or Audacity Preferences using only the keyboard.
(Windows and Linux) Some LADSPA "Blop" plug-ins ( http://blop.sourceforge.net/index.html ) are reported to crash in Audacity on Linux Debian. On Windows, the Blop plug-ins included in http://opensourcepack.blogspot.co.uk/p/ladspa-for-win32.html can also crash, but this can be avoided if you ensure the "blop_files" folder contains the necessary "_data.dll" files for the plug-ins and that this folder is present in the Audacity "Plug-Ins" folder.
(Windows and Mac OS X) The SC4 compressor shipped with Audacity crashes if used in a Chain.
(Windows) Very rarely, Audacity may show no built-in effects, generators or analyzers after upgrading from an earlier Audacity 2.1.x version. If this happens, open Effect > Add / Remove Plug-ins..., enable the built-in effects if not already showing as enabled, then click OK.
(Windows) LADSPA Multiband EQ may not be visible in Effect menu (occurs on Windows XP), and crashes soon after opening
Cut Preview only plays the upper track of multiple selected or Sync-Locked tracks.
The following effects remove envelope control points: Change Speed/Pitch/Tempo; Equalization; Noise Removal; Sliding Time Scale/Pitch Shift; any Nyquist effect in the Effect menu. Workaround: Use Tracks > Mix and Render to apply the envelope to the waveform before applying the effect.
The Reverse effect retains the control points, but does not move them.
Set Rate in the Audio Track Dropdown Menu does not work correctly when there is a separate clip in the track or when there are envelope points. Clips will cause Set Rate to shorten the audio too much or insert white space into it. Envelope points will not move in response to Set Rate.
You may not be able to drag a clip into another track if the clip's starting position overlaps a clip in the target track. As a workaround: release the mouse when the horizontal drag is complete, then drag vertically.
Boundary Snap Guides often do not appear when snapping to Split Lines created with Snap To enabled at hh:mm:ss + milliseconds or higher resolution. You could label the split lines or turn Snap To off to see the guides.
When pasting audio into tracks with envelope points, the envelope points may move in unexpected ways, so causing unwanted amplitude adjustments.
(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.
(Mac OS X) When exporting using (external program) using any encoder, or using "Custom FFmpeg Export", you must agree to create and replace an unwanted "NoOverwritePrompt" file before you can export. The exported audio file is correct.
(OS X) If you include / in the file name when using File > Export Audio... or Export Selected Audio..., the text before the / will be missing from the exported file name. As a Workaround: add the required file name to a label then Export Multiple.
(macOS) The Export Multiple progress dialogues may be hidden behind the Export Multiple window for each file after the first one. Files are still exported normally, and you can move the Export Multiple window to one side to view the subsequent progress dialogues. The confirmation dialogue listing the exported files appears normally on top of Export Multiple after export completes.
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 FFmpeg 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.
You can change or remove the extension in the export dialogue, or if you leave the extension unchanged, the extension of the exported file will be changed automatically to the correct default for the chosen header.
On Linux, .aiff extension will be offered after project save or audio import for all formats, not just for "Other uncompressed files". For other than "Other uncompressed files", the extension will be wrongly exported as AIFF unless you change or remove the extension, but the encoded data will still be correct.
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 Foobar2000 for this purpose.
On a fresh installation of Audacity or initialized Preferences, the "FFmpeg-compatible files" filter cannot be used to make FFmpeg import native Audacity formats such as WAV, AIFF or MP3. Similarly on macOS, the "QuickTime files" filter cannot be used to make QuickTime import MPEG-4 files instead of installed FFmpeg.Workaround: Open Preferences and click "OK" then the FFmpeg and QuickTime filters will work as expected.
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".
When exporting using the "Other uncompressed files" option, the extension of the exported file is forced to the default for the format. For example it is not possible to export AIFF files with .aif or .aifc extension except by using the "AIFF (Apple) signed 16-bit PCM" option instead.
(Linux) When using Export Multiple, asterisks (*) or question marks (?) in track names or labels are wrongly rejected as illegal characters. As a Workaround you can force use of * or ? by exporting each region with File > Export Selected Audio... instead.
(Linux) After opening a sufficiently long audio file, opening a second file of any size might lead to locked GUI/console messages until the 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) 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 Pre El Capitan) iTunes files cannot be opened from Media > Music in the Sidebar 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) When exporting using the "Other uncompressed files" option, the "Save As:" dropdown always offers .aiff extension even when other headers are chosen. However the file will be exported in the correct format with the correct default extension for that format, even if you don't change the Save As extension from AIFF.
(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 here.
(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 FFmpeg 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 Extended Import Preferences. 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 reading it directly, 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 Quality Preferences. To fix any files that have already been affected, see this Forum topic.
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 IDTE (or use Windows Media Player 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 Metadata Editor 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".
ID3 v2.4 tags in imported MP3 files are not seen and will be removed on export.
Audacity writes both ID3 v2.3 (TYER) and v2.4 (TDRC) tags for "Year", but any applications that require the older TYER on its own (without TDRC) will not see "Year" in Audacity-exported files. The id3 command-line application on Linux is one example.
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.
When importing a MIDI track, the channel selection buttons to left of the track are not currently available.
On Linux, TXT and XML exports default to the root of your Home directory.
(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.
Performing an action which can be undone, making some types of display change then undoing the action will unexpectedly undo the display change as well. Examples of display changes that will be undone are changes to track height, track view mode or per-track Spectrogram Settings.
(Linux) Audacity currently does not support being extended across multiple displays, so that Audacity is visibly straddled between monitors. If Audacity is quit when the greater part is on the primary monitor, Audacity reopens centred on the primary monitor. If Audacity is quit when the greater part is on the secondary monitor, Audacity reopens on and at left of the secondary monitor.
(Mac) Copying or cutting from text boxes in file save dialogs using COMMAND + C and COMMAND + X respectively does not work. You can however right-click or CTRL-click and choose the option to Copy or Cut.
(Mac) Pasting into file save dialogs using COMMAND + V has been restored with some limitations.
COMMAND + V can only paste into the "Save As:" box even if another box has focus. You can use right-click or CTRL-click to paste into other boxes.
The entire contents of the box are replaced with the pasted content, ignoring the selection cursor or partial text selections.
(MacOS) The "Window" menu does not currently provide a list of open windows for moving between projects. Use the Mac shortcut COMMAND + Accent (`) instead to navigate open project windows. You can customize this key binding at System Preferences > Keyboard > Shortcuts, then choose Keyboard in the list on the left.
(OS X and Linux) In some locales, Preferences text may be truncated or overlapped, or dropdown boxes truncated.
(OS X) The "Cmd - Wheel - Rotate" mouse binding does not zoom in unless you modify the default System Preferences. ** On OS X 10.6 or later, go to Universal Access / Seeing / Zoom / Options and uncheck "Use scroll wheel with modifier keys to zoom".
Prior to OS X 10.6, go to "Mouse and Keyboard" and uncheck "Zoom using scroll ball while holding Command".
(Windows) The "Files Missing" warning always restores maximised windows to smaller size.
(macOS) If upgrading from Audacity 2.1.1 directly to 2.1.3 release or later, the Audacity Title Bar and window buttons may be hidden under the Menu Bar. Workaround: Use Window > Zoom or restart 2.1.3.
After changing language in Preferences, a few parts of the interface don't change until Audacity is restarted.
Audacity has several weaknesses in preserving the context of the audio being worked with:
If playback scrolls, pressing Stop leaves the waveform where it stopped and the cursor or left selection edge invisible. Pressing Play to resume then scrolls the waveform to start at the playback start point, hiding the previously visible context before the cursor or left selection edge. Workaround: Left arrow after Stop centers the view at the cursor position. or move the left or right selection edge into view with the edge centered, so can show context that has been moved out of view.
Zoom to Selection shows none of the surrounding context
Zoom Normal doesn't always keep the selection or cursor on screen.
By default, all audio in the project is selected if an action requiring a selection is requested when there is no selection (this behavior can be turned off in the Tracks Preferences). If enabled:
You can always apply effects to the whole project in one step, but you can also delete audio in all tracks if you press Delete when there is no selection. That is easy to Undo, but we aim to tweak this behavior and make it more customizable in a future Audacity.
A few items in Edit menu are incorrectly grayed out if no track is selected.
Crashes on incorrect behaviour on quit:
(Windows) Audacity crashes after quit if quit from the Windows 7 Task Manager and "About Audacity" is open. If you save changes to a project, these changes are saved correctly.
(Windows) Audacity cannot be quit from the Task Bar icon if "About Audacity" is open.
(Linux) Any quit by any method produces "OS_IS_BAR (bar)" and "GTK_IS_WIDGET" (widget) assertion errors in the terminal if Audacity is launched from there.
If Sync-Lock Tracks is enabled, there is no indication of the cursor in the Sync-Locked tracks.
Mouse Bindings are not currently configurable by the user.
We're aware that some error messages in Audacity are not as helpful as we would like them to be. If you see a cryptic error message from Audacity, try a search (or ask) on https://forum.audacityteam.org/
When using TAB to move into a TimeText control (for example, in a Generator, Change Speed or Selection Toolbar) the first character is highlighted instead of the first non-zero character.
(Linux) If Audacity is left open but without focus, its CPU use will rise slowly until all available system CPU is consumed. This is a bug in wxGTK 2.8.10 (not previous versions) - see http://trac.wxwidgets.org/ticket/11315 . This issue can be fixed by updating to wxGTK 2.8.11 or 2.8.12.
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.
You can instead change the frequency range and save a new label in the same time selection then click in each label to display its frequency range, but if you TAB between labels in the same time selection all labels will show the frequency range of the last added label.
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".
(OS X) Audacity set to "System" language in Interface Preferences as in a new installation or after preferences reset will always be in English language irrespective of the Mac system locale. Workaround: Follow the steps at https://manual.audacityteam.org/o/man/faq_about_audacity.html#language to change the Audacity language in Interface Preferences.
(Windows) Audacity must be explicitly set to use Galician or Valencian in Interface Preferences to display those languages. Setting the Windows Region and Language format to Galician or Valencian and Audacity to "System" language will only display Audacity in English.
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) Meters may not respond immediately to playback which could cause them to report incorrect peak level or not display clipping.
(Windows and Linux) The Select All (CTRL + A) and Deselect All (CTRL+ SHIFT+ A) shortcuts may not work when focus is in Mixer Board. Workaround: CTRL+TAB to return focus to the main project window, then use the shortcuts there.
Sound Activated Recording mode is disabled if there is no displayed recording meter (neither Recording Meter Toolbar or Combined Meter Toolbar). Recording will proceed regardless of the Sound Activation Level threshold and the actual recording level.
The level of an active recording can be changed by the Mixer Toolbar sliders in any other open project windows.
Timer Record warns of insufficient disk space to save the recording as a project, but does not warn about sufficient space to export. If space is insufficient to export, the exported file will be shortened to fit the available space.
(Mac OS X) The default 100 ms "Audio to buffer" setting in Audacity's Recording Preferences (which also affects playback) is too high, especially for many USB or firewire devices or if using Soundflower. 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. Also see: How can I prevent clicky recordings on Mac OS X?.
(OS X and Linux) Audacity now works very well with JACK, 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.
On Mac, Audacity may freeze if JACK is launched by QjackCtl then Audacity is launched. Workaround: Use JackPilot to launch JACK, or launch QJackCtrl after Audacity and JACK are running.
(OS X and Linux) PortAudio's default latency values which are used when recording with software playthrough are much lower than Audacity's default "Audio to buffer" setting. This may cause playthrough or recording glitches when recording with software playthrough enabled, especially when using pulse on Linux. Workaround for Linux: record from an (hw) device instead if software playthrough is required.
(OS X) Playback to Bluetooth headsets gives an error. Workaround: Revert to Audacity 1.3.3 (this may only work with stereo headsets), or use Soundflower to send the Audacity output to an audio application that works with the headset.
(OS X) The "Hardware Playthrough" option in Recording Preferences is currently unsupported on all known Mac hardware. Try the "Software Playthrough" preference instead. If that does not work, the third-party LineIn application also provides software playthrough.
(Windows and OS X) Launching Audacity or using Devices Preferences or Device Toolbar to change host or device resets the left/right balance of connected audio devices to center. Workaround: on a few Windows machines choosing Windows WASAPI host in Device Toolbar or Devices Preferences might prevent the balance reset.
(Windows) When a USB device is connected, the Mixer Toolbar input slider for that device (and sometimes for any device) may wrongly appear active even though it has no control over the device's input level. Sometimes the Audacity slider will apply a software gain to the level (which is dangerous as it will only make the same clipped input quieter rather than stopping the clipping). Sometimes the Audacity slider will not affect the input volume at all. Workaround: use the slider in the Windows Control Panel where available, or any gain control on the device, or reduce the output being sent to the device.
(Windows) When you install Audacity for the first time or launch it after resetting Preferences Audacity will choose the named recording and playback devices that are the current Windows default devices, rather then the MME "Sound Mapper" devices which are permanently mapped to whatever the current defaults are. Workaround: If you lose playback audio or only record silence after changing the Windows default devices, use Device Toolbar to change the devices as needed, then Audacity will remember them.
(Windows) Audacity is incompatible (or not fully compatible) with some professional sound cards or audio devices, and may crash or have limited or faulty functionality. Occasionally, this may be true of some AC97 devices built into the motherboard. Workaround: make a different sound card your default when using Audacity, but please e-mail the following details to our feedback address:
Your version of Windows and Service Pack
Name, model number and driver version number of the sound card or device.
Note: Multichannel Recording in Audacity is often not possible with professional devices unless you compile Audacity with ASIO support.
Adding or removing an external audio device while Audacity is open will not be automatically reflected in the list in Device Toolbar or Devices Preferences. On Mac, unplugging then replugging an external device will give "error while opening sound device" (on Linux, pressing "Record" a second time will remove the error). Workaround: Use Transport > Rescan Audio Devices.
If you move tracks while playing for example using the Audio Track Dropdown Menu, playback does not change, and if you use that menu to Swap Stereo Channels during playback, the left channel is silenced. Playback responds to the other commands in that menu.
Play-at-Speed slider: Change of playback speed is no longer automatic after you move the play-at-speed slider. To change speed, move the slider, then click the green button to left of the slider to play at the new speed.
Timer Record cannot maintain scheduled duration if system clock changes
(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.
(Windows Vista and later) The "Windows WASAPI" host supplies playback, plus a "loopback" device for recording computer playback and experimental support for physical inputs.
Not everyone will necessarily experience all or any of the issues noted below, but please report any WASAPI issues not covered below to our feedback address.
When Windows is installed in a language using Unicode characters (such as Russian or German), WASAPI host in Device Toolbar shows incorrect characters for the names of Playback and Recording subdevices.
Although volume slider support for WASAPI is implemented, on some devices the Mixer Toolbar recording volume slider will be grayed out when selecting the Windows WASAPI host. Even if the Audacity recording slider is available, the sound device may not support Audacity adjusting its system playback or recording sliders. To control loopback recording on those systems, try adjusting the playback level of the audio player.
On many other devices, the Audacity recording and playback volume sliders will be "linked" together when loopback recording with playback and recording device set to the same device. Adjusting either slider will often adjust the sound you hear without affecting the achieved recording level, enabling you to record without listening. If "silent" recording does not work, mute the "Device" slider at far left of the Windows "Volume Mixer" or plug in speakers or headphones and turn off their volume.
If the achieved loopback recording level is too low, try turning up the volume in the application playing the audio.
Adjusting linked sliders during loopback recording may cause audio breakup or recording glitches.
Loopback recording may fail "error opening" when Audacity is set to record in mono.
You will normally need to start playing the loopback stream (or to have previously played some other audio in the application you are using for playback) before starting loopback recording in Audacity.
Changing Default Format or Exclusive Mode settings in Windows Sound while Audacity is open may cause "error opening" when starting to play or record. Try Transport > Rescan Audio Devices or restarting Audacity.
If you receive dropouts or poor quality when recording, try setting the Audacity to 44100 Hz and setting Default Format in Windows Sound to 44100 Hz, with both "Exclusive Mode" boxes unchecked. Other rates may work, providing the same rate is set in both places. The most likely place for a dropout is within the first second or two of recording.
Physical inputs may fail "error opening", especially when overdub recording. Try setting Audacity project rate to 44100 Hz then for both the playback and the recording device in Windows Sound, ensure both "Exclusive Mode" are checked (enabled). You can also try setting Audacity Project Rate to the same as Windows "Default Format" with both Exclusive Mode boxes unchecked.
Latency when overdubbing may substantially increase shortly after starting the recording.
"Audio to buffer" in Recording Preferences cannot be used to adjust recording latency.
Non-looped playback plays the selection minus the "Audio to buffer" (for example, standard playback may fail to play the buffered length at the end of the selection). Setting the buffer setting to zero when using WASAPI host may make it more likely that audio will play fully.
(macOS) The button order in the "Save Changes?" dialog changed in 2.1.2 to a less Mac-like sequence of Cancel, No. Yes.
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.
Projects created by Audacity 1.1.x or earlier are no longer supported. Workaround: Export each project track as WAV using the appropriate legacy version of Audacity, then import the WAV files into current Audacity.
Projects created by Audacity 1.2.x are partially supported - there is a possibility Audacity could corrupt them. Please make a backup copy of the project's .aup file and _data folder to a new folder before opening the project in this version of Audacity. Once you save the project in this version, it cannot be opened in 1.2.
Projects created by previous versions of Audacity may contain audio "block files" longer than the project format allows. Reopening such projects in previous versions might or might not result in deletion of the overlong audio. Audacity has been provisionally fixed so that it can no longer create or delete overlong files, but it cannot read any such files it encounters. If overlong files are found, a "Problems Reading Sequence Tags" message will display .
If you continue with the offered repair then choose "Continue without deleting" in the Orphan Block File(s) dialogue, the overlong files will be retained as "orphans" in the project's _data folder but will appear as silence in the track(s).
As long as you choose "Close project immediately" in the Orphan Block File(s) dialogue, the project will quit and will not be changed in any way.
If you encounter the "Problems Reading Sequence Tags" message, please write to our feedback address with a copy of the .aup file and the log as found at Help > Show Log.
Time Track warp points saved in a 2.0.3 or later project will be preserved if opened in previous Audacity versions, but playback and display will be incorrect.
Horizontal scrolling is permitted during Scrubbing and Seeking although it is unhelpful for the waveform to shift while in Scrub mode. If you are using a Magic Mouse on MacOS (or other mouse with a control surface) be careful not to brush the mouse surface during Scrub, or try temporarily disbling horizontal scroll in the mouse's preferences.
Scrubbing or Seeking with Pinned head:
To Scrub at normal 1x forwards speed without using the mouse wheel it is always necessary to move the mouse to the end of the window, even if the project is shorter than the window width. To backwards play at 1x, move the pointer to the start of the project. You can Seek at 1x with the pointer in the center of the window.
If you try to forwards scroll-scrub in a less than half-width project by moving the mousewheel downwards to reduce backwards speed, moving the pointer to the end of the window will then achieve less than 1x speed. In that case, move the mousehweel upwards.
You cannot easily forwards-scrub from the start of the audio or backwards-scrub from the end of the audio because playback might cease before the pointer moves far enough to change playback direction. Enabling "scrolling left of zero" in will make scrubbing easier for these use cases.
Starting Scrub using Scrub Ruler, or then changing to Seek by clicking or dragging in Scrub Ruler, changes any pre-existing waveform selection or cursor position
(MacOS) If Scrub Toolbar is enabled and you remain hovered over a button after clicking it, the button tooltip may incorrectly change to "Hide Scrub Ruler" (or to "Show Scrub Ruler" if Scrub Ruler is turned off).
(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 keyboard shortcut alternatives for the buttons instead.