alsa-devel.alsa-project.org archive mirror
 help / color / mirror / Atom feed
From: Anssi Hannula <anssi.hannula@iki.fi>
To: Joerg-Cyril.Hoehle@t-systems.com
Cc: aeikum@codeweavers.com, alsa-devel@alsa-project.org
Subject: Re: how to enumerate useful ALSA devices?
Date: Thu, 05 Jan 2012 19:26:03 +0200	[thread overview]
Message-ID: <4F05DD2B.9080400@iki.fi> (raw)
In-Reply-To: <8E4C156DA5797D418DBFADFD8CE655A41782620646@HE113481.emea1.cds.t-internal.com>

On 05.01.2012 11:59, Joerg-Cyril.Hoehle@t-systems.com wrote:
> Andrew Eikum wrote:
>> I tried experimenting with snd_device_name_hint().
>> surround40:CARD=SB,DEV=0
>> surround41:CARD=SB,DEV=0
>> surround50:CARD=SB,DEV=0
>> surround51:CARD=SB,DEV=0
>> surround71:CARD=SB,DEV=0
> I'm not sure Wine should enumerate these.  How can it tell the difference
> so as to announce the correct channel mapping to applications?
> E.g. 41 vs 50, both 5 channels? Ideally, that should be announced as
> one device (as it really is), capable of supporting different formats,
> with one preferred format (perhaps the one with most channels) that GetMixFormat uses.

Yep, as noted I think it should just ignore "surroundXX" and "front" and
only announce the "default" ones (there will be multiple "default" ones
with different $CARD when there are multiple cards, except when
pulseaudio is in use in which case there is only one "default" which
goes to pulseaudio).

IIRC the "surroundXX" and "front" ones are just legacy stuff. Then
again, if that is the case, one'd except them to not have the hint tag
making them listed in "-L"...

> OTOH, I find it important that Wine announces a device capable of more
> than stereo if there's one in the system.


-- 
Anssi Hannula

  parent reply	other threads:[~2012-01-05 17:26 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-01-04 19:49 how to enumerate useful ALSA devices? Andrew Eikum
2012-01-04 20:47 ` Anssi Hannula
2012-01-04 21:04   ` Andrew Eikum
2012-01-04 21:16   ` Anssi Hannula
2012-01-05 23:06     ` Raymond Yau
2012-01-06  0:36       ` Anssi Hannula
2012-03-11  3:01         ` Raymond Yau
2012-01-05  5:35   ` Raymond Yau
2012-01-05  9:59 ` Joerg-Cyril.Hoehle
2012-01-05 13:30   ` Raymond Yau
2012-01-05 17:26   ` Anssi Hannula [this message]
  -- strict thread matches above, loose matches on Subject: below --
2011-12-21 14:37 Joerg-Cyril.Hoehle
2011-12-22  6:27 ` Raymond Yau

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=4F05DD2B.9080400@iki.fi \
    --to=anssi.hannula@iki.fi \
    --cc=Joerg-Cyril.Hoehle@t-systems.com \
    --cc=aeikum@codeweavers.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).