|This page provides a detailed list of issues for Audacity 2.2.2
Known Major Issues at Release
- Many, but not all parts of the Audacity interface are accessible on Windows and Mac (read the alert above about Mac) to those who can't use a mouse, and/or use a screen reader. It may be possible to make more of Audacity accessible in the longer term. For details, see https://manual.audacityteam.org/o/man/accessibility.html
- There are some accessibility bugs in the parts of Audacity that are accessible (or behavior may vary according to the specific screen reader).
- Toolbars that show disabled at View > Toolbars and are then re-enabled will launch undocked if Audacity has already been restarted. Workaround: perform View > Toolbars > Reset Toolbars before enabling any disabled toolbars.
- After mouse down to drag a docked toolbar to a new docked or undocked position, the track focus is removed and the selected control loses its focus border even though that toolbar still has focus. When dragging or resizing an already undocked toolbar, the selected control similarly loses its focus border.
- Keyboard Preferences: Window-Eyes doesn't read the key bindings when View by Tree is selected, and may not always read the bindings in other views. VoiceOver and Orca do not read the key bindings at all. You could export the bindings, modify them in a text editor then import the modified list.
- Spectral Selection Toolbar:
- You can't enter a new low frequency first if it is above the current high frequency - in that case, you must enter the new high frequency first.
- If you change low and high frequencies to kHz, then typing or incrementing values in the High Frequencies box has unpredictable results.
- It is not possible to use the keyboard to move the cursor or selection region to an arbitrary position when playing or recording. However you can use the [ or ] shortcuts respectively to set the left or right boundary of the selection at the playback or recording position ( https://manual.audacityteam.org/man/edit_menu_select.html#left ). Different Scrubbing modes may also be started using shortcuts or the Transport Menu, but there is no keyboard interface yet to control scrubbing. Scrubbing may be started by shortcut even if the pointer is in the waveform, although the Status Bar messages don't refer to moving the pointer to Scrub.
- Edit toolbar buttons that depend on selection are (at least in NVDA) announced as Disabled when there is no selection, rather than being skipped over. Hitting ENTER on such a disabled button will auto-select the audio, applying the edit to all of that automatic selection.
- In certain parts of the main window, NVDA does not speak typed characters (JAWS and Window-Eyes are not affected):
- In the main window, not speaking a character if it is a command for example, j,k,[ or ]
- In a label track, not speaking characters typed into a label.
- (OS X/macOS):
- Audacity is not yet fully Retina-ready. It is known that the Track Control Panel appears fuzzy. Please let us know of any other issues. Retinizer can no longer be applied to Audacity. If Retinizer is applied to previous Audacity this will prevent the export format being changed.
- Selection is not in the first control of Generators, Effects or Analyzers. In most effects the selection is invisible and one TAB puts selection in the Manage Button. In Change Speed the selection is "Current Length" and in Change Pitch the selection is the first octave.
- If you apply a real-time preview effect while focus has remained in Audacity, the effect loses focus. If you apply a real-time preview effect after task switching away from and back to Audacity, the effect will go behind the project window. The effect may be brought back to focus in both cases with ALT + F6.
- It is not possible to move between the main Audacity window and some VST and Audio Unit effects using the ALT + F6 or ALT + SHIFT + F6 shortcuts when the effect is in Graphical Mode. You can use the "Manage" menu then Options... to change the effect to textual mode.
- (OS X/macOS) Issues with VoiceOver:
||Unfortunately, current Audacity is not accessible for users of VoiceOver for the reasons given below. This was also the case for releases starting from Audacity 2.1.1. However, an accessible version of Audacity 2.1.1 is available on our Mac OS X downloads page. The name of this accessible version is "2.1.1-screen-reader" (DMG and ZIP downloads are available). It is hoped that future versions of Audacity will be accessible for users of VoiceOver.
- (reported on OS X 10.9.x) After exporting, the black accessibility area is trapped in the Tooldock area, so there is no way to read the tracks. Workaround: Save as a project, close the project then reopen it. You can then navigate the tracks with VoiceOver.
- If you use arrow keys to navigate the Timetext controls in Selection Toolbar, VoiceOver stops reading. Workaround: Use Control-Option-W
- When you TAB forwards from "Audio Position" in Selection Toolbar, the "Selection End" or "Selection Length" radio button is read as "Selection Start". When you use COMMAND + F6 or COMMAND + SHIFT + F6 to move directly into "Selection End" from another toolbar, the button is read as "Selection Start".
- Mixer Toolbar input/output sliders are not read, but just described as "multiple indicators". The "Graphic EQ" and vertical sliders in Equalization *are* read.
- Metadata Editor table not read.
- Edit Labels dialog not read.
- In the "Edit Chains" window, only the first command in the "Chain" list is read, and it is only read when first accessed. In the "Select Command" window for inserting a new command in a Chain, commands in the table are not read.
- "Manage Curves" table in Equalization not read.
- (Linux) Issues with Orca:
- Audacity tracks are not read.
- Not all toolbar controls are read, examples being Timetext controls, Project Rate and controls in Device Toolbar.
- Not all controls in Preferences are read.
- Control labels for VAMP and VST plugins are not read.
- Control labels for Nyquist plugins are read inconsistently in older version 3 or earlier plugins (Version 4 seems to read more consistently).
- (Linux Ubuntu) On high resolution monitors, Plot Spectrum may initialize with the lower part of the display and the effect controls off the bottom of the monitor. As a Workaround: you could try holding ALT and pressing E on your keyboard to export a text file of the plot.
- If Audacity 2.1.1 or earlier had the interface language set to "Simplified" (an optional English language that can remove menu items) then current Audacity will show an error on each launch "Language "en-simple" is unknown". No menu items will be hidden. Workaround: To prevent the error occurring at each launch, open Preferences then OK which changes the language to English.
- Simplified menus are also not currently supported in any other languages, but no errors are shown. Menu items that should be hidden will be shown starting with an "!" exclamation mark.
- (Linux) If a Bluetooth audio device is in use on a PulseAudio system, Audacity may hang on launch on initial attempts, then after eventual launch Bluetooth will no longer work on the system. 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.
- (Mac and Linux) Audacity will not launch if the temporary directory is set to a USB or hard drive formatted with FAT16, FAT32 or exFAT. To make Audacity launch again, open the audacity.cfg settings file. Underneath the [Directories] line, change TempDir to any drive or partition formatted with the operating system's native file system (MacOS Extended (HFS+) on Mac, or ext3/ext4 on Linux).
- If you launch Audacity by COMMAND + Space (Spotlight Search) then ENTER (or double-click the search result), a false error prompt appears "The application "Audacity.app" can't be opened" when in fact it will open anyway.
Bugs requiring more investigation
- (Windows Vista or later) On upgrading to current Audacity from earlier versions, "error opening sound device" occurs when recording from the inbuilt sound device where there was no error in the previous Audacity with the same device configuration and operating system. Workaround: Use Transport > Rescan Audio Devices, or go to "Sound" in the Windows Control Panel and click OK. Note that if devices listed in Device Toolbar are disabled in "Sound" then the error is legitimate - you will need to enable those devices.
- Please report make and model number of sound devices that exhibit the issue, along with driver version number. Please first ensure your sound device drivers are up-to-date and not generic Microsoft drivers - help available here.
- (Windows Vista) If you change the input volume in Audacity and then record, the volume is reset to its original level. This appears to occur mostly with a few specific USB devices, and sometimes only on Vista SP1, so it is currently hard for us to fix. 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) Some devices that used to offer multiple recording channels in Audacity without ASIO may now only offer mono or stereo recording instead of the expected number of channels. Usually the multi or similar device only has 2 channels instead of the expected number. Occasionally the multi device is missing, leaving only two-channel devices to choose from. These devices have been reported:
- Alesis Multimix-8 USB
- M-Audio Delta 66
- Motu 896 AD/DA FW
- Tascam US 1641 and US 1800
If you experience this issue please report make and model number of the device, your operating system (for example, Windows 7 Service Pack 1) and the device driver version number you are using. It is possible that more than stereo recording may be possible if you can find earlier drivers that are still compatible with your version of Windows, or if you try the Windows WASAPI host in Device Toolbar. See Multichannel Recording for a list of devices reported to record multi-channels into Audacity without ASIO.
- (Windows) There may be substantial delays drawing the waveform in longer projects of an hour or more. The main problems are with opening saved projects that were fitted to the window, and fitting already zoomed in projects to the window, such as a new recording. Additionally:
- Opening and closing large projects one after the other may eventually cause project opening to slow significantly
- Import or effect progress dialogs may stall "whited out" for a few seconds after the progress bars complete before the waveform is drawn.
- Audacity's built-in generators don't yet work intuitively with Chains. In particular, using the generator from the Generate Menu resets the Chain to use the settings last used from the Generate Menu. Plugin generators should work better with Chains.
- Chains do not currently support export as AIFF, Other uncompressed files or any formats supported by FFmpeg.
- For some effects (Equalization is a known example) parameters stored in Chains may not persist are not independent of the settings saved when running the effect from the Effect Menu. Changing the effect parameters from the Effect menu will thus change the effect parameters stored in the Chain and vice-versa. Workaround: For Equalization, you can use Save / Manage Curves... to save the required curve as a named curve, then choose that curve from the "Select Curve:" dropdown when setting the parameters for the Chain command.
- You cannot set export format options or export sample rate in the Chain. If you need to specify export options other than the current default, import or generate some audio, File > Export, select the audio type, click "Options..." then choose and save the option and cancel the export.
- (Windows) LV2 effects can only be used in a Chain at their default settings.
- Noise Reduction does not yet support storing its parameters in a Chain. Noise Reduction will run at its last used settings if used in a Chain.
- Audacity cannot build against wxWidgets compiled with STL. . There will be many errors of the form "cannot convert ‘const wxString’ to ‘const wxChar*". The best approach to a solution has not been decided, but if you would like to help with this please start a discussion on our audacity-devel mailing list.
- (Windows) LADSPA effects cannot be categorized even when Audacity is compiled with USE_LIBLRDF defined.
- (Linux) Audacity may not always compile against supported versions of libav or FFmpeg. Audacity 2.0.6 and later supports FFmpeg 1.2 to 2.3.x (or libav 0.8 to 0.10.x).
- 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, Generators or Analyzers plug-ins (except Nyquist) that are no longer available remain listed in the menus until you open the Plug-in Manager. The plugins will then be removed from the menus after restarting Audacity. This also applies to previously shipped plug-ins that are no longer available in current Audacity, such as Hard Limiter.
- Equalization: do not use the "Manage > Save Preset" function to save a custom curve; use "Save / Manage Curves" instead. Using the "Manage" button to save and recall presets can cause unexpected results, and in rare cases can cause Audacity to hang.
- Identically-named effects cannot be differentiated in the "Select Command" dialog in chain editing. When clicking "Edit Parameters", Audacity will show the dialog for one version of the effect, regardless of which one is selected in the "Select Command" list.
- Plug-in Manager dialog: The dialog may include some VST instruments or VST 3 effects but these are not supported so will not load even if enabled.
- (Windows) The Plug-in Manager does not properly disable the SC4 effect. If you disable SC4 in the Plug-in Manager, it will remain disabled during your current Audacity session but the next time you re-open Audacity the SC4 effect will be shown as enabled and will be available for use.
- If the track rate differs from the project rate, the Equalization effect will give the wrong result.
- In the Equalization effect if you create a "curve" with a vertical segment, then that vertical segment will not be recalled properly by Audacity when you next use the effect. Also note that you cannot use the "Manage" or the "Save/Manage Curves" - as these will exhibit the same corruption of the curve.
Effects (Audio Units) (OS X)
- AU effects cannot show graphical interface if Audacity is set in its Preferences to a language that uses comma as decimal separator. French however is a known exception to this.
- AUPeakLimiter when opened may show only its title bar or show a visually corrupted title bar containing black pieces from the interface. To correct the interface it may be possible to click on the plug-in controls or to click the Apply button then undo the effect. Alternatively, click the "Manage" button, then in "Options" select the "Basic" or "Generic" interface.
- In LV2 effects that operate in textual mode, any saved User Presets are not recalled but reset the effect to default settings. In graphical LV2 effects, resetting to defaults or recalling a saved User Preset may not affect the controls.
- MDA LV2 plug-ins on macOS crash Audacity if applied in a Chain, even at default parameters.
- (Mac OS X and Linux) LV2 instruments that Audacity should ignore because they are incompatible are listed in Plug-in Manager (64-bit Linux may not be affected). These plug-ins will not work in Audacity even if you re-enable them.
- Nyquist effects may crash Audacity if used on extremely long selections containing more than 2^31 samples (just over 13.5 hours at 44100 Hz). Workaround Apply the effect to multiple shorter regions (you can drag the selection back on itself to create a region contiguous with the previous one).
- Many Nyquist plug-ins will fail or may be sluggish if the track selection is too long, or could cause Audacity to crash. This is because the maximum selection length is limited by the amount of available ram, up to a maximum of 2 GB. Workaround: Unless you know that a particular Nyquist plug-in is safe to use with long selections, do not select more than about 1 hour of audio (44100 Hz sample rate) at a time. For higher sample rates the limit is proportionally less. If necessary, apply the effect to sections of 1 hour or less.
- Nyquist effects render the space between clips as silence. Workaround: Edit > Clip Boundaries > Detach at Silences (this may also remove parts of the original audio if any of it was totally silent).
Effects (Real-time preview)
- (MacOS) Audacity CPU use will be 100% if a non-Real time preview effect (such as most built-in effects) or other modal dialogue is open at the same time as any Audio Unit effect or a graphical VST or LV2 effect. This is currently necessary to prevent a modal dialogue freezing Audacity when certain graphical VST or Audio Unit effects are running. Workaround: Excessive CPU use will not occur if you open the Manage button in the VST or LV2 effect then disable the option for graphical interface. Excessive CPU use will occur even with AU effects running in textual interface.
Effects (VST and Audio Units)
- (GNU/Linux): When exporting VST effect presets, the FXP or XML file extension is not automatically offered in the file name, and not added by Audacity if you omit it. Make sure the extension you add is the same as that shown in the "File Format" drop-down menu, otherwise the preset will not be loadable.
- (Windows and Mac OS X) When running VST effects in graphical mode the controls of many plug-ins do not visibly respond when loading a preset file from the "Load" button. The new settings are however loaded internally, will apply when running the effect and will be visible if you reopen the effect after running it. Controls do respond to loading a preset file if you turn off graphical mode.
- Betabugs PhaseBug and PhaseBug Mono hang the Add/Remove Plug-ins dialogue on high CPU usage after Enable and OK. Try Audiocation Phase instead.
- DFX Geometer from http://destroyfx.smartelectronix.com/ may crash Audacity when loading the effect from the Effect Menu. This usually happens only once or twice when the effect is first loaded in the operating system session. Once the effect is open in Audacity it should work properly.
- DISTRHO Mini Series VST's from http://distrho.sourceforge.net/plugins.php crash Audacity in graphic mode but will run in text mode (open the Effects Preferences and uncheck "Display VST effects in graphical mode").
- MDA Tracker may crash if the effect is applied while playing audio or if stopping and starting playback.
- ReaPlugs plugins do not see user presets which were saved in Audacity 2.1.0 or 2.1.1.
- You must restart playback to hear the result of enabling or disabling ReaEQ tabs. "Enable" or "Active" checkboxes work correctly while playing in other ReaPlug effects.
- SimulAnalog Guitar suite plugins may crash Audacity at the default Buffer Size of 8192. For the most stable results, use the Manage button in the effect, then Options... and change Buffer Size to 8000. If crashes persist, use the effect by just applying it, without playing audio while the effect is open.
- Waves v5 may cause Audacity to hang if you select it in the "Register Effects" dialog then click OK.
- (OS X)
- The following plug-ins may cause Audacity to crash.
- AURoundTripAAC from "Apple audio mastering tools" (this requires OS X 10.6 or later so may crash on 10.4 or 10.5).
- Endless Series AU
- Digitech RP250 (effects pedal)
- Native Instruments B4 and Native Instruments Guitar Rig v3 and v4 (v5 does not have this issue)
- Waves Version 7 and 8 AU: These effects may crash Audacity on quit, after project data has been saved. Waves Version 9 AU should now work correctly.
Effects and Analysis
- (Windows 64-bit) There is no HKEY_LOCAL_MACHINE\SOFTWARE\ registry key where Audacity detects VST plug-ins. The HKEY_CURRENT_USER key searched is HKEY_CURRENT_USER\Software\VST\VSTPluginsPath instead of the expected HKEY_CURRENT_USER\SOFTWARE\Wow6432Node\VST .
- "Classic Filters" which can be enabled at Add / Remove Plug-ins has no vertical scale for the graph.
- Noise Reduction values are not validated, so unwanted results may occur. Entering a negative value for Noise Reduction can lead to severe overamplification of the audio, and entering values well above the slider values for the Sensitivity and Frequency smoothing parameters can lead to excessive deamplification.
- Noise reduction: Preview is not possible if the sample rate of the project is different from the rate of the track to be processed - an error message appears "Sample rate of the noise profile must match that of the sound to be processed" (even if that condition is met). Providing the noise profile rate does match the track rate, you can still apply the effect. Alternatively, change the project rate temporarily to the rate of the track.
- Plot Spectrum and Contrast cannot currently be removed from the Analyze Menu.
- (Linux) On Ubuntu with the Unity interface enabled in audacity.desktop, previewing a built-in or Nyquist effect or generator in one project then opening the same effect or generator in another project will cause a crash. There may sometimes be a crash if opening any built-in or Nyquist effect or generator in another project when such an effect is already previewing.
- (Linux) Opening the "Help on the Internet" dialog from the Help menu or from Contrast... creates an additional empty and unclosable dialog, and the real help dialog asserts when closed. Be sure to press "Continue" in the assertion error dialog. If you press "Stop", Audacity will force quit.
- (Linux) Sliding Time Scale / Pitch Shift may crash randomly in Audacity built with pre-2.0.2 versions of libsbsms. This may occur for example in the Ubuntu package of Audacity 2.0.5 on Ubuntu 14.04. Workaround: Build Audacity configured --with-sbsms="local", or use the Audacity package in Ubuntu 14.10 which uses libsbsms 2.0.2-1.
- (Mac) Typing or pasting values in the parameter boxes of the Reverb effect will either not change the parameter applied or set it to zero, as shown by the slider positions. Workaround: User the sliders to set effect parameters. To do so using the keyboard, CTRL + F7 if necessary to enable Full Keyboard Access, then TAB into the slider and use arrow keys or Page Up/Down.
- (Windows and Linux) Some LADSPA "Blop" plug-ins ( http://blop.sourceforge.net/index.html ) are reported to crash in Audacity on Linux Debian. On Windows, the Blop plug-ins included in http://opensourcepack.blogspot.co.uk/p/ladspa-for-win32.html can also crash, but this can be avoided if you ensure the "blop_files" folder contains the necessary "_data.dll" files for the plug-ins and that this folder is present in the Audacity "Plug-Ins" folder.
- (Windows and Mac OS X) The SC4 compressor shipped with Audacity crashes if used in a Chain.
- (Windows) Very rarely, Audacity may show no built-in effects, generators or analyzers after upgrading from an earlier Audacity 2.1.x version. If this happens, open Effect > Add / Remove Plug-ins..., enable the built-in effects if not already showing as enabled, then click OK.
- (Windows) LADSPA Multiband EQ may not be visible in Effect menu and crashes soon after opening
- (macOS) Many items in the Generate, Effect and Analyze menus (except for example Plot Spectrum) cannot by default be applied/closed by ENTER on the keyboard unless you first press TAB once. Effects which have no text boxes for input values, such as Audacity's Compressor or most VST or Audio Unit Effects will not respond to the TAB workaround.
- An alternative which avoids having to use TAB is to CTRL + F7 once to enable Full Keyboard Access for all applications. In any case, without this setting enabled, it will be impossible to navigate dialog buttons or Audacity Preferences using only the keyboard.
- Cut Preview only plays the upper track of multiple selected or Sync-Locked tracks.
- The following effects remove envelope control points:
- Change Speed/Pitch/Tempo; Equalization; Noise Removal; Sliding Time Scale/Pitch Shift; any Nyquist effect in the Effect menu. Workaround: Use Tracks > Mix and Render to apply the envelope to the waveform before applying the effect.
- The Reverse effect retains the control points, but does not move them.
- The volume envelope can become corrupted when joining adjacent clips.
Envelopes and Clips
- If audio is created at other than time zero, a selection made in that clip could act on the sample before the first visually selected sample but not act on the last visually selected sample. If fully selecting such a clip or dragging to or from its left border, the first sample will appear unselected despite being selected.
- In a few cases, pasting into a track containing clips could remove the envelope points in the clip being pasted into. Tracks > Mix and Render on that track could crash Audacity. It is recommended to select the track and File > Export Selected Audio... as WAV. This should render the envelope points then you can import the WAV back into Audacity.
- Boundary Snap Guides often do not appear when snapping to Split Lines created with Snap To enabled at hh:mm:ss + milliseconds or higher resolution. You could label the split lines or turn Snap To off to see the guides.
- WAVEX (Microsoft) headers: GSM 6.10 files cannot be exported with WAVEX headers. Use WAV headers instead (note that GSM 6.10 only supports mono). A-Law and U-Law files with WAVEX headers may not be playable - use WAV headers instead. Choose "Other uncompressed files" then "Options..." to export to GSM 6.10 or A-/U-Law with WAV headers.
- When exporting, tracks with Mute button down are excluded from the export mix as intended but currently no warning is provided about this.
- (Linux) Exports using "M4A (AAC) Files" are very slow irrespective of the AAC encoder FFmpeg is configured to use. Workaround: choose (external program) when exporting, entering an appropriate path and command (for example, /usr/bin/ffmpeg -i - "%f") to run FFmpeg using Audacity's command-line encoder.
- (Linux) Files exported using the FFmpeg native AAC encoder included with many system versions of FFmpeg may be of poor quality. This is an issue with the library itself. Workaround: When compiling FFmpeg, configure with the libfaac encoder thus: --disable-encoder=aac --enable-libfaac --enable-nonfree. Note that libfaac has an issue not present in the native FFmpeg encoder that saved files are short at the end by about 3000 samples. Alternatively build the VisualOn AAC encoder library and configure FFmpeg with --disable-encoder=aac --disable-encoder=libfaac --enable-libvo-aacenc.
- (Linux) Mono AAC files import as stereo if FFmpeg uses the libfaad decoder. This is again an issue with the library itself.
- (Mac OS X) When exporting using (external program) using any encoder, or using "Custom FFmpeg Export", you must agree to create and replace an unwanted "NoOverwritePrompt" file before you can export. The exported audio file is correct.
- (OS X) If you include / in the file name when using File > Export Audio... or Export Selected Audio..., the text before the / will be missing from the exported file name. As a Workaround: add the required file name to a label then Export Multiple.
- Audacity may freeze if using the Nero AAC encoder to export via (external program). It is reported this only occurs when using multiple CPU cores. Workaround: Export to AAC directly by adding FFmpeg to your computer, or set Audacity to use only one CPU core.
- Custom FFmpeg Export: many combinations of formats and codecs are incompatible, as are some combinations of general options and codecs. Some files may be exported as zero kb files.
- When exporting AAC (MP4) audio files the only control is a quality slider. There is no indication of the bitrate that will be achieved with the slider setting.
Imports and Exports
- A-Law, U-Law and ADPCM export formats (also RF64 for PCM exports larger than 4 GB in size) must be chosen by selecting "Other uncompressed files", ensure the "Header" is "WAV (Microsoft)", then from the "Encoding" dropdown menu select your desired encoding. We may redesign the export list in due course to make these formats easier to find.
- AAC exports using "M4A (AAC) Files (FFmpeg)" with project rate below 22050 Hz produce a zero bytes file if the linked to FFmpeg is configured with the default AAC encoder or libfaac. This will not affect the recommended builds of FFmpeg for Windows and Mac OS X which are built with libvo-aacenc. Workaround: You can export AAC below 22050 Hz using default-configured FFmpeg by choosing (external program) export instead.
- Files containing PCM audio but misnamed as MP3 cause a freeze or crash if an Extended Import rule is set in Preferences to force import of MP3 files using the MP3 importer.
- ID3 metadata tags in imported MP3 or MP2 files may display incorrectly if the metadata is UTF-16 encoded. The tags will seem to have Chinese characters and these incorrect tags will also be present if the files are re-exported. Workaround: Before importing the file into Audacity, open it in a tag editor or an audio application that can edit tags. If the tags are seen correctly, save the file in that application. On Windows you can use Foobar2000 for this purpose.
- On a fresh installation of Audacity or initialized Preferences, the "FFmpeg-compatible files" filter cannot be used to make FFmpeg import native Audacity formats such as WAV, AIFF or MP3. Similarly on macOS, the "QuickTime files" filter cannot be used to make QuickTime import MPEG-4 files instead of installed FFmpeg.Workaround: Open Preferences and click "OK" then the FFmpeg and QuickTime filters will work as expected.
- The Import / Export Preference "When importing audio files, Normalize all tracks in project" will cause import of WAV/AIFF files using "Read the files directly from the original" to lock up at the Normalize step. If you require normalize on import for WAV/AIFF, please change the Import / Export Preference to "Make a copy... before editing".
- When exporting using the "Other uncompressed files" option, if you change the required file-type in the "Header" dropdown in the "Format options" the filename extension will not change in the "File name" box to the left of the Save button.
- However the file will be exported in the correct format with the correct default extension for that format, even if you don't change the extension in the "File name:" box.
- When exporting using the "Other uncompressed files" option, the extension of the exported file is forced to the default for the format. For example it is not possible to export AIFF files with .aif or .aifc extension except by using the "AIFF (Apple) signed 16-bit PCM" option instead.
- (Linux) When using Export Multiple, asterisks (*) or question marks (?) in track names or labels are wrongly rejected as illegal characters. As a Workaround you can force use of * or ? by exporting each region with File > Export Selected Audio... instead.
- (Linux) After opening a sufficiently long audio file, opening a second file of any size might lead to locked GUI/console messages until the first file completes play.
- (Mac OS X) Dragging audio files to Audacity's icon in the Dock will only import the file for WAV, AIFF, AU, MP2, MP3, OGG, FLAC and M4A. Workaround: Rename MP4 files (audio or video) to M4A extension. Alternatively the files may be dragged to the Audacity icon in the folder where you have Audacity installed, dragged into the open Audacity window or imported using the Audacity menus.
- (OS X Pre El Capitan) iTunes files cannot be opened from Media > Music in the Sidebar in Audacity's file open dialogs. You could drag your iTunes "Music" folder to the Finder sidebar to give quicker access in Audacity open dialogs.
- (OS X) 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.
- When you import a MIDI or Allegro file into a Note Track, you will only see a restricted rage of notes with 2 and a half octaves, for the notes. So important notes are not visible. If there are un-shown notes you will see black markers at the top and/or bottom of the note track display.
- Workaround: Right-click on the note track's Vertical Scale and use Zoom Out or Zoom Reset
- "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 Edit > Metadata... before exporting. Audacity will then silently add the common and automatically generated Track Title and Track Number tags for each exported file.
- 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... 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.
- Album art and lyrics in imported metadata are lost when exporting. Workaround: Copy the lyrics (or search for them online) then add them back to the exported file in your favorite media player. Extract the album art using a tag editor such as IDTE (or use Windows Media Player or iTunes to search online for the art) then add the art back to the exported file using your media player.
- Tags other than the seven default Metadata Editor tags will be rewritten as custom ID3 TXXX tags, which will cause them not to be seen in applications like Windows Media Player and iTunes. Common tag examples include "Album Artist", "BPM" and "Composer".
- ID3 v2.4 tags in imported MP3 files are not seen and will be removed on export.
- Audacity writes both ID3 v2.3 (TYER) and v2.4 (TDRC) tags for "Year", but any applications that require the older TYER on its own (without TDRC) will not see "Year" in Audacity-exported files. The id3 command-line application on Linux is one example.
- WMA and APE (Monkeys Audio): "Artist Name" is not seen on importing the file (Audacity bug)
- Other metadata import/export may not always be consistent. This may depend on the program that created the imported tags and the program used to read the exported tags.
- When importing a MIDI track, the channel selection buttons to left of the track are not currently available.
- You cannot use File > Open to open a .txt label file (open a next project and silently import the label file). If you try you will get an (inappropriate and not relevant) error message.
- Workaround: Use File > New to create the new project, then use File > Import to import the .txt label file
Imports and Exports (FFmpeg)
- Custom FFmpeg Export dialog: It is necessary to save a preset before exporting it but there is no error message when exporting from an empty presets list and no advice in the interface that presets must be saved before export.
- M4A (AAC) exports: The Quality Slider in "Specify AAC Options" has no effect if the FFmpeg library is built with the libvo-aac encoder, as are recommended builds of FFmpeg for Windows and Mac OS X. Workaround: You can specify a constant bit rate if you select "Custom FFmpeg Export". Click the Options... button, choose "mp4" in the formats list and "libvo_aacenc" in the codecs list, then set bit rate in bits per second. Up to 320000 bps (320 kbps) is supported. Given the alternative AAC encoders for FFmpeg also have problems as described in these notes, you can instead export as WAV and convert to AAC in iTunes on Windows and Mac.
- M4A/MP4 (AAC): Artist and Year metadata is not exported or imported due to a bug in FFmpeg 2.2.2.
- Although first installation of Audacity will default audio export and project save to the user's Documents folder, TXT and XML exports such as for labels files, Plot Spectrum or keyboard bindings may offer to export elsewhere.
- On Windows the offered location will be the Audacity installation folder - if you are not running Audacity as Administrator, you must change the export folder in order to save the file.
- On Mac, keyboard bindings will open first time in Applications if you have not already exported or saved any files. You must change the export directory to save if you are not running as administrator. If you cancel keyboard bindings export after it offers the Applications directory, all other TXT and XML exports will then default to saving in Applications.
- On Linux, TXT and XML exports default to the root of your Home directory.
- (Windows) In the Audacity installer, selecting the language to use during installation now selects the language Audacity will run in, even if Windows is running in a different language.
- After upgrading from version 2.1.3, it is possible to create duplicate key bindings (keyboard shortcuts) if you create a keyboard shortcut that is the same as an existing shortcut that exists only in the full set.
- Set the defaults to full set before creating custom keyboard shortcuts (but you will lose any custom shortcuts you had set in 2.1.3).
- Set the command which has the shortcut only in the full set to another shortcut. For example if you want to set the shortcut "A" to a command other than "Next Tool", first set the "Next Tool" shortcut to something other than "A". Note that clearing the shortcut does not work.
- Audacity does not alert you if it cannot write to its configuration or settings files or cannot remove its temporary settings files. The problem could occur due to interaction with a virus checker (this is most likely on Windows) or due to permissions problems.
- If the problem occurs, you might find a change you made in Preferences does not take hold, or that changing the settings in an effect then trying to apply the effect won't run the effect. On Windows, you will also find a build up of aud*.tmp or plu*.tmp files in Audacity's Preferences folder for application data though these are noted at Help > Show Log... .
- Performing an action which can be undone, making some types of display change then undoing the action will unexpectedly undo the display change as well. Examples of display changes that will be undone are changes to track height, track view mode or per-track Spectrogram Settings.
- When importing key bindings (keyboard shortcuts) in Keyboard Preferences, some may fail to import. **Workaround: in Keyboard Preferences, set Defaults to Full before importing the xml file.
- (Linux) Audacity currently does not support being extended across multiple displays, so that Audacity is visibly straddled between monitors. If Audacity is quit when the greater part is on the primary monitor, Audacity reopens centred on the primary monitor. If Audacity is quit when the greater part is on the secondary monitor, Audacity reopens on and at left of the secondary monitor.
- (Linux) Numeric value of track Pan / Gain sliders is malformed and appears only as a horizontal line.
- Workaround: Double-click the slider to bring up a window where you can see the gain value.
- (Mac) Copying or cutting from text boxes in file save dialogs using COMMAND + C and COMMAND + X respectively does not work. You can however right-click or CTRL-click and choose the option to Copy or Cut.
- (Mac) Pasting into file save dialogs using COMMAND + V has been restored with some limitations.
- COMMAND + V can only paste into the "Save As:" box even if another box has focus. You can use right-click or CTRL-click to paste into other boxes.
- The entire contents of the box are replaced with the pasted content, ignoring the selection cursor or partial text selections.
- (OS X and Linux) In some locales, Preferences text may be truncated or overlapped, or dropdown boxes truncated.
- (Windows) The "Files Missing" warning always restores maximised windows to smaller size.
- (macOS) If upgrading from Audacity 2.1.1 directly to 2.1.3 release or later, the Audacity Title Bar and window buttons may be hidden under the Menu Bar. Workaround: Use Window > Zoom or restart 2.2.0.
- (macOS) The "Window" menu does not currently provide a list of open windows for moving between projects. Use the Mac shortcut COMMAND + Accent (`) instead to navigate open project windows. You can customize this key binding at System Preferences > Keyboard > Shortcuts, then choose Keyboard in the list on the left.
More usefully, if you right click on the Audacity icon in the Task bar at the bottom of the Mac screen, you can then select "Show All Windows". This will display all open Audacity project windows enabling to choose any one by clicking it.
- After changing language in Preferences, a few parts of the interface don't change until Audacity is restarted.
- Crashes on incorrect behaviour on quit:
- (Windows) Audacity crashes after quit if quit from the Windows 7 Task Manager and "About Audacity" is open. If you save changes to a project, these changes are saved correctly.
- (Windows) Audacity cannot be quit from the Task Bar icon if "About Audacity" is open.
- (Linux) Any quit by any method produces "OS_IS_BAR (bar)" and "GTK_IS_WIDGET" (widget) assertion errors in the terminal if Audacity is launched from there.
- If Sync-Lock Tracks is enabled, there is no indication of the cursor in the Sync-Locked tracks.
- If you attempt to open an Audacity Project using the Import command you will be shown an error message (telling you to use File>Open instead).
- Clicking the (?) help button in the "xxx.aup is an Audacity Project File ..." message will take you to an Audacity dialog offering more help - but that help is inappropriate to opening a project.
- Further, if the local manual is installed (standard on Windows and Mac, optional according to your download choice on Mac and Windows), clicking the (?) help button in the "xxx.aup is an Audacity Project File ..." and then clicking on the links in the further message will take you to the online Manual and not your local installed Manual - and this will fail if you have no Internet connection.
- Mouse Bindings are not currently configurable by the user.
- The Device Toolbar width can shrink as you move the undocked toolbar around. WORKAROUND: Use the resize handle to resize and restore the width of the contents.
- When Logarithmic scale is selected for the Time Track, it is not possible to add or move control points.
Workaround: Set the control points with "Linear scale" selected, then change to Logarithmic scale (if required).
- When using TAB to move into a TimeText control (for example, in a Generator, Change Speed or Selection Toolbar) the first character is highlighted instead of the first non-zero character.
- The default track name for new audio tracks is not translated into the language chosen in Interface Preferences. As a Workaround: you can type in your preferred default track name in Tracks Preferences.
- (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).
- (Windows) It is not yet possible to drag .lnk shortcuts to audio files or projects into Audacity, or to drag them to the Audacity executable's icon. Workaround: Use File > Open or File > Import > Audio, or double-click the shortcut to the .aup from Windows Explorer.
- (Windows) The Audacity executable cannot be added to the Explorer "Open with" context menu if you have another version of Audacity on the system which is also called "audacity.exe". Workaround: either use the "Open with" dialogue to browse to the executable each time, or rename the executable to or some other unique name.
- Dragging a clip or track up or down with Time Shift Tool does not scroll the project window when tracks exist out of view above or below the scroll. Workaround: Choose View > Fit Vertically before drag, or click and hold the piece to be dragged, use up or down arrow on the keyboard to scroll to the target track, then drag and release the clip or track.
- On Linux if you have no local Manual installed, when you use Help > Quick Help you get two dialogs (instead of the single one expected). One of these dialogs is empty.
- Sync-Locked Tracks are not affected by all actions that change the length of a track in the Sync-Locked Track Group. Applying Paulstretch or using the Audio Track dropdown menu to change sample rate will leave the other Sync-Locked tracks desynchronised.
- (Linux) 'On some systems it is not possible to use keyboard shortcuts while focus is in the Karaoke window. If necessary, click to place focus in the main project window before using transport shortcuts. On some systems you may be able to pin the Karaoke window on top even if it lacks focus.
- (Mac) If you use Libraries Preferences to locate LAME manually, it is necessary to change the "File type:" filter to the choice for Dynamic Libraries or All Files in order to make libmp3lame.dylib selectable.
- (Mac / Linux) Cannot type diacritical characters into a label. Workaround - type the desired label into TextEdit then copy and paste into the label.
- The Tracks preference "Type to create a label" for typing in the focused label track doesn't work if you play audio then arrow-key into the label track to give it focus. Workaround: During playback, either use CTRL + B to add a label at the selection then type, or make a different selection in the label track then type.
- The frequency range stored in a Region label created in a Spectrogram track with Spectral Selection enabled can only be modified by "Edit..." from the label's right-click context menu.
- Currently there is no validation on OK'ing the entered frequency value, so invalid values can be entered with unexpected results.
- You can instead change the frequency range and save a new label in the same time selection then click in each label to display its frequency range, but if you TAB between labels in the same time selection all labels will show the frequency range of the last added label.
- Unless Tracks > Sync-Lock Tracks is on, pasting or inserting audio does not affect labels even if the label track is included in the selection.
- Yellow "snap" guidelines do not appear in re-opened projects or imported label tracks when dragging a selection to a label edge if "Snap To" is checked and a high resolution Selection Format chosen. Formats affected include "hh:mm:ss + CDDA frames (75 fps)", "hh:mm:ss + milliseconds" and "hh:mm:ss + samples".
- (Mac El Capitan) Audacity may not launch and a "Can't be opened" message will be displayed. Console log messages may refer to "Could not store lsd-identifiers file at /private/var/db/lsd/com.apple.lsdschemes.plist".
- Workarounds: Right-click or CTRL-click over Audacity.app, choose "Show Package Contents", then in the "MacOS" folder, double-click the "Audacity" executable. This will launch a Terminal window and Audacity will also launch. Alternatively you can try resetting the LaunchServices database by running the following Terminal command then rebooting:
|sudo /System/Library/Frameworks/CoreServices.framework/Frameworks/LaunchServices.framework/Support/lsregister -kill -r -domain local -domain system -domain user ; killall Dock
- For languages that use comma decimal separator, comma can only be used in effects on OS X by choosing that language in Audacity Preferences. This applies even if Mac system language is set to a comma-separated locale. On all systems, comma separator in effects after choosing a comma-separated language in Audacity Preferences requires that language to be installed on the system.
- (Linux Ubuntu/Debian): If Ubuntu or Debian is installed in a right-to-left (RTL) language such as Hebrew or Arabic, most of the Audacity interface will be empty and thus unusable. The only guaranteed solution is to set system language to English in system settings then restart the computer and change Audacity language to Hebrew at Edit > Preferences..., "Interface". There will still be some less serious RTL issues.
- (Linux) If system locale is set to Valencian and Audacity language in Interface Preferences is set to "System", Audacity will be in Catalan. You can change to Valencian language in Interface Preferences.
- (Windows) Audacity must be explicitly set to use Galician or Valencian in Interface Preferences to display those languages. Setting the Windows Region and Language format to Galician or Valencian and Audacity to "System" language will only display Audacity in English.
- Exporting Note tracks: Selecting "Allegro (*.gro)" as the file type when exporting note tracks does not produce an Allegro file unless the file name includes the extension ".gro".
- (OS X and Linux) Note track playback requires additional setup on Mac and Linux. See these pages on the wiki for Mac and Linux
Miscellaneous platform-specific issues
- (Mac OS X) If using Audacity when the "Hear" audio plug-in is running (or has been since boot), there will be excessive memory usage which could cause a crash: this appears to be due to buggy memory allocation in "Hear"
- (Mac OS X) Very occasionally, users may find that after running Audacity, other media players don't produce any sound, or crash: to resolve this, set up your sound device in Apple Audio MIDI Setup to work in stereo, 16-bit, with a sample rate of 44100 Hz or 48000 Hz, and set the sample format and rate identically in Audacity. More help at: http://audacityteam.org/forum/viewtopic.php?f=17&t=5064
- (Linux) A playback or recording freeze, recording dropouts or fast playback may occur when using PulseAudio. Freezes may be caused by repeatedly starting and stopping playback or recording in quick succession (or by holding down the Play or Record button). Workarounds: Try launching Audacity from the terminal with the pulse latency set to 30 ms in an environment variable:
|env PULSE_LATENCY_MSEC=30 audacity
If you get underruns noted in the terminal, try a higher number in the PULSE_LATENCY_MSEC command. If the problem is unchanged, try a lower number. Alternatively, bypass pulseaudio by setting the playback and recording device to an ALSA (hw) choice in Device Toolbar. More help with this can be found here
- (Windows and Linux) The Select All (CTRL + A) and Deselect All (CTRL+ SHIFT+ A) shortcuts may not work when focus is in Mixer Board. Workaround: CTRL+TAB to return focus to the main project window, then use the shortcuts there.
- Very occasionally, Audacity projects may reopen with missing block files, orphan block files and/or silenced audio data. There may be unwanted renaming or moving of AU files within the project. We believe having multiple projects open at once or having projects open in file manager programs are among the possible causes. See Bug:137 for more background to this.
- The AUP file may be saved with references to only a few of the AU files, again leading to "orphan block file" warnings. Sometimes the AUP file may not be found after saving and closing the project.
- Sometimes errors occur when saving the project or when Audacity autosaves, perhaps wrongly suggesting the disk is full or not writable (if this happens, try exporting the audio as WAV).
Please write to our feedback address if you encounter any of the above symptoms. As many as possible of the following will help us enormously if you can attach them to your report:
- A copy of the saved AUP project file
- A copy of the AUTOSAVE (temporary project) file. This file is stored inside the "AutoSave" folder in Audacity's application data folder.
- For problems that occur when reopening or working in a project, the log file at Help > Show Log....
Playback and Recording
- (Linux) If your project window is not maximised and you OK in Preferences with a label track present, the project window will be resized very narrow and there will be an assert in the terminal and possibly the project. Audacity will not be usable if a whited out assertion dialogue appears in the project window.
- If you try to save changes to an already saved project but the save fails, for example due to write error or write protection, only a cryptic error is displayed: "Could not create safety file: <path>\<project name>.aup.bak" (or aup~ on Linux).
- (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.
- (macOS) The button order in the "Save Changes?" dialog changed in 2.1.2 to a less Mac-like sequence of Cancel, No. Yes.
- Projects created by Audacity 1.1.x or earlier are no longer supported. Workaround: Export each project track as WAV using the appropriate legacy version of Audacity, then import the WAV files into current Audacity.
- Projects created by Audacity 1.2.x are partially supported - there is a possibility Audacity could corrupt them. Please make a backup copy of the project's .aup file and _data folder to a new folder before opening the project in this version of Audacity. Once you save the project in this version, it cannot be opened in 1.2.
- Projects created by previous versions of Audacity may contain audio "block files" longer than the project format allows. Reopening such projects in previous versions might or might not result in deletion of the overlong audio. Audacity has been provisionally fixed so that it can no longer create or delete overlong files, but it cannot read any such files it encounters. If overlong files are found, a "Problems Reading Sequence Tags" message will display .
- If you continue with the offered repair then choose "Continue without deleting" in the Orphan Block File(s) dialogue, the overlong files will be retained as "orphans" in the project's _data folder but will appear as silence in the track(s).
- As long as you choose "Close project immediately" in the Orphan Block File(s) dialogue, the project will quit and will not be changed in any way.
If you encounter the "Problems Reading Sequence Tags" message, please write to our feedback address with a copy of the .aup file and the log as found at Help > Show Log.
- Time Track warp points saved in a 2.0.3 or later project will be preserved if opened in previous Audacity versions, but playback and display will be incorrect.
Scrubbing and Seeking
- Currently we allow Scrub or Seek to be paused, but there are two problems if Pause is used:
- Unlike during other paused playback, menu items cannot be clicked on in order to stop playback and carry out the requested action. If you pause scrubbing, press ESC, SPACE or the Stop button when you want to edit.
- If you start Scrub or Seek by menu item, Scrub Toolbar button or shortcut then engage Pause, move the mouse then release Pause, moving or dragging will not start Scrub or Seek. If you click and release in Scrub Ruler then engage Pause, move the mouse then release Pause, moving the mouse will not start Scrub.
- Horizontal scrolling is permitted during Scrubbing and Seeking although it is unhelpful for the waveform to shift while in Scrub mode. If you are using a Magic Mouse on MacOS (or other mouse with a control surface) be careful not to brush the mouse surface during Scrub, or try temporarily disbling horizontal scroll in the mouse's preferences.
- Scrubbing or Seeking with Pinned head:
- To Scrub at normal 1x forwards speed without using the mouse wheel it is always necessary to move the mouse to the end of the window, even if the project is shorter than the window width. To backwards play at 1x, move the pointer to the start of the project. You can Seek at 1x with the pointer in the center of the window.
- If you try to forwards scroll-scrub in a less than half-width project by moving the mousewheel downwards to reduce backwards speed, moving the pointer to the end of the window will then achieve less than 1x speed. In that case, move the mousehweel upwards.
- You cannot easily forwards-scrub from the start of the audio or backwards-scrub from the end of the audio because playback might cease before the pointer moves far enough to change playback direction. Enabling "scrolling left of zero" in Tracks Preferences will make scrubbing easier for these use cases.
- (MacOS) If Scrub Toolbar is enabled and you remain hovered over a button after clicking it, the button tooltip may incorrectly change to "Hide Scrub Ruler" (or to "Show Scrub Ruler" if Scrub Ruler is turned off).
- A Spectral Selection created in Spectrogram view currently only works with the three specific spectral edit effects. These effects can also only be used while in Spectrogram view and require that Spectral Selection be checked "on" in either the Track Control Panel for the track or in Spectrogram Preferences. All other effects and for example cut or delete will act on the entire spectrum in the time range regardless of the spectral selection.
Sync-Locked Track Groups
- If Sync-Locked Track Groups are enabled but "Editing a clip can move other clips" in Tracks Preferences is disabled, sometimes not all sync-lock-selected tracks will be affected by Timeline-changing edits, and sometimes audio clips may be removed. You can Edit > Undo any unwanted changes.
- If you have unselected Spectrogram or Note (MIDI) tracks in a Sync-Locked Track Group and there is a selected time range, the Note or Spectrogram tracks may show only an indistinct "clocks" indication that they will be affected in that time range by an operation applied to other tracks in the Group.
- The lower and upper speed limits are not stored in the project, so will be restored to their default values of 90 and 110 respectively when reopening or recovering a project, or if removing a Time Track then undoing removal. Please make a note of the correct values before closing the project or the Time Track.
- Timer Record warns of insufficient disk space to save the recording as a project, but does not warn about sufficient space to export. If space is insufficient to export, you will get an error message and no exported file.
- (Mac) The Timer Record setup, "Waiting" and "Progress" dialogs may show the date in UK dd/mm/yy format even if the language in System Preferences is set to "US English". The exact behaviour may depend on the machine or version of OS X.
- (MacOS and Linux) If Timer Record is set to "Exit Audacity" after recording completes, a crash will be reported on exit. The project and/or audio file will be still be saved correctly.
- (Windows and MacOS) On a few machines, Timer Record may not respond to a request to stop the recording or may carry on recording past the scheduled end time. The Elapsed and Remaining Time counters may stop counting. In this case it will be necessary to force quit Audacity. On a few affected machines, the problem can be avoided if you leave focus on Audacity or ensure it has focus when recording is due to end.
- Timer Record cannot maintain scheduled duration if system clock changes
- When in either of the waveform views, vertical zoom in by left-clicking on the the vertical scale (or by using the Vertical Scale context menu "Zoom In" command) above the 0.5 level causes the scale to revert to normal vertical zoom level at the second click (rather than continuing to zoom in). Below the 0.5 level it continues to zoom in further with additional clicks. This is true whether in the upper vertical scale or lower vertical scale, i.e. above 0.5 or below -0.5.