alsa-devel.alsa-project.org archive mirror
 help / color / mirror / Atom feed
From: Raymond Yau <superquad.vortex2@gmail.com>
To: ALSA Development Mailing List <alsa-devel@alsa-project.org>
Subject: Re: explicit commandline control of speakers vs headphone output
Date: Thu, 26 Aug 2010 06:48:34 +0800	[thread overview]
Message-ID: <AANLkTi=8tUSmD+h4oUODAWk7xU63Mb66FU_7N4OxgxFz@mail.gmail.com> (raw)
In-Reply-To: <858637.27362.qm@web50708.mail.re2.yahoo.com>

2010/8/26 Eric Holstege <eric_holstege@yahoo.com>

> It appears that when I have a headphone plugged in, the speakers are
> automatically disabled and the output sound is sent to the headphone.
>
> However, I want to explicitly control (e.g. via a script or commandline
> - not a GUI) whether the sound from an (arbitrary) application is going
> to the speakers or to the headphone even when the headphone is plugged in.
> (When I say "arbitrary application" that means I can't alter the code of
> the application itself).
>
> Is this possible?
>
> (I have heard that ALSA mutes the speakers when it detects plugged-in
> headphones. Is switching between them as simple as using e.g. amixer(1)
> to unmute the speakers and mute the headphones and vice versa, or is
> there more to it.)
>
>
>
it is really hardware dependent

Which on-board sound driver are you using ?

auto mute is a specific feature for notebook in old day

For the desktop,  the front panel audio connector of the AC97' chassis and
HDA chassis

http://www.intel.com/support/motherboards/desktop/sb/cs-015851.htm

For some HDA codec, the headphone (front panel green jack) can be used
indpendent of the rear panel jacks on desktop

  reply	other threads:[~2010-08-25 22:48 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-08-25 16:41 explicit commandline control of speakers vs headphone output Eric Holstege
2010-08-25 22:48 ` Raymond Yau [this message]
  -- strict thread matches above, loose matches on Subject: below --
2010-08-26 18:40 Eric Holstege
2010-08-27  6:26 ` Clemens Ladisch
2010-08-27 14:18 Eric Holstege
2010-08-27 16:48 ` Clemens Ladisch
2010-08-27 18:46 Eric Holstege
2010-08-27 19:26 ` David Henningsson
2010-08-27 23:26   ` Raymond Yau
2010-08-28  8:02 ` Raymond Yau
2010-08-27 19:49 Eric Holstege

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='AANLkTi=8tUSmD+h4oUODAWk7xU63Mb66FU_7N4OxgxFz@mail.gmail.com' \
    --to=superquad.vortex2@gmail.com \
    --cc=alsa-devel@alsa-project.org \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).