alsa-devel.alsa-project.org archive mirror
 help / color / mirror / Atom feed
From: "Lee Revell" <rlrevell@joe-job.com>
To: Nicholas Smethurst <smethurst@gmail.com>
Cc: alsa-devel@alsa-project.org
Subject: Re: alsa-lib functions reporting conflicting information with two sound cards
Date: Thu, 19 Apr 2007 14:45:36 -0400	[thread overview]
Message-ID: <75b66ecd0704191145u3414a5e6id9e3f10ef9c6b854@mail.gmail.com> (raw)
In-Reply-To: <4627B015.7030401@gmail.com>

On 4/19/07, Nicholas Smethurst <smethurst@gmail.com> wrote:
> Lee Revell wrote:
> > On 4/19/07, nick smethurst <nick.smethurst@gmail.com> wrote:
> >> I am rather confused that I am getting crossed information when
> >> calling snd_names_list
> >> and snd_pcm_info in order to gather information about pcm devices.
> >
> > I think ALSA's new device enumeration API can do this for you.  See
> > the implementation of aplay -l (or -L, don't remember which) in the
> > latest alsa-utils.
> Ok, thanks for the hint (no pun intended :) ).
>
> I see that the pcm_list() function has changed in aplay. The new hints
> API looks good.
>
> However, I note that snd_device_name_hint() does not return hw, plughw,
> plug, dmix, etc. Are these obtained elsewhere? I would like to build a
> complete list of all available devices in order to allow the user to
> select them from a dropdown list in a GUI.

Not sure, I don't have access to a machine with a modern ALSA now but
the new aplay list function definitely lists those.  I do know that
yours is exactly the problem it was designed to solve.

Lee

  reply	other threads:[~2007-04-19 18:45 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-04-19 14:30 alsa-lib functions reporting conflicting information with two sound cards nick smethurst
2007-04-19 15:46 ` Lee Revell
2007-04-19 18:08   ` Nicholas Smethurst
2007-04-19 18:45     ` Lee Revell [this message]
2007-05-11 10:28       ` Getting a full device list (was: alsa-lib functions reporting conflicting information with two sound cards) Nicholas Smethurst
2007-05-11 10:35         ` Jaroslav Kysela
2007-05-11 11:05           ` Getting a full device list Nicholas Smethurst
2007-05-11 11:46             ` Jaroslav Kysela
2007-05-11 15:13             ` Takashi Iwai
2007-05-11 17:01               ` Nicholas Smethurst
2007-05-14  8:36               ` Nicholas Smethurst
2007-05-14  9:18                 ` Takashi Iwai
2007-05-14  9:27                   ` Nicholas Smethurst
2007-05-14  9:57                     ` Takashi Iwai
2007-05-14 10:38                       ` Nicholas Smethurst
2007-05-14 12:55                         ` Takashi Iwai
2007-04-20 10:13     ` alsa-lib functions reporting conflicting information with two sound cards 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=75b66ecd0704191145u3414a5e6id9e3f10ef9c6b854@mail.gmail.com \
    --to=rlrevell@joe-job.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=smethurst@gmail.com \
    /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).