Known Issues

From Audacity Wiki
Revision as of 16:44, 17 May 2008 by Richardash1981 (talk | contribs) (Active issues: problem with project rate (to do with other hacking no doubt))
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.
For all current source code changes made since 1.3.5 release, see Changes since 1.3.5.

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.5: Released 08 May 2008 for Windows, Mac OS X and Linux

Active issues

All platforms

  • Keyboard shortcuts don't work when the focus is in any of the Selection Bar spinboxes or the project rate list. So for example if you are playing a track, click in the Selection Start spinbox, change the start time then double spacebar to stop and restart from the new time, the track just goes on playing.
Status: Will be investigated, but a fix in time for 1.3.6 Release at the end of May cannot be guaranteed.
  • (Linux only?)Project rate set incorrectly at start-up. When audacity is started or a new project is opened, the project rate list-box shows the default sample rate set in the preferences. However, any new tracks created by recording or generating tones will be created at a sample rate of 8 kHz. This continues until the project rate is set by the user, whereupon everything works as expected (new tracks are created at the project rate).

Cleared in CVS

These problems 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