From: Raymond Yau <superquad.vortex2@gmail.com>
To: alsa-devel@alsa-project.org
Subject: Re: how to enumerate useful ALSA devices?
Date: Fri, 6 Jan 2012 07:06:45 +0800 [thread overview]
Message-ID: <CAN8ccibZTviHienALPBhzLT+a5Tmy+J60-Ds_3c0LmtKtfG2mA@mail.gmail.com> (raw)
In-Reply-To: <4F04C1CA.7070000@iki.fi>
2012/1/5, Anssi Hannula <anssi.hannula@iki.fi>:
> On 04.01.2012 22:47, Anssi Hannula wrote:
>> On 04.01.2012 21:49, Andrew Eikum wrote:
>
>>> So I'm really stuck here. Where am I supposed to get a list of devices
>>> that I can present to the user, including their Bluetooth devices and
>>> virtual devices from asound.conf?
>>
>> I guess the preferred one is 'snd_device_name_hint()', but I don't
>> really know if the caller is supposed to then handle surroundXX stuff
>> themself.
>
> Reading your last reply made me realize that I forgot that when
> pulseaudio is not configured, there is also the "default:CARD=foo"
> device listed (which you noticed), so I guess one could just ignore
> entries beginning with "front:" or "surround(40|41|50|51|71):", since
> one can just use "default" instead of them.
>
No , this won't work for emu10k1 and ca0106
snd-emu10k1 require "front", "surround40","surround51" and
"surround71" which use "multi" plugin of "front" , "rear" , "clfe" or
"side" devices
you can play stereo stream to "rear" device
next prev parent reply other threads:[~2012-01-05 23:06 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 [this message]
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
-- 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=CAN8ccibZTviHienALPBhzLT+a5Tmy+J60-Ds_3c0LmtKtfG2mA@mail.gmail.com \
--to=superquad.vortex2@gmail.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).