From: Nicholas Smethurst <nick.smethurst@gmail.com>
To: alsa-devel@alsa-project.org
Subject: Re: Getting a full device list
Date: Fri, 11 May 2007 13:05:36 +0200 [thread overview]
Message-ID: <46444E00.1040808@gmail.com> (raw)
In-Reply-To: <Pine.LNX.4.61.0705111233090.7579@tm8103.perex-int.cz>
Jaroslav Kysela wrote:
> On Fri, 11 May 2007, Nicholas Smethurst wrote:
>
>> Is this possible? If not, can we work towards implementing such
>> functionality?
>
> User or system software manager should create a configuration which is
> suitable for users. You're trying to overload the user settings. Why?
> Use information returned without any hacks in your application (you may
> eventually describe in documentation, how users can get more devices).
I'm not sure I understand.
I found the global variable "defaults.namehint.showall" in alsa.conf, which
lives in /usr/share/alsa/. This is not the sort of place a user should be
fiddling with. Users don't have the knowledge (or the desire) to manually
change system configuration files.. us developers should be able to do all we
need to do via alsa-lib.
I understand that you are suggesting that user applications list what ever
snd_device_name_hint() returns, and then describe in the application
documentation that if the user does not see devices such as hw, they should
manually edit a system configuration file.
Or do you mean that a user application can create its own global
configuration? I didn't know that that was possible.
If this is the case, can I copy the default configuration and turn on
"defaults.namehint.showall" in order that my user application can call have
the full list from snd_device_name_hint()?
Nicholas
next prev parent reply other threads:[~2007-05-11 11:05 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
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 ` Nicholas Smethurst [this message]
2007-05-11 11:46 ` Getting a full device list 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=46444E00.1040808@gmail.com \
--to=nick.smethurst@gmail.com \
--cc=alsa-devel@alsa-project.org \
/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).