|Think you've found a bug in Audacity? Having trouble getting it to work? This page describes how to report this to the development team in a way that will help us find and fix the problem as quickly as possible.
|We are no longer accepting bug reports for the Audacity 1.2 line. The 1.3 Beta line is being bug-fixed in order to release it as a new 2.0 version to replace 1.2.x. If the problem in 1.2 is irksome, please try the Beta instead.|
Here are examples of bad or useless bug reports that are likely to just be ignored:
|* "Audacity crashed! Please fix it."|
|* "Recording isn't working properly. I have done everything I can."|
|* "I can't hear anything"|
If you want your bug report to be useful to us, read on.
|1.||First, make sure your problem isn't merely an Audacity feature you haven't found yet! You can find immediate answers to many common questions on the on our main site, and on this Wiki. You can search for information on the from the Search box top right of any page, and you can search this Wiki from the search box at the left hand side of any page.|
|2.||Next, please check your problem isn't already known about. Check the Release Notes for the or Beta version of Audacity, plus the Known Issues page for known Beta issues reported since the last release. Some problems are entirely specific to particular operating systems, so please check our pages for known Windows, Mac and Linux/Unix problems. It's also possible issues may come up that haven't yet made it to the Frequently Asked Questions or the Wiki. So please search our Forum. If you're using the Beta version of Audacity and have a problem you didn't have in the stable version, narrow your search down to the Audacity 1.3.x (Beta) Forum. If you don't see your isssue, please register on the Forum and ask our active user community for help directly.|
|3.||If you've gone through the above steps without success, you may have found a bug we don't know about, so please tell us about it! Very often problems are only found and fixed when they are reported to us by users trying to do a particular task in Audacity. Please give us reports of possible bugs by sending an e-mail to our . Please note that we won't necessarily reply, unless we need more information from you, but all reports will be investigated. Please include all the following five pieces of information in your bug report, so our developers can deal with the problem effectively with the minimum of correspondence:|
|* The exact three-digit version of Audacity you are running for example 1.3.12. You can always find this by clicking in the program (or if you are on a Mac).|
|* If not downloaded from , where you obtained Audacity from - for example was it purchased from some other site, bundled on a CD with a hardware product, or obtained from the distributor of your Linux/Unix operating system?|
|* What operating system you are running including the exact version (for example Windows XP, Windows Vista, Mac OS X 10.4.8, Linux Ubuntu Feisty Fawn).|
|* What exactly you are trying to do (for example, import a WAV audio file, use an effect, or record from a microphone attached to a mixer).|
|* What is preventing you doing that, including the exact text of any error messages given. If Audacity is crashing or freezing, please give us exact steps which always reproduce the crash on your computer (for example, import an .aup Audacity Project file, then use the "Amplify" effect).|
The above information will give us a good bug report to go on.
If you can give us more information...
With 1.3.12 and later we have a couple of important bugs which only show very occasionally and which we are particularly keen to track down. If you see these, and are pretty familiar with Audacity, some additional information could really help us. Let us know if you think there is something else that might be relevant to the bug showing.
(Bug 35) Crash on importing audio: We've heard of this happening when importing WAV and AIFF files.
- What is the size of the file being imported in MB or GB?
- What is your project rate bottom left of the Audacity window?
- Did you copy in the WAV/AIFF or read it directly from source when Audacity asked (or how is this set in the Import / Export Preferences)?
- If you "read directly", were you interacting with the waveform whilst the audio was loading?
(Bug 137) Potential issues when reopening saved projects in Audacity 1.3.14. Not everyone will be affected, but we recommend exporting as WAV or AIFF for full safety before closing the project. Please help us if you see these issues so we can release a 2.0 stable version in the near future.
- Projects reopen with any of "Missing Audio Data Block File(s)", "Problems Reading Sequence Tags" or "Orphan Block File(s)" errors. Silenced audio may result.
- Projects reopen with silenced audio without warning. Various symptoms may be seen either after reopening the project, or may have already occurred when the project was last open. Please look out for these:
- Errors saving a project or the autosave file, suggesting the disk may be full or not writable when there is no such problem (if this happens, try exporting the audio as WAV)
- Unwanted renaming or moving of .au files within the project; multiple or duplicated .aup files or project folders appearing within the same project
- Unexplained crashes or corrupted audio.
Please let us know whenever you see the errors or symptoms listed above. Are there any steps you took when the project(s) were previously open that could enable us to reproduce the problem? We believe having multiple projects open at once, having projects open in file manager programs or having a long project with many tracks are among the causes. Also do you have an virus checker enabled, if so, what brand/type?
|Note: it is known that projects with more than 2^31 samples (just over 13.5 hours at 44100 Hz) will not re-open correctly. We don't need you to report this.|