From: Clemens Ladisch <clemens@ladisch.de>
To: Raymond Toy <rtoy@google.com>
Cc: alsa-devel@alsa-project.org
Subject: Re: Determining the plugins being used?
Date: Tue, 13 Sep 2011 08:54:14 +0200 [thread overview]
Message-ID: <4E6EFE16.4040902@ladisch.de> (raw)
In-Reply-To: <CAE3TgXEWbnacMSbfgor4gk54ADDY60prBHu4mX3aSLmYDO6AsQ@mail.gmail.com>
Raymond Toy wrote:
> On Mon, Sep 12, 2011 at 1:31 PM, Clemens Ladisch <clemens@ladisch.de> wrote:
> > Raymond Toy wrote:
> > > Is there a way to determine the plugins being used?
> >
> > Not really. snd_pcm_type() gives you the topmost plugin's type.
The pulse plugin typically is the topmost plugin. However, you won't be
able to differentiate between 'plain' hw and dmix devices this way
because both often have a plug plugin on top.
> Bummer. So the only hacky way is to look at the output of snd_pcm_dump,
> then?
Well, there is the even more hacky way of sifting through /proc/asound/
files to see who is accessing the hw device, but let's pretend I didn't
mention it ...
snd_pcm_dump() was designed for debugging only, but at the moment there
is no better way.
Regards,
Clemens
prev parent reply other threads:[~2011-09-13 6:53 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-12 19:16 Determining the plugins being used? Raymond Toy
2011-09-12 20:31 ` Clemens Ladisch
2011-09-12 21:04 ` Raymond Toy
2011-09-13 6:54 ` Clemens Ladisch [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=4E6EFE16.4040902@ladisch.de \
--to=clemens@ladisch.de \
--cc=alsa-devel@alsa-project.org \
--cc=rtoy@google.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 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.