Alsa-Devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Lee Revell <rlrevell@joe-job.com>
To: "Matthias König" <list@phasorlab.de>
Cc: alsa-devel@lists.sourceforge.net
Subject: Re: list all available devices
Date: Mon, 06 Feb 2006 13:58:39 -0500	[thread overview]
Message-ID: <1139252320.2791.295.camel@mindpipe> (raw)
In-Reply-To: <874q3ce3vn.fsf@zebra.localdomain>

On Mon, 2006-02-06 at 19:30 +0100, Matthias König wrote:
> Hi,
> 
> Lee Revell <rlrevell@joe-job.com> writes:
> 
> > It's insane to expect every app to use 100 lines of code list to list
> > available PCMs.  It should be a single function call.
> 
> Hmm, doesn't this exist already? What about this:
> 
> int snd_names_list(const char *iface, snd_devname_t **list)
> Give a list of device names and associated comments for selected interface. 
> 

No, that's something different (and does not even work here):

$ aplay -n
ALSA lib names.c:173:(snd_names_list) cannot access
file /etc/asound.names
aplay: names_list:199: snd_names_list error: No such file or directory

Lee



-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems?  Stop!  Download the new AJAX search engine that makes
searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=103432&bid=230486&dat=121642

      reply	other threads:[~2006-02-06 18:58 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-02-06  9:25 list all available devices Timo Steuerwald
2006-02-06 10:19 ` Giuliano Pochini
2006-02-06 10:32   ` Timo Steuerwald
2006-02-06 18:00   ` Lee Revell
2006-02-06 18:10     ` Timo Steuerwald
2006-02-06 18:13       ` Lee Revell
2006-02-06 18:30         ` Matthias König
2006-02-06 18:58           ` Lee Revell [this message]

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=1139252320.2791.295.camel@mindpipe \
    --to=rlrevell@joe-job.com \
    --cc=alsa-devel@lists.sourceforge.net \
    --cc=list@phasorlab.de \
    /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