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 15:01:55 +0200 [thread overview]
Message-ID: <s5hptyg96f0.wl@alsa2.suse.de> (raw)
In-Reply-To: <200206241248.g5OCm3f17394@post2.fast.net>
At Mon, 24 Jun 2002 08:49:25 -0400,
Paul Davis wrote:
>
> >> 2. How is device selection designed to work with ALSA? My experience
> >> with ALSA has been very confusing in this regard. I recall reading at
> >> least once that ALSA is not designed to have applications enumerate all
> >> the devices; that the correct way is to use ~/.asoundrc to define a
> >> hardware device and then supply that name to applications. But is there
> >> anything more sophisticated an application can do than to just present
> >> the user with a text box?
> >
> >the pcm name really depends on the driver implementation.
> >usually, device #0 is provided for general use. but, for example, the
> >implementation of 4-channel sound is driver speicific.
> >some driver implements using a control switch and other combines
> >multiple pcm streams, etc.
> >
> >however, there are standard names, too:
> >default, front, rear, center_lfe, surround40, surround51, spdif and
> >iec958 (identical with spdif).
> >it would be nice if users can choose one of them from a list, and
> >additionally have an input text field (well, not sophisticated,
> >though).
>
> but there's no straightforward method of determining which names
> actually exist. the code in aplay that handles the -L request, for
> example, is baroque to the point of extremity. an application could
> not just use those standard names, because the audio interface they
> have may not support them.
yep. that's actually a problem, too.
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.
> in addition this also doesn't deal with the issue of users with more
> than one soundcard installed.
this is not difficult, since the card number can be passed via
CARD argument.
Takashi
-------------------------------------------------------
Sponsored by:
ThinkGeek at http://www.ThinkGeek.com/
next prev parent reply other threads:[~2002-06-24 13:01 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 [this message]
2002-06-24 14:17 ` Paul Davis
2002-06-24 15:18 ` Fred Gleason
2002-06-24 16:13 ` Takashi Iwai
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=s5hptyg96f0.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.