From: Randell Jesup <randell1@jesup.org>
To: Clemens Ladisch <clemens@ladisch.de>
Cc: alsa-devel@alsa-project.org, Randell Jesup <randell1@jesup.org>
Subject: Re: Use of _hint() functions and older machines
Date: Mon, 24 Oct 2011 01:19:47 -0400 [thread overview]
Message-ID: <4EA4F573.9060704@jesup.org> (raw)
In-Reply-To: <4EA3EE43.3010904@ladisch.de>
On 10/23/2011 6:36 AM, Clemens Ladisch wrote:
> On 10/21/2011 05:28 AM, Randell Jesup wrote:
>> On older machines, _hint() aren't available, so even if I make them
>> optional to dlsym-loading, I would need some other method to get the
>> information I assume using older, now-deprecated-or-gone interfaces.
>
> On older machines, that information wasn't available at all.
>
> The recommendation was to use "default" or to let the user enter
> a device name.
Ah. Ok. Wow, was it really that painful? I didn't do a lot of Linux
media stuff back then, and generally had only built-in-audio (no USB
headsets, etc) with simple speakers.
> The best way to get a list of devices would have been to enumerate sound
> cards with snd_card_next(), then use device names "default:CARD=x".
> However, this gets only the primary device of each card, there might be
> sound cards without a PCM device, devices not based on an ALSA kernel
> driver aren't listed, and the "default:CARD=x" mechanism doesn't work if
> the user has redefined the "default" device.
Ugh. So, there's no reasonable way to get a user-understandable list
before .14? How useful was
snd_ctl_card_info_get_name()/snd_ctl_card_info()? And I guess I'd need
to enumerate the 'devices' and 'subdevices' on each card as well...
Thanks for the info, BTW
--
Randell Jesup
randell-ietf@jesup.org
next prev parent reply other threads:[~2011-10-24 5:24 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-21 3:28 Use of _hint() functions and older machines Randell Jesup
2011-10-22 18:04 ` Colin Guthrie
2011-10-23 7:46 ` Randell Jesup
2011-10-23 10:36 ` Clemens Ladisch
2011-10-24 5:19 ` Randell Jesup [this message]
2011-10-24 7:00 ` Raymond Yau
2011-10-24 10:26 ` Clemens Ladisch
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=4EA4F573.9060704@jesup.org \
--to=randell1@jesup.org \
--cc=alsa-devel@alsa-project.org \
--cc=clemens@ladisch.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 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.