Known Issues

From Audacity Wiki
Revision as of 19:51, 15 January 2010 by Richardash1981 (talk | contribs) (add a section at the bottom of the page for library issues which need to remain around longer)
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 Issues at Release" 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 issues 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.10: Released 1 December 2009 for Windows (2000, XP, and Vista), Mac OS X and Linux, including provisional support for Windows 7

Active issues

  • 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.
  • Toolbar buttons cannot be clicked on by using ENTER on the keyboard. ENTER navigates to the next button instead.

Fixed since release

The following problems can be corrected by downloading one of our nightly development builds, or by compiling Audacity from our latest development code:

  • Exporting partial tracks (whether by File > Export Selection or File > Export Multiple) extends the exported track to the nearest 5 seconds.

Issues outside Audacity

These are bugs or known issues in the libraries used by Audacity, which will therefore tend to take longer to be fixed and propagate back into Audacity. This is particularly a problem for Linux users using distribution packages which lag behind the library releases.

  • (Linux) Audacity CPU consumption rises steadily when it is not being used If an Audacity window is left open and not being used (so it does not have focus) then it's CPU usage will slowly rise until (if left long enough) it uses all the available CPU. This is a bug in wxGTK 2.8.10 (not previous versions) which will be fixed in wxGTK 2.8.11 (not yet released). There is thus nothing that Audacity can do about the problem.
    • For Package Maintaners / Distributors: The upstream change in wxGTK is simple and can easily be patched into wxGTK 2.8.10 if desired: Grab the changeset, 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).