From: Takashi Iwai <tiwai@suse.de>
To: Paul Davis <pbd@op.net>
Cc: Joshua Haberman <joshua@haberman.com>, alsa-devel@lists.sourceforge.net
Subject: Re: PCM API questions
Date: Mon, 24 Jun 2002 18:13:51 +0200 [thread overview]
Message-ID: <s5hptyg7iyo.wl@alsa2.suse.de> (raw)
In-Reply-To: <200206241415.g5OEFkf09744@post2.fast.net>
At Mon, 24 Jun 2002 10:17:08 -0400,
Paul Davis wrote:
>
> >the names above are not defined on all cards (except for default).
> >i think we need a kind of config database for each card.
> >this is useful not only for pcm but also for parsing the mixer
> >structure.
>
> i think this is the wrong solution. i believe the correct solution is
> to provide a **simple** way to get every defined PCM device name.
>
> a config database for cards doesn't cover multi devices, or channel
> subsets, or share devices, etc. etc.
that's right. (but i think it's not a bad idea to put something more
descriptive for each pcm device which is card-specific.)
regarding to the device listing:
afaik, you can look up all pcm devices by calling
snd_config_search(config, "PCM", &conf)
and then run snd_config_for_each()... ah, not SIMPLE as you wrote.
so, making a list of pcm names would be relatively easy. we can add a
new function to alsa-lib.
but arising problem is that this will list up all possible
definitions. that is, it will include the standard pcm names with
arguments such as hw or plughw. it's not bad (you can use them even
without arguments) but maybe confusing.
anyway it would be nice to add a "description" entry for each
definition in the config, so that it will appear on the list more
intuitively.
Takashi
-------------------------------------------------------
Sponsored by:
ThinkGeek at http://www.ThinkGeek.com/
next prev parent reply other threads:[~2002-06-24 16:13 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-06-23 3:41 PCM API questions Joshua Haberman
2002-06-24 12:39 ` Takashi Iwai
2002-06-24 12:49 ` Paul Davis
2002-06-24 13:01 ` Takashi Iwai
2002-06-24 14:17 ` Paul Davis
2002-06-24 15:18 ` Fred Gleason
2002-06-24 16:13 ` Takashi Iwai [this message]
2002-06-24 16:57 ` Joshua Haberman
2002-06-24 21:14 ` Paul Davis
2002-06-25 1:12 ` Jaroslav Kysela
2002-06-25 6:04 ` Joshua Haberman
2002-06-25 13:53 ` Jaroslav Kysela
2002-06-25 7:11 ` Joshua Haberman
2002-06-25 10:36 ` Takashi Iwai
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=s5hptyg7iyo.wl@alsa2.suse.de \
--to=tiwai@suse.de \
--cc=alsa-devel@lists.sourceforge.net \
--cc=joshua@haberman.com \
--cc=pbd@op.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 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.