From: Colin Guthrie <gmane@colin.guthr.ie>
To: alsa-devel@alsa-project.org
Subject: "default" device. Is there a way to detect if it's a plugin, and if so which one?
Date: Sun, 03 Apr 2011 13:22:34 +0100 [thread overview]
Message-ID: <in9oqa$46g$1@dough.gmane.org> (raw)
Hi,
If the user opens the "default" device in alsa, is there a way to find
out if that "device" is actually a plugin?
i.e. is it possible to tell if you have opened the pulseaudio plugin via
alsa?
There are various hacky ways (e.g. checking hints etc.) but that relies
on downstream packaging which certainly isn't fool proof.
Col
--
Colin Guthrie
gmane(at)colin.guthr.ie
http://colin.guthr.ie/
Day Job:
Tribalogic Limited [http://www.tribalogic.net/]
Open Source:
Mageia Contributor [http://www.mageia.org/]
PulseAudio Hacker [http://www.pulseaudio.org/]
Trac Hacker [http://trac.edgewall.org/]
next reply other threads:[~2011-04-03 12:22 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-03 12:22 Colin Guthrie [this message]
2011-04-04 10:57 ` "default" device. Is there a way to detect if it's a plugin, and if so which one? Takashi Iwai
2011-04-04 11:22 ` Colin Guthrie
2011-04-04 11:38 ` Sebastian H.
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='in9oqa$46g$1@dough.gmane.org' \
--to=gmane@colin.guthr.ie \
--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).