Low USB microphone recording volume (AT2020)

Anonymous
2013-01-12T10:07:02+00:00

I've been using an AT2020 USB microphone for several years now, first on Vista and then on Windows 7, with no problems at all. After upgrading to Windows 8, I've found that the recording volume using this microphone is now very low. The hardware is all the same, as is all the configuration.

I usually have the volume set at ~30-40. On Windows 7 it's loud and clear, and there is no distortion. On Windows 8, even if I turn it all the way up to 100, the recording volume is way too low and the sound is distorted due to the volume being set so high.

There is clearly something wrong here and as of now Windows 8 is completely unusable to me because I need to be able to record. Any possible solutions would be very much appreciated.

Thank you.

(Also, there are no actual drivers for this device. I've always just plugged it in and it has worked right away.)

--

Update (7/29/15): This issue has not been fixed with Windows 10. I've started a new thread here for those who have updated. If you want this fixed, please continue to post about it. I doubt it will help, but the only other option is to stick with W7 or buy a new mic.

Windows for home | Previous Windows versions | Devices and drivers

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments

89 answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. Anonymous
    2015-03-29T04:52:47+00:00

    Ok now, as this thread is still going on (since 1-2 years or something) I thought I'd give it a shot....

    I recently wanted to purchase the AT2020 in order to do some recordings. I'm currently running Windows 8.1. My question is very simple and direct: Should I go for it, and buy the Mic hoping Windows 10 magically fixes this, or should I go a completly different route?

    On this subject.... Is there any "fix" to this problem yet? Running compatibility mode won't help, right?

    Any input is gladly appreciated!

    Was this answer helpful?

    0 comments
  2. Anonymous
    2015-03-26T17:20:04+00:00

    Hi,

    Sorry for the delay in replying.

    As Windows 10 Technical Preview is still in developmental stage, you may expect some compatibility issues as of now and some features or settings might not work as expected.

    As the issue persists in Windows 10 Technical Preview, I recommend you to leave your findings, comments and feedback related to this product using the “Feedback app”.

    Members of the Windows Insider Program can provide feedback about the Tech Preview directly to our engineers by using the Windows Feedback app.

    Refer to this article by “Nirmal S” to know more on “How to share feedback on Windows 10 Technical Preview?” : http://answers.microsoft.com/en-us/windows/forum/windows\_tp-winipp/how-to-share-feedback-on-windows-10-technical/5e501781-a580-43e3-8926-40ae19343805

    Cheers.

    Was this answer helpful?

    0 comments
  3. Anonymous
    2015-03-22T17:10:13+00:00

    I'm using a completely clean install of build 10041 on another hard drive in the same computer.  The Issue is completely unchanged from my Windows 8 installation.  The speech recognition prompt in both operating systems sets the level of my microphone to 100, which is barely audible in recordings.

    Was this answer helpful?

    0 comments
  4. Anonymous
    2015-03-22T13:22:03+00:00

    Hi Asonenine,

    You might know that Windows 10 Technical Preview has a latest build update released recently. I encourage you to install Windows 10 Technical Preview on a separate partition and check the status of the issue.

    Windows 10 Technical Preview Build 10041 now available: http://blogs.windows.com/bloggingwindows/2015/03/18/windows-10-technical-preview-build-10041-now-available/

    Keep us informed to help you further.

    Was this answer helpful?

    0 comments
  5. Anonymous
    2015-03-22T03:44:22+00:00

    Figured as much. Mostly was just putting out a semi-PSA about it to anyone hoping for a fix with the next Windows release. It's still too early to rule that out entirely, but it's certainly not encouraging that this is an issue they've known about for years and don't feel compelled to address even this late in the development cycle.

    Was this answer helpful?

    0 comments