Difference between revisions of "Release Notes 2.0.6"

From Audacity Wiki
Jump to: navigation, search
m
m (Text replace - "http://lame.buanzo.org" to "https://lame.buanzo.org")
 
(29 intermediate revisions by 3 users not shown)
Line 1: Line 1:
 
{{Template:Audacity Devel}}
 
{{Template:Audacity Devel}}
{| style="font-size:120%; background-color:#ffffff; padding: 0.5em; border:3px solid #FF8800; margin: 10px 10%"  
+
<!--{| style="font-size:120%; background-color:#ffffff; padding: 0.5em; border:3px solid #FF8800; margin: 10px 10%"  
 
|-align="center"
 
|-align="center"
 
|[[Image:Example.png|52px|center]]  
 
|[[Image:Example.png|52px|center]]  
 
'''In preparation'''
 
'''In preparation'''
 
|}
 
|}
<includeonly>[[Category:User Work in Progress]]</includeonly>
+
<includeonly>[[Category:User Work in Progress]]</includeonly>-->
{{Introrel|'''Audacity 2.0.6 is expected to be released shortly.''' ||[[Release Notes]] for previous versions
+
{{Introrel|'''Audacity 2.0.6 was available from 29 September 2014 until 28 March 2015.''' ||[[Release Notes]] for previous versions
 
* [[Bug Lists]] - complete Audacity Bugzilla database}}
 
* [[Bug Lists]] - complete Audacity Bugzilla database}}
 
{{hint|1='''Tip:''' You can use {{shortcut|CTRL + F}} to search this page for different words to do with the issue you are looking for. Use {{shortcut|Command - F}} on Mac.}}
 
{{hint|1='''Tip:''' You can use {{shortcut|CTRL + F}} to search this page for different words to do with the issue you are looking for. Use {{shortcut|Command - F}} on Mac.}}
 
__TOC__
 
__TOC__
 
 
{{advice|1='''FFmpeg updated for 2.0.6:'''
 
{{advice|1='''FFmpeg updated for 2.0.6:'''
* Users upgrading to Audacity 2.0.6 who had FFmpeg installed previously will see a notice that FFmpeg needs to be reconfigured. Please visit http://manual.audacityteam.org/o/man/faq_installation_and_plug_ins.html#ffdown for a link to the recommended 2.2.2 updated version of FFmpeg for Windows and Mac OS X, and for information for Linux.}}   
+
* Users upgrading to Audacity 2.0.6 who had FFmpeg installed previously will see a notice that FFmpeg needs to be reconfigured. Please visit https://manual.audacityteam.org/o/man/faq_installation_and_plug_ins.html#ffdown for a link to the recommended 2.2.2 updated version of FFmpeg for Windows and Mac OS X, and for information for Linux.}}   
 +
{{advice|'''OS X 10.10 Yosemite:''' Audacity 2.0.6 will not officially support OS X 10.10 Yosemite when released (in particular, Apple Audio Units may not open in Audacity).}}
 
{{advice|1='''Extra notes for Windows:'''  
 
{{advice|1='''Extra notes for Windows:'''  
 
* The Windows installer for 2.0.x versions will replace 1.2.x or any previous 2.0.x installation, but install alongside legacy 1.3.x Beta versions. It is strongly recommended to uninstall previous Beta versions.
 
* The Windows installer for 2.0.x versions will replace 1.2.x or any previous 2.0.x installation, but install alongside legacy 1.3.x Beta versions. It is strongly recommended to uninstall previous Beta versions.
* '''The language choice in the Windows EXE Audacity installer only selects the language for the installer.''' The language Audacity runs in is determined by the "Format" for date and time in the "Region and Language" section of the Windows Control Panel. To change the Audacity language, please see these [http://manual.audacityteam.org/o/man/faq_about_audacity.html#language instructions].
+
* '''The language choice in the Windows EXE Audacity installer only selects the language for the installer.''' The language Audacity runs in is determined by the "Format" for date and time in the "Region and Language" section of the Windows Control Panel. To change the Audacity language, please see these [https://manual.audacityteam.org/o/man/faq_about_audacity.html#language instructions].
 
* You may see the error '''Application configuration incorrect''' when launching Audacity after installation. This mainly affects some Windows XP or 2000 machines. This can be fixed by downloading and installing the appropriate Microsoft "Redistributable Package" as follows:
 
* 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:
** [http://www.microsoft.com/downloads/details.aspx?familyid=A5C84275-3B97-4AB7-A40D-3802B2AF5FC2&displaylang=en Microsoft Visual C++ 2008 SP1 Redistributable Package (x86)] for 32-bit Windows
+
** [https://www.microsoft.com/en-us/download/details.aspx?id=5582 Microsoft Visual C++ 2008 SP1 Redistributable Package (x86)] for 32-bit Windows
** [http://www.microsoft.com/downloads/details.aspx?familyid=BA9257CA-337F-4B40-8C14-157CFDFFEE4E&displaylang=en Microsoft Visual C++ 2008 SP1 Redistributable Package (x64)] for 64-bit Windows.
+
** [https://www.microsoft.com/en-us/download/details.aspx?id=2092 Microsoft Visual C++ 2008 SP1 Redistributable Package (x64)] for 64-bit Windows.
 
<ul style="list-style-image: none; list-style-type: none">Be sure to get the correct package according to whether you have 32-bit or 64-bit Windows. To check, right-click over {{Menu|My Computer}} and choose {{Menu|Properties}}. If 64-bit is not mentioned, you have 32-bit.</ul>
 
<ul style="list-style-image: none; list-style-type: none">Be sure to get the correct package according to whether you have 32-bit or 64-bit Windows. To check, right-click over {{Menu|My Computer}} and choose {{Menu|Properties}}. If 64-bit is not mentioned, you have 32-bit.</ul>
 
* On first use of Audacity you need to confirm the new [[#install_vst|Install VST Effects]] dialog for detected effects before you can start the Audacity program.
 
* On first use of Audacity you need to confirm the new [[#install_vst|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 [http://manual.audacityteam.org/help/manual/man/faq_installation_and_plug_ins.html#lame latest version] of the LAME MP3 encoder. }}
+
* Users upgrading to 2.0.x versions from 1.3.6 or earlier must download the [https://manual.audacityteam.org/help/manual/man/faq_installation_and_plug_ins.html#lame latest version] of the LAME MP3 encoder. }}
<!--{{Hint|1= Items <del style=color:#660000>struck out</del> have been fixed in the latest [http://audacity.sourceforge.net/community/developers#cvs development code], meaning that if you [[Developer_Guide#Platform_Specific_Guides|compile Audacity]] yourself from that code, or use one of our [[Nightly Builds|nightly development builds]], these issues should not occur.}}  -->
+
<!--{{Hint|1= Items <del style=color:#660000>struck out</del> have been fixed in the latest [https://web.audacityteam.org/community/developers#cvs development code], meaning that if you [[Developer_Guide#Platform_Specific_Guides|compile Audacity]] yourself from that code, or use one of our [[Nightly Builds|nightly development builds]], these issues should not occur.}}  -->
  
 
== Changes since previous version ==
 
== Changes since previous version ==
Line 28: Line 28:
 
=== Improvements ===
 
=== Improvements ===
  
* Interface:
+
* '''Interface:'''
  * Redesigned, searchable Keyboard Preferences with Tree, Name and Key views.   
+
** Redesigned, searchable Keyboard Preferences with Tree, Name and Key views.   
  * Edit Menu: "Cut" and "Delete" are now in the top level of the menu.   
+
** Edit Menu: "Cut" and "Delete" are now in the top level of the menu.   
  * Transport Menu now includes "Play/Stop" and "Play/Stop and Set Cursor"  
+
** Transport Menu now includes "Play/Stop" and "Play/Stop and Set Cursor" (use Keyboard Preferences to create shortcuts for "Play" and "Stop").
      (use Keyboard Preferences to create shortcuts for "Play" and "Stop").
+
** Tracks Menu now includes "Mix and Render to New Track".  
  * Tracks Menu now includes "Mix and Render to New Track".  
+
** Track Dropdown Menu now has Move Track To Top and Move Track To Bottom.  
  * Track Drop-Down Menu now has Move Track To Top and Move Track To Bottom.  
+
** New right-click menu choice "Delete Label" to remove single labels.
  * New right-click menu choice "Delete Label" to remove single labels.
+
** "Snap To" now offers choice of snap to the "closest" or "prior" position. Note: the previous "Snap To On" keyboard shortcut will no longer work.   
  * "Snap To" now offers choice of snap to the "closest" or "prior" position.
+
** "Snap To" settings are now independent for each project.
      Note: the previous "Snap To On" keyboard shortcut will no longer work.   
 
  * "Snap To" settings are now independent for each project.
 
  
* Effects:
+
* '''Effects:'''
  * Truncate Silence: redesigned with simpler option "Truncate Detected  
+
** Truncate Silence: redesigned with simpler option "Truncate Detected Silence" to shorten to the specified length without compressing silence.
      Silence" to shorten to the specified length without compressing silence.
+
** VST effects: New "Settings" dialog lets you specify buffer size (for faster processing) and enable buffer delay compensation (to prevent inserted silence). Compensation may cause a crash in a few plug-ins.  
  * VST effects: New "Settings" dialog lets you specify buffer size (for  
+
** VST effects now support standard FXP presets.   
      faster processing) and enable buffer delay compensation (to prevent
+
** LV2 effects are now supported on all platforms (textual interface only).     
      inserted silence). Compensation may cause a crash in a few plug-ins.  
+
 
  * VST effects now support standard FXP presets.   
+
* Import or export using FFmpeg now requires FFmpeg 1.2 or later (or libav 0.8 or later). For recommended downloads of recent FFmpeg please visit https://manual.audacityteam.org/o/man/faq_installation_and_plug_ins.html#ffdown.
  * LV2 effects are now supported on all platforms (textual interface only).     
+
* New Tamil translation (largely complete).  
{{ednote|1='''Peter 26Sep14:''' The Manual states FFmpeg 2.2.2 is required for "latest Audacity" and that is the version on Buanzo's site.
+
* (Windows) FLAC exports can now exceed 2 GB in size.  
* '''Gale 27Sep14:''' Where does it say that? I see on http://manual.audacityteam.org/man/FAQ:Installation_and_Plug-Ins#ffdown: 
+
* (OS X) Easier Audacity installation using the DMG: drag the Audacity folder to the /Applications shortcut.  
<ul style="list-style-image: none; list-style-type: none">
+
* (Linux) Self-compiled builds of Audacity now search for system LADSPA effects in /usr/lib/ladspa.
"FFmpeg 2.2.2 for Windows and Mac should be used with the latest version of Audacity.
 
The previous FFmpeg 0.6.2 for Audacity will not be recognized by Audacity 2.0.6 and later, and FFmpeg 2.2.2 will not be recognized by Audacity versions before 2.0.6."
 
FFmpeg 1.2 will work, as it says in the instructions for Linux, but who is going to self-compile FFmpeg on Win and Mac when a ready build of 2.2.2 is available?</ul>}}
 
* Import or export using FFmpeg now requires FFmpeg 1.2 or later (or libav
 
    0.8 or later). For recommended downloads of recent FFmpeg please visit:
 
    http://manual.audacityteam.org/o/man/faq_installation_and_plug_ins.html#ffdown .
 
* New Tamil translation (largely complete).  
 
* (Windows) FLAC exports can now exceed 2 GB in size.  
 
* (OS X) Easier Audacity installation using the DMG: drag the Audacity folder
 
    to the /Applications shortcut,
 
* (OS X) Audacity 2.0.6 will not officially support OS X 10.10 Yosemite when
 
    released (in particular, Apple Audio Units may not open in Audacity).
 
* (Linux) Self-compiled builds of Audacity now search for system LADSPA  
 
    effects in /usr/lib/ladspa.
 
  
 
=== Bug Fixes ===
 
=== Bug Fixes ===
  
* Interface:
+
* '''Interface:'''
  * Region Restore did not restore the region after using Preferences.  
+
** Region Restore did not restore the region after using Preferences.  
  * Dragging selections with the keyboard or Selection Toolbar digits  
+
** Dragging selections with the keyboard or Selection Toolbar digits was very slow.   
      was very slow.   
+
** (Windows) Help > About Audacity crashed when run in Magyar language.   
  * (Windows) Help > About Audacity crashed when run in Magyar language.   
+
** (OS X) Some full and reduced Menu Bar items were not translated.   
  * (OS X) Some full and reduced Menu Bar items were not translated.   
+
** (OS X and Linux) Fixed various interface crashes.
  * (OS X and Linux) Fixed various interface crashes.
+
 
 +
* '''Effects:'''
 +
** Reverb and Paulstretch were missing from Chains.
 +
** Analyze > Contrast could report very inaccurate RMS levels.
 +
** Noise Removal: Attack and decay times were half as long as set. 
 +
** (OS X and Linux) Nyquist effects ran much more slowly than on Windows.  
  
* Effects:
+
* Click or drag on the Timeline after Loop Play continued to loop.
  * Reverb and Paulstretch were missing from Chains.
+
* Transcription Toolbar did not play slower than 0.1x speed.
  * Analyze > Contrast could report very inaccurate rms levels.
+
* (Linux) Audacity did not build if python 2 was not available.
  * Noise Removal: Attack and decay times were half as long as set.
 
  * (OS X and Linux) Nyquist effects ran much more slowly than on Windows.  
 
  
* Click or drag on the Timeline after Loop Play continued to loop.
+
== Known Issues at Release ==
* Transcription Toolbar did not play slower than 0.1x speed.
 
* (Linux) Audacity did not build if python 2 was not available.
 
  
 
===Accessibility===
 
===Accessibility===
* Many, but not all parts of the Audacity interface are accessible on Windows and Mac to those who can't use a mouse, and/or use a screen reader. It may be possible to make more of Audacity accessible in the longer term. For details, see http://manual.audacityteam.org/o/man/accessibility.html  
+
* Many, but not all parts of the Audacity interface are accessible on Windows and Mac to those who can't use a mouse, and/or use a screen reader. It may be possible to make more of Audacity accessible in the longer term. For details, see https://manual.audacityteam.org/o/man/accessibility.html  
* There are some accessibility bugs in the parts of Audacity that are accessible (or behavior may vary according to the specific screen reader).  
+
There are some accessibility bugs in the parts of Audacity that are accessible (or behavior may vary according to the specific screen reader).  
** Some interface text or markings remain in black when using High Contrast light-on-dark themes, so cannot be read properly.
+
* Some interface text or markings remain in black when using High Contrast light-on-dark themes, so cannot be read properly.
** Install VST Effects dialog: The list view of plug-ins is a check box list view, and all the plug-ins are checked initially. Unfortunately Jaws and Window-Eyes do not read whether or not a check box is checked, but you can still press SPACE to change this.
+
* Install VST Effects dialog: The list view of plug-ins is a check box list view, and all the plug-ins are checked initially. Unfortunately Jaws and Window-Eyes do not read whether or not a check box is checked, but you can still press SPACE to change this.
** Keyboard Preferences: Window-Eyes doesn't read the key bindings when View by Tree is selected, and may not always read the bindings in other views.
+
* Keyboard Preferences: Window-Eyes doesn't read the key bindings when View by Tree is selected, and may not always read the bindings in other views.
** (OS X) It is not possible to TAB through Keyboard Preferences.  
+
* (OS X) It is not possible to TAB through Keyboard Preferences.  
** (OS X) Issues with VoiceOver:
+
* (OS X) Issues with VoiceOver:
*** (reported on OS X 10.9.x) After exporting, the black accessibility area is trapped in the Tooldock area, so there is no way to read the tracks. '''Workaround:''' Save as a project, close the project then reopen it. You can then navigate the tracks with VoiceOver.
+
** (reported on OS X 10.9.x) After exporting, the black accessibility area is trapped in the Tooldock area, so there is no way to read the tracks. '''Workaround:''' Save as a project, close the project then reopen it. You can then navigate the tracks with VoiceOver.
*** If you use arrow keys to navigate the Timetext controls in Selection Toolbar, VoiceOver stops reading. '''Workaround:''' Use Control-Option-W  
+
** 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".  
+
** When you TAB forwards from "Audio Position" in Selection Toolbar, the "Selection End" or "Selection Length" radio button is read as "Selection Start". When you use COMMAND + F6 or COMMAND + SHIFT + F6 to move directly into "Selection End" from another toolbar, the button is read as "Selection Start".  
*** Mixer Toolbar input/output sliders are not read, but just described as "multiple indicators". The "Graphic EQ"  and vertical sliders in Equalization *are* read.
+
** Mixer Toolbar input/output sliders are not read, but just described as "multiple indicators". The "Graphic EQ"  and vertical sliders in Equalization *are* read.
*** Metadata Editor table not read.
+
** Metadata Editor table not read.
*** Edit Labels dialog not read.
+
** Edit Labels dialog not read.
*** In the "Edit Chains" window, only the first command in the "Chain" list is read, and it is only read when first accessed. In the "Select Command" window for inserting a new command in a Chain, commands in the table are not read.
+
** In the "Edit Chains" window, only the first command in the "Chain" list is read, and it is only read when first accessed. In the "Select Command" window for inserting a new command in a Chain, commands in the table are not read.
*** "Manage Curves" table in Equalization not read.
+
** "Manage Curves" table in Equalization not read.
** (Linux) Using the Unity shell, most or all keyboard shortcuts are not listed in the Audacity menus. Gnome Fallback is not affected. '''Workaround:''' You can view shortcuts at {{menu|Edit > Preferences: Keyboard}} or online at http://manual.audacityteam.org/o/man/keyboard_shortcut_reference.html.
+
* (Linux) Using the Unity shell, most or all keyboard shortcuts are not listed in the Audacity menus. Gnome Fallback is not affected. '''Workaround:''' You can view shortcuts at {{menu|Edit > Preferences: Keyboard}} or online at https://manual.audacityteam.org/o/man/keyboard_shortcut_reference.html.
** (Linux) SPACE cannot be used to change context menu items that have a checkbox (such as Selection Format in the context menu of TimeText digits, or Mono/Left/Right and Set Rate and Set Sample Format in the Track Drop-Down Menu). Using SPACE in these menus could crash Audacity. '''Workaround:''' Use ENTER instead of SPACE to select the new choice.  
+
* (Linux) SPACE cannot be used to change context menu items that have a checkbox (such as Selection Format in the context menu of TimeText digits, or Mono/Left/Right and Set Rate and Set Sample Format in the Track Dropdown Menu). Using SPACE in these menus could crash Audacity. '''Workaround:''' Use ENTER instead of SPACE to select the new choice.  
** (Linux) Issues with Orca:  
+
* (Linux) Issues with Orca:  
*** Audacity tracks are not read.  
+
** Audacity tracks are not read.  
*** Not all toolbar controls are read, examples being Timetext controls, Project Rate and controls in Device Toolbar.
+
** Not all toolbar controls are read, examples being Timetext controls, Project Rate and controls in Device Toolbar.
*** Not all controls in Preferences are read.
+
** Not all controls in Preferences are read.
*See issue 33.
 
*See issue 33.
 
===Bugs requiring more investigation===
 
* (Linux) If Audacity is compiled with the option to use libsamplerate and the default "Best Sinc Interpolator" for high-quality conversion is used, Tracks > Resample may lead to truncation of the waveform.  Workaround: change the project rate to the desired rate, export the track and re-import it.
 
* (Windows Vista) If you change the input volume in Audacity and then record, the volume is reset to its original level. This appears to occur mostly with a few specific USB devices, and sometimes only on Vista SP1, so it is currently hard for us to fix. '''Workaround:''' Check if the manufacturer supplies their own drivers for the device and try those. See if upgrading to Vista SP2 or Windows 7 helps.
 
** Please report make and model number of devices that exhibit the issue, also the drivers and exact version of  Vista and Service Pack in use (for example, Vista 32-bit, SP1)
 
* (Windows Vista, 7) When a USB device is connected, the listing of inputs for the built-in sound device in Device Toolbar or Devices Preferences may become corrupt, indicating single inputs as multiple inputs. It may only be possible to record from the built-in input which is currently set as default at "Sound" in the Windows Control Panel, irrespective of the input selected in Audacity. '''Workaround:''' Try Transport > Rescan Audio Devices, or a computer reboot. 
 
** Please report make and model number of devices that exhibit the issue, along with description of symptoms and any steps you have noticed that create the issue.
 
* (Windows Vista,7) On upgrading to the current Beta from 1.3.12 or earlier, "error opening sound device" occurs when recording from the inbuilt sound device where there was no error in the previous Audacity with the same device configuration and operating system. '''Workaround:''' Use Transport > Rescan Audio Devices, or go to "Sound" in the Windows Control Panel and click OK. Note that if devices listed in Device Toolbar are disabled in "Sound" then the error is legitimate - you will need to enable those devices.
 
** Please report make and model number of sound devices that exhibit the issue, along with driver version number. Please first ensure your sound device drivers are up-to-date and not generic Microsoft drivers - help available [[Updating Sound Device Drivers|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.
 
 
===Chains===
 
===Chains===
 
* '''Chains do not currently support export as AIFF, Other uncompressed files or any formats supported by FFmpeg.'''
 
* '''Chains do not currently support export as AIFF, Other uncompressed files or any formats supported by FFmpeg.'''
Line 131: Line 100:
 
** '''Only one resampling library is permitted.''' If you enable either libresample or libsamplerate in configure, libsoxr will not be enabled. Any configure of resampling libraries other than  libsoxr only will enable one only of libresample, libsamplerate or libsoxr in that order of precedence; however the intermediate configure output may suggest that other libraries will be favored.   
 
** '''Only one resampling library is permitted.''' If you enable either libresample or libsamplerate in configure, libsoxr will not be enabled. Any configure of resampling libraries other than  libsoxr only will enable one only of libresample, libsamplerate or libsoxr in that order of precedence; however the intermediate configure output may suggest that other libraries will be favored.   
 
** '''To enable libresample''', your configure must include --without-libsoxr  as well as --with-libresample.
 
** '''To enable libresample''', your configure must include --without-libsoxr  as well as --with-libresample.
* (Windows) Compilation with Visual Studio 2010 is not  supported or recommended. See the Wiki page [http://wiki.audacityteam.org/wiki/Developing_On_Windows#What_about_Visual_Studio_2010.3F__Or_64-bit.3F Developing on Windows] for information.
+
* (Windows) Compilation with Visual Studio 2010 is not  supported or recommended. See the Wiki page [https://wiki.audacityteam.org/wiki/Developing_On_Windows#What_about_Visual_Studio_2010.3F__Or_64-bit.3F Developing on Windows] for information.
 
* (Windows) LADSPA effects cannot be categorized even when Audacity is compiled with USE_LIBLRDF defined.
 
* (Windows) LADSPA effects cannot be categorized even when Audacity is compiled with USE_LIBLRDF defined.
 
*(Linux) Audacity may not always compile against supported versions of libav or FFmpeg. Audacity 2.0.6 supports FFmpeg 1.2 or higher (FFmpeg 2.2.3 is known to work) or libav 0.8 or higher.
 
*(Linux) Audacity may not always compile against supported versions of libav or FFmpeg. Audacity 2.0.6 supports FFmpeg 1.2 or higher (FFmpeg 2.2.3 is known to work) or libav 0.8 or higher.
Line 138: Line 107:
 
** Building against self-compiled FFmpeg 2.2.2 with --disable-dynamic-loading the only argument fails on Ubuntu 13.10 with "undefined reference to 'av_codec_is_encoder'". '''Workaround:''' Configuring with --disable-dynamic-loading and --with-lib-preference="local" (or at least  --with-ffmpeg="local") may build successfully, but may not disable Libraries Preferences. The best solution may be not to disable dynamic loading.
 
** Building against self-compiled FFmpeg 2.2.2 with --disable-dynamic-loading the only argument fails on Ubuntu 13.10 with "undefined reference to 'av_codec_is_encoder'". '''Workaround:''' Configuring with --disable-dynamic-loading and --with-lib-preference="local" (or at least  --with-ffmpeg="local") may build successfully, but may not disable Libraries Preferences. The best solution may be not to disable dynamic loading.
 
===Effects (VST and Audio Units)===
 
===Effects (VST and Audio Units)===
* (OS X) '''When saving presets, the FXP or XML file extension is not automatically offered in the file name, and not added by Audacity if you omit it.'''  Make sure the extension you add is the same as that shown in the "File Format" drop-down menu, otherwise the preset will not be loadable.
+
* (Windows and Mac OS X) '''When running VST effects in [https://manual.audacityteam.org/o/man/effects_preferences.html#vst graphical mode] the controls of many plug-ins do not visibly respond when loading a preset file from the "Load" button'''. The new settings are however loaded internally, will apply when running the effect and will be visible if you reopen the effect after running it. Controls do respond to loading a preset file if you turn off graphical mode.
 +
* (OS X) '''When saving presets, the FXP or XML file extension is not automatically offered in the file name, and not added by Audacity if you omit it.'''  Make sure the extension you add is the same as that shown in the "File Format" dropdown menu, otherwise the preset will not be loadable.
 
* (OS X) The following plug-ins may cause Audacity to crash if they are used after starting Audacity.   
 
* (OS X) The following plug-ins may cause Audacity to crash if they are used after starting Audacity.   
 
** '''AURoundTripAAC''' from "Apple audio mastering tools"  (this requires OS X 10.6 or later so may crash on 10.4 or 10.5).
 
** '''AURoundTripAAC''' from "Apple audio mastering tools"  (this requires OS X 10.6 or later so may crash on 10.4 or 10.5).
Line 153: Line 123:
 
** DISTRHO Mini Series VST's from http://distrho.sourceforge.net/plugins.php crash Audacity in graphic mode but will run in text mode (open the Effects Preferences and uncheck "Display VST effects in graphical mode").  
 
** DISTRHO Mini Series VST's from http://distrho.sourceforge.net/plugins.php crash Audacity in graphic mode but will run in text mode (open the Effects Preferences and uncheck "Display VST effects in graphical mode").  
 
** Waves v5 may cause Audacity to hang if you select it in the "Install VST Effects" dialog then click OK.
 
** Waves v5 may cause Audacity to hang if you select it in the "Install VST Effects" dialog then click OK.
*(OS X) '''Some VST plug-ins no longer allow text input in the presets drop-down, either by typing or pasting.''' Examples are Sound Hack "Delay Trio / Freesound Bundle" and Blue Cat.
+
* (OS X) '''Some VST plug-ins no longer allow text input in the presets dropdown, either by typing or pasting.''' Examples are Sound Hack "Delay Trio / Freesound Bundle" and Blue Cat.
===Effects (VST)===
 
 
* (OS X) '''Blue Cat plug-ins:''' Opening the dialog to save a preset will hide the plug-in interface and lock out the main Audacity window. '''Workaround:''' Right-click or CONTROL-click over Audacity's Dock icon, choose "Quit" then choose to save changes or not. Other plug-ins that use JUCE (such as GRM Tools) are also likely to be affected.
 
* (OS X) '''Blue Cat plug-ins:''' Opening the dialog to save a preset will hide the plug-in interface and lock out the main Audacity window. '''Workaround:''' Right-click or CONTROL-click over Audacity's Dock icon, choose "Quit" then choose to save changes or not. Other plug-ins that use JUCE (such as GRM Tools) are also likely to be affected.
 
===Effects and Analysis===
 
===Effects and Analysis===
 
* '''LADSPA generate plug-ins may fail to generate into an empty track''' or into white space separating audio clips. '''Workaround:''' Before using the LADSPA generator, generate audio using any of the Audacity Generators above the divider in the Generate Menu, then generate into that audio selection.
 
* '''LADSPA generate plug-ins may fail to generate into an empty track''' or into white space separating audio clips. '''Workaround:''' Before using the LADSPA generator, generate audio using any of the Audacity Generators above the divider in the Generate Menu, then generate into that audio selection.
 
* '''Nyquist plug-ins:''' In locales where comma is the decimal separator, entering a comma in a text input box that has no associated slider will produce an error message, or only result in the whole number before the comma (for example, in Regular Interval Labels). '''Workaround:''' Use a dot (period) as the decimal separator.
 
* '''Nyquist plug-ins:''' In locales where comma is the decimal separator, entering a comma in a text input box that has no associated slider will produce an error message, or only result in the whole number before the comma (for example, in Regular Interval Labels). '''Workaround:''' Use a dot (period) as the decimal separator.
* (Linux) '''Sliding Time Scale / Pitch Shift may crash randomly in Audacity built with pre-2.0.2 versions of libsbsms.''' This may occur for example in the Ubuntu package of Audacity 2.0.5 on Ubuntu 14.04. '''Workaround:'''' Build Audacity configured --with-sbsms="local", or use the Audacity package in Ubuntu 14.10 which uses libsbsms 2.0.2-1.
+
* (Linux) '''Sliding Time Scale / Pitch Shift may crash randomly in Audacity built with pre-2.0.2 versions of libsbsms.''' This may occur for example in the Ubuntu package of Audacity 2.0.5 on Ubuntu 14.04. '''Workaround:''' Build Audacity configured --with-sbsms="local", or use the Audacity package in Ubuntu 14.10 which uses libsbsms 2.0.2-1.
 
* (Windows 64-bit) There is no  HKEY_LOCAL_MACHINE\SOFTWARE\ registry key where Audacity detects VST plug-ins. The HKEY_CURRENT_USER key searched is HKEY_CURRENT_USER\Software\VST\VSTPluginsPath instead of the expected HKEY_CURRENT_USER\SOFTWARE\Wow6432Node\VST .
 
* (Windows 64-bit) There is no  HKEY_LOCAL_MACHINE\SOFTWARE\ registry key where Audacity detects VST plug-ins. The HKEY_CURRENT_USER key searched is HKEY_CURRENT_USER\Software\VST\VSTPluginsPath instead of the expected HKEY_CURRENT_USER\SOFTWARE\Wow6432Node\VST .
 
* (Windows and Linux) Some LADSPA "Blop" plug-ins ( http://blop.sourceforge.net/index.html ) are reported to crash in Audacity on Linux Debian. On Windows, the Blop plug-ins included in http://opensourcepack.blogspot.co.uk/p/ladspa-for-win32.html can also crash, but this can be avoided if you ensure the "blop_files" folder contains the necessary "_data.dll" files for the plug-ins and that this folder is present in the Audacity "Plug-Ins" folder.
 
* (Windows and 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.
Line 178: Line 147:
 
<ul style="list-style-image: none; list-style-type: none">'''Workaround:''' Edit > Undo if necessary then drag from outside the selection region or single-click in the clip to remove the selection.</ul>
 
<ul style="list-style-image: none; list-style-type: none">'''Workaround:''' Edit > Undo if necessary then drag from outside the selection region or single-click in the clip to remove the selection.</ul>
 
* '''Undo may fail silently after applying an effect or edit''' across one or more split lines. '''Workaround:''' Effect > Repeat the effect from the top of the Effect Menu then undo both applications of the effect, or open View > History... and click on the step above the currently indicated line.
 
* '''Undo may fail silently after applying an effect or edit''' across one or more split lines. '''Workaround:''' Effect > Repeat the effect from the top of the Effect Menu then undo both applications of the effect, or open View > History... and click on the step above the currently indicated line.
* Left-clicking in a stereo track to merge a clip at a split line may cause other clips to move. It is believed this only happens after having used the Track Drop-Down Menu to make two mono tracks into stereo. '''Workaround:''' Select over the split line and Edit > Clip Boundaries > Join.
+
* 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.
 
* When pasting audio into tracks with envelope points, the envelope points may move in unexpected ways, so causing unwanted amplitude adjustments.
===Exports===
+
=== Imports and Exports===
 
* (Linux) Exports using "M4A (AAC) Files" are very slow irrespective of the AAC encoder FFmpeg is configured to use.  Workaround: choose (external program) when exporting, entering an appropriate path and command (for example, /usr/bin/ffmpeg -i - "%f") to run FFmpeg using Audacity's command-line encoder.
 
* (Linux) Exports using "M4A (AAC) Files" are very slow irrespective of the AAC encoder FFmpeg is configured to use.  Workaround: choose (external program) when exporting, entering an appropriate path and command (for example, /usr/bin/ffmpeg -i - "%f") to run FFmpeg using Audacity's command-line encoder.
 
* (Linux) Files exported using the '''FFmpeg native AAC encoder''' included with many system versions of FFmpeg may be of poor quality. This is an issue with the library itself. '''Workaround:''' When compiling FFmpeg, configure with the libfaac encoder thus: --disable-encoder=aac --enable-libfaac --enable-nonfree. Note that libfaac has an issue not present in the native FFmpeg encoder that saved files are short at the end by about 3000 samples. Alternatively build the VisualOn AAC encoder library and configure FFmpeg with --disable-encoder=aac --disable-encoder=libfaac --enable-libvo-aacenc.  
 
* (Linux) Files exported using the '''FFmpeg native AAC encoder''' included with many system versions of FFmpeg may be of poor quality. This is an issue with the library itself. '''Workaround:''' When compiling FFmpeg, configure with the libfaac encoder thus: --disable-encoder=aac --enable-libfaac --enable-nonfree. Note that libfaac has an issue not present in the native FFmpeg encoder that saved files are short at the end by about 3000 samples. Alternatively build the VisualOn AAC encoder library and configure FFmpeg with --disable-encoder=aac --disable-encoder=libfaac --enable-libvo-aacenc.  
 
* (Linux) Mono AAC files import as stereo if FFmpeg uses the libfaad decoder. This is again an issue with the library itself.
 
* (Linux) Mono AAC files import as stereo if FFmpeg uses the libfaad decoder. This is again an issue with the library itself.
* Audacity may freeze if using the Nero AAC encoder to export via (external program). It is reported this only occurs when using multiple CPU cores. '''Workaround:''' Export to AAC directly by adding [http://manual.audacityteam.org/o/man/faq_installation_and_plug_ins.html#ffdown FFmpeg] to your computer, or set Audacity to use only one CPU core.
+
* 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 [https://manual.audacityteam.org/o/man/faq_installation_and_plug_ins.html#ffdown 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.
 
* WAVEX (Microsoft) headers: GSM 6.10 files cannot be exported, and U-Law/A-Law files may not be playable.
===Imports and Exports===
 
* '''AAC exports using "M4A (AAC) Files (FFmpeg)" with project rate below 22050 Hz produce a zero bytes file if the linked to FFmpeg is configured with the default AAC encoder or libfaac. This will not affect the recommended builds of FFmpeg for Windows and Mac OS X which are built with libvo-aacenc. '''Workaround:''' You can export AAC below 22050 Hz using default-configured FFmpeg by choosing (external program) export instead.
 
 
* '''Files containing PCM audio but misnamed as MP3 cause a freeze or crash''' if an Extended Import rule is set in Preferences to force import of MP3 files using the MP3 importer.
 
* '''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 [http://www.foobar2000.org/download Foobar2000] for this purpose.
 
* '''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 [http://www.foobar2000.org/download 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) After opening a sufficiently long audio file, opening a second file of any size leads to locked GUI/console messages until first file completes play.
* (Linux) Custom FFmpeg Export dialogue does not respond to ENTER after clicking in the Formats or Codec selector.
+
* (Linux) Custom FFmpeg Export dialog does not respond to ENTER after clicking in the Formats or Codec selector.
 
* (Mac OS X) Dragging audio files to Audacity's icon in the Dock will only import the file for WAV, AIFF, AU, MP2, MP3, OGG, FLAC and M4A. '''Workaround:''' Rename MP4 files (audio or video) to M4A extension. Alternatively the files may be dragged to the Audacity icon in the folder where you have Audacity installed, dragged into the open Audacity window or imported using the Audacity menus.
 
* (Mac OS X) Dragging audio files to Audacity's icon in the Dock will only import the file for WAV, AIFF, AU, MP2, MP3, OGG, FLAC and M4A. '''Workaround:''' Rename MP4 files (audio or video) to M4A extension. Alternatively the files may be dragged to the Audacity icon in the folder where you have Audacity installed, dragged into the open Audacity window or imported using the Audacity menus.
* (Mac OS X) Exporting using (external program) will crash using the built-in commands or if the absolute path is entered incorrectly or its accompanying command syntax is incorrect. See http://manual.audacityteam.org/o/man/exporting_to_an_external_program.html for how to browse to the correct path and enter the correct syntax.
+
* (Mac OS X) Exporting using (external program) will crash using the built-in commands or if the absolute path is entered incorrectly or its accompanying command syntax is incorrect. See https://manual.audacityteam.org/o/man/exporting_to_an_external_program.html for how to browse to the correct path and enter the correct syntax.
 
* (OS X and Linux) When using Export Multiple, asterisks (*) or question marks (?) in labels are wrongly rejected as illegal characters, and forward slashes (/) cause a false "cannot export audio" warning. '''Workaround:''' To force use of * or ? (and / on OS X), export each region with File > Export Selection instead (/ is illegal in a file or folder name on Linux).
 
* (OS X 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 [http://manual.audacityteam.org/o/man/faq_errors.html#nwf here].
+
* (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 [https://manual.audacityteam.org/o/man/faq_errors.html#nwf 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.
 
* (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 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.
 
* 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.
* M4A (AAC) exports: The Quality Slider in "Specify AAC Options" has no effect if the FFmpeg library is built with the libvo-aac encoder, as are recommended builds of FFmpeg for Windows and Mac OS X. '''Workaround:''' Given the alternative AAC encoders for FFmpeg have other problems as described in these notes, you can instead export as WAV and convert to AAC in iTunes on Windows and Mac.
+
<div id="metadata"></div>
 
* Metadata:  
 
* Metadata:  
 
** Album art and lyrics in imported metadata are lost when exporting. '''Workaround:''' Copy the lyrics (or search for them online) then add them back to the exported file in your favorite media player. Extract the album art using a tag editor such as [http://sourceforge.net/projects/idteid3tagedito/ IDTE] (or use [http://windows.microsoft.com/en-us/windows/add-change-media-player-album-art#1TC=windows-7 Windows Media Player] or iTunes to search online for the art) then add the art back to the exported file using your media player.     
 
** Album art and lyrics in imported metadata are lost when exporting. '''Workaround:''' Copy the lyrics (or search for them online) then add them back to the exported file in your favorite media player. Extract the album art using a tag editor such as [http://sourceforge.net/projects/idteid3tagedito/ IDTE] (or use [http://windows.microsoft.com/en-us/windows/add-change-media-player-album-art#1TC=windows-7 Windows Media Player] or iTunes to search online for the art) then add the art back to the exported file using your media player.     
** Tags other than the seven default [http://manual.audacityteam.org/o/man/metadata_editor.html Metadata Editor] tags will be rewritten as custom ID3 TXXX tags, which will cause them not to be seen in applications like Windows Media Player and iTunes. Common tag examples include "Album Artist", "BPM" and "Composer".
+
** Tags other than the seven default [https://manual.audacityteam.org/o/man/metadata_editor.html Metadata Editor] tags will be rewritten as custom ID3 TXXX tags, which will cause them not to be seen in applications like Windows Media Player and iTunes. Common tag examples include "Album Artist", "BPM" and "Composer".
 
** ID3 v2.4 tags in imported MP3 files are not seen and will be removed on export.
 
** 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.   
 
** Audacity writes both ID3 v2.3 (TYER) and v2.4 (TDRC) tags for "Year", but any applications that require the older TYER on its own (without TDRC) will not see "Year" in Audacity-exported files. The id3 command-line application on Linux is one example.   
** AAC: Artist and Year metadata is not exported or imported due to a bug in FFmpeg 2.2.2. 
 
* WMA and APE (Monkeys Audio): "Artist Name" is not seen on importing the file (Audacity bug)
 
 
** Other metadata import/export may not always be consistent. This may depend on the program that created the imported tags and the program used to read the exported tags.
 
** 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.
* 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.
 
 
*"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.
 
*"Background on-demand loading" for FFmpeg (in the Libraries Preferences) does not currently allow changing the focus of waveform computation by clicking in the track. You can apply an effect to a selection wherever the normal waveform has appeared, but if you do so before the normal waveform has appeared, the audio will be silenced.
 
*'''(Linux):''' When exporting to MIDI over an existing file, no overwrite warning is given.
 
*'''(Linux):''' When exporting to MIDI over an existing file, no overwrite warning is given.
*'''By default, the importer used depends on the import method.''' For example, to be able to use [http://manual.audacityteam.org/o/man/faq_installation_and_plug_ins.html#ffdown 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 [http://manual.audacityteam.org/o/man/extended_import_preferences.html 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.
+
*'''By default, the importer used depends on the import method.''' For example, to be able to use [https://manual.audacityteam.org/o/man/faq_installation_and_plug_ins.html#ffdown 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 [https://manual.audacityteam.org/o/man/extended_import_preferences.html 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.
 
*'''Export Multiple does not pass metadata common to all tracks to the Metadata Editor windows for each track.''' '''Workaround:''' Export by unchecking "Show Metadata Editor before export step" in Import / Export Preferences, then enter any tags common to all tracks at File > Open Metadata Editor... before exporting. Audacity will then silently add the common and automatically generated Track Title and Track Number tags for each exported file.
 
*'''Import > Raw Data... imports files as noise''' if the Quality Preferences are set to 24-bit Default Sample Format. Set this to 16-bit or 32-bit float instead.
 
*'''Import > Raw Data... imports files as noise''' if the Quality Preferences are set to 24-bit Default Sample Format. Set this to 16-bit or 32-bit float instead.
*'''WAV and AIFF exports will fail without warning''' if you import a WAV or AIFF by [http://manual.audacityteam.org/o/man/import_export_preferences.html 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.
+
*'''WAV and AIFF exports will fail without warning''' if you import a WAV or AIFF by [https://manual.audacityteam.org/o/man/import_export_preferences.html reading it directly], delete the file and its track then export new audio to the same file name and location as the deleted file. '''Workaround:''' Set the Preference in the above link to "Make a copy" of uncompressed files when importing.
 
*(OS X) Audio files containing a backslash (\) in the name will fail "Could not open file" if you import them using File > Open... , File > Import > Audio... or File > Open Recent. This is a bug in wxWidgets. '''Workaround:''' Drag the file into the Audacity window instead.
 
*(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.
 
*<div id="dither"></div>
 
*<div id="dither"></div>
* '''[[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 [http://manual.audacityteam.org/o/man/quality_preferences.html Quality Preferences]. To fix any files that have already been affected, see [http://forum.audacityteam.org/viewtopic.php?f=28&t=38756 this Forum topic].
+
* '''[[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 [https://manual.audacityteam.org/o/man/quality_preferences.html Quality Preferences]. To fix any files that have already been affected, see [https://forum.audacityteam.org/viewtopic.php?f=28&t=38756 this Forum topic].
*On a fresh installation of Audacity or [http://manual.audacityteam.org/help/manual/man/preferences.html#stored 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".
+
*On a fresh installation of Audacity or [https://manual.audacityteam.org/help/manual/man/preferences.html#stored 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.
 
*When importing a MIDI track, the channel selection buttons to left of the track are not currently available.
 +
<div id="ffmpeg"></div> 
 
===Imports and Exports (FFmpeg)===
 
===Imports and Exports (FFmpeg)===
 
* '''In the "Custom FFmpeg Export" dialog, deleting a preset crashes Audacity.''' Importing a preset crashes Audacity unless the "ffmpeg_presets" file in Audacity's folder for application data is empty or does not exist.
 
* '''In the "Custom FFmpeg Export" dialog, deleting a preset crashes Audacity.''' Importing a preset crashes Audacity unless the "ffmpeg_presets" file in Audacity's folder for application data is empty or does not exist.
 +
* M4A (AAC) exports: The Quality Slider in "Specify AAC Options" has no effect if the FFmpeg library is built with the libvo-aac encoder, as are recommended builds of FFmpeg for Windows and Mac OS X. '''Workaround:''' Given the alternative AAC encoders for FFmpeg have other problems as described in these notes, you can instead export as WAV and convert to AAC in iTunes on Windows and Mac.
 +
* '''AAC exports using "M4A (AAC) Files (FFmpeg)" with project rate below 22050 Hz produce a zero bytes file if the linked to FFmpeg is configured with the default AAC encoder or libfaac.''' This will not affect the recommended builds of FFmpeg for Windows and Mac OS X which are built with libvo-aacenc. '''Workaround:''' You can export AAC below 22050 Hz using default-configured FFmpeg by choosing (external program) export instead.
 +
* AAC: Artist and Year metadata is not exported or imported due to a bug in FFmpeg 2.2.2. 
 +
* WMA and APE (Monkeys Audio): "Artist Name" is not seen on importing the file (Audacity bug)
 +
* Custom FFmpeg Export: many combinations of formats and codecs are incompatible, as are some combinations of general options and codecs. Some files may be exported as zero kb files.
 +
 
===Installation===
 
===Installation===
* (OS X 10.6 or later) Administrative (and occasionally, root) permissions may be needed on some machines to read the optional LAME libraries at /usr/local/lib/audacity. In case of difficulty, please download the zip version "Lame Library v3.98.2 for Audacity on OSX.zip" from the [http://lame.buanzo.org/ download site] and extract the files to your own preferred location.
+
* (OS X 10.6 or later) Administrative (and occasionally, root) permissions may be needed on some machines to read the optional LAME libraries at /usr/local/lib/audacity. In case of difficulty, please download the zip version "Lame Library v3.98.2 for Audacity on OSX.zip" from the [https://lame.buanzo.org/ download site] and extract the files to your own preferred location.
 
===Interface===
 
===Interface===
* (Linux) If Audacity is configured with the option to use libsamplerate, an action involving resampling outside libsamplerate's limits of 1/256 to 256x will cause the progress dialogue to hang, or possibly a crash.
+
* In projects containing an hour or more of total audio, there may be a delay compared to previous versions of Audacity when:
 +
** Dragging sample points with Draw Tool
 +
** Using Cut, Copy, Paste, Delete or Silence Audio.
 +
<ul style="list-style-image: none; list-style-type: none">
 +
The delay may be more evident on slower computers. In addition, label text may not be recovered if there is a crash.</ul>
 +
* (Linux) If Audacity is configured with the option to use libsamplerate, an action involving resampling outside libsamplerate's limits of 1/256 to 256x will cause the progress dialog to hang, or possibly a crash.
 
* (Linux) Using a file manager (for example, context menu) or the command line to open further files gives an error. Even if Audacity is closed, only one file can be opened from the file manager. '''Workaround:''' Use File > Open, or (for audio files) File > New then drag the files in.
 
* (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 and Linux) In some locales, Preferences text may be truncated or overlapped, or dropdown boxes truncated.
Line 245: Line 220:
 
* Mouse Bindings are not currently configurable by the user.
 
* Mouse Bindings are not currently configurable by the user.
 
* Snap-To does not move the cursor when first enabled or when the selection format is changed.
 
* 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 http://forum.audacityteam.org/
+
* 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.
 
*(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.
 
:For Package Maintainers / Distributors / anyone building against 2.8.10: The upstream change in wxGTK is simple and can easily be patched into wxGTK 2.8.10 if desired: Grab http://trac.wxwidgets.org/changeset/62397?format=diff&new=62397, run it through dos2unix (as it seems to come with dos line-endings), and apply it to the wxGTK 2.8.10 sources (with -p3 to get the paths right if you patch from the top level of the tarball distribution).
 
:For Package Maintainers / Distributors / anyone building against 2.8.10: The upstream change in wxGTK is simple and can easily be patched into wxGTK 2.8.10 if desired: Grab http://trac.wxwidgets.org/changeset/62397?format=diff&new=62397, run it through dos2unix (as it seems to come with dos line-endings), and apply it to the wxGTK 2.8.10 sources (with -p3 to get the paths right if you patch from the top level of the tarball distribution).
*(OS X 10.5.8 PPC) '''The How to Get Help" window that appears by default on launch of Audacity cannot be moved or closed. The Audacity Log window may also be affected. '''Workaround:''' To stop the Welcome Screen appearing, open Audacity > Preferences: Interface and uncheck "Show How to Get Help". You can also quit Audacity, open Finder, Go > Go to Folder and type {{path|~/Library/Application Support/audacity/}} . Open audacity.cfg,select all the text and delete it. Then type the following at the top of the file:
+
*(OS X 10.5.8 PPC) '''"The How to Get Help" window that appears by default on launch of Audacity cannot be moved or closed.''' The Audacity Log window may also be affected. '''Workaround:''' To stop the Welcome Screen appearing, open Audacity > Preferences: Interface and uncheck "Show How to Get Help". You can also quit Audacity, open Finder, Go > Go to Folder and type {{path|~/Library/Application Support/audacity/}} . Open audacity.cfg,select all the text and delete it. Then type the following at the top of the file:
{{code|1=NewPrefsInitialized=1<br>[GUI]<br>ShowSplashScreen=0}}
+
<ul style="list-style-image: none; list-style-type: none">{{code|1=NewPrefsInitialized=1<br>[GUI]<br>ShowSplashScreen=0}}
Save the changes to audacity.cfg then restart Audacity.
+
Save the changes to audacity.cfg then restart Audacity.</ul>
 
*(Windows) It is not yet possible to drag .lnk shortcuts to audio files or projects into Audacity, or to drag them to the Audacity executable's icon. '''Workaround:''' Use File > Open or File > Import > Audio, or double-click the shortcut to the .aup from Windows Explorer.
 
*(Windows) It is not yet possible to drag .lnk shortcuts to audio files or projects into Audacity, or to drag them to the Audacity executable's icon. '''Workaround:''' Use File > Open or File > Import > Audio, or double-click the shortcut to the .aup from Windows Explorer.
*(Windows) The Audacity executable cannot be added to the Explorer "Open with" context menu if you have another version of Audacity on the system which is also called "audacity.exe". '''Workaround:''' either use the "Open with" dialogue to browse to the executable each time, or rename the executable to or some other unique name.
+
*(Windows) The Audacity executable cannot be added to the Explorer "Open with" context menu if you have another version of Audacity on the system which is also called "audacity.exe". '''Workaround:''' either use the "Open with" dialog to browse to the executable each time, or rename the executable to or some other unique name.
 
*Dragging a clip or track up or down with Time Shift Tool does not scroll the project window when tracks exist out of view above or below the scroll. '''Workaround:''' Choose View > Fit Vertically before drag, or click and hold the piece to be dragged, use up or down arrow on the keyboard to scroll to the target track, then drag and release the clip or track.
 
*Dragging a clip or track up or down with Time Shift Tool does not scroll the project window when tracks exist out of view above or below the scroll. '''Workaround:''' Choose View > Fit Vertically before drag, or click and hold the piece to be dragged, use up or down arrow on the keyboard to scroll to the target track, then drag and release the clip or track.
 
===Keyboard Shortcuts===
 
===Keyboard Shortcuts===
Line 262: Line 237:
 
*'''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".
 
*'''Yellow "snap" guidelines do not appear in re-opened projects or imported label tracks''' when dragging a selection to a label edge if "Snap To" is checked and a high resolution Selection Format chosen. Formats affected include "hh:mm:ss + CDDA frames (75 fps)", "hh:mm:ss + milliseconds" and "hh:mm:ss + samples".
 
===Miscellaneous platform-specific issues===
 
===Miscellaneous platform-specific issues===
* (Linux) '''A playback or recording freeze with pulseaudio may occur''' if repeatedly starting and stopping playback or recording in quick succession (or holding down the Play or Record button).  '''Workarounds:''' Try launching Audacity from the terminal with the pulse latency set in an environment variable, for example: {{code|1=env PULSE_LATENCY_MSEC=30 audacity}}  Alternatively, bypass pulseaudio by setting the playback and recording device to an ALSA (hw) choice in Device Toolbar.
+
* (Linux) '''A playback or recording freeze with pulseaudio may occur''' if repeatedly starting and stopping playback or recording in quick succession (or holding down the Play or Record button).  '''Workarounds:''' Try launching Audacity from the terminal with the pulse latency set in an environment variable, for example: <ul style="list-style-image: none; list-style-type: none">
 +
{{code|1=env PULSE_LATENCY_MSEC=30 audacity}}  Alternatively, bypass pulseaudio by setting the playback and recording device to an ALSA (hw) choice in Device Toolbar.</ul>
 
* (Mac OS X) If using Audacity when the "Hear" audio plug-in is running (or has been since boot), there will be excessive memory usage which could cause a crash: this appears to be due to buggy memory allocation in "Hear"
 
* (Mac OS X) If using Audacity when the "Hear" audio plug-in is running (or has been since boot), there will be excessive memory usage which could cause a crash: this appears to be due to buggy memory allocation in "Hear"
 
* (Mac OS X) Very occasionally, users may find that after running Audacity, other media players don't produce any sound, or crash:  to resolve this, set up your sound device in Apple Audio MIDI Setup to work in stereo, 16-bit, with a sample rate of 44100 Hz or 48000 Hz, and set the sample format and rate identically in Audacity. More help at: http://audacityteam.org/forum/viewtopic.php?f=17&t=5064
 
* (Mac OS X) Very occasionally, users may find that after running Audacity, other media players don't produce any sound, or crash:  to resolve this, set up your sound device in Apple Audio MIDI Setup to work in stereo, 16-bit, with a sample rate of 44100 Hz or 48000 Hz, and set the sample format and rate identically in Audacity. More help at: http://audacityteam.org/forum/viewtopic.php?f=17&t=5064
Line 270: Line 246:
 
* If you change the meter range in Preferences this is not reflected in the Mixer Board meters until restart.
 
* If you change the meter range in Preferences this is not reflected in the Mixer Board meters until restart.
 
* (Linux) Meters may not respond immediately to playback which could cause them to report incorrect peak level or not display clipping.
 
* (Linux) Meters may not respond immediately to playback which could cause them to report incorrect peak level or not display clipping.
===None===
 
 
  
// Already release noted in "Notes for Windows" div at the top of each release note.
 
// See Bug 51
 
// See bug 33
 
// See bug 51
 
// See bug 665
 
// see bug 602
 
//See bug 33
 
//See bug 33
 
//See bug 33
 
//See bug 36
 
//See bug 665
 
//See bug 665
 
//See bug 665
 
//See bug 665
 
//see bug 36
 
In "Notes for Windows"
 
*'''The language choice in the Windows EXE installer for Audacity only selects the language for the installer.''' The language Audacity runs in is determined by the "Format" for date and time in the "Region and Language" section of the Windows Control Panel. To change the Audacity language, please see these [http://manual.audacityteam.org/o/man/faq_about_audacity.html#language instructions].
 
See Bug 36.
 
See bug 33
 
See bug 393.
 
See bug 51
 
 
===Playback and Recording===
 
===Playback and Recording===
 
* '''Append Record with Transport > Overdub (on/off) enabled may cause periodic playthrough''' of previously recorded audio. If you use the Stop button or SPACE to stop the previous recording instead of  SHIFT + A (Stop and Set Cursor), this may reduce occurrences of the issue.
 
* '''Append Record with Transport > Overdub (on/off) enabled may cause periodic playthrough''' of previously recorded audio. If you use the Stop button or SPACE to stop the previous recording instead of  SHIFT + A (Stop and Set Cursor), this may reduce occurrences of the issue.
Line 303: Line 256:
 
* (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 [http://www.cycling74.com/products/soundflower Soundflower] to send the Audacity output to an audio application that works with the headset.
 
* (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 [http://www.cycling74.com/products/soundflower 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 [http://www.rogueamoeba.com/freebies/ LineIn] application also provides software playthrough.
 
* (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 [http://www.rogueamoeba.com/freebies/ LineIn] application also provides software playthrough.
* (Windows) "Windows WDM-KS" host is currently the least compatible of the four hosts, and may produce "error opening sound device" on some machines or have other quirks (such as some inputs not being available under this host).  Please report detailed problems to [http://audacity.sourceforge.net/contact/#feedback our feedback address] and state your exact version of Windows.
+
<!--* (Windows) "Windows WDM-KS" host is currently the least compatible of the four hosts, and may produce "error opening sound device" on some machines or have other quirks (such as some inputs not being available under this host).  Please report detailed problems to [https://web.audacityteam.org/contact/#feedback our feedback address] and state your exact version of Windows.-->
** The input slider in [http://manual.audacityteam.org/o/man/device_toolbar.html Device Toolbar] is disabled for all or most inputs. Please use the Windows system input slider instead.  
+
* (Windows) The input slider in [https://manual.audacityteam.org/o/man/device_toolbar.html 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) 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 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 [http://manual.audacityteam.org/o/man/device_toolbar.html Device Toolbar] to change the devices as needed, then Audacity will remember them.
+
* (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 [https://manual.audacityteam.org/o/man/device_toolbar.html Device Toolbar] to change the devices as needed, then Audacity will remember them.
* (Windows) Audacity is incompatible (or not fully compatible) with some professional sound cards or audio devices, and may crash or have limited or faulty functionality. Occasionally, this may be true of some AC97 devices built into the motherboard. '''Workaround:''' make a different sound card your default when using Audacity, but please e-mail the following details to our [http://audacity.sourceforge.net/contact/#feedback feedback address]:
+
* (Windows) Audacity is incompatible (or not fully compatible) with some professional soundcards or audio devices, and may crash or have limited or faulty functionality. Occasionally, this may be true of some AC97 devices built into the motherboard. '''Workaround:''' make a different soundcard your default when using Audacity, but please email the following details to our [https://web.audacityteam.org/contact/#feedback feedback address]:
 
** Your version of Windows and Service Pack
 
** Your version of Windows and Service Pack
** Name, model number and driver version number of the sound card or device.<p>'''Note:''' [[Multichannel Recording]] in Audacity is often not possible with professional devices unless you compile Audacity with [[ASIO Audio Interface|ASIO]] support.</p>
+
** Name, model number and driver version number of the soundcard or device.<p>'''Note:''' [[Multichannel Recording]] in Audacity is often not possible with professional devices unless you compile Audacity with [[ASIO Audio Interface|ASIO]] support.</p>
 
* (Windows) The "Windows WASAPI" host currently has the following limitations:
 
* (Windows) The "Windows WASAPI" host currently has the following limitations:
** The only available inputs are "loopback" inputs for [http://manual.audacityteam.org/o/man/tutorial_recording_computer_playback_on_windows.html recording computer playback].   
+
** The only available inputs are "loopback" inputs for [https://manual.audacityteam.org/o/man/tutorial_recording_computer_playback_on_windows.html recording computer playback].   
** The input slider in [http://manual.audacityteam.org/o/man/device_toolbar.html Device Toolbar] is disabled.  
+
** The input slider in [https://manual.audacityteam.org/o/man/device_toolbar.html 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.  
 
** 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 [http://manual.audacityteam.org/o/man/selection_toolbar.html Project Rate] set to 44100 Hz . Setting other project rates will cause Audacity to resample the input to the project rate any may cause glitches in the recorded audio.  
+
** Loopback recordings should only be made with the Audacity [https://manual.audacityteam.org/o/man/selection_toolbar.html Project Rate] set to 44100 Hz . Setting other project rates will cause Audacity to resample the input to the project rate any may cause glitches in the recorded audio.  
 
** "Audio to buffer" in Recording Preferences cannot be used to adjust recording latency.
 
** "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.
 
* 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.
Line 323: Line 276:
 
*(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 Vista, 7) If you change the explicit output and/or input device selected in Device Toolbar or Devices Preferences and then change "Host", the selected devices will change back to those originally selected.
 
*(Windows XP and earlier) Changing the default playback or recording devices in the Windows Control Panel while Audacity is open may cause all the playback or recording choices in Device Toolbar to produce silence (or to fail with "Error opening sound device"). This problem may also occur when connecting or disconnecting a USB device while Audacity is open. '''Workaround:''' Click Transport > Rescan Audio Devices then you can play or record.
 
*(Windows 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.
 +
 
===Program Launch===
 
===Program Launch===
 
* (Linux) If a Bluetooth audio device is in use on a PulseAudio system, Audacity may hang on launch on initial attempts, then after eventual launch Bluetooth will no longer work on the system. '''Workarounds:'''  
 
* (Linux) If a Bluetooth audio device is in use on a PulseAudio system, Audacity may hang on launch on initial attempts, then after eventual launch Bluetooth will no longer work on the system. '''Workarounds:'''  
Line 328: Line 282:
 
** To prevent Audacity affecting Bluetooth support, move /usr/share/alsa/bluetooth.conf to another location then reboot, or create a symbolic link from /var/lib/alsa/asound.state to /dev/null and reboot.
 
** To prevent Audacity affecting Bluetooth support, move /usr/share/alsa/bluetooth.conf to another location then reboot, or create a symbolic link from /var/lib/alsa/asound.state to /dev/null and reboot.
 
* (Windows and OS X)  '''"Install VST Effects" dialog:'''
 
* (Windows and OS X)  '''"Install VST Effects" dialog:'''
** '''The dialog lists more than VST effects:''' On first use, Audacity scans for [http://manual.audacityteam.org/o/man/effect_menu.html#VST_Effects VST effects] then (before launching Audacity) presents a dialog where you can choose which VST effects to load into the Audacity Effect menu. Remove the checkmark from any VST effects you do not want to load then click {{button|OK}} to load the checkmarked effects. If you click {{button|Cancel}} the dialog will reappear on next Audacity launch.
+
** '''The dialog lists more than VST effects:''' On first use, Audacity scans for [https://manual.audacityteam.org/o/man/effect_menu.html#VST_Effects VST effects] then (before launching Audacity) presents a dialog where you can choose which VST effects to load into the Audacity Effect menu. Remove the checkmark from any VST effects you do not want to load then click {{button|OK}} to load the checkmarked effects. If you click {{button|Cancel}} the dialog will reappear on next Audacity launch.
 
** '''VST instruments will appear in the list but are not supported''', so will '''not''' load even if checkmarked.
 
** '''VST instruments will appear in the list but are not supported''', so will '''not''' load even if checkmarked.
 
** '''On Windows the dialog will appear even if you have no VST effects''', because Audacity detects the two shipped LADPSA plug-ins (hard_limiter_1413.dll and sc4_1882.dll) and also any optional LADSPA DLL plug-ins you may have installed. These LADSPA plug-ins will load whether you enable them in the dialog or not. '''Therefore you should just click {{button|OK}} on the dialog if you have no VST effects'''.
 
** '''On Windows the dialog will appear even if you have no VST effects''', because Audacity detects the two shipped LADPSA plug-ins (hard_limiter_1413.dll and sc4_1882.dll) and also any optional LADSPA DLL plug-ins you may have installed. These LADSPA plug-ins will load whether you enable them in the dialog or not. '''Therefore you should just click {{button|OK}} on the dialog if you have no VST effects'''.
Line 340: Line 294:
 
* 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 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 .
 
* Projects created by previous versions of Audacity may contain audio "block files" longer than the project format allows. Reopening such projects in previous versions might or might not result in deletion of the overlong audio. Audacity has been provisionally fixed so that it can no longer create or delete overlong files, but it cannot read any such files it encounters. If overlong files are found, a "Problems Reading Sequence Tags" message will display .
**  If you continue with the offered repair then choose "Continue without deleting" in the Orphan Block File(s) dialogue, the overlong files will be retained as "orphans" in the project's _data folder but will appear as silence in the track(s).  
+
**  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) dialogue,  the project will quit and will not be changed in any way.
+
** 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.
 
<ul style="list-style-image: none; list-style-type: none">
 
<ul style="list-style-image: none; list-style-type: none">
If you encounter the "Problems Reading Sequence Tags" message, please write to our [http://audacity.sourceforge.net/contact/#feedback feedback address] with a copy of the .aup file and the log as found at Help > Show Log.</ul>
+
If you encounter the "Problems Reading Sequence Tags" message, please write to our [https://web.audacityteam.org/contact/#feedback feedback address] with a copy of the .aup file and the log as found at Help > Show Log.</ul>
 
* 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.
 
* 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.
 
===Time Tracks===
 
===Time Tracks===
Line 350: Line 304:
 
* (OS X and Linux) Using keyboard Undo while dragging envelope points or sample points will crash Audacity (this affects Envelope Tool, Draw Tool and Multi-Tool).
 
* (OS X and Linux) Using keyboard Undo while dragging envelope points or sample points will crash Audacity (this affects Envelope Tool, Draw Tool and Multi-Tool).
 
*'''Meter Toolbar vertical orientation''' is not remembered across sessions, and resizing the meters reverts from vertical to horizontal.
 
*'''Meter Toolbar vertical orientation''' is not remembered across sessions, and resizing the meters reverts from vertical to horizontal.
*(Windows XP) '''Transport and Tools Toolbar buttons all display as Pause buttons.''' The buttons may redraw correctly if you hover over them. '''Workaround:''' You can use [http://manual.audacityteam.org/o/man/keyboard_shortcut_reference.html keyboard shortcut alternatives] for the buttons instead.
+
*(Windows XP) '''Transport and Tools Toolbar buttons all display as Pause buttons.''' The buttons may redraw correctly if you hover over them. '''Workaround:''' You can use [https://manual.audacityteam.org/o/man/keyboard_shortcut_reference.html keyboard shortcut alternatives] for the buttons instead.
===VST and Audio Units===
 
* (Windows and Mac OS X) '''When running VST effects in [http://manual.audacityteam.org/o/man/effects_preferences.html#vst graphical mode] the controls of many plug-ins do not visibly respond when loading a preset file from the "Load" button'''. The new settings are however loaded internally, will apply when running the effect and will be visible if you reopen the effect after running it. Controls do respond to loading a preset file if you turn off graphical mode.
 
  
 
+
==Bugs requiring more investigation==
=Release Notes with Bugzilla Links=
+
{{advice|
 
+
<ul><li>Very occasionally, Audacity projects may reopen with missing block files, orphan block files and/or silenced audio data. There may be unwanted renaming or moving of AU files within the project. We believe having multiple projects open at once or having projects open in file manager programs are among the possible causes. See [[Bug:137]] for more background to this.  
{| cellspacing="0" cellpadding="3" border="1" bordercolor="Black"
+
<li> The AUP file may be saved with references to only a few of the AU files, again leading to "orphan block file" warnings. Sometimes the AUP file may not be found after saving and closing the project.  
! scope="col" width="100" |Group
+
<li>Sometimes errors occur when saving the project or when Audacity autosaves, perhaps wrongly suggesting the disk is full or not writable (if this happens, try exporting the audio as WAV).</ul>
! scope="col" width="500" |Description
+
Please write to our [https://web.audacityteam.org/contact/#feedback feedback address] if you encounter any of the above symptoms. As many as possible of the following will help us enormously if you can attach them to your report:
|----
+
* A copy of the saved AUP project file 
|Accessibility
+
* A copy of the AUTOSAVE (temporary project) file. This file is stored inside the "AutoSave" folder in Audacity's [https://manual.audacityteam.org/o/man/preferences.html#stored application data folder].
|{{P3|Extra=|Description=Bug:33 [http://bugzilla.audacityteam.org/show_bug.cgi?id=33 Accessibility issues]}}
+
* For problems that occur when reopening or working in a project, the log file at {{path|Help > Show Log...}}.}}
* Many, but not all parts of the Audacity interface are accessible on Windows and Mac to those who can't use a mouse, and/or use a screen reader. It may be possible to make more of Audacity accessible in the longer term. For details, see http://manual.audacityteam.org/o/man/accessibility.html
 
* There are some accessibility bugs in the parts of Audacity that are accessible (or behavior may vary according to the specific screen reader).  
 
** Some interface text or markings remain in black when using High Contrast light-on-dark themes, so cannot be read properly.
 
** Install VST Effects dialog: The list view of plug-ins is a check box list view, and all the plug-ins are checked initially. Unfortunately Jaws and Window-Eyes do not read whether or not a check box is checked, but you can still press SPACE to change this.
 
** Keyboard Preferences: Window-Eyes doesn't read the key bindings when View by Tree is selected, and may not always read the bindings in other views.
 
** (OS X) It is not possible to TAB through Keyboard Preferences.
 
** (OS X) Issues with VoiceOver:
 
*** (reported on OS X 10.9.x) After exporting, the black accessibility area is trapped in the Tooldock area, so there is no way to read the tracks. '''Workaround:''' Save as a project, close the project then reopen it. You can then navigate the tracks with VoiceOver.
 
*** If you use arrow keys to navigate the Timetext controls in Selection Toolbar, VoiceOver stops reading. '''Workaround:''' Use Control-Option-W
 
*** When you TAB forwards from "Audio Position" in Selection Toolbar, the "Selection End" or "Selection Length" radio button is read as "Selection Start". When you use COMMAND + F6 or COMMAND + SHIFT + F6 to move directly into "Selection End" from another toolbar, the button is read as "Selection Start".
 
*** Mixer Toolbar input/output sliders are not read, but just described as "multiple indicators". The "Graphic EQ"  and vertical sliders in Equalization *are* read.
 
*** Metadata Editor table not read.
 
*** Edit Labels dialog not read.
 
*** In the "Edit Chains" window, only the first command in the "Chain" list is read, and it is only read when first accessed. In the "Select Command" window for inserting a new command in a Chain, commands in the table are not read.
 
*** "Manage Curves" table in Equalization not read.
 
** (Linux) Using the Unity shell, most or all keyboard shortcuts are not listed in the Audacity menus. Gnome Fallback is not affected. '''Workaround:''' You can view shortcuts at {{menu|Edit > Preferences: Keyboard}} or online at http://manual.audacityteam.org/o/man/keyboard_shortcut_reference.html.
 
** (Linux) SPACE cannot be used to change context menu items that have a checkbox (such as Selection Format in the context menu of TimeText digits, or Mono/Left/Right and Set Rate and Set Sample Format in the Track Drop-Down Menu). Using SPACE in these menus could crash Audacity. '''Workaround:''' Use ENTER instead of SPACE to select the new choice.
 
** (Linux) Issues with Orca:
 
*** Audacity tracks are not read.  
 
*** Not all toolbar controls are read, examples being Timetext controls, Project Rate and controls in Device Toolbar.
 
*** Not all controls in Preferences are read.
 
|----
 
|Accessibility
 
|{{P3|Extra=|Description=Bug:186 [http://bugzilla.audacityteam.org/show_bug.cgi?id=186 Some interface elements invisible in "High Contrast" themes (or other themes including light-on-dark)]}}
 
*See issue 33.
 
|----
 
|Accessibility
 
|{{P3|Extra=|Description=Bug:249 [http://bugzilla.audacityteam.org/show_bug.cgi?id=249 A track is always shown as being the focus]}}
 
*See issue 33.
 
|----
 
|Bugs requiring more investigation
 
|{{P3|Extra=|Description=Bug:287 [http://bugzilla.audacityteam.org/show_bug.cgi?id=287 Tracks > Resample removes end of waveform when using libsamplerate with Best Sinc Interpolator]}}
 
 
* (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.
 
* (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.
|----
 
|Bugs requiring more investigation
 
|{{P3|Extra=|Description=Bug:12 [http://bugzilla.audacityteam.org/show_bug.cgi?id=12 Input volume reset if changed before recording]}}
 
 
* (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.
 
* (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)
 
** 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)
|----
 
|Bugs requiring more investigation
 
|{{P3|Extra=|Description=Bug:11 [http://bugzilla.audacityteam.org/show_bug.cgi?id=11 Occasional corruption in list of motherboard inputs when USB device connected]}}
 
 
* (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.   
 
* (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.
 
** 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.
|----
 
|Bugs requiring more investigation
 
|{{P3|Extra=|Description=Bug:417 [http://bugzilla.audacityteam.org/show_bug.cgi?id=417 Error opening input device on upgrading from < 1.3.13, requiring device rescan]}}
 
 
* (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.  
 
* (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 [[Updating Sound Device Drivers|here]].
 
** 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 [[Updating Sound Device Drivers|here]].
|----
 
|Bugs requiring more investigation
 
|{{P3|Extra=|Description=Bug:291 [http://bugzilla.audacityteam.org/show_bug.cgi?id=291 USB/FW devices record silence or have reduced recording channels]}}
 
 
* (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.
 
* (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).
 
** Please report make and model number of devices that exhibit the issue, and your operating system details (for example, Windows 7 Service Pack 1).
|----
 
|Bugs requiring more investigation
 
|{{P3|Extra=|Description=Bug:218 [http://bugzilla.audacityteam.org/show_bug.cgi?id=218 Delays up to 30 seconds fitting and unfitting long projects]}}
 
 
* (Windows) There may be substantial delays drawing the waveform in longer projects. These include:
 
* (Windows) There may be substantial delays drawing the waveform in longer projects. These include:
 
** opening saved projects that were fitted to the window
 
** 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
 
** 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.
 
** progress dialog remains white for a long time after the progress bars complete for a file import or effect.
|----
 
|Chains
 
|{{P3|Extra=|Description=Bug:549 [http://bugzilla.audacityteam.org/show_bug.cgi?id=549 Add missing export formats to Chains]}}
 
* '''Chains do not currently support export as AIFF, Other uncompressed files or any formats supported by FFmpeg.'''
 
|----
 
|Chains
 
|{{P3|Extra=|Description=Bug:548 [http://bugzilla.audacityteam.org/show_bug.cgi?id=548 Add export format options and export sample rate to Chain parameters]}}
 
* '''You cannot set export format options or export sample rate in the Chain.''' If you need to specify export options other than the current default, import or generate some audio, File > Export, select the audio type, click "Options..." then choose and save the option and cancel the export.
 
|----
 
|Compiling
 
|{{P3|Extra=|Description=Bug:609 [http://bugzilla.audacityteam.org/show_bug.cgi?id=609 Bugs in configure progress and final output when enabling other than libsoxr]}}
 
* (Linux) '''New libsoxr resampling library:''' Default ./configure will enable a new library [https://sourceforge.net/p/soxr/wiki/Home/ libsoxr] for resampling and disable libresample and libsamplerate (the previous resampling libraries). [http://www.cmake.org/ Cmake] is required to build libsoxr. We strongly recommend libsoxr for its combination of high quality and high speed.
 
** '''Only one resampling library is permitted.''' If you enable either libresample or libsamplerate in configure, libsoxr will not be enabled. Any configure of resampling libraries other than  libsoxr only will enable one only of libresample, libsamplerate or libsoxr in that order of precedence; however the intermediate configure output may suggest that other libraries will be favored. 
 
** '''To enable libresample''', your configure must include --without-libsoxr  as well as --with-libresample.
 
|----
 
|Compiling
 
|{{P3|Extra=|Description=Bug:178 [http://bugzilla.audacityteam.org/show_bug.cgi?id=178 Audacity will not compile with MS VC++ 2010 Express]}}
 
* (Windows) Compilation with Visual Studio 2010 is not  supported or recommended. See the Wiki page [http://wiki.audacityteam.org/wiki/Developing_On_Windows#What_about_Visual_Studio_2010.3F__Or_64-bit.3F Developing on Windows] for information.
 
|----
 
|Compiling
 
|{{P3|Extra=|Description=Bug:54 [http://bugzilla.audacityteam.org/show_bug.cgi?id=54 LADSPA plug-ins not categorisable despite compiling with USE_LIBLRDF defined and installing RDF data files in Audacity data directory]}}
 
* (Windows) LADSPA effects cannot be categorized even when Audacity is compiled with USE_LIBLRDF defined.
 
|----
 
|Compiling
 
|{{P3|Extra=|Description=Bug:540 [http://bugzilla.audacityteam.org/show_bug.cgi?id=540 Audacity does not build against FFmpeg SVN]}}
 
*(Linux) Audacity may not always compile against supported versions of libav or FFmpeg. Audacity 2.0.6 supports FFmpeg 1.2 or higher (FFmpeg 2.2.3 is known to work) or libav 0.8 or higher.
 
** Dynamic loading (as in default Audacity ./configure) requires building against the FFmpeg project - it will not build against the libav* headers from the libav project. '''Workarounds:''' Configure Audacity with --disable-dynamic-loading. If dynamic loading is required, build against FFmpeg instead of libav, or you can build against libav if you remove the "#define IS_FFMPEG_PROJECT 1" line in src/FFmpeg.h.
 
** Audacity may still build against no-longer-supported FFmpeg versions (such as FFmpeg 0.8 which is system-installed on Debian Wheezy), but configuring with --disable-dynamic-loading will be necessary. FFmpeg 0.8 has at least one known issue in Audacity 2.0.6 or later: mono WMA files export with no audio data. This issue will not be fixed given FFmpeg 0.8 is no longer supported by Audacity 2.0.6. 
 
** Building against self-compiled FFmpeg 2.2.2 with --disable-dynamic-loading the only argument fails on Ubuntu 13.10 with "undefined reference to 'av_codec_is_encoder'". '''Workaround:''' Configuring with --disable-dynamic-loading and --with-lib-preference="local" (or at least  --with-ffmpeg="local") may build successfully, but may not disable Libraries Preferences. The best solution may be not to disable dynamic loading.
 
|----
 
|Effects (VST and Audio Units)
 
|{{P3|Extra=|Description=Bug:761 [http://bugzilla.audacityteam.org/show_bug.cgi?id=761 VST presets (OS X): correct extension no longer offered in file name/no longer added if omitted]}}
 
* (OS X) '''When saving presets, the FXP or XML file extension is not automatically offered in the file name, and not added by Audacity if you omit it.'''  Make sure the extension you add is the same as that shown in the "File Format" drop-down menu, otherwise the preset will not be loadable.
 
|----
 
|Effects (VST and Audio Units)
 
|{{P3|Extra=|Description=Bug:665 [http://bugzilla.audacityteam.org/show_bug.cgi?id=665 Summary: AU and VST crash and hang bugs]}}
 
* (OS X) The following plug-ins may cause Audacity to crash if they are used after starting Audacity. 
 
** '''AURoundTripAAC''' from "Apple audio mastering tools"  (this requires OS X 10.6 or later so may crash on 10.4 or 10.5).
 
** '''[http://www.bluecataudio.com/Products/Product_FreqAnalyst/ Blue Cat FreqAnalyst (real time)]'''
 
** '''[http://www.olilarkin.co.uk/index.php?p=eseries Endless Series] AU'''
 
** '''Digitech RP250''' (effects pedal)
 
** '''MNoiseGenerator''' AU and others in [http://www.meldaproduction.com/plugins/product.php?id=MFreeEffectsBundle 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'''
 
<ul style="list-style-image: none; list-style-type: none">
 
'''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 [[User:BillWharrie/How_to_prevent_Audio_Unit_and_VST_plug-ins_crashing_Audacity_launch_on_Mac_OS_X|this page]] for more help.</ul>
 
* (Windows)
 
** DISTRHO Mini Series VST's from http://distrho.sourceforge.net/plugins.php crash Audacity in graphic mode but will run in text mode (open the Effects Preferences and uncheck "Display VST effects in graphical mode").
 
** Waves v5 may cause Audacity to hang if you select it in the "Install VST Effects" dialog then click OK.
 
|----
 
|Effects (VST and Audio Units)
 
|{{P3|Extra=|Description=Bug:760 [http://bugzilla.audacityteam.org/show_bug.cgi?id=760 VST (OS X) some effects no longer accept type or paste input in presets drop-down.]}}
 
*(OS X) '''Some VST plug-ins no longer allow text input in the presets drop-down, either by typing or pasting.''' Examples are Sound Hack "Delay Trio / Freesound Bundle" and Blue Cat.
 
|----
 
|Effects (VST)
 
|{{P3|Extra=|Description=Bug:758 [http://bugzilla.audacityteam.org/show_bug.cgi?id=758 VST BlueCat (OS X): Attempting to save a preset locks out the main window.]}}
 
* (OS X) '''Blue Cat plug-ins:''' Opening the dialog to save a preset will hide the plug-in interface and lock out the main Audacity window. '''Workaround:''' Right-click or CONTROL-click over Audacity's Dock icon, choose "Quit" then choose to save changes or not. Other plug-ins that use JUCE (such as GRM Tools) are also likely to be affected.
 
|----
 
|Effects and Analysis
 
|{{P3|Extra=|Description=Bug:607 [http://bugzilla.audacityteam.org/show_bug.cgi?id=607 LADSPA generate plug-ins fail when white space selected]}}
 
* '''LADSPA generate plug-ins may fail to generate into an empty track''' or into white space separating audio clips. '''Workaround:''' Before using the LADSPA generator, generate audio using any of the Audacity Generators above the divider in the Generate Menu, then generate into that audio selection.
 
|----
 
|Effects and Analysis
 
|{{P3|Extra=|Description=Bug:661 [http://bugzilla.audacityteam.org/show_bug.cgi?id=661 A few shipped Nyquist plug-ins fail with comma as decimal separator]}}
 
* '''Nyquist plug-ins:''' In locales where comma is the decimal separator, entering a comma in a text input box that has no associated slider will produce an error message, or only result in the whole number before the comma (for example, in Regular Interval Labels). '''Workaround:''' Use a dot (period) as the decimal separator.
 
|----
 
|Effects and Analysis
 
|{{P3|Extra=|Description=Bug:764 [http://bugzilla.audacityteam.org/show_bug.cgi?id=764 Sliding Time Scale / Pitch Shift may crash using libsbsms < 2.0.2]}}
 
* (Linux) '''Sliding Time Scale / Pitch Shift may crash randomly in Audacity built with pre-2.0.2 versions of libsbsms.''' This may occur for example in the Ubuntu package of Audacity 2.0.5 on Ubuntu 14.04. '''Workaround:'''' Build Audacity configured --with-sbsms="local", or use the Audacity package in Ubuntu 14.10 which uses libsbsms 2.0.2-1.
 
|----
 
|Effects and Analysis
 
|{{P3|Extra=|Description=Bug:142 [http://bugzilla.audacityteam.org/show_bug.cgi?id=142 VST Plug-ins: Wow6432 registry keys not searched on 64-bit systems]}}
 
* (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 .
 
|----
 
|Effects and Analysis
 
|{{P3|Extra=|Description=Bug:590 [http://bugzilla.audacityteam.org/show_bug.cgi?id=590 Audacity crashes with LADSPA blop plug-ins]}}
 
* (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.
 
|----
 
|Effects and Analysis
 
|{{P3|Extra=|Description=Bug:47 [http://bugzilla.audacityteam.org/show_bug.cgi?id=47 LADSPA Multiband EQ may not be visible in Effect menu (occurs on Windows XP), and crashes soon after opening]}}
 
* (Windows) LADSPA Multiband EQ may not be visible in Effect menu (occurs on Windows XP), and crashes soon after opening
 
|----
 
|Effects and Analysis
 
|{{P3|Extra=|Description=Bug:231 [http://bugzilla.audacityteam.org/show_bug.cgi?id=231 Cut Preview should play all selected/sync-locked tracks]}}
 
* Cut Preview only plays the upper track of multiple selected or Sync-Locked tracks.
 
|----
 
|Effects and Analysis
 
|{{P3|Extra=|Description=Bug:7 [http://bugzilla.audacityteam.org/show_bug.cgi?id=7 Nyquist effects join separate clips together, and add spurious split lines if applied over clip boundaries]}}
 
* 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.
 
|----
 
|Effects and Analysis
 
|{{P3|Extra=|Description=Bug:570 [http://bugzilla.audacityteam.org/show_bug.cgi?id=570 Audio playback / Nyquist latency settings, not working correctly]}}
 
* 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.
 
|----
 
|Effects and Analysis
 
|{{P3|Extra=|Description=Bug:208 [http://bugzilla.audacityteam.org/show_bug.cgi?id=208 Some effects delete Envelope Control Points, or do not move them when timeline changes]}}
 
* The following effects remove envelope control points: Change Speed/Pitch/Tempo; Equalization; Noise Removal; Sliding Time Scale/Pitch Shift; any Nyquist effect in the Effect menu. Workaround: Use Tracks > Mix and Render to apply the envelope to the waveform before applying the effect.
 
* The Reverse effect retains the control points, but does not move them.
 
|----
 
|Effects and Analysis
 
|{{P3|Extra=|Description=Bug:52 [http://bugzilla.audacityteam.org/show_bug.cgi?id=52 Truncate Silence doesn't work well on multiple tracks]}}
 
* Truncate Silence doesn't work intuitively if run on multiple tracks. It may be preferable to run it on each track at a time.
 
|----
 
|Effects and Analysis
 
|{{P3|Extra=|Description=Bug:439 [http://bugzilla.audacityteam.org/show_bug.cgi?id=439 Nyquist effects overflow at > 2^31 samples]}}
 
*'''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.
 
|----
 
|Envelopes and Clips
 
|{{P3|Extra=|Description=Bug:501 [http://bugzilla.audacityteam.org/show_bug.cgi?id=501 Vertical drag in selected area of a clip gives wrong behaviour if selection extends past clip]}}
 
* '''A clip may now be vertically dragged from inside a selection region, but if that region extends over the edge of the clip into space or into an adjoining clip there may be unexpected behavior''':
 
** one channel of a stereo clip may jump sideways
 
** a mono clip may fail to horizontal-drag in its new track
 
** faint, specious clip lines could occur if the clip is dragged back to its original track.
 
<ul style="list-style-image: none; list-style-type: none">'''Workaround:''' Edit > Undo if necessary then drag from outside the selection region or single-click in the clip to remove the selection.</ul>
 
|----
 
|Envelopes and Clips
 
|{{P2|Extra=|Description=Bug:756 [http://bugzilla.audacityteam.org/show_bug.cgi?id=756 Undo fails silently when there are several clips in the track]}}
 
* '''Undo may fail silently after applying an effect or edit''' across one or more split lines. '''Workaround:''' Effect > Repeat the effect from the top of the Effect Menu then undo both applications of the effect, or open View > History... and click on the step above the currently indicated line.
 
|----
 
|Envelopes and Clips
 
|{{P3|Extra=|Description=Bug:389 [http://bugzilla.audacityteam.org/show_bug.cgi?id=389 Left-click to merge a stereo clip can move other clips if track was made from mono]}}
 
* Left-clicking in a stereo track to merge a clip at a split line may cause other clips to move. It is believed this only happens after having used the Track Drop-Down Menu to make two mono tracks into stereo. '''Workaround:''' Select over the split line and Edit > Clip Boundaries > Join.
 
|----
 
|Envelopes and Clips
 
|{{P3|Extra=|Description=Bug:527 [http://bugzilla.audacityteam.org/show_bug.cgi?id=527 Envelope corrupted when pasting audio clips into track]}}
 
* When pasting audio into tracks with envelope points, the envelope points may move in unexpected ways, so causing unwanted amplitude adjustments.
 
|----
 
|Exports
 
|{{P3|Extra=|Description=Bug:317 [http://bugzilla.audacityteam.org/show_bug.cgi?id=317 FFmpeg: "M4A Files" exports take unreasonably long compared to (external program)]}}
 
* (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.
 
|----
 
|Exports
 
|{{P3|Extra=|Description=Bug:339 [http://bugzilla.audacityteam.org/show_bug.cgi?id=339 FFmpeg: watch libfaad and native AAC encoder in case they fix issues that prevent us using them in Audacity's FFmpeg]}}
 
* (Linux) Files exported using the '''FFmpeg native AAC encoder''' included with many system versions of FFmpeg may be of poor quality. This is an issue with the library itself. '''Workaround:''' When compiling FFmpeg, configure with the libfaac encoder thus: --disable-encoder=aac --enable-libfaac --enable-nonfree. Note that libfaac has an issue not present in the native FFmpeg encoder that saved files are short at the end by about 3000 samples. Alternatively build the VisualOn AAC encoder library and configure FFmpeg with --disable-encoder=aac --disable-encoder=libfaac --enable-libvo-aacenc.
 
* (Linux) Mono AAC files import as stereo if FFmpeg uses the libfaad decoder. This is again an issue with the library itself.
 
|----
 
|Exports
 
|{{P3|Extra=|Description=Bug:165 [http://bugzilla.audacityteam.org/show_bug.cgi?id=165 Freeze using nero AAC encoder on multiple cores]}}
 
* 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 [http://manual.audacityteam.org/o/man/faq_installation_and_plug_ins.html#ffdown FFmpeg] to your computer, or set Audacity to use only one CPU core.
 
|----
 
|Exports
 
|{{P3|Extra=|Description=Bug:59 [http://bugzilla.audacityteam.org/show_bug.cgi?id=59 Custom FFmpeg Export includes many invalid combinations]}}
 
* 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.
 
|----
 
|Exports
 
|{{P3|Extra=|Description=Bug:46 [http://bugzilla.audacityteam.org/show_bug.cgi?id=46 WAVEX (Microsoft) headers: GSM 6.10 files cannot be exported, and U-Law/A-Law files may not be playable]}}
 
* WAVEX (Microsoft) headers: GSM 6.10 files cannot be exported, and U-Law/A-Law files may not be playable.
 
|----
 
|Imports and Exports
 
|{{P3|Extra=|Description=Bug:407 [http://bugzilla.audacityteam.org/show_bug.cgi?id=407 FFmpeg: AAC export below 22050 Hz produces zero bytes file]}}
 
* '''AAC exports using "M4A (AAC) Files (FFmpeg)" with project rate below 22050 Hz produce a zero bytes file if the linked to FFmpeg is configured with the default AAC encoder or libfaac. This will not affect the recommended builds of FFmpeg for Windows and Mac OS X which are built with libvo-aacenc. '''Workaround:''' You can export AAC below 22050 Hz using default-configured FFmpeg by choosing (external program) export instead.
 
|----
 
|Imports and Exports
 
|{{P3|Extra=|Description=Bug:421 [http://bugzilla.audacityteam.org/show_bug.cgi?id=421 Crash importing WAV with MP3 extension when extended import rule forces use of libmad]}}
 
* '''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.
 
|----
 
|Imports and Exports
 
|{{P3|Extra=|Description=Bug:653 [http://bugzilla.audacityteam.org/show_bug.cgi?id=653 Metadata: UTF-16 ID3 tags read incorrectly.]}}
 
* '''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 [http://www.foobar2000.org/download Foobar2000] for this purpose.
 
|----
 
|Imports and Exports
 
|{{P3|Extra=|Description=Bug:58 [http://bugzilla.audacityteam.org/show_bug.cgi?id=58 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) 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.
 
|----
 
|Imports and Exports
 
|{{P3|Extra=|Description=Bug:135 [http://bugzilla.audacityteam.org/show_bug.cgi?id=135 Custom FFmpeg Export dialogue does not respond to ENTER after clicking in the Formats or Codec selector]}}
 
* (Linux) Custom FFmpeg Export dialogue does not respond to ENTER after clicking in the Formats or Codec selector.
 
|----
 
|Imports and Exports
 
|{{P3|Extra=|Description=Bug:738 [http://bugzilla.audacityteam.org/show_bug.cgi?id=738 File formats not in info.plist cannot be dragged to Audacity's Dock icon.]}}
 
* (Mac OS X) Dragging audio files to Audacity's icon in the Dock will only import the file for WAV, AIFF, AU, MP2, MP3, OGG, FLAC and M4A. '''Workaround:''' Rename MP4 files (audio or video) to M4A extension. Alternatively the files may be dragged to the Audacity icon in the folder where you have Audacity installed, dragged into the open Audacity window or imported using the Audacity menus.
 
|----
 
|Imports and Exports
 
|{{P2|Extra=|Description=Bug:739 [http://bugzilla.audacityteam.org/show_bug.cgi?id=739 Exporting using (external program) crashes if unrecognised binary/wrong path or command syntax incorrect]}}
 
* (Mac OS X) Exporting using (external program) will crash using the built-in commands or if the absolute path is entered incorrectly or its accompanying command syntax is incorrect. See http://manual.audacityteam.org/o/man/exporting_to_an_external_program.html for how to browse to the correct path and enter the correct syntax.
 
|----
 
|Imports and Exports
 
|{{P3|Extra=|Description=Bug:119 [http://bugzilla.audacityteam.org/show_bug.cgi?id=119 Export Multiple: "/", "*" and "?" in label or track name handled incorrectly]}}
 
* (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).
 
|----
 
|Imports and Exports
 
|{{P3|Extra=|Description=Bug:296 [http://bugzilla.audacityteam.org/show_bug.cgi?id=296 Control characters in .aup tag values prevent project opening]}}
 
* (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 [http://manual.audacityteam.org/o/man/faq_errors.html#nwf here].
 
|----
 
|Imports and Exports
 
|{{P3|Extra=|Description=Bug:210 [http://bugzilla.audacityteam.org/show_bug.cgi?id=210 Repeatable crash accessing a file being written by Psycle]}}
 
* (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.
 
|----
 
|Imports and Exports
 
|{{P3|Extra=|Description=Bug:329 [http://bugzilla.audacityteam.org/show_bug.cgi?id=329 Triggering behaviour for "Files Missing" warning]}}
 
* 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.
 
|----
 
|Imports and Exports
 
|{{P3|Extra=|Description=Bug:550 [http://bugzilla.audacityteam.org/show_bug.cgi?id=550 Add Directories Preference to export to directory the file came from]}}
 
* 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.
 
|----
 
|Imports and Exports
 
|{{P3|Extra=|Description=Bug:762 [http://bugzilla.audacityteam.org/show_bug.cgi?id=762 FFmpeg: AAC Quality slider has no effect with libvo-aac encoder.]}}
 
* M4A (AAC) exports: The Quality Slider in "Specify AAC Options" has no effect if the FFmpeg library is built with the libvo-aac encoder, as are recommended builds of FFmpeg for Windows and Mac OS X. '''Workaround:''' Given the alternative AAC encoders for FFmpeg have other problems as described in these notes, you can instead export as WAV and convert to AAC in iTunes on Windows and Mac.
 
|----
 
|Imports and Exports
 
|{{P3|Extra=|Description=Bug:51 [http://bugzilla.audacityteam.org/show_bug.cgi?id=51 Metadata import/export occasionally non-orthogonal]}}
 
* Metadata:
 
** Album art and lyrics in imported metadata are lost when exporting. '''Workaround:''' Copy the lyrics (or search for them online) then add them back to the exported file in your favorite media player. Extract the album art using a tag editor such as [http://sourceforge.net/projects/idteid3tagedito/ IDTE] (or use [http://windows.microsoft.com/en-us/windows/add-change-media-player-album-art#1TC=windows-7 Windows Media Player] or iTunes to search online for the art) then add the art back to the exported file using your media player.   
 
** Tags other than the seven default [http://manual.audacityteam.org/o/man/metadata_editor.html Metadata Editor] tags will be rewritten as custom ID3 TXXX tags, which will cause them not to be seen in applications like Windows Media Player and iTunes. Common tag examples include "Album Artist", "BPM" and "Composer".
 
** ID3 v2.4 tags in imported MP3 files are not seen and will be removed on export.
 
** Audacity writes both ID3 v2.3 (TYER) and v2.4 (TDRC) tags for "Year", but any applications that require the older TYER on its own (without TDRC) will not see "Year" in Audacity-exported files. The id3 command-line application on Linux is one example. 
 
** AAC: Artist and Year metadata is not exported or imported due to a bug in FFmpeg 2.2.2. 
 
* WMA and APE (Monkeys Audio): "Artist Name" is not seen on importing the file (Audacity bug)
 
** Other metadata import/export may not always be consistent. This may depend on the program that created the imported tags and the program used to read the exported tags.
 
|----
 
|Imports and Exports
 
|{{P3|Extra=|Description=Bug:353 [http://bugzilla.audacityteam.org/show_bug.cgi?id=353 FFmpeg: WMA metadata not fully seen by most other apps]}}
 
* 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.
 
|----
 
|Imports and Exports
 
|{{P3|Extra=|Description=Bug:538 [http://bugzilla.audacityteam.org/show_bug.cgi?id=538 FFmpeg OD without seeking: an effect can be applied to a selection before the computation is made, silencing the audio.]}}
 
*"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.
 
|----
 
|Imports and Exports
 
|{{P3|Extra=|Description=Bug:745 [http://bugzilla.audacityteam.org/show_bug.cgi?id=745 MIDI: No overwrite warning on export]}}
 
*'''(Linux):''' When exporting to MIDI over an existing file, no overwrite warning is given.
 
|----
 
|Imports and Exports
 
|{{P3|Extra=|Description=Bug:420 [http://bugzilla.audacityteam.org/show_bug.cgi?id=420 Unintuitive/inconsistent Extended Import behaviour]}}
 
*'''By default, the importer used depends on the import method.''' For example, to be able to use [http://manual.audacityteam.org/o/man/faq_installation_and_plug_ins.html#ffdown 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 [http://manual.audacityteam.org/o/man/extended_import_preferences.html 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.
 
|----
 
|Imports and Exports
 
|{{P3|Extra=|Description=Bug:551 [http://bugzilla.audacityteam.org/show_bug.cgi?id=551 Export Multiple: Pass through common metadata to next window]}}
 
*'''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.
 
|----
 
|Imports and Exports
 
|{{P3|Extra=|Description=Bug:597 [http://bugzilla.audacityteam.org/show_bug.cgi?id=597 Import RAW produces noise at 24-bit resolution]}}
 
*'''Import > Raw Data... imports files as noise''' if the Quality Preferences are set to 24-bit Default Sample Format. Set this to 16-bit or 32-bit float instead.
 
|----
 
|Imports and Exports
 
|{{P3|Extra=|Description=Bug:555 [http://bugzilla.audacityteam.org/show_bug.cgi?id=555 Export fails without warning if missing alias file but current project state does not depend on it]}}
 
*'''WAV and AIFF exports will fail without warning''' if you import a WAV or AIFF by [http://manual.audacityteam.org/o/man/import_export_preferences.html 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.
 
|----
 
|Imports and Exports
 
|{{P3|Extra=|Description=Bug:666 [http://bugzilla.audacityteam.org/show_bug.cgi?id=666 Cannot import audio files named with "\" using menus.]}}
 
*(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.
 
|----
 
|Imports and Exports
 
|{{P3|Extra=|Description=Bug:22 [http://bugzilla.audacityteam.org/show_bug.cgi?id=22 Exporting from integer internal formats to files in same format or higher adds unwanted dither noise]}}
 
*<div id="dither"></div>
 
* '''[[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 [http://manual.audacityteam.org/o/man/quality_preferences.html Quality Preferences]. To fix any files that have already been affected, see [http://forum.audacityteam.org/viewtopic.php?f=28&t=38756 this Forum topic].
 
|----
 
|Imports and Exports
 
|{{P3|Extra=|Description=Bug:535 [http://bugzilla.audacityteam.org/show_bug.cgi?id=535 Native Audacity formats won't import via FFmpeg until click OK on Preferences]}}
 
*On a fresh installation of Audacity or [http://manual.audacityteam.org/help/manual/man/preferences.html#stored 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".
 
|----
 
|Imports and Exports
 
|{{P3|Extra=|Description=Bug:411 [http://bugzilla.audacityteam.org/show_bug.cgi?id=411 MIDI channel selection buttons missing]}}
 
*When importing a MIDI track, the channel selection buttons to left of the track are not currently available.
 
|----
 
|Imports and Exports (FFmpeg)
 
|{{P3|Extra=|Description=Bug:763 [http://bugzilla.audacityteam.org/show_bug.cgi?id=763 FFmpeg Custom Export: Crashes deleting or importing presets]}}
 
* '''In the "Custom FFmpeg Export" dialog, deleting a preset crashes Audacity.''' Importing a preset crashes Audacity unless the "ffmpeg_presets" file in Audacity's folder for application data is empty or does not exist.
 
|----
 
|Installation
 
|{{P3|Extra=|Description=Bug:290 [http://bugzilla.audacityteam.org/show_bug.cgi?id=290 LAME and FFmpeg installation (Apple permission problems)]}}
 
* (OS X 10.6 or later) Administrative (and occasionally, root) permissions may be needed on some machines to read the optional LAME libraries at /usr/local/lib/audacity. In case of difficulty, please download the zip version "Lame Library v3.98.2 for Audacity on OSX.zip" from the [http://lame.buanzo.org/ download site] and extract the files to your own preferred location.
 
|----
 
|Interface
 
|{{P3|Extra=|Description=Bug:333 [http://bugzilla.audacityteam.org/show_bug.cgi?id=333 Libsamplerate: Progress dialogue hangs or Audacity segfaults when resampling ratio exceeds libsamplerate limits]}}
 
* (Linux) If Audacity is configured with the option to use libsamplerate, an action involving resampling outside libsamplerate's limits of 1/256 to 256x will cause the progress dialogue to hang, or possibly a crash.
 
|----
 
|Interface
 
|{{P3|Extra=|Description=Bug:202 [http://bugzilla.audacityteam.org/show_bug.cgi?id=202 "Audacity is already running" prevents opening further files]}}
 
* (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.
 
|----
 
|Interface
 
|{{P3|Extra=|Description=Bug:295 [http://bugzilla.audacityteam.org/show_bug.cgi?id=295 Preferences: localised text causes vertical/horizontal corruption]}}
 
* (OS X and Linux) In some locales, Preferences text may be truncated or overlapped, or dropdown boxes truncated.
 
|----
 
|Interface
 
|{{P3|Extra=|Description=Bug:629 [http://bugzilla.audacityteam.org/show_bug.cgi?id=629 Screenshot Tools images are saved jet black]}}
 
* (OS X) Images captured with Help > Screenshot Tools are completely black.
 
|----
 
|Interface
 
|{{P3|Extra=|Description=Bug:88 [http://bugzilla.audacityteam.org/show_bug.cgi?id=88 The "Cmd - Wheel - Rotate" mouse binding conflicts with system screen zoom]}}
 
* (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".
 
|----
 
|Interface
 
|{{P3|Extra=|Description=Bug:349 [http://bugzilla.audacityteam.org/show_bug.cgi?id=349 "Files Missing" warning restores maximised windows]}}
 
* (Windows) The "Files Missing" warning always restores maximised windows to smaller size.
 
|----
 
|Interface
 
|{{P3|Extra=|Description=Bug:217 [http://bugzilla.audacityteam.org/show_bug.cgi?id=217 Progress dialogue/better handling needed for waveform drawing]}}
 
* (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.
 
|----
 
|Interface
 
|{{P3|Extra=|Description=Bug:49 [http://bugzilla.audacityteam.org/show_bug.cgi?id=49 When changing language in Preferences, some elements in Unicode Release don't change until restart]}}
 
* After changing language in Preferences, a few parts of the interface don't change until Audacity is restarted.
 
|----
 
|Interface
 
|{{P3|Extra=|Description=Bug:15 [http://bugzilla.audacityteam.org/show_bug.cgi?id=15 Scrolling/zooming behaviour doesn't preserve context of audio being worked with]}}
 
* 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 {{menu|View > Go to Selection Start}} or {{menu|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
 
|----
 
|Interface
 
|{{P3|Extra=|Description=Bug:39 [http://bugzilla.audacityteam.org/show_bug.cgi?id=39 All Edit menu items to be consistently enabled and work consistently when select-all-on-none enabled]}}
 
* 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.
 
|----
 
|Interface
 
|{{P3|Extra=|Description=Bug:222 [http://bugzilla.audacityteam.org/show_bug.cgi?id=222 No sync-lock cursor when sync-lock is on]}}
 
* If Sync-Lock Tracks is enabled, there is no indication of the cursor in the Sync-Locked tracks.
 
|----
 
|Interface
 
|{{P3|Extra=|Description=Bug:279 [http://bugzilla.audacityteam.org/show_bug.cgi?id=279 Mouse Bindings are not currently configurable by the user.]}}
 
* Mouse Bindings are not currently configurable by the user.
 
|----
 
|Interface
 
|{{P3|Extra=|Description=Bug:198 [http://bugzilla.audacityteam.org/show_bug.cgi?id=198 Snap-To does not move cursor when first enabled/selection format changed]}}
 
* Snap-To does not move the cursor when first enabled or when the selection format is changed.
 
|----
 
|Interface
 
|{{P3|Extra=|Description=Bug:299 [http://bugzilla.audacityteam.org/show_bug.cgi?id=299 Some error messages would benefit from hyperlinks (to wiki).]}}
 
* 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 http://forum.audacityteam.org/
 
|----
 
|Interface
 
|{{P3|Extra=|Description=Bug:397 [http://bugzilla.audacityteam.org/show_bug.cgi?id=397 Widgets 2.8.10: all available CPU used if Audacity left open without focus]}}
 
*(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.
 
:For Package Maintainers / Distributors / anyone building against 2.8.10: The upstream change in wxGTK is simple and can easily be patched into wxGTK 2.8.10 if desired: Grab http://trac.wxwidgets.org/changeset/62397?format=diff&new=62397, run it through dos2unix (as it seems to come with dos line-endings), and apply it to the wxGTK 2.8.10 sources (with -p3 to get the paths right if you patch from the top level of the tarball distribution).
 
|----
 
|Interface
 
|{{P3|Extra=|Description=Bug:692 [http://bugzilla.audacityteam.org/show_bug.cgi?id=692 OS X 10.5.8 PPC: Splash Screen and Log are disabled and unmovable.]}}
 
*(OS X 10.5.8 PPC) '''The How to Get Help" window that appears by default on launch of Audacity cannot be moved or closed. The Audacity Log window may also be affected. '''Workaround:''' To stop the Welcome Screen appearing, open Audacity > Preferences: Interface and uncheck "Show How to Get Help". You can also quit Audacity, open Finder, Go > Go to Folder and type {{path|~/Library/Application Support/audacity/}} . Open audacity.cfg,select all the text and delete it. Then type the following at the top of the file:
 
{{code|1=NewPrefsInitialized=1<br>[GUI]<br>ShowSplashScreen=0}}
 
Save the changes to audacity.cfg then restart Audacity.
 
|----
 
|Interface
 
|{{P3|Extra=|Description=Bug:445 [http://bugzilla.audacityteam.org/show_bug.cgi?id=445 .lnk shortcuts to audio or .aup files cannot be dragged to interface or executable]}}
 
*(Windows) It is not yet possible to drag .lnk shortcuts to audio files or projects into Audacity, or to drag them to the Audacity executable's icon. '''Workaround:''' Use File > Open or File > Import > Audio, or double-click the shortcut to the .aup from Windows Explorer.
 
|----
 
|Interface
 
|{{P3|Extra=|Description=Bug:403 [http://bugzilla.audacityteam.org/show_bug.cgi?id=403 Only one "audacity.exe" can be added to Explorer "Open with"]}}
 
*(Windows) The Audacity executable cannot be added to the Explorer "Open with" context menu if you have another version of Audacity on the system which is also called "audacity.exe". '''Workaround:''' either use the "Open with" dialogue to browse to the executable each time, or rename the executable to or some other unique name.
 
|----
 
|Interface
 
|{{P3|Extra=|Description=Bug:393 [http://bugzilla.audacityteam.org/show_bug.cgi?id=393 Vertical drag does not scroll the project]}}
 
*Dragging a clip or track up or down with Time Shift Tool does not scroll the project window when tracks exist out of view above or below the scroll. '''Workaround:''' Choose View > Fit Vertically before drag, or click and hold the piece to be dragged, use up or down arrow on the keyboard to scroll to the target track, then drag and release the clip or track.
 
|----
 
|Keyboard Shortcuts
 
|{{P3|Extra=|Description=Bug:30 [http://bugzilla.audacityteam.org/show_bug.cgi?id=30 Transport shortcuts write label at cursor position when label track has focus]}}
 
* (Windows) SHIFT + A (Play/Stop and Set Cursor) and custom unmodified shortcuts for playback or recording write a label at the cursor position if the label track has the yellow focus border. '''Workaround:''' use up or down arrow to move focus out of the label track before using the shortcut.
 
|----
 
|Label Tracks
 
|{{P3|Extra=|Description=Bug:40 [http://bugzilla.audacityteam.org/show_bug.cgi?id=40 Label tracks: typing "j" or"k" in a label track activates the "move cursor" shortcut instead]}}
 
* '''Typing "j", "J", "k", "K" or other shortcuts in a label track may activate the shortcut''' instead of typing in the label. '''Workaround:''' In many cases, Edit > Undo then Edit > Redo will allow you to type in the label. Otherwise, click Edit > Preferences: Keyboard, choose the correct category, then clear the affected shortcuts or change them to include a CTRL + SHIFT modifier or other modifier than SHIFT.
 
|----
 
|Label Tracks
 
|{{P3|Extra=|Description=Bug:144 [http://bugzilla.audacityteam.org/show_bug.cgi?id=144 Lyrics Window makes things slow, when many labels.]}}
 
* (Linux) In projects containing several hundred labels or more, Audacity will freeze on 100% CPU when opening the "Audacity Karaoke" window, and will freeze again while that window is open when editing a label or performing other actions on the project. Workaround: Open or place an empty label track above the one you want to use.
 
|----
 
|Label Tracks
 
|{{P3|Extra=|Description=Bug:293 [http://bugzilla.audacityteam.org/show_bug.cgi?id=293 Paste/insert does not affect included label tracks when Sync-Lock is off]}}
 
* Unless Tracks > Sync-Lock Tracks is on, pasting or inserting audio does not affect labels even if the label track is included in the selection.
 
|----
 
|Label Tracks
 
|{{P3|Extra=|Description=Bug:498 [http://bugzilla.audacityteam.org/show_bug.cgi?id=498 Yellow snap guidelines lost after saving in high resolution selection format]}}
 
*'''Yellow "snap" guidelines do not appear in re-opened projects or imported label tracks''' when dragging a selection to a label edge if "Snap To" is checked and a high resolution Selection Format chosen. Formats affected include "hh:mm:ss + CDDA frames (75 fps)", "hh:mm:ss + milliseconds" and "hh:mm:ss + samples".
 
|----
 
|Miscellaneous platform-specific issues
 
|{{P3|Extra=|Description=Bug:276 [http://bugzilla.audacityteam.org/show_bug.cgi?id=276 Freeze repeatedly starting/stopping streams when using pulseaudio]}}
 
* (Linux) '''A playback or recording freeze with pulseaudio may occur''' if repeatedly starting and stopping playback or recording in quick succession (or holding down the Play or Record button).  '''Workarounds:''' Try launching Audacity from the terminal with the pulse latency set in an environment variable, for example: {{code|1=env PULSE_LATENCY_MSEC=30 audacity}}  Alternatively, bypass pulseaudio by setting the playback and recording device to an ALSA (hw) choice in Device Toolbar.
 
|----
 
|Miscellaneous platform-specific issues
 
|{{P3|Extra=|Description=Bug:401 [http://bugzilla.audacityteam.org/show_bug.cgi?id=401 "Hear" plug-in causes excessive memory usage resulting in Audacity crash]}}
 
* (Mac OS X) If using Audacity when the "Hear" audio plug-in is running (or has been since boot), there will be excessive memory usage which could cause a crash: this appears to be due to buggy memory allocation in "Hear"
 
|----
 
|Miscellaneous platform-specific issues
 
|{{P3|Extra=|Description=Bug:399 [http://bugzilla.audacityteam.org/show_bug.cgi?id=399 System audio playback lost after using Audacity]}}
 
* (Mac OS X) Very occasionally, users may find that after running Audacity, other media players don't produce any sound, or crash:  to resolve this, set up your sound device in Apple Audio MIDI Setup to work in stereo, 16-bit, with a sample rate of 44100 Hz or 48000 Hz, and set the sample format and rate identically in Audacity. More help at: http://audacityteam.org/forum/viewtopic.php?f=17&t=5064
 
|----
 
|Mixer Board
 
|{{P3|Extra=|Description=Bug:36 [http://bugzilla.audacityteam.org/show_bug.cgi?id=36 Mixer Board release-noted issues]}}
 
* '''Soloing or unsoloing a track in Mixer Board when in "Standard" Solo button mode''' may not immediately update the Solo button or waveform greyed/ungreyed state in the project window. '''Workaround:''' Click anywhere in (or task switch back to) the project window to refresh it (on Mac, you must click in the waveform or Track Control Panel or wait for the tracks to scroll when playing).
 
* (Windows and Linux) If Mixer Board is open and more tracks are added so that the horizontal scrollbar must be used, newly added tracks may not be visible or newly deleted tracks may show as empty space. '''Workaround:''' To see all the tracks without redundant space, close and reopen the project then reopen Mixer Board. 
 
* If you change the meter range in Preferences this is not reflected in the Mixer Board meters until restart.
 
* (Linux) Meters may not respond immediately to playback which could cause them to report incorrect peak level or not display clipping.
 
|----
 
|None
 
|{{P3|Extra=|Description=Bug:736 [http://bugzilla.audacityteam.org/show_bug.cgi?id=736 Audacity HEAD shows almost no shortcuts in menus using Unity]}}
 
 
|----
 
|None
 
|{{P3|Extra=|Description=Bug:729 [http://bugzilla.audacityteam.org/show_bug.cgi?id=729 Edit Menu too long and separates commands that cut and delete between root and non-standard submenu.]}}
 
  
|----
+
[[Category:For Users]][[Category:Legacy Release Notes]]
|None
 
|{{P2|Extra=|Description=Bug:672 [http://bugzilla.audacityteam.org/show_bug.cgi?id=672 Configuration error launching Audacity on fresh Windows XP installation.]}}
 
// Already release noted in "Notes for Windows" div at the top of each release note.
 
|----
 
|None
 
|{{P3|Extra=|Description=Bug:541 [http://bugzilla.audacityteam.org/show_bug.cgi?id=541 Audacity non-default ID3 frames rewritten as TXXX, rendering them invisible in WMP and iTunes]}}
 
// See Bug 51
 
|----
 
|None
 
|{{P3|Extra=|Description=Bug:754 [http://bugzilla.audacityteam.org/show_bug.cgi?id=754 Keyboard preferences and screen readers]}}
 
// See bug 33
 
|----
 
|None
 
|{{P3|Extra=|Description=Bug:701 [http://bugzilla.audacityteam.org/show_bug.cgi?id=701 Embedded album art and lyrics discarded]}}
 
// See bug 51
 
|----
 
|None
 
|{{P3|Extra=|Description=Bug:664 [http://bugzilla.audacityteam.org/show_bug.cgi?id=664 MFreeEffectsBundle AU effects crash on preview]}}
 
// See bug 665
 
|----
 
|None
 
|{{P2|Extra=|Description=Bug:603 [http://bugzilla.audacityteam.org/show_bug.cgi?id=603 Crash using Undo while dragging sample points]}}
 
// see bug 602
 
|----
 
|None
 
|{{P3|Extra=|Description=Bug:759 [http://bugzilla.audacityteam.org/show_bug.cgi?id=759 SPACE cannot be used/may crash in context menus that have a checkbox.]}}
 
//See bug 33
 
|----
 
|None
 
|{{P3|Extra=|Description=Bug:727 [http://bugzilla.audacityteam.org/show_bug.cgi?id=727 Orca: Tracks not read.]}}
 
//See bug 33
 
|----
 
|None
 
|{{P2|Extra=|Description=Bug:682 [http://bugzilla.audacityteam.org/show_bug.cgi?id=682 Keyboard Preferences: focus trapped in Search box]}}
 
//See bug 33
 
|----
 
|None
 
|{{P3|Extra=|Description=Bug:735 [http://bugzilla.audacityteam.org/show_bug.cgi?id=735 Mixer Board: tracks are not added or removed when tracks exceed scroll width.]}}
 
//See bug 36
 
|----
 
|None
 
|{{P3|Extra=|Description=Bug:741 [http://bugzilla.audacityteam.org/show_bug.cgi?id=741 DISTRHO VST's crash in Graphic Mode]}}
 
//See bug 665
 
|----
 
|None
 
|{{P3|Extra=|Description=Bug:494 [http://bugzilla.audacityteam.org/show_bug.cgi?id=494 AURoundTripAAC Audio Unit crashes Audacity on launch]}}
 
//See bug 665
 
|----
 
|None
 
|{{P3|Extra=|Description=Bug:481 [http://bugzilla.audacityteam.org/show_bug.cgi?id=481 Native Instruments B4 / Guitar Rig v3 / v4 crash Audacity on launch]}}
 
//See bug 665
 
|----
 
|None
 
|{{P3|Extra=|Description=Bug:460 [http://bugzilla.audacityteam.org/show_bug.cgi?id=460 Waves plug-ins crash Audacity at launch]}}
 
//See bug 665
 
|----
 
|None
 
|{{P3|Extra=|Description=Bug:289 [http://bugzilla.audacityteam.org/show_bug.cgi?id=289 Mixer Board: Slow meter response at start of playback]}}
 
//see bug 36
 
|----
 
|None
 
|{{P2|Extra=|Description=Bug:673 [http://bugzilla.audacityteam.org/show_bug.cgi?id=673 Installer language choice unintuitive to users wanting Audacity in English while Windows is in localised language]}}
 
In "Notes for Windows"
 
*'''The language choice in the Windows EXE installer for Audacity only selects the language for the installer.''' The language Audacity runs in is determined by the "Format" for date and time in the "Region and Language" section of the Windows Control Panel. To change the Audacity language, please see these [http://manual.audacityteam.org/o/man/faq_about_audacity.html#language instructions].
 
|----
 
|None
 
|{{P3|Extra=|Description=Bug:509 [http://bugzilla.audacityteam.org/show_bug.cgi?id=509 Soloing/unsoloing in Mixer Board does not repaint waveform colour until window or Track Panel refresh]}}
 
See Bug 36.
 
|----
 
|None
 
|{{P3|Extra=|Description=Bug:726 [http://bugzilla.audacityteam.org/show_bug.cgi?id=726 VoiceOver: Tracks not read after exporting]}}
 
See bug 33
 
|----
 
|None
 
|{{P3|Extra=|Description=Bug:391 [http://bugzilla.audacityteam.org/show_bug.cgi?id=391 Unintuitive behaviour of tracks and backgrounds when vertically scrolling or resizing windows]}}
 
See bug 393.
 
|----
 
|None
 
|{{P3|Extra=|Description=Bug:563 [http://bugzilla.audacityteam.org/show_bug.cgi?id=563 ID3 v2.4 tags in imported MP3 files are not seen so are removed on export]}}
 
See bug 51
 
|----
 
|Playback and Recording
 
|{{P3|Extra=|Description=Bug:641 [http://bugzilla.audacityteam.org/show_bug.cgi?id=641 Append record causes spurious playthrough and may crash.]}}
 
* '''Append Record with Transport > Overdub (on/off) enabled may cause periodic playthrough''' of previously recorded audio. If you use the Stop button or SPACE to stop the previous recording instead of  SHIFT + A (Stop and Set Cursor), this may reduce occurrences of the issue.
 
|----
 
|Playback and Recording
 
|{{P3|Extra=|Description=Bug:56 [http://bugzilla.audacityteam.org/show_bug.cgi?id=56 JACK issues]}}
 
* (OS X and Linux) Audacity now works very well with [http://jackaudio.org/ JACK], with the following bugs and limitations:
 
** Clicking in the input meter to start monitoring will crash Audacity if it has not yet used JACK for playback or recording in that session. '''Workaround:''' Before recording the first track in a session, click "Pause" then "Record" to enable the recording meter.
 
** The best way to connect to available JACK inputs and outputs is directly from Device Toolbar. Use Transport > Rescan Audio Devices when necessary, for example to make new JACK applications ports available to Audacity. See [[Linux Issues#JACK|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.
 
|----
 
|Playback and Recording
 
|{{P3|Extra=|Description=Bug:306 [http://bugzilla.audacityteam.org/show_bug.cgi?id=306 xrun glitches when recording with software playthrough, caused by too demanding PortAudio latencies]}}
 
* (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.
 
|----
 
|Playback and Recording
 
|{{P3|Extra=|Description=Bug:167 [http://bugzilla.audacityteam.org/show_bug.cgi?id=167 Output error to Bluetooth playback devices]}}
 
* (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 [http://www.cycling74.com/products/soundflower Soundflower] to send the Audacity output to an audio application that works with the headset.
 
|----
 
|Playback and Recording
 
|{{P3|Extra=|Description=Bug:388 [http://bugzilla.audacityteam.org/show_bug.cgi?id=388 Recording Preferences has an unsupported "Hardware Playthrough" option]}}
 
* (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 [http://www.rogueamoeba.com/freebies/ LineIn] application also provides software playthrough.
 
|----
 
|Playback and Recording
 
|{{P2|Extra=|Description=Bug:651 [http://bugzilla.audacityteam.org/show_bug.cgi?id=651 WDM/KS issues]}}
 
* (Windows) "Windows WDM-KS" host is currently the least compatible of the four hosts, and may produce "error opening sound device" on some machines or have other quirks (such as some inputs not being available under this host).  Please report detailed problems to [http://audacity.sourceforge.net/contact/#feedback our feedback address] and state your exact version of Windows.
 
** The input slider in [http://manual.audacityteam.org/o/man/device_toolbar.html 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.
 
|----
 
|Playback and Recording
 
|{{P3|Extra=|Description=Bug:29 [http://bugzilla.audacityteam.org/show_bug.cgi?id=29 Input slider not greyed out when it has no control of input device]}}
 
* (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.
 
|----
 
|Playback and Recording
 
|{{P3|Extra=|Description=Bug:612 [http://bugzilla.audacityteam.org/show_bug.cgi?id=612 Audacity does not initialise to Sound Mapper devices]}}
 
* (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 [http://manual.audacityteam.org/o/man/device_toolbar.html Device Toolbar] to change the devices as needed, then Audacity will remember them.
 
|----
 
|Playback and Recording
 
|{{P3|Extra=|Description=Bug:404 [http://bugzilla.audacityteam.org/show_bug.cgi?id=404 Some professional sound cards/devices are not (fully) compatible]}}
 
* (Windows) Audacity is incompatible (or not fully compatible) with some professional sound cards or audio devices, and may crash or have limited or faulty functionality. Occasionally, this may be true of some AC97 devices built into the motherboard. '''Workaround:''' make a different sound card your default when using Audacity, but please e-mail the following details to our [http://audacity.sourceforge.net/contact/#feedback feedback address]:
 
** Your version of Windows and Service Pack
 
** Name, model number and driver version number of the sound card or device.<p>'''Note:''' [[Multichannel Recording]] in Audacity is often not possible with professional devices unless you compile Audacity with [[ASIO Audio Interface|ASIO]] support.</p>
 
|----
 
|Playback and Recording
 
|{{P3|Extra=|Description=Bug:652 [http://bugzilla.audacityteam.org/show_bug.cgi?id=652 WASAPI issues]}}
 
* (Windows) The "Windows WASAPI" host currently has the following limitations:
 
** The only available inputs are "loopback" inputs for [http://manual.audacityteam.org/o/man/tutorial_recording_computer_playback_on_windows.html recording computer playback]. 
 
** The input slider in [http://manual.audacityteam.org/o/man/device_toolbar.html 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 [http://manual.audacityteam.org/o/man/selection_toolbar.html Project Rate] set to 44100 Hz . Setting other project rates will cause Audacity to resample the input to the project rate any may cause glitches in the recorded audio.
 
** "Audio to buffer" in Recording Preferences cannot be used to adjust recording latency.
 
|----
 
|Playback and Recording
 
|{{P3|Extra=|Description=Bug:41 [http://bugzilla.audacityteam.org/show_bug.cgi?id=41 Changes in available devices not detected without restart]}}
 
* 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.
 
|----
 
|Playback and Recording
 
|{{P3|Extra=|Description=Bug:50 [http://bugzilla.audacityteam.org/show_bug.cgi?id=50 Calculation of "disk space remains for recording (time)" incorrect when recording in 24 bit quality]}}
 
* Calculation of "disk space remains for recording (time)" incorrect when recording in 24 bit quality.
 
|----
 
|Playback and Recording
 
|{{P3|Extra=|Description=Bug:133 [http://bugzilla.audacityteam.org/show_bug.cgi?id=133 Play-at-Speed slider: Change of playback speed is no longer automatic]}}
 
* 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.
 
|----
 
|Playback and Recording
 
|{{P3|Extra=|Description=Bug:43 [http://bugzilla.audacityteam.org/show_bug.cgi?id=43 Timer Record cannot maintain scheduled duration if system clock changes]}}
 
* Timer Record cannot maintain scheduled duration if system clock changes
 
|----
 
|Playback and Recording
 
|{{P3|Extra=|Description=Bug:424 [http://bugzilla.audacityteam.org/show_bug.cgi?id=424 Changing Host reverts changes in selected devices]}}
 
*(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.
 
|----
 
|Playback and Recording
 
|{{P3|Extra=|Description=Bug:435 [http://bugzilla.audacityteam.org/show_bug.cgi?id=435 Changing Windows default devices in Audacity session breaks recording or playback until rescan]}}
 
*(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.
 
|----
 
|Program Launch
 
|{{P3|Extra=|Description=Bug:270 [http://bugzilla.audacityteam.org/show_bug.cgi?id=270 Audacity breaks system bluetooth support]}}
 
* (Linux) If a Bluetooth audio device is in use on a PulseAudio system, Audacity may hang on launch on initial attempts, then after eventual launch Bluetooth will no longer work on the system. '''Workarounds:'''
 
** Remove and reconnect the external Bluetooth adaptor, then launch bluetooth-applet from the command line.
 
** To prevent Audacity affecting Bluetooth support, move /usr/share/alsa/bluetooth.conf to another location then reboot, or create a symbolic link from /var/lib/alsa/asound.state to /dev/null and reboot.
 
|----
 
|Program Launch
 
|{{P3|Extra=|Description=Bug:646 [http://bugzilla.audacityteam.org/show_bug.cgi?id=646 VST List of Plugins - Residual Issues.]}}
 
* (Windows and OS X)  '''"Install VST Effects" dialog:'''
 
** '''The dialog lists more than VST effects:''' On first use, Audacity scans for [http://manual.audacityteam.org/o/man/effect_menu.html#VST_Effects VST effects] then (before launching Audacity) presents a dialog where you can choose which VST effects to load into the Audacity Effect menu. Remove the checkmark from any VST effects you do not want to load then click {{button|OK}} to load the checkmarked effects. If you click {{button|Cancel}} the dialog will reappear on next Audacity launch.
 
** '''VST instruments will appear in the list but are not supported''', so will '''not''' load even if checkmarked.
 
** '''On Windows the dialog will appear even if you have no VST effects''', because Audacity detects the two shipped LADPSA plug-ins (hard_limiter_1413.dll and sc4_1882.dll) and also any optional LADSPA DLL plug-ins you may have installed. These LADSPA plug-ins will load whether you enable them in the dialog or not. '''Therefore you should just click {{button|OK}} on the dialog if you have no VST effects'''.
 
** The dialog is on top of other windows, so could hide any prompts that VST effects show when effects are loaded after pressing OK. This would be evident by the "loading progress" arrow in the check boxes coming to a halt and the VST dialog losing focus. To continue loading the effects in this case, press ENTER on your keyboard to OK the hidden prompt, or drag the VST dialog away to reveal the prompt then click OK on the prompt.
 
|----
 
|Projects
 
|{{P3|Extra=|Description=Bug:437 [http://bugzilla.audacityteam.org/show_bug.cgi?id=437 Write fails without error message box on disk full]}}
 
* '''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.
 
|----
 
|Projects
 
|{{P3|Extra=|Description=Bug:120 [http://bugzilla.audacityteam.org/show_bug.cgi?id=120 Entering "\" in file name when saving projects disallows the save.]}}
 
* (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.
 
|----
 
|Projects
 
|{{P3|Extra=|Description=Bug:334 [http://bugzilla.audacityteam.org/show_bug.cgi?id=334 Crash closing project window between save project dialogues]}}
 
* (OS X) '''Crash closing project window immediately after saving project:''' After saving a project, if you close the project window immediately the "Saving project data files" dialog completes, there will be an unexpected "Save changes?" prompt and then a crash when you choose "Yes" or "No". As long as you say "Yes", the project will be saved correctly and can be reopened normally after you restart Audacity. To be sure there is no crash, wait after "Saving project data files" completes for any "Inspecting Project Data" dialog to appear and disappear before closing the project window.
 
|----
 
|Projects
 
|{{P3|Extra=|Description=Bug:32 [http://bugzilla.audacityteam.org/show_bug.cgi?id=32 No longer possible to overwrite a closed project]}}
 
* 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
 
|{{P3|Extra=|Description=Bug:400 [http://bugzilla.audacityteam.org/show_bug.cgi?id=400 Projects created by Audacity 1.1.x or earlier are no longer supported]}}
 
* 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
 
|{{P3|Extra=|Description=Bug:457 [http://bugzilla.audacityteam.org/show_bug.cgi?id=457 Overlong block files are orphaned rather than read or exported to WAV]}}
 
* Projects created by previous versions of Audacity may contain audio "block files" longer than the project format allows. Reopening such projects in previous versions might or might not result in deletion of the overlong audio. Audacity has been provisionally fixed so that it can no longer create or delete overlong files, but it cannot read any such files it encounters. If overlong files are found, a "Problems Reading Sequence Tags" message will display .
 
**  If you continue with the offered repair then choose "Continue without deleting" in the Orphan Block File(s) dialogue, the overlong files will be retained as "orphans" in the project's _data folder but will appear as silence in the track(s).
 
** As long as you choose "Close project immediately" in the Orphan Block File(s) dialogue,  the project will quit and will not be changed in any way.
 
<ul style="list-style-image: none; list-style-type: none">
 
If you encounter the "Problems Reading Sequence Tags" message, please write to our [http://audacity.sourceforge.net/contact/#feedback feedback address] with a copy of the .aup file and the log as found at Help > Show Log.</ul>
 
|----
 
|Projects
 
|{{P3|Extra=|Description=Bug:610 [http://bugzilla.audacityteam.org/show_bug.cgi?id=610 Time Tracks saved in >2.0.2 display or play incorrectly in previous Audacity versions]}}
 
* 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.
 
|----
 
|Time Tracks
 
|{{P3|Extra=|Description=Bug:595 [http://bugzilla.audacityteam.org/show_bug.cgi?id=595 Time Track: Speed limits not stored in project]}}
 
* The lower and upper speed limits are not stored in the project, so will be restored to their default values of 90 and 110 respectively when reopening or recovering a project, or if removing a Time Track then undoing removal. Please make a note of the correct values before closing the project or the Time Track.
 
|----
 
|Toolbars
 
|{{P2|Extra=|Description=Bug:602 [http://bugzilla.audacityteam.org/show_bug.cgi?id=602 Crash using Undo while dragging envelope points]}}
 
* (OS X and Linux) Using keyboard Undo while dragging envelope points or sample points will crash Audacity (this affects Envelope Tool, Draw Tool and Multi-Tool).
 
|----
 
|Toolbars
 
|{{P3|Extra=|Description=Bug:574 [http://bugzilla.audacityteam.org/show_bug.cgi?id=574 Meter Toolbar: Vertical Orientation not remembered/respected]}}
 
*'''Meter Toolbar vertical orientation''' is not remembered across sessions, and resizing the meters reverts from vertical to horizontal.
 
|----
 
|Toolbars
 
|{{P3|Extra=|Description=Bug:505 [http://bugzilla.audacityteam.org/show_bug.cgi?id=505 Transport and Tools Toolbar buttons all display as Pause buttons]}}
 
*(Windows XP) '''Transport and Tools Toolbar buttons all display as Pause buttons.''' The buttons may redraw correctly if you hover over them. '''Workaround:''' You can use [http://manual.audacityteam.org/o/man/keyboard_shortcut_reference.html keyboard shortcut alternatives] for the buttons instead.
 
|----
 
|VST and Audio Units
 
|{{P3|Extra=|Description=Bug:743 [http://bugzilla.audacityteam.org/show_bug.cgi?id=743 VST: Controls in graphical mode do not respond to loaded preset file.]}}
 
* (Windows and Mac OS X) '''When running VST effects in [http://manual.audacityteam.org/o/man/effects_preferences.html#vst graphical mode] the controls of many plug-ins do not visibly respond when loading a preset file from the "Load" button'''. The new settings are however loaded internally, will apply when running the effect and will be visible if you reopen the effect after running it. Controls do respond to loading a preset file if you turn off graphical mode.
 
|----
 
|}
 

Latest revision as of 10:54, 15 December 2017


Audacity 2.0.6 was available from 29 September 2014 until 28 March 2015.
 
Related article(s):
Tip: You can use CTRL + F to search this page for different words to do with the issue you are looking for. Use Command - F on Mac.
Warning icon FFmpeg updated for 2.0.6:
Warning icon OS X 10.10 Yosemite: Audacity 2.0.6 will not officially support OS X 10.10 Yosemite when released (in particular, Apple Audio Units may not open in Audacity).
Warning icon Extra notes for Windows:
  • The Windows installer for 2.0.x versions will replace 1.2.x or any previous 2.0.x installation, but install alongside legacy 1.3.x Beta versions. It is strongly recommended to uninstall previous Beta versions.
  • The language choice in the Windows EXE Audacity installer only selects the language for the installer. The language Audacity runs in is determined by the "Format" for date and time in the "Region and Language" section of the Windows Control Panel. To change the Audacity language, please see these instructions.
  • You may see the error Application configuration incorrect when launching Audacity after installation. This mainly affects some Windows XP or 2000 machines. This can be fixed by downloading and installing the appropriate Microsoft "Redistributable Package" as follows:
    Be sure to get the correct package according to whether you have 32-bit or 64-bit Windows. To check, right-click over My Computer and choose Properties. 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.

Changes since previous version

Improvements

  • Interface:
    • Redesigned, searchable Keyboard Preferences with Tree, Name and Key views.
    • Edit Menu: "Cut" and "Delete" are now in the top level of the menu.
    • Transport Menu now includes "Play/Stop" and "Play/Stop and Set Cursor" (use Keyboard Preferences to create shortcuts for "Play" and "Stop").
    • Tracks Menu now includes "Mix and Render to New Track".
    • Track Dropdown Menu now has Move Track To Top and Move Track To Bottom.
    • New right-click menu choice "Delete Label" to remove single labels.
    • "Snap To" now offers choice of snap to the "closest" or "prior" position. Note: the previous "Snap To On" keyboard shortcut will no longer work.
    • "Snap To" settings are now independent for each project.
  • Effects:
    • Truncate Silence: redesigned with simpler option "Truncate Detected Silence" to shorten to the specified length without compressing silence.
    • VST effects: New "Settings" dialog lets you specify buffer size (for faster processing) and enable buffer delay compensation (to prevent inserted silence). Compensation may cause a crash in a few plug-ins.
    • VST effects now support standard FXP presets.
    • LV2 effects are now supported on all platforms (textual interface only).
  • Import or export using FFmpeg now requires FFmpeg 1.2 or later (or libav 0.8 or later). For recommended downloads of recent FFmpeg please visit https://manual.audacityteam.org/o/man/faq_installation_and_plug_ins.html#ffdown.
  • New Tamil translation (largely complete).
  • (Windows) FLAC exports can now exceed 2 GB in size.
  • (OS X) Easier Audacity installation using the DMG: drag the Audacity folder to the /Applications shortcut.
  • (Linux) Self-compiled builds of Audacity now search for system LADSPA effects in /usr/lib/ladspa.

Bug Fixes

  • Interface:
    • Region Restore did not restore the region after using Preferences.
    • Dragging selections with the keyboard or Selection Toolbar digits was very slow.
    • (Windows) Help > About Audacity crashed when run in Magyar language.
    • (OS X) Some full and reduced Menu Bar items were not translated.
    • (OS X and Linux) Fixed various interface crashes.
  • Effects:
    • Reverb and Paulstretch were missing from Chains.
    • Analyze > Contrast could report very inaccurate RMS levels.
    • Noise Removal: Attack and decay times were half as long as set.
    • (OS X and Linux) Nyquist effects ran much more slowly than on Windows.
  • Click or drag on the Timeline after Loop Play continued to loop.
  • Transcription Toolbar did not play slower than 0.1x speed.
  • (Linux) Audacity did not build if python 2 was not available.

Known Issues at Release

Accessibility

  • Many, but not all parts of the Audacity interface are accessible on Windows and Mac to those who can't use a mouse, and/or use a screen reader. It may be possible to make more of Audacity accessible in the longer term. For details, see https://manual.audacityteam.org/o/man/accessibility.html

There are some accessibility bugs in the parts of Audacity that are accessible (or behavior may vary according to the specific screen reader).

  • Some interface text or markings remain in black when using High Contrast light-on-dark themes, so cannot be read properly.
  • Install VST Effects dialog: The list view of plug-ins is a check box list view, and all the plug-ins are checked initially. Unfortunately Jaws and Window-Eyes do not read whether or not a check box is checked, but you can still press SPACE to change this.
  • Keyboard Preferences: Window-Eyes doesn't read the key bindings when View by Tree is selected, and may not always read the bindings in other views.
  • (OS X) It is not possible to TAB through Keyboard Preferences.
  • (OS X) Issues with VoiceOver:
    • (reported on OS X 10.9.x) After exporting, the black accessibility area is trapped in the Tooldock area, so there is no way to read the tracks. Workaround: Save as a project, close the project then reopen it. You can then navigate the tracks with VoiceOver.
    • If you use arrow keys to navigate the Timetext controls in Selection Toolbar, VoiceOver stops reading. Workaround: Use Control-Option-W
    • When you TAB forwards from "Audio Position" in Selection Toolbar, the "Selection End" or "Selection Length" radio button is read as "Selection Start". When you use COMMAND + F6 or COMMAND + SHIFT + F6 to move directly into "Selection End" from another toolbar, the button is read as "Selection Start".
    • Mixer Toolbar input/output sliders are not read, but just described as "multiple indicators". The "Graphic EQ" and vertical sliders in Equalization *are* read.
    • Metadata Editor table not read.
    • Edit Labels dialog not read.
    • In the "Edit Chains" window, only the first command in the "Chain" list is read, and it is only read when first accessed. In the "Select Command" window for inserting a new command in a Chain, commands in the table are not read.
    • "Manage Curves" table in Equalization not read.
  • (Linux) Using the Unity shell, most or all keyboard shortcuts are not listed in the Audacity menus. Gnome Fallback is not affected. Workaround: You can view shortcuts at Edit > Preferences: Keyboard or online at https://manual.audacityteam.org/o/man/keyboard_shortcut_reference.html.
  • (Linux) SPACE cannot be used to change context menu items that have a checkbox (such as Selection Format in the context menu of TimeText digits, or Mono/Left/Right and Set Rate and Set Sample Format in the Track Dropdown Menu). Using SPACE in these menus could crash Audacity. Workaround: Use ENTER instead of SPACE to select the new choice.
  • (Linux) Issues with Orca:
    • Audacity tracks are not read.
    • Not all toolbar controls are read, examples being Timetext controls, Project Rate and controls in Device Toolbar.
    • Not all controls in Preferences are read.

Chains

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

Compiling

  • (Linux) New libsoxr resampling library: Default ./configure will enable a new library libsoxr for resampling and disable libresample and libsamplerate (the previous resampling libraries). Cmake is required to build libsoxr. We strongly recommend libsoxr for its combination of high quality and high speed.
    • Only one resampling library is permitted. If you enable either libresample or libsamplerate in configure, libsoxr will not be enabled. Any configure of resampling libraries other than libsoxr only will enable one only of libresample, libsamplerate or libsoxr in that order of precedence; however the intermediate configure output may suggest that other libraries will be favored.
    • To enable libresample, your configure must include --without-libsoxr as well as --with-libresample.
  • (Windows) Compilation with Visual Studio 2010 is not supported or recommended. See the Wiki page Developing on Windows for information.
  • (Windows) LADSPA effects cannot be categorized even when Audacity is compiled with USE_LIBLRDF defined.
  • (Linux) Audacity may not always compile against supported versions of libav or FFmpeg. Audacity 2.0.6 supports FFmpeg 1.2 or higher (FFmpeg 2.2.3 is known to work) or libav 0.8 or higher.
    • Dynamic loading (as in default Audacity ./configure) requires building against the FFmpeg project - it will not build against the libav* headers from the libav project. Workarounds: Configure Audacity with --disable-dynamic-loading. If dynamic loading is required, build against FFmpeg instead of libav, or you can build against libav if you remove the "#define IS_FFMPEG_PROJECT 1" line in src/FFmpeg.h.
    • Audacity may still build against no-longer-supported FFmpeg versions (such as FFmpeg 0.8 which is system-installed on Debian Wheezy), but configuring with --disable-dynamic-loading will be necessary. FFmpeg 0.8 has at least one known issue in Audacity 2.0.6 or later: mono WMA files export with no audio data. This issue will not be fixed given FFmpeg 0.8 is no longer supported by Audacity 2.0.6.
    • Building against self-compiled FFmpeg 2.2.2 with --disable-dynamic-loading the only argument fails on Ubuntu 13.10 with "undefined reference to 'av_codec_is_encoder'". Workaround: Configuring with --disable-dynamic-loading and --with-lib-preference="local" (or at least --with-ffmpeg="local") may build successfully, but may not disable Libraries Preferences. The best solution may be not to disable dynamic loading.

Effects (VST and Audio Units)

  • (Windows and Mac OS X) When running VST effects in graphical mode the controls of many plug-ins do not visibly respond when loading a preset file from the "Load" button. The new settings are however loaded internally, will apply when running the effect and will be visible if you reopen the effect after running it. Controls do respond to loading a preset file if you turn off graphical mode.
  • (OS X) When saving presets, the FXP or XML file extension is not automatically offered in the file name, and not added by Audacity if you omit it. Make sure the extension you add is the same as that shown in the "File Format" dropdown menu, otherwise the preset will not be loadable.
  • (OS X) The following plug-ins may cause Audacity to crash if they are used after starting Audacity.
    • AURoundTripAAC from "Apple audio mastering tools" (this requires OS X 10.6 or later so may crash on 10.4 or 10.5).
    • Blue Cat FreqAnalyst (real time)
    • Endless Series AU
    • 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)
    • DISTRHO Mini Series VST's from http://distrho.sourceforge.net/plugins.php crash Audacity in graphic mode but will run in text mode (open the Effects Preferences and uncheck "Display VST effects in graphical mode").
    • Waves v5 may cause Audacity to hang if you select it in the "Install VST Effects" dialog then click OK.
  • (OS X) Some VST plug-ins no longer allow text input in the presets dropdown, either by typing or pasting. Examples are Sound Hack "Delay Trio / Freesound Bundle" and Blue Cat.
  • (OS X) Blue Cat plug-ins: Opening the dialog to save a preset will hide the plug-in interface and lock out the main Audacity window. Workaround: Right-click or CONTROL-click over Audacity's Dock icon, choose "Quit" then choose to save changes or not. Other plug-ins that use JUCE (such as GRM Tools) are also likely to be affected.

Effects and Analysis

  • LADSPA generate plug-ins may fail to generate into an empty track or into white space separating audio clips. Workaround: Before using the LADSPA generator, generate audio using any of the Audacity Generators above the divider in the Generate Menu, then generate into that audio selection.
  • Nyquist plug-ins: In locales where comma is the decimal separator, entering a comma in a text input box that has no associated slider will produce an error message, or only result in the whole number before the comma (for example, in Regular Interval Labels). Workaround: Use a dot (period) as the decimal separator.
  • (Linux) Sliding Time Scale / Pitch Shift may crash randomly in Audacity built with pre-2.0.2 versions of libsbsms. This may occur for example in the Ubuntu package of Audacity 2.0.5 on Ubuntu 14.04. Workaround: Build Audacity configured --with-sbsms="local", or use the Audacity package in Ubuntu 14.10 which uses libsbsms 2.0.2-1.
  • (Windows 64-bit) There is no HKEY_LOCAL_MACHINE\SOFTWARE\ registry key where Audacity detects VST plug-ins. The HKEY_CURRENT_USER key searched is HKEY_CURRENT_USER\Software\VST\VSTPluginsPath instead of the expected HKEY_CURRENT_USER\SOFTWARE\Wow6432Node\VST .
  • (Windows and Linux) Some LADSPA "Blop" plug-ins ( 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
  • Cut Preview only plays the upper track of multiple selected or Sync-Locked tracks.
  • Nyquist effects render the space between clips as silence. Workarounds: Edit > Clip Boundaries > Detach at Silences (this could reduce the length of clips that have silent fades) or double-click each clip and apply the effect separately to it.
  • Nyquist effects add spurious split lines if applied over clip boundaries.
  • Preview is not supported in Nyquist plug-ins. "Play" or "Preview" features that are included in a few Nyquist plug-ins do not work on Mac OS X and may cause Audacity to freeze or crash on Linux.
  • The following effects remove envelope control points: Change Speed/Pitch/Tempo; Equalization; Noise Removal; Sliding Time Scale/Pitch Shift; any Nyquist effect in the Effect menu. Workaround: Use Tracks > Mix and Render to apply the envelope to the waveform before applying the effect.
  • The Reverse effect retains the control points, but does not move them.
  • Truncate Silence doesn't work intuitively if run on multiple tracks. It may be preferable to run it on each track at a time.
  • Nyquist effects may crash Audacity if used on extremely long selections containing more than 2^31 samples (just over 13.5 hours at 44100 Hz). Workaround Apply the effect to multiple shorter regions (you can drag the selection back on itself to create a region contiguous with the previous one). Also note that projects containing more than 2^31 samples of total audio cannot be correctly saved.

Envelopes and Clips

  • A clip may now be vertically dragged from inside a selection region, but if that region extends over the edge of the clip into space or into an adjoining clip there may be unexpected behavior:
    • one channel of a stereo clip may jump sideways
    • a mono clip may fail to horizontal-drag in its new track
    • faint, specious clip lines could occur if the clip is dragged back to its original track.
    Workaround: Edit > Undo if necessary then drag from outside the selection region or single-click in the clip to remove the selection.
  • Undo may fail silently after applying an effect or edit across one or more split lines. Workaround: Effect > Repeat the effect from the top of the Effect Menu then undo both applications of the effect, or open View > History... and click on the step above the currently indicated line.
  • Left-clicking in a stereo track to merge a clip at a split line may cause other clips to move. It is believed this only happens after having used the Track Dropdown Menu to make two mono tracks into stereo. Workaround: Select over the split line and Edit > Clip Boundaries > Join.
  • When pasting audio into tracks with envelope points, the envelope points may move in unexpected ways, so causing unwanted amplitude adjustments.

Imports and Exports

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

Imports and Exports (FFmpeg)

  • In the "Custom FFmpeg Export" dialog, deleting a preset crashes Audacity. Importing a preset crashes Audacity unless the "ffmpeg_presets" file in Audacity's folder for application data is empty or does not exist.
  • M4A (AAC) exports: The Quality Slider in "Specify AAC Options" has no effect if the FFmpeg library is built with the libvo-aac encoder, as are recommended builds of FFmpeg for Windows and Mac OS X. Workaround: Given the alternative AAC encoders for FFmpeg have other problems as described in these notes, you can instead export as WAV and convert to AAC in iTunes on Windows and Mac.
  • AAC exports using "M4A (AAC) Files (FFmpeg)" with project rate below 22050 Hz produce a zero bytes file if the linked to FFmpeg is configured with the default AAC encoder or libfaac. This will not affect the recommended builds of FFmpeg for Windows and Mac OS X which are built with libvo-aacenc. Workaround: You can export AAC below 22050 Hz using default-configured FFmpeg by choosing (external program) export instead.
  • AAC: Artist and Year metadata is not exported or imported due to a bug in FFmpeg 2.2.2.
  • WMA and APE (Monkeys Audio): "Artist Name" is not seen on importing the file (Audacity bug)
  • Custom FFmpeg Export: many combinations of formats and codecs are incompatible, as are some combinations of general options and codecs. Some files may be exported as zero kb files.

Installation

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

Interface

  • In projects containing an hour or more of total audio, there may be a delay compared to previous versions of Audacity when:
    • Dragging sample points with Draw Tool
    • Using Cut, Copy, Paste, Delete or Silence Audio.
    The delay may be more evident on slower computers. In addition, label text may not be recovered if there is a crash.
  • (Linux) If Audacity is configured with the option to use libsamplerate, an action involving resampling outside libsamplerate's limits of 1/256 to 256x will cause the progress dialog to hang, or possibly a crash.
  • (Linux) Using a file manager (for example, context menu) or the command line to open further files gives an error. Even if Audacity is closed, only one file can be opened from the file manager. Workaround: Use File > Open, or (for audio files) File > New then drag the files in.
  • (OS X and Linux) In some locales, Preferences text may be truncated or overlapped, or dropdown boxes truncated.
  • (OS X) Images captured with Help > Screenshot Tools are completely black.
  • (OS X) The "Cmd - Wheel - Rotate" mouse binding does not zoom in unless you modify the default System Preferences. ** On OS X 10.6 or later, go to Universal Access / Seeing / Zoom / Options and uncheck "Use scroll wheel with modifier keys to zoom".
    • Prior to OS X 10.6, go to "Mouse and Keyboard" and uncheck "Zoom using scroll ball while holding Command".
  • (Windows) The "Files Missing" warning always restores maximised windows to smaller size.
  • (Windows) There may be substantial delays drawing the waveform in some circumstances. These include fitting longer zoomed-in projects to the window, or when zooming in on fitted projects, also after importing files or running effects.
  • After changing language in Preferences, a few parts of the interface don't change until Audacity is restarted.
  • Audacity has several weaknesses in preserving the context of the audio being worked with:
    • If playback scrolls, pressing Stop leaves the waveform where it stopped and the cursor invisible. Pressing Play to resume then scrolls the waveform to start at the left edge, hiding the previously visible context before the cursor position. Workaround: If you had a selection and a special playback command like Cut Preview or Quick-Play caused the waveform to scroll, use View > Go to Selection Start or View > Go to Selection End to move the selection back into view.
    • Current scrolling behaviour makes it too hard to watch the waveform progress, with a single shift of cursor and waveform position when cursor reaches the right edge
    • 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.
  • Mouse Bindings are not currently configurable by the user.
  • Snap-To does not move the cursor when first enabled or when the selection format is changed.
  • We're aware that some error messages in Audacity are not as helpful as we would like them to be. If you see a cryptic error message from Audacity, try a search (or ask) on https://forum.audacityteam.org/
  • (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.
For Package Maintainers / Distributors / anyone building against 2.8.10: The upstream change in wxGTK is simple and can easily be patched into wxGTK 2.8.10 if desired: Grab http://trac.wxwidgets.org/changeset/62397?format=diff&new=62397, run it through dos2unix (as it seems to come with dos line-endings), and apply it to the wxGTK 2.8.10 sources (with -p3 to get the paths right if you patch from the top level of the tarball distribution).
  • (OS X 10.5.8 PPC) "The How to Get Help" window that appears by default on launch of Audacity cannot be moved or closed. The Audacity Log window may also be affected. Workaround: To stop the Welcome Screen appearing, open Audacity > Preferences: Interface and uncheck "Show How to Get Help". You can also quit Audacity, open Finder, Go > Go to Folder and type ~/Library/Application Support/audacity/ . Open audacity.cfg,select all the text and delete it. Then type the following at the top of the file:
    NewPrefsInitialized=1
    [GUI]
    ShowSplashScreen=0
    Save the changes to audacity.cfg then restart Audacity.
  • (Windows) It is not yet possible to drag .lnk shortcuts to audio files or projects into Audacity, or to drag them to the Audacity executable's icon. Workaround: Use File > Open or File > Import > Audio, or double-click the shortcut to the .aup from Windows Explorer.
  • (Windows) The Audacity executable cannot be added to the Explorer "Open with" context menu if you have another version of Audacity on the system which is also called "audacity.exe". Workaround: either use the "Open with" dialog to browse to the executable each time, or rename the executable to or some other unique name.
  • Dragging a clip or track up or down with Time Shift Tool does not scroll the project window when tracks exist out of view above or below the scroll. Workaround: Choose View > Fit Vertically before drag, or click and hold the piece to be dragged, use up or down arrow on the keyboard to scroll to the target track, then drag and release the clip or track.

Keyboard Shortcuts

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

Label Tracks

  • Typing "j", "J", "k", "K" or other shortcuts in a label track may activate the shortcut instead of typing in the label. Workaround: In many cases, Edit > Undo then Edit > Redo will allow you to type in the label. Otherwise, click Edit > Preferences: Keyboard, choose the correct category, then clear the affected shortcuts or change them to include a CTRL + SHIFT modifier or other modifier than SHIFT.
  • (Linux) In projects containing several hundred labels or more, Audacity will freeze on 100% CPU when opening the "Audacity Karaoke" window, and will freeze again while that window is open when editing a label or performing other actions on the project. Workaround: Open or place an empty label track above the one you want to use.
  • Unless Tracks > Sync-Lock Tracks is on, pasting or inserting audio does not affect labels even if the label track is included in the selection.
  • Yellow "snap" guidelines do not appear in re-opened projects or imported label tracks when dragging a selection to a label edge if "Snap To" is checked and a high resolution Selection Format chosen. Formats affected include "hh:mm:ss + CDDA frames (75 fps)", "hh:mm:ss + milliseconds" and "hh:mm:ss + samples".

Miscellaneous platform-specific issues

  • (Linux) A playback or recording freeze with pulseaudio may occur if repeatedly starting and stopping playback or recording in quick succession (or holding down the Play or Record button). Workarounds: Try launching Audacity from the terminal with the pulse latency set in an environment variable, for example:
      env PULSE_LATENCY_MSEC=30 audacity
      Alternatively, bypass pulseaudio by setting the playback and recording device to an ALSA (hw) choice in Device Toolbar.
    • (Mac OS X) If using Audacity when the "Hear" audio plug-in is running (or has been since boot), there will be excessive memory usage which could cause a crash: this appears to be due to buggy memory allocation in "Hear"
    • (Mac OS X) Very occasionally, users may find that after running Audacity, other media players don't produce any sound, or crash: to resolve this, set up your sound device in Apple Audio MIDI Setup to work in stereo, 16-bit, with a sample rate of 44100 Hz or 48000 Hz, and set the sample format and rate identically in Audacity. More help at: http://audacityteam.org/forum/viewtopic.php?f=17&t=5064

    Mixer Board

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

    Playback and Recording

    • Append Record with Transport > Overdub (on/off) enabled may cause periodic playthrough of previously recorded audio. If you use the Stop button or SPACE to stop the previous recording instead of SHIFT + A (Stop and Set Cursor), this may reduce occurrences of the issue.
    • (OS X and Linux) Audacity now works very well with JACK, with the following bugs and limitations:
      • Clicking in the input meter to start monitoring will crash Audacity if it has not yet used JACK for playback or recording in that session. Workaround: Before recording the first track in a session, click "Pause" then "Record" to enable the recording meter.
      • The best way to connect to available JACK inputs and outputs is directly from Device Toolbar. Use Transport > Rescan Audio Devices when necessary, for example to make new JACK applications ports available to Audacity. See here for details.
      • On Mac, Audacity may freeze if JACK is launched by QjackCtl then Audacity is launched. Workaround: Use JackPilot to launch JACK, or launch QJackCtrl after Audacity and JACK are running.
    • (OS X and Linux) PortAudio's default latency values which are used when recording with software playthrough are much lower than Audacity's default "Audio to buffer" setting. This may cause playthrough or recording glitches when recording with software playthrough enabled, especially when using pulse on Linux. Workaround for Linux: record from an (hw) device instead if software playthrough is required.
    • (OS X) Playback to Bluetooth headsets gives an error. Workaround: Revert to Audacity 1.3.3 (this may only work with stereo headsets), or use Soundflower to send the Audacity output to an audio application that works with the headset.
    • (OS X) The "Hardware Playthrough" option in Recording Preferences is currently unsupported on all known Mac hardware. Try the "Software Playthrough" preference instead. If that does not work, the third-party LineIn application also provides software playthrough.
    • (Windows) The input slider in Device Toolbar is disabled for all or most inputs. Please use the Windows system input slider instead.
    • (Windows) Recording from the stereo mix input may not produce an adequate input level unless you turn the system audio output up very high. On Windows Vista and later you can choose the "Windows WASAPI" host and a "loopback" input instead for recording computer playback.
    • (Windows) When a USB device is connected, the Mixer Toolbar input slider for that device (and sometimes for any device) may wrongly appear active even though it has no control over the device's input level. Sometimes the Audacity slider will apply a software gain to the level (which is dangerous as it will only make the same clipped input quieter rather than stopping the clipping). Sometimes the Audacity slider will not affect the input volume at all. Workaround: use the slider in the Windows Control Panel where available, or any gain control on the device, or reduce the output being sent to the device.
    • (Windows) When you install Audacity for the first time or launch it after resetting Preferences Audacity will choose a specific output and input device rather than the Sound Mapper devices that are the current Windows default devices. Workaround: If you lose playback audio or only record silence for this reason, use 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 email 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 Project Rate set to 44100 Hz . Setting other project rates will cause Audacity to resample the input to the project rate any may cause glitches in the recorded audio.
      • "Audio to buffer" in Recording Preferences cannot be used to adjust recording latency.
    • Adding or removing an external audio device while Audacity is open will not be automatically reflected in the list in Device Toolbar or Devices Preferences. On Mac, unplugging then replugging an external device will give "error while opening sound device" (on Linux, pressing "Record" a second time will remove the error). Workaround: Use Transport > Rescan Audio Devices.
    • Calculation of "disk space remains for recording (time)" incorrect when recording in 24 bit quality.
    • Play-at-Speed slider: Change of playback speed is no longer automatic after you move the play-at-speed slider. To change speed, move the slider, then click the green button to left of the slider to play at the new speed.
    • Timer Record cannot maintain scheduled duration if system clock changes
    • (Windows Vista, 7) If you change the explicit output and/or input device selected in Device Toolbar or Devices Preferences and then change "Host", the selected devices will change back to those originally selected.
    • (Windows XP and earlier) Changing the default playback or recording devices in the Windows Control Panel while Audacity is open may cause all the playback or recording choices in Device Toolbar to produce silence (or to fail with "Error opening sound device"). This problem may also occur when connecting or disconnecting a USB device while Audacity is open. Workaround: Click Transport > Rescan Audio Devices then you can play or record.

    Program Launch

    • (Linux) If a Bluetooth audio device is in use on a PulseAudio system, Audacity may hang on launch on initial attempts, then after eventual launch Bluetooth will no longer work on the system. Workarounds:
      • Remove and reconnect the external Bluetooth adaptor, then launch bluetooth-applet from the command line.
      • To prevent Audacity affecting Bluetooth support, move /usr/share/alsa/bluetooth.conf to another location then reboot, or create a symbolic link from /var/lib/alsa/asound.state to /dev/null and reboot.
    • (Windows and OS X) "Install VST Effects" dialog:
      • The dialog lists more than VST effects: On first use, Audacity scans for VST effects then (before launching Audacity) presents a dialog where you can choose which VST effects to load into the Audacity Effect menu. Remove the checkmark from any VST effects you do not want to load then click OK to load the checkmarked effects. If you click Cancel the dialog will reappear on next Audacity launch.
      • VST instruments will appear in the list but are not supported, so will not load even if checkmarked.
      • On Windows the dialog will appear even if you have no VST effects, because Audacity detects the two shipped LADPSA plug-ins (hard_limiter_1413.dll and sc4_1882.dll) and also any optional LADSPA DLL plug-ins you may have installed. These LADSPA plug-ins will load whether you enable them in the dialog or not. Therefore you should just click OK on the dialog if you have no VST effects.
      • The dialog is on top of other windows, so could hide any prompts that VST effects show when effects are loaded after pressing OK. This would be evident by the "loading progress" arrow in the check boxes coming to a halt and the VST dialog losing focus. To continue loading the effects in this case, press ENTER on your keyboard to OK the hidden prompt, or drag the VST dialog away to reveal the prompt then click OK on the prompt.

    Projects

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

    Time Tracks

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

    Toolbars

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

    Bugs requiring more investigation

    Warning icon
    • Very occasionally, Audacity projects may reopen with missing block files, orphan block files and/or silenced audio data. There may be unwanted renaming or moving of AU files within the project. We believe having multiple projects open at once or having projects open in file manager programs are among the possible causes. See Bug:137 for more background to this.
    • The AUP file may be saved with references to only a few of the AU files, again leading to "orphan block file" warnings. Sometimes the AUP file may not be found after saving and closing the project.
    • Sometimes errors occur when saving the project or when Audacity autosaves, perhaps wrongly suggesting the disk is full or not writable (if this happens, try exporting the audio as WAV).

    Please write to our feedback address if you encounter any of the above symptoms. As many as possible of the following will help us enormously if you can attach them to your report:

    • A copy of the saved AUP project file
    • A copy of the AUTOSAVE (temporary project) file. This file is stored inside the "AutoSave" folder in Audacity's application data folder.
    • For problems that occur when reopening or working in a project, the log file at Help > Show Log....
    • (Linux) If Audacity is compiled with the option to use libsamplerate and the default "Best Sinc Interpolator" for high-quality conversion is used, Tracks > Resample may lead to truncation of the waveform. Workaround: change the project rate to the desired rate, export the track and re-import it.
    • (Windows Vista) If you change the input volume in Audacity and then record, the volume is reset to its original level. This appears to occur mostly with a few specific USB devices, and sometimes only on Vista SP1, so it is currently hard for us to fix. Workaround: Check if the manufacturer supplies their own drivers for the device and try those. See if upgrading to Vista SP2 or Windows 7 helps.
      • Please report make and model number of devices that exhibit the issue, also the drivers and exact version of Vista and Service Pack in use (for example, Vista 32-bit, SP1)
    • (Windows Vista, 7) When a USB device is connected, the listing of inputs for the built-in sound device in Device Toolbar or Devices Preferences may become corrupt, indicating single inputs as multiple inputs. It may only be possible to record from the built-in input which is currently set as default at "Sound" in the Windows Control Panel, irrespective of the input selected in Audacity. Workaround: Try Transport > Rescan Audio Devices, or a computer reboot.
      • Please report make and model number of devices that exhibit the issue, along with description of symptoms and any steps you have noticed that create the issue.
    • (Windows Vista,7) On upgrading to the current Beta from 1.3.12 or earlier, "error opening sound device" occurs when recording from the inbuilt sound device where there was no error in the previous Audacity with the same device configuration and operating system. Workaround: Use Transport > Rescan Audio Devices, or go to "Sound" in the Windows Control Panel and click OK. Note that if devices listed in Device Toolbar are disabled in "Sound" then the error is legitimate - you will need to enable those devices.
      • Please report make and model number of sound devices that exhibit the issue, along with driver version number. Please first ensure your sound device drivers are up-to-date and not generic Microsoft drivers - help available here.
    • (Windows and OS X) Some USB or Firewire recording devices only record silence, or only offer mono recording for a stereo device, or only mono or stereo for a device that previously supported multi-channel recording. Workaround: You can try 1.3.10 Beta or earlier (including 1.2.5/6), but these versions may have other bugs or limitations.
      • Please report make and model number of devices that exhibit the issue, and your operating system details (for example, Windows 7 Service Pack 1).
    • (Windows) There may be substantial delays drawing the waveform in longer projects. These include:
      • opening saved projects that were fitted to the window
      • fitting an already zoomed in project to the window or zooming in on a fitted project
      • progress dialog remains white for a long time after the progress bars complete for a file import or effect.