From: "Alexander E. Patrakov" <patrakov@gmail.com>
To: Shawn Starr <shawn.starr@rogers.com>
Cc: "alsa-devel@alsa-project.org" <alsa-devel@alsa-project.org>
Subject: Re: [Intel HDA][ALC3226] Too much white noise from microphone
Date: Fri, 06 Feb 2015 16:48:09 +0500 [thread overview]
Message-ID: <54D4A9F9.6090709@gmail.com> (raw)
In-Reply-To: <8841801.KiuVFG1hDJ@segfault>
05.02.2015 02:13, Shawn Starr wrote:
> Hello ALSA devs,
>
> I spoke to patrakov on Freenode from the #Alsa IRC channel and they mentioned that
> the noise background I am experiencing is not normal. I tried two different headsets,
> both headsets have two separate jacks, the same result.
>
> I will test any patches/quirks for kernel as needed.
>
> Here is the alsa-info:
>
> http://www.alsa-project.org/db/?f=29d3c45e2d66c58be03a10bd0186067a9d735a11
I am not an expert on Intel HDA cards, but... some microphones are picky
about the reference voltage supplied by the soundcard. You can change
this temporarily, for debugging purposes, with hda-analyzer. See general
instructions at
http://www.alsa-project.org/main/index.php/HDA_Analyzer
Note: it needs the "snd-hwdep" module loaded, and needs to be run as root.
In your case, you need to select Node[0x18] PIN in the left pane, and,
at the bottom of the right pane, select 50 or 100 instead of 80 in the
VREF box. See https://imgur.com/F84raSN for a screenshot based on your
alsa-info.
If this doesn't help, just click around randomly. Maybe you'll find the
magic checkbox that makes the noise go away and the voice stay :) - if
that happens, please email the resulting diff file that hda-analyzer
creates.
--
Alexander E. Patrakov
next prev parent reply other threads:[~2015-02-06 11:48 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-04 21:13 [Intel HDA][ALC3226] Too much white noise from microphone Shawn Starr
2015-02-06 11:48 ` Alexander E. Patrakov [this message]
2015-02-06 15:22 ` Shawn Starr
2015-02-06 15:34 ` Alexander E. Patrakov
2015-02-07 11:12 ` Harry van Haaren
2015-02-07 14:36 ` Alexander E. Patrakov
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=54D4A9F9.6090709@gmail.com \
--to=patrakov@gmail.com \
--cc=alsa-devel@alsa-project.org \
--cc=shawn.starr@rogers.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.