There are some accessibility bugs in the parts of Audacity that are accessible.
| Group
|
Description
|
| Accessibility
|
- (Windows, OS X) If you click in Device Toolbar then use a shortcut to Play or Record, you must click in the waveform or background before you can use any further shortcuts.
|
| Accessibility
|
- Many, but not all parts of the Audacity interface are accessible on Windows to those who can't use a mouse, and/or use a screen reader. For details, see:
http://manual.audacityteam.org/man/Accessibility
There are some accessibility bugs in the parts of Audacity that are accessible.
- Toolbar buttons cannot be operated by pressing either ENTER or Space: ENTER incorrectly moves to the next control and Space starts/stops playback. However the buttons can be operated either by using their shortcut keys, or for users of screen readers by using the Jaws cursor or equivalent. Note: it will be necessary to go to the Keyboard Preferences to set a shortcut for the Play-at-speed button.
- For users of screen readers, when the Silence Generator dialog opens, the duration control is incorrectly read as 0 seconds. However, if you tab round to the control again, the correct value is read.
- Some interface text or markings remain in black when using High Contrast light-on-dark themes, so cannot be read properly
- The yellow track focus border remains "on" even when toolbars or dialogs have focus.
|
| Accessibility
|
See issue 33.
|
| Accessibility
|
See issue 33.
|
| Accessibility
|
See issue 33.
|
| Compiling
|
- (Windows) Compilation with Visual Studio 2010 is not yet supported.
|
| Compiling
|
- The slv2 library needed for LV2 support does not build.
|
| Compiling
|
- When building Audacity from source, using system libraries (including system versions of portsmf, sbsms, libmad libvorbis and FFmpeg) may or may not work out depending on the exact versions. Similarly using Cygwin or MSVC 2010 will need extra work by you. To check the options and configurations we have successfully built with, visit this wiki page / join the developer list.
|
| Effects and Analysis
|
- (Windows) Processing of built-in effects may be somewhat slower than in previous versions of Audacity
|
| Effects and Analysis
|
- Cut Preview only plays the upper track of multiple selected or Sync-Locked tracks.
|
| Effects and Analysis
|
- LADSPA Multiband EQ may not be visible in Effect menu (occurs on Windows XP), and crashes soon after opening
|
| Effects and Analysis
|
- LADSPA effects not categorized, even though compiled with categorization data.
|
| Effects and Analysis
|
- Nyquist effects join separate clips together, and add spurious split lines if applied over clip boundaries
|
| Effects and Analysis
|
- Nyquist effects: in locales where comma acts as the decimal separator, entering a comma in a text box to left of a slider only produces the whole number before the comma. Workaround: use a dot (period) as the decimal separator
|
| Effects and Analysis
|
- The following effects remove envelope control points: Change Speed/Pitch/Tempo; Equalization; Noise Removal; Sliding Time Scale/Pitch Shift; any Nyquist effect in the Effect menu. Workaround: Use Tracks > Mix and Render to apply the envelope to the waveform before applying the effect. Reverse retains the control points, but does not move them.
|
| Effects and Analysis
|
- Truncate Silence does not adjust clip boundaries inside the selection being truncated.
|
| Effects and Analysis
|
- Truncate Silence doesn't work well on multiple tracks.
|
| Effects and Analysis
|
- Truncate Silence: The resultant silence after the effect is 1 ms less than that expected, unless the result was expected to be 1 ms.
|
| Effects and Analysis
|
- Truncate silence deletes audio when multiple clips in same track.
|
| Exports
|
- (Linux) Exports using "M4A (AAC) Files" are very slow irrespective of the AAC encoder FFmpeg is configured to use. Workaround: choose (external program) when exporting, entering an appropriate path and command (for example, /usr/bin/ffmpeg -i - "%f") to run FFmpeg using Audacity's command-line encoder.
|
| Exports
|
- (Linux) Files exported using the FFmpeg native encoder included with many system versions of FFmpeg are of very poor quality. This is an issue with the library itself. Workaround: When compiling FFmpeg, configure with the libfaac encoder thus: --disable-encoder=aac --enable-libfaac .
- Also mono AAC files import as stereo if FFmpeg uses the libfaad decoder. This is again an issue with the library itself.
|
| Exports
|
- (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.
|
| Exports
|
- (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.
|
| Exports
|
|
| Exports
|
- Custom FFmpeg Export dialogue does not respond to ENTER after clicking in the Formats or Codec selector.
|
| Exports
|
- 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
|
- Dither noise is incorrectly applied by default if exporting to WAV or AIFF PCM files having the same bit-depth as the project (for example, to 16-bit WAV from a 16-bit project). Workaround: Set "High Quality" dither to "None" in the Quality Preferences.
|
| Exports
|
- Metadata import/export, i.e. tags, album art etc, occasionally not consistent. What tags work and what tags don't may depend on both what program reads the tags and on what program added the tags.
|
| Exports
|
- Muting specific time-shifted mono tracks when exporting produces audio at wrong point on timeline in exported file if muted tracks are to left of unmuted.
|
| Exports
|
|
| Exports
|
- WAVEX (Microsoft) headers: GSM 6.10 files cannot be exported, and U-Law/A-Law files may not be playable.
|
| Exports
|
- 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
|
- 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
|
- Even if the file filter in the File Open or Import window is set to "FFmpeg-compatible files", native formats like WAV or MP3 still import using the native importer when using File > Recent Files, dragging in or opening from a file manager program.
|
| Imports
|
- If WAV/AIFF files are imported into a project using "Read Directly" import, there is no warning that the files must be retained with their original names and in their original location. Warnings are given when acting on the audio and exporting, but editing actions might not be warned. Also if exporting to the same file name and location as a file that is now missing, the export could be aborted or exported to some other location.
|
| Imports
|
- Occasionally unreliable importing of WAV and AIFF files
|
| Imports
|
- On-Demand WAV/AIFF import not available if using the optional FFmpeg importer (that is, if "FFmpeg-compatible files" set in the import dialogue).
|
| Installer
|
- (OS X 10.6.x) Administrative (and occasionally, root) permissions may be needed on some machines to install the optional LAME or FFmpeg libraries into /usr/local/lib/audacity. In case of difficulty, please download the zip version of FFmpeg 0.6.2 for Audacity and extract the files to your own preferred location.
|
| Interface
|
- (Linux) The OK button has focus on opening effects and other dialogs, instead of fields for changing values. This is a bug in wxGTK. To navigate the dialog, tab into it or click in it.
|
| Interface
|
- (Linux) Tracks that were selected on project save are deselected when re-opening the project.
|
| Interface
|
- (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
|
- (OS X and Linux) In some locales, Preferences text may be truncated or overlapped, or dropdown boxes truncated.
|
| Interface
|
- (OS X) The "Cmd - Wheel - Rotate" mouse binding does not zoom in unless you uncheck "Zoom using scroll ball while holding Command" at "Mouse and Keyboard" in the Mac System Preferences.
|
| Interface
|
- (Windows) On a few Windows XP or 2000 machines, the background of the Frequency Analysis graph is reported to be completely transparent, and new spectrum plots are drawn underneath previous plots.
|
| Interface
|
- (Windows) The "Files Missing" warning always restores maximised windows to smaller size.
|
| Interface
|
- (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
|
- Audacity has several weaknesses in preserving the context of the audio being worked with:
- If playback scrolls, pressing Stop leaves the waveform where it stopped and the cursor invisible. Pressing Play to resume then scrolls the waveform to start at the left edge, hiding the previously visible context before the cursor position
- Current scrolling behaviour makes it too hard to watch the waveform progress, with a single shift of cursor and waveform position when cursor reaches the right edge
- Zoom to Selection shows none of the surrounding context
|
| Interface
|
- Deleting a region starting at time zero which has been fitted to zero crossings will leave the first sample of the remaining audio behind time zero (left pointing arrows at edge of waveform), hence not exportable. Workaround: Use Time Shift Tool or Tracks > Align Tracks > Align with Zero to align the track correctly.
|
| Interface
|
- If you save a region with Edit > Save Region then click OK in Preferences, the saved region cannot be restored.
|
| Interface
|
- 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.
|
| Interface
|
- Menu items are often shown grayed out - when no audio is selected. We've reduced this by sometimes selecting all audio, if none is selected, but this is not yet as consistent as it could be.
|
| Interface
|
- Mouse Bindings are not currently configurable by the user.
|
| Interface
|
- Snap To state and Selection Format when Snap To is on are global. Therefore changing these in one project will make them show incorrectly in any other projects.
|
| Interface
|
- Snap-To does not move the cursor when first enabled or when the selection format is changed.
|
| Interface
|
- 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
|
- When changing language in Preferences, some elements in Unicode Release don't change until restart.
|
| Interface
|
- When exiting Audacity with multiple project windows open, the "Save changes?" prompt does not indicate which project is being closed.
|
| Label Tracks
|
- (Linux) In projects containing several hundred labels or more, Audacity will freeze on 100% CPU when opening the "Audacity Karaoke" window, and will freeze again while that window is open when editing a label or performing other actions on the project. Workaround: Open or place an empty label track above the one you want to use.
|
| Label Tracks
|
- Label tracks: typing "j" or"k" in a label track may activate the "move cursor" shortcut instead.
|
| Label Tracks
|
- Unless Tracks > Sync-Lock Tracks is on, pasting or inserting audio does not affect labels even if the label track is included in the selection.
|
| Mixer Board
|
- Meter range does not reflect a change in the dB range meter preferences until restart
|
| Moonphase
|
- (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.
|
| Moonphase
|
- Unreliable project re-opening due to duplicate attributes.
|
| Moonphase
|
- Wording under discussion on wiki.
|
| Platform Specific
|
- (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.
|
| Platform Specific
|
- (Mac) it is possible, by being quick, to get two imports (or exports) going at the same time. This can lead to a crash. Audacity attempts to prevent it, but is not doing so on Mac.
|
| Platform Specific
|
- (Linux) If pulseaudio is used as the audio device, repeatedly starting and stopping playback or recording in quick succession (or holding down the Play or Record button) may lead to a freeze. Workaround: bypass pulseaudio by setting the playback and recording device to an ALSA/hw choice in Device Toolbar.
|
| Playback and Recording
|
- (Linux) Audacity has some bugs and limitations interfacing with JACK. Patches to resolve the following will be welcomed:
- Recording/Playback ports for JACK are only opened on demand, so they exist during record and playback but disappear after pressing "Stop"
- Re-routing the default ports to/from JACK can only be done when Audacity is paused
- Clicking in the input meter to start monitoring will crash Audacity if it hasn't previously recorded from JACK in that session. Workaround: Record for a few seconds then Stop before monitoring.
|
| Playback and Recording
|
- (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 from pulse with software playthrough enabled. Workaround: record from an (hw) device instead if software playthrough is required.
|
| Playback and Recording
|
- (OS X) Playback to Bluetooth headsets gives an error. Workaround: Revert to Audacity 1.3.3, or use Soundlower (http://www.cycling74.com/products/soundflower) to send the Audacity output to an audio application that works with the headset.
|
| Playback and Recording
|
- (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.
|
| Playback and Recording
|
- (Windows XP) When a USB device is connected and the motherboard playback or recording device is selected, the Audacity input/output sliders may have no effect or the input selector may disappear. When the USB device is selected, the input/output sliders may move together or have no effect.
|
| Playback and Recording
|
- (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.
|
| Playback and Recording
|
- (Windows) Recording at 24-bit quality or higher isn't possible even with devices that support it due to current limitations in PortAudio.
|
| Playback and Recording
|
- (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.
|
| Playback and Recording
|
- (Windows) Timer Record may carry on recording past the scheduled end time resulting in Audacity having to be force quit.
|
| Playback and Recording
|
- Calculation of "disk space remains for recording (time)" incorrect when recording in 24 bit quality.
|
| Playback and Recording
|
- Changes in available devices not detected without restart
|
| Playback and Recording
|
- Mixer Board: (Linux) Meters may not respond immediately to playback which could cause them to report incorrect peak level or not display clipping.
|
| Playback and Recording
|
- 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
|
- Timer Record cannot maintain scheduled duration if system clock changes
|
