From: David Henningsson <david.henningsson@canonical.com>
To: ALSA Development Mailing List <alsa-devel@alsa-project.org>
Subject: Expected behaviour for two mic jacks
Date: Fri, 12 Nov 2010 10:50:19 +0100 [thread overview]
Message-ID: <4CDD0DDB.9020509@canonical.com> (raw)
Hi,
A while ago I asked for the default/expected behaviour for auto-mute.
Here's the same question for mics:
If there are two mic jacks, e g one on the front and one on the back, is
the standard/default behaviour that we should:
1) Show one mic only and add auto-switch functionality, and if so, what
should determine which mic takes precedence?
2) Show both mics and let the user choose between them?
3) Show both mics, two volume control and let the user mix both signals
together (when possible)?
--
David Henningsson, Canonical Ltd.
http://launchpad.net/~diwic
next reply other threads:[~2010-11-12 9:50 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-12 9:50 David Henningsson [this message]
2010-11-14 1:01 ` Expected behaviour for two mic jacks Raymond Yau
2010-11-14 16:14 ` Colin Guthrie
2010-11-30 4:15 ` Raymond Yau
2010-11-16 1:52 ` Raymond Yau
2010-11-16 11:03 ` Colin Guthrie
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=4CDD0DDB.9020509@canonical.com \
--to=david.henningsson@canonical.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).