Error opening sound device
There are three forms of this message
- Error opening recording device - Error code -xxxx this means there is a problem with your Audacity, operating system or sound device recording settings, where xxxx is replaced by a numeric code.
- Error opening recording device - Error code -xxxx this means there is a problem with your playback settings, where xxxx is replaced by a numeric code.
- Error opening sound device ... this is a generic message that is usually associated with a failure to start the audio stream.
These messages 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.
See the Numeric error codes section for details of the particular codes.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.
- Microphone and input device problems
- Check Audacity settings
- Check sound device drivers and firmware
- Check sound device drivers and firmware
- Check PCI card or external sound device settings and connections
- Windows WASAPI: Recording from a USB device
- Numeric error codes
Microphone and input device problems
For some users Windows 10 is now blocking Audacity from using the microphone, on the basis of privacy settings.
After upgrading to version 1803 of Windows 10 (April 2018), a small number of users have been reporting that the microphone is getting detected, but it does not pick up any sound.
In order to get around this issue, Microsoft recommends that you need to enable the microphone in your Privacy settings using these steps:
- Open Settings
- Click on Privacy
- Click on Microphone
- Turn on the Allow apps to access your microphone toggle switch.
See this Microsoft website for more details.
A problem of no recording level in Audacity is occurring quite frequently on Mojave, Catalina and later, due to Apple changing the Privacy settings for recording devices (making it more conservative, "safer"). Note that, although macOS refers to this setting as Microphone, it applies to all recording devices, including external USB / Thunderbolt interfaces.
To fix this problem:
- On your Mac, choose then click in the left-hand menu and the click the Privacy tab.
- Click in the left-hand menu.
- Select the checkbox next to an application (Audacity) to allow it to access the microphone.
Check Audacity settings
- Set the project rate bottom left of the Audacity window to the standard rate of 44,100 Hz (or if your audio interface only supports a particular rate such as 48,000 Hz, set the project rate to that). should show the rates the device claims to support.
- Try turning off recording computer playback). (this should never be enabled if
- Try turning off Updating Sound Device Drivers and Managing Computer Resources and Drivers for advice on how to make your sound device or computer more capable. because recording while playing could stress your sound device or computer. If this solves the problem, read the Wiki pages
- Check in Device Toolbar that the playback and recording devices are correctly and explicitly selected.
- On Windows, do not choose "Microsoft Sound Mapper" or "Primary Sound Driver" which point to the current Windows default device; choose the required device by name. Try selecting "Windows DirectSound" as the "Host" instead of "MME".
Check operating system settings
- Windows: Follow the instructions for Windows to access and configure the Windows Sound settings. The key points are:
- Ensure all available inputs are listed and enabled in the Windows Sound dialog.
- Additionally for Windows: Ensure Default Format for the playback and recording devices contains the same sample rate and number of recording channels as in Audacity.
- Very rarely, it can help to use 16-bit or 24-bit Default Format then change the Audacity Quality Preferences to that sample format.
- If necessary, put a checkmark in both Exclusive Mode boxes then set the "Host" in Audacity's Device Toolbar to "Windows DirectSound" and choose a project rate that your playback and recording devices support. Audacity can then request that rate directly from the sound device.
- Mac: In Finder, choose sample rate, bit-depth and number of recording channels as in Audacity. . In "Audio Devices", select in turn the required Recording and Playback devices. Set "Format" to the same
- In the first instance, try refreshing Audacity's list of audio devices at Device Toolbar. If the error still occurs, recheck the Audacity settings. then select the default option in
- It is possible that another application may have exclusive access to the audio device. Try logging out and back in again, then re-check the Audacity settings before opening any other application that may use the audio device.
- If pulse is an option in Device Toolbar, ensure that you have Pulse Audio Volume Control (pavucontrol) installed. If it is not installed, use your system's package manager to install it. Open Pulse Audio Volume Control and check that there is an available output device.
- If Jack Audio System is running on the computer, ensure that it is selected as the Host in Device Toolbar.
- Open the system Sound Preferences and check that a recording device is available. Sound Preferences is often available through a loudspeaker icon on the Desktop, Desktop panel, or in the system Preferences menu.
- Open AlsaMixer (type alsamixer in a terminal window) and check the audio interface and recording device settings. To view the AlsaMixer manual, type man alsamixer in a terminal window.
Check sound device drivers and firmware
The computer's built-in sound device should usually have the latest drivers for your operating system, supplied by the motherboard or computer manufacturer. A PCI or external sound card should usually have 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.
Check PCI card or external sound device settings and connections
If you use a high-end PCI sound card or external USB or FireWire interface, you must make the sample rate, bit-depth and number of input channels the same in all possible places. This is especially important if you are recording Multi-Track Overdubs where you play and record at the same time. Settings must match in:
- the Audacity Project Rate
- the track(s) in Audacity (to resample tracks to the Project Rate, select each track in turn then choose ).
- all inputs and outputs in the operating system sound control panel or application
- all inputs and outputs in any software or hardware control panel the sound device may have.
Windows WASAPI: Recording from a USB device
- Use MME or Windows DirectSound as your Audio Host
- Use your USB device for both input and output (not possible if recording from a USB turntable or USB tapedeck)
Numeric error codes
- -9996 Invalid device: this means that the sound device is not valid, if it is an external sound device:
- it may have been unplugged
- you may have a faulty or loose connection
- you may have a bad lead
- the device itself may be faulty.
- -9997 Invalid sample rate: make sure that you have matched the sample rate in Audacity with that set on your device - both for playback and recording.
- -9999 Unanticipated host error: this means means "something is wrong". And appears to most often be due to either: