All of lore.kernel.org
 help / color / mirror / Atom feed
From: Takashi Iwai <tiwai@suse.de>
To: Tanu Kaskinen <tanuk@iki.fi>
Cc: alsa-devel@alsa-project.org, Clemens Ladisch <clemens@ladisch.de>
Subject: Re: Logical device name for 4-channel microphones?
Date: Tue, 24 Apr 2012 17:42:47 +0200	[thread overview]
Message-ID: <s5hty092l1k.wl%tiwai@suse.de> (raw)
In-Reply-To: <1335281294.4604.19.camel@laptop>

At Tue, 24 Apr 2012 18:28:14 +0300,
Tanu Kaskinen wrote:
> 
> On Tue, 2012-04-24 at 16:09 +0200, Takashi Iwai wrote:
> > At Tue, 24 Apr 2012 16:08:45 +0200,
> > Clemens Ladisch wrote:
> > > 
> > > Tanu Kaskinen wrote:
> > > > 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?
> > > 
> > > These device name are useful only for device types that are generic
> > > enough.  Four-channel microphones aren't.
> > 
> > Hm, we have already surround51 or such specific one, so it's not too
> > bad to have a definition for multi-channel mics.  OTOH, surround51 &
> > co were the possible cause of confusions, as there are way too many
> > surround types.  A generic type with the channels argument might be
> > more generic?
> > 
> > In anyway, I think it's fine to define some new generic name.
> 
> From Pulseaudio point of view using "hw" should be fine if you can
> guarantee that any current or future 4-channel mics can be opened in the
> 4-channel mode using the "hw:CARD" device name.

Such a thing can be never guaranteed with "hw" :)
The hw provides nothing but what kernel driver provides.  And the
hardware might be a link of two stereo streams.


Takashi

> I'm just worried that
> there might be cards that split the four channels to e.g. two stereo
> devices, "hw:CARD,0" and "hw:CARD,1", and then "hw:CARD" won't work. I
> might be mistaken, but aren't there some such cases with playback, which
> have to be opened with the "surround" device names to get all the
> channels?
> 
> The "surround" devices also guarantee some specific channel mapping,
> which may not match what "hw" uses, which is another reason to prefer
> "surround" over "hw", but I don't think this applies to input side.
> Therefore, the only possible problem that I can see with "hw" is that it
> might not provide all channels.
> 
> -- 
> Tanu
> 

  reply	other threads:[~2012-04-24 15:42 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-04-21 12:24 Logical device name for 4-channel microphones? Tanu Kaskinen
2012-04-24 14:08 ` Clemens Ladisch
2012-04-24 14:09   ` Takashi Iwai
2012-04-24 15:28     ` Tanu Kaskinen
2012-04-24 15:42       ` Takashi Iwai [this message]
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=s5hty092l1k.wl%tiwai@suse.de \
    --to=tiwai@suse.de \
    --cc=alsa-devel@alsa-project.org \
    --cc=clemens@ladisch.de \
    --cc=tanuk@iki.fi \
    /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.