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

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.

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

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.

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

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

(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.==

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.

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.

PredatorFX

AURoundTripAAC from "Apple audio mastering tools".

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 Install VST Effects 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 latest version of the LAME MP3 encoder.

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.

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.

Unexplained crashes or corrupted audio occurs (note this can happen if the computer is low on memory or disk space).

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

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

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

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, 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

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

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.

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

• Tags other than the seven default Metadata Editor 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".

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

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

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

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

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.

• The input slider in Device Toolbar 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 Device Toolbar 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 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.

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

• The Audacity output slider may also be grayed out, or if not, will not affect the system output level or 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 any may cause glitches in the recorded audio.

• "Audio to buffer" in Recording Preferences cannot be used to adjust recording latency.

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.

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

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.

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.

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.

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.

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.

Unexplained crashes or corrupted audio occurs (note this can happen if the computer is low on memory or disk space).

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.

(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".

(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 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 Linux, where system locale uses comma as decimal separator) Built-in tone and noise generators may produce silence if used on audio that has had a Nyquist effect applied to it. Workaround: Run Audacity in English language, 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.

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.

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

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

• Tags other than the seven default Metadata Editor 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".

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

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

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

(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

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

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

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 Project Rate 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.