From: Lee Revell <rlrevell@joe-job.com>
To: alsa-devel <alsa-devel@lists.sourceforge.net>
Subject: Device enumeration
Date: Fri, 09 Jun 2006 02:36:49 -0400 [thread overview]
Message-ID: <1149835010.3894.171.camel@mindpipe> (raw)
In order for apps to support ALSA properly there NEEDS to be a proper
device enumeration API! I was just looking at the OpenWengo site:
http://www.openwengo.org/index.php/openwengo/public/homePage/news?payload[newsId]=0
and it seems that their ALSA device selector only lists hw devices. IOW
it's no improvement over OSS.
Will this be fixed soon? I cannot see how we can ever expect apps to
support ALSA properly without it. There's currently a perception that
apps must be modified to "support dmix" when all that is really needed
is to have a device enumeration that will list the default device.
It cannot be a coincidence that 99% of the apps that try to support ALSA
get it wrong.
Lee
next reply other threads:[~2006-06-09 6:36 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-09 6:36 Lee Revell [this message]
-- strict thread matches above, loose matches on Subject: below --
2013-06-10 9:05 Device enumeration Robert Billing
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=1149835010.3894.171.camel@mindpipe \
--to=rlrevell@joe-job.com \
--cc=alsa-devel@lists.sourceforge.net \
/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