Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Learn about causes and fixes for this error.
This error indicates a problem with the hardware used for playback, whether it is permissions, drivers, connections, or if you ask the device to do something it cannot do. You can attempt the following steps to resolve it.
Common troubleshooting stepsIf the troubleshooting steps aren't working for you, feel free to ask in our communities:
Learn about causes and fixes for this error.
This error occurs if you try to record an unsupported number of channels.
Go to Audio Setup -> Recording channels and choose a different number of channels. Values which typically work are 1 (mono), 2 (stereo), and the highest number presented on the list. So for a 8 channel interface, 8 should work.
Learn about causes and fixes for this error.
This error can indicate an unsupported sample rate.
This error can also occur when using Audacity on Windows to record a track while listening another existing track (also known as overdubbing) with Windows WASAPI as the Host if the sample rate of the recording device is different than the sample rate of the playback device.
This error can also occur when you are trying to record a number of channels that is not supported in the current configuration.
Double-check that both your OS settings and the Audacity project rate are set to a supported sample rate (usually 44100 Hz or 48000 Hz).
Use a different audio host. Sometimes WASAPI works when MME doesn't, sometimes it's the other way round.
Use a different number of channels. For example, some Realtek only work when recording in Mono, while some others only work in Stereo when recording a (loopback) stream.
Use the same playback device that you use as a recording device, especially when recording desktop audio.
Your device is unable to playback other tracks while recording.
This most commonly happens if you're trying to record at a different sample rate than the device's playback rate. Making sure the sample rate matches in both the Windows Settings and Audacity's Audio Setup -> Audio Settings may fix this.
Turning off Overdub via Transport -> Transport Options may fix this.
You can try the Common troubleshooting steps, or attempt any of the other workarounds of this page.
The device itself is faulty or not a real audio device.
This error can also occur when you are trying to record a number of channels that is not supported in the current configuration.
This error can also occur when using Audacity on Windows with Windows WASAPI as the Host if the selected recording device is being used exclusively by another application. Some applications that could make use of the recording device exclusively are ASIO4ALL, Voicemod (when configured to do so) or Voicemeeter (when configured to do so).
You can attempt to fix this issue with the following methods:
Use a different USB port and USB cable. This will resolve the issue if the fault was in the cable.
Use a different audio host. Sometimes WASAPI works when MME doesn't, sometimes it's the other way round.
Use a different number of channels. For example, some Realtek only work when recording in Mono, while some others only work in Stereo when recording a (loopback) stream.
Modules which handle importing of the file may be missing or disabled.
The file themselves may misreport their contents (for example: Say they're .mp3 despite being actually .m4a), or be corrupted.
You may have set custom import rules.
You can attempt the following things to fix it:
Install FFMPEG. FFMPEG allows you to open most kinds of media files. Read more: Installing FFmpeg
Check Preferences -> Modules. You should see several modules called something like "mod-mp3" or "mod-pcm", all of which should be set to "enabled", or, in the case of "mod-script-pipe", to "no choice made". If you are missing modules, reinstall Audacity, and reset the preferences.
Check if the file you're trying to open actually is what it says on the tin. For example, some lower-quality programs name any audio file *.mp3, regardless of whether it actually is an MP3 file. Read more:
Check if your file is an actual audio file. Some files which are used to output audio in certain programs don't actually contain sound themselves, but are instructions for for the program to make some sounds. Try to see if the program used to create the file has an export button. If not, you can also try recording desktop audio while playing back the file in another program. Read more:
Check if you have accidentally created custom import rules. In Edit -> Preferences -> Extended Import (on macOS: Audacity -> Preferences -> Extended Import), make sure that you have not created any custom rules. If there are any rules, you can safely delete the rules.
Import the audio as RAW. This only works on uncompressed audio. You can do so via File -> Import -> Import raw data...
Learn about causes and fixes for this error.
This error indicates a problem with the hardware used for recording, whether it is permissions, drivers, connections, or if you ask the device to do something it cannot do.
You can attempt the common troubleshooting steps to attempt to resolve it
If these troubleshooting steps aren't working for you, feel free to ask in our communities:
Learn about causes and fixes for this error.
This is caused by an unexpected system state. Specifically, macOS typically allows allocation of 32 instances of shared memory, out of which Audacity requires one to start. However, other apps on your computer may have filled up these allocations, in which case Audacity cannot start.
Rebooting the computer generally resolves it as it clears the shared memory.
You also can edit the macOS kernel to allow for more shared memory, but this is a very technical process. Essentially, various shared memory limits need to be increased. (Catalina) or (Sonoma) may have further instructions.
If the troubleshooting steps aren't working for you, feel free to ask in our communities:
Learn about causes and fixes for this error.
Error code 101
These errors may occur when the project you're trying to open is in a read-only location.
These errors may also occur when attempting to load a damaged .aup3 project file.
Make sure Audacity has write access to the folder the file is located in, or move the project file to a different location.
If your project is damaged, you can also try project recovery.
This page lists Audacity error codes and provides some troubleshooting steps on how to fix them.
The setup program may return one of the following exit codes:
0
Setup was successfully run to completion or the /HELP or /? command line parameter was used.
1
Setup failed to initialize.
2
The user clicked Cancel in the wizard before the actual installation started, or chose “No” on the opening “This will install…” message box.
3
Before returning an exit code of 1, 3 or 4 an error message explaining the problem will normally be displayed.
Future versions may return additional exit codes, so applications checking the exit code should be programmed to handle unexpected exit codes gracefully. Any non-zero exit code indicates that Setup was not run to completion.
A fatal error occurred while preparing to move to the next installation phase (for example, from displaying the pre-installation wizard pages to the actual installation process). This should never happen except under the most unusual of circumstances, such as running out of memory or Windows resources.
4
A fatal error occurred during the actual installation process.
Note: Errors that cause an Abort-Retry-Ignore box to be displayed are not fatal errors. If the user chooses Abort at such a message box, exit code 5 will be returned.
5
The user clicked Cancel during the actual installation process, or chose Abort at an Abort-Retry-Ignore box.
6
The Setup process was forcefully terminated by the debugger (Run | Terminate was used in the Compiler IDE).
Learn about causes and fixes for this error.
This is caused by missing realtime effects.
You can replace any missing effects from the effects sidebar.
Before opening a project on a new computer, ensure that all plugins you've used are in the same location as where they would've been in your old computer.
If the troubleshooting steps aren't working for you, feel free to ask in our communities:
Learn about causes and fixes for this error.
If you are on a low-end machine, this may be caused by insufficient resources, specifically memory.
This also can happen if you assign yourself a static IP in the hosts file.
Try closing other programs or restarting your computer to clear up memory.
If you're using static IP assignments in the hosts file, simply commenting out the assignment may solve this.
If the troubleshooting steps aren't working for you, feel free to ask in our communities: