My microphone works everywhere perfectly but when it comes to audacity it can't detect anything, please help
Audacity cant recognize my microphone
Forum rules
This forum is for Audacity on Windows.
Please state which version of Windows you are using,
and the exact three-section version number of Audacity from "Help menu > About Audacity".
Audacity 1.2.x and 1.3.x are obsolete and no longer supported. If you still have those versions, please upgrade at https://www.audacityteam.org/download/.
The old forums for those versions are now closed, but you can still read the archives of the 1.2.x and 1.3.x forums.
Please state which version of Windows you are using,
and the exact three-section version number of Audacity from "Help menu > About Audacity".
Audacity 1.2.x and 1.3.x are obsolete and no longer supported. If you still have those versions, please upgrade at https://www.audacityteam.org/download/.
The old forums for those versions are now closed, but you can still read the archives of the 1.2.x and 1.3.x forums.
Audacity cant recognize my microphone
Last edited by steve on Fri Feb 19, 2021 2:31 pm, edited 1 time in total.
Reason: Replace broken link with image file
Reason: Replace broken link with image file
Re: Audacity cant recognize my microphone
Audacity can't see any audio devices connected to your computer. What audio devices do you have? (Please include any "virtual" devices)
Are you running any other audio apps (including any running in the background)?
Are you running any other audio apps (including any running in the background)?
9/10 questions are answered in the FREQUENTLY ASKED QUESTIONS (FAQ)
Re: Audacity cant recognize my microphone
Also, sometimes, when Audacity starts, it gets hung up by a single audio device that prevents it from "seeing" all of the rest of them. Frequently, when this occurs, the "problem" device is a Bluetooth or a USB port or device.
Sometimes, by disconnecting or disabling all of these devices then re-enabling them one-by-one it is possible to identify the "culprit". Re-booting might also change the situation.
I hope this helps.
Sometimes, by disconnecting or disabling all of these devices then re-enabling them one-by-one it is possible to identify the "culprit". Re-booting might also change the situation.
I hope this helps.