- 1 Why do I get "Error opening sound device"?
- 2 Why do I get "FFmpeg Error - Can't open audio codec 0x15002" (or 0x15003)?
- 3 Why does the computer reboot or show a blue screen message when I launch Audacity or play or record?
- 4 "I found a bug! now what?"
- 5 "Feature X is not good enough or is missing"
Why do I get "Error opening sound device"?
This error message asks you to check the recording or playback device settings and the Audacity project sample rate. If the message mentions "recording device", it means there's a problem with your Audacity, operating system or sound device recording settings. If the message mentions "playback device", it means there is a problem with your playback settings.
Either message can suggest a problem with the drivers of the sound device, or possibly that you are asking the device to do something it cannot do. For example you will see this error if you attempt to Record to more channels than your device supports, or if you try to overdub on a device that can either record or play back but not both.
The recording device message most commonly occurs on Windows when one of the sound device inputs is not properly enabled or otherwise cannot respond to Audacity's request to start recording.
For details of how to fix this please see Error opening sound device.
Why do I get "FFmpeg Error - Can't open audio codec 0x15002" (or 0x15003)?
Error 0x15002 occurs if you export more than a 2-channel M4A file (such as a 5.1 surround sound file), using the "M4A (AAC) Files (FFmpeg)" export choice. To correct the error and export up to 8 channels, choose (external application) and specify a command that tells Audacity to explicitly use the native FFmpeg AAC encoder.
Error 0x15003 occurs if you export more than a 6-channel AC3 file. Six channels is the maximum possible for AC3.
Why does the computer reboot or show a blue screen message when I launch Audacity or play or record?
This mostly affects Windows computers. It happens when your computer sound device has a bad or mismatched driver or there is a problem with a system driver that interacts with that sound device. Even if the problem occurs after updating to the latest Audacity version, it still is not Audacity's direct fault because Audacity does not have kernel privileges to make the computer restart. Inappropriate drivers can also cause Audacity to crash during playback or recording, without necessarily crashing the computer.
The best practice is to make sure the computer's built-in sound device has the latest drivers for your operating system, supplied by the motherboard or computer manufacturer. For a PCI or external soundcard, obtain the latest drivers and firmware supplied by the manufacturer of the device. See Updating Sound Device Drivers on the Wiki for help with correcting driver issues. If playback or recording worked previously, but the sound device drivers are appropriate or cannot be changed to a version that prevents the problem, try Windows System Restore to revert the computer to a state before the problem occurred.
If necessary the exact driver or module causing a computer crash can be pinpointed on Windows by examining the memory dump made when the crash occurred. You can find the dump by right-clicking over WhoCrashed is a Windows tool that makes it easy to identify the driver or module at fault. Another good idea is to test the computer's memory for errors (see help for Windows and Mac). Faulty memory can sometimes cause computer freezes or crashes.or , then click the "Advanced" link or tab, and under "Startup and Recovery", choose "Settings...".
If your best available soundcard drivers prove to be incompatible with current Audacity, we may not be able to take any direct action, but do let us know:
- the exact make and model number of the sound device
- the exact driver and firmware model numbers
- the exact operating system you are using, including the Service Pack if you are on Windows.
"I found a bug! now what?"
The most important things when reporting a bug are to be as specific as possible and check first in the Release Notes if we already know about the problem.
If the bug is not known about, please give us enough information that we can reproduce the bug ourselves on the correct operating system. Otherwise it's unlikely that we'll be able to fix it.
If you can make the problem happen consistently, tell us the exact sequence of events, step-by-step from launch of Audacity that causes the bug to occur.
If you see an error message, be sure to send us the exact text of the error message, or attach an image. If you are on Mac or Linux a crash report is useful too.
When you have your bug report ready, please email our feedback address.
"Feature X is not good enough or is missing"
You can also send your ideas for new or improved features to our feedback address. Again, be as specific as possible, and feel free to suggest your preferred way of achieving the functionality you desire. If you are a regular visitor to our Forum, you can instead post your suggestions on the Adding Features to Audacity board.
Thanks for all your reports, suggestions and patches! All of these help us make Audacity better.