All of lore.kernel.org
 help / color / mirror / Atom feed
From: Eliot Blennerhassett <linux@audioscience.com>
To: Raymond Yau <superquad.vortex2@gmail.com>
Cc: Takashi Iwai <tiwai@suse.de>,
	ALSA Development Mailing List <alsa-devel@alsa-project.org>
Subject: Re: Help wanted: emachines em350 internal mic
Date: Tue, 07 Dec 2010 16:11:59 +1300	[thread overview]
Message-ID: <4CFDA5FF.6060403@audioscience.com> (raw)
In-Reply-To: <AANLkTi=T_5nGv85YE8DcDvyF_HFouh7a-6tOmk58+8EO@mail.gmail.com>

Thanks Raymond,

On 03/12/10 15:33, Raymond Yau wrote:
>>> Greetings,
> 
> 
>>> There is only a single mic on this netbook. However, the alsa device
>>> shows up as stereo, and the right channel carries an inverted copy of
>>> the left channel.
> 
> http://git.alsa-project.org/?p=alsa-lib.git;a=commit;h=59c774ed5ee00e9623a204c3234191d6a6d8cf7a

Commitlog was "Add route_policy copy to HDA-Intel.conf for capture
Since some digital mics have the phase-inversion problem in one channel,
adding both channels for mono stream results in the noise. Use
route_policy copy to avoid that situation."

As far as I can guess, the commit helps when an application asks to
record mono from the stereo device, by copying L rather than summing L+R

My machine already has this, however it doesn't really fix the root of
the problem.

Because the internal mic appears as a stereo device, rather than a mono,
applications can open it as stereo.

Only later when the resulting signal L+R is sent to a mono output does
the signal "disappear".

So I'm back to wondering how to force an app (primarily PulseAudio) to
see the mic as mono?

(I think the external jack is also only mono, at least when used as a
mic input?)

>>> So when the two channels are summed to make a mono (e.g. for
>>> telephony, or playback on mono internal speaker) it appears that there
>>> is no signal.
> 
>>> Is there a way to "cure" this problem in the driver?  I can think of
>>> * Force internal mic capture to be mono (left only)
>>> * Copy left to right capture

Even in stereo mode!

>>> * Invert right capture
>>> but don't know how easy any are to implement.


-- 
Eliot Blennerhassett
AudioScience Inc.

  reply	other threads:[~2010-12-07  3:12 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-12-03  2:33 Help wanted: emachines em350 internal mic Raymond Yau
2010-12-07  3:11 ` Eliot Blennerhassett [this message]
2010-12-07  3:43   ` Raymond Yau
2010-12-07 16:12   ` Takashi Iwai
2010-12-08  4:13     ` Raymond Yau
2010-12-09 20:27     ` Eliot Blennerhassett
2010-12-08  7:12   ` Raymond Yau
  -- strict thread matches above, loose matches on Subject: below --
2010-11-30  6:56 Eliot Blennerhassett

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=4CFDA5FF.6060403@audioscience.com \
    --to=linux@audioscience.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=superquad.vortex2@gmail.com \
    --cc=tiwai@suse.de \
    /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.