From: Colin Guthrie <gmane@colin.guthr.ie>
To: alsa-devel@alsa-project.org
Subject: Adding a "capture" device naming scheme
Date: Tue, 11 Jan 2011 18:40:01 +0000 [thread overview]
Message-ID: <igi861$q8o$1@dough.gmane.org> (raw)
Hi,
As has been pointed out a few times, it's incorrect to use "front:" for
capture, but can we have an official name/wrapper (I'm unsure of the
terminology here) for this so we don't use hw: for recording?
I'd be in favour of "capture:" or "input:" as these both seem quite
logical and easy to understand.
It would be used thusly:
arecord -f S16_LE -c 2 -D capture:CARD=Intel
as opposed to the incorrect:
arecord -f S16_LE -c 2 -D front:CARD=Intel
or the low level:
arecord -f S16_LE -c 2 -D hw:CARD=Intel
Keeping it wrapped up allows for e.g. softvol or other things to be
plugged in as appropriate in the config and thus future proofs things a
little.
If someone could point me roughly in the right direction I'll make a
patch. I suspect it'll be easy enough to cook up the relevant config
needed (and I suspect it's just config rather than code that needs
patched, but I could be wrong).
It would be nice to get this into a release (alsa-lib?) soon so that it
can propigate and we can require it.
Cheers
Col
--
Colin Guthrie
gmane(at)colin.guthr.ie
http://colin.guthr.ie/
Day Job:
Tribalogic Limited [http://www.tribalogic.net/]
Open Source:
Mageia Contributor [http://www.mageia.org/]
PulseAudio Hacker [http://www.pulseaudio.org/]
Trac Hacker [http://trac.edgewall.org/]
next reply other threads:[~2011-01-11 18:40 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-11 18:40 Colin Guthrie [this message]
2011-01-12 1:08 ` Adding a "capture" device naming scheme Raymond Yau
2011-01-12 6:53 ` Takashi Iwai
2011-01-12 8:38 ` Raymond Yau
2011-01-12 9:04 ` Colin Guthrie
2011-01-12 9:10 ` Colin Guthrie
2011-01-12 9:17 ` Jaroslav Kysela
2011-01-12 11:12 ` Colin Guthrie
2011-01-12 17:00 ` Takashi Iwai
2011-01-12 8:53 ` Raymond Yau
2011-01-12 9:04 ` 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='igi861$q8o$1@dough.gmane.org' \
--to=gmane@colin.guthr.ie \
--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 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.