All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tanu Kaskinen <tanuk@iki.fi>
To: alsa-devel@alsa-project.org
Subject: Logical device name for 4-channel microphones?
Date: Sat, 21 Apr 2012 15:24:12 +0300	[thread overview]
Message-ID: <1335011052.2268.18.camel@laptop> (raw)

Hi,

What is the best source of information about device names ("front",
"surround40" etc)? Is it the DeviceNames wiki page[1]? That page was
slightly out of date, so I updated and expanded it (review would be
welcome).

I'm looking for information specifically about capture device names. The
wiki page didn't help me there, as it only listed playback device names.
My problem is that I'd like to make Pulseaudio handle 4-channel webcam
microphones[2], but I'm not aware of any input device names for
4-channel devices. Are there such device names? If not, what should be
done?

Pulseaudio could just use "hw", but I'd prefer there to be a standard
device name for 4-channel mics. AFAIK, at playback side, some surround
implementations are using multiple devices on one card, and using "hw"
wouldn't work in those cases, while e.g. "surround40" can use the
multiple devices behind the scenes. I would guess that the same could be
the case with some multichannel microphones, and therefore a logical
name like "fourchannelmic" would be better than using "hw".

[1] http://www.alsa-project.org/main/index.php/DeviceNames
[2] https://bugs.freedesktop.org/show_bug.cgi?id=45813

-- 
Tanu

             reply	other threads:[~2012-04-21 12:24 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-04-21 12:24 Tanu Kaskinen [this message]
2012-04-24 14:08 ` Logical device name for 4-channel microphones? Clemens Ladisch
2012-04-24 14:09   ` Takashi Iwai
2012-04-24 15:28     ` Tanu Kaskinen
2012-04-24 15:42       ` Takashi Iwai
2012-04-25 13:11     ` Tanu Kaskinen

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=1335011052.2268.18.camel@laptop \
    --to=tanuk@iki.fi \
    --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.