Known Issues

From Audacity Wiki
Revision as of 19:08, 15 December 2007 by Richardash1981 (talk | contribs) (All platforms: added note of problem with disabled libraries builds)
Jump to: navigation, search

This page contains details of Audacity problems that are identified after a version has been released, and so are not included in the "Known Problems" section of the Release Notes for current stable  and Beta versions. This page will be cleared after each release of Audacity, as all issues will by then either be fixed or appear as known problems in the Release Notes for the new version.

Please do not use this page to report problems you are having with Audacity or suspected bugs, as it will not be regularly checked by the support team. Instead, please see our Reporting Bugs page for advice on how to identify your problem and report it to us if you need to.

Audacity 1.3.4: Released 13 November 2007 for Windows and Linux only

Active issues

All platforms

  • Some strings are not translated in the interface, although translations exist in the language files.
Status: being worked on, fixes will appear in the next Beta release. Note that Beta versions of Audacity will always have incomplete translations to some extent or another - only stable releases have a "string freeze" and translation cycle.
  • With foreign languages (at least French and German) selected, MP3 metadata tags for "Artist Name", "Track Title", "Album Title" and "Track Number" are not filled, so not seen by media applications. Instead, duplicated custom tags with these identifiers are created.
Status: awaiting further investigation. Possibly some strings are marked for translation but used as keys.
  • Opening project files created by Audacity 1.0.0 no longer shows any warning that doing so may corrupt the file, but only converts the project to the new format and creates a backup.
Status: awaiting investigation
  • Playback of a file restarts if a second file is opened during play. Pressing Play (but not spacebar) in a second project when another is already playing stops playback of the first project.
Status: under investigation - possible fix identified.
  • Nyquist generate plug-ins (such as Click Track and Pluck) only generate the correct length with a Project Rate of 44100 Hz, with proportionately incorrect results for other rates. Workround: Use "Set Rate" on the Track Pop-Down Menu to select 44100 Hz, then Tracks > Resample and enter the current Project Rate.
Status: awaiting investigation
  • If ownership of Audacity's temporary directory is changed before running the program, a freeze occurs after stopping recording. Additionally, the ability to change ownership of the temporary directory creates a potential security risk that could be exploited by malicious local users.
Status: under investigation

Windows only

  • "Welcome" screen cannot be read by some screen readers, in particular JAWS and NVDA.
Status: awaiting investigation

Cleared in CVS

These items have been cleared in the latest development code , meaning that if you compile Audacity yourself from that code, these issues should not occur. Where applicable, they will still be present in the released binary versions available on our download page .

All platforms

  • Links in the Welcome Message and other dialogues such as the LAME download button do not open correctly in many platform / browser combinations.
  • The Stereo-To-Mono effect corrupts the Audacity internal project structure, and so results in a crash shortly after it is used.
  • Trying to build with MP3 or Ogg importing disabled fails with a compile error. This patch fixes it (thanks to Gentoo) and is now in CVS.

Linux Only

  • The audacity.1  man page is out of date, and contains several factual errors.