All of lore.kernel.org
 help / color / mirror / Atom feed
From: Robert Hancock <hancockrwd@gmail.com>
To: komputes <komputes@gmail.com>
Cc: alsa-devel@alsa-project.org
Subject: Re: Requesting opinions and experiences concerning laptops and external microphones
Date: Wed, 03 Jun 2009 17:57:25 -0600	[thread overview]
Message-ID: <4A270DE5.5040309@gmail.com> (raw)
In-Reply-To: <4A26F0D9.8020506@gmail.com>

komputes wrote:
> I am trying to gather opinions and experiences from the ALSA developer
> community to understand what they expect to happen when they plug in an
> analog microphone into their laptops (which already has a built in mic).
> 
> I am looking for more of an official ALSA document which states how
> capture should change when an analogue microphone is plugged in; should
> it takeover from the internal microphone or not? Is there specification,
> standard, or "correct" behavior which is applied to this process?
> 
> If I am not mistaking, the computer can detect a signal/message when the
> jack goes in, right? The expected behavior when plugging in headphones
> is that the headphones are detected, the speakers are muted and the
> audio is channeled to the headphones. Is this not applicable to external
> microphone and the internal microphone as well?
> 
> -komputes

That rather depends on the how the audio controller works and the 
hardware capabilities. In some cases this might happen in hardware 
without the driver needing to do anything. Or it's possible the two 
inputs have separate ADCs, etc.

      reply	other threads:[~2009-06-03 23:57 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-03 21:53 Requesting opinions and experiences concerning laptops and external microphones komputes
2009-06-03 23:57 ` Robert Hancock [this message]

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=4A270DE5.5040309@gmail.com \
    --to=hancockrwd@gmail.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=komputes@gmail.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.