alsa-devel.alsa-project.org archive mirror
 help / color / mirror / Atom feed
From: Eliot Blennerhassett <linux@audioscience.com>
To: Takashi Iwai <tiwai@suse.de>
Cc: alsa-devel@alsa-project.org
Subject: Re: View alsa-lib plugins setup for any app?
Date: Wed, 22 Oct 2008 09:55:01 +1300	[thread overview]
Message-ID: <200810220955.01218.linux@audioscience.com> (raw)
In-Reply-To: <s5h1vyaa22e.wl%tiwai@suse.de>

On Tuesday 21 October 2008 19:34:49 Takashi Iwai wrote:
> Sorry, I don't understand well your question.  Do you want to see the
> alsa-plugin chain of a running application from the outside, 

Yes. Basically see something that looks like the result of "aplay -v", but for 
a running app from the outside.  

E.g. to see if the app is using dmix, plughw etc, what parameters the app sees 
vs how the card is accessed.

Best if this info was available like the proc files for the driver, but if it 
required running the app in a special context (debugger-like or LD_PRELOAD) 
that would probably still be useful.

The app should not have to be recompiled.


> or do you 
> ask an API to show the alsa-plugin chains, 

no. Now I see that you are thinking of snd_pcm_*_dump() family.

> or a way to show hw_params/sw_params for plugins?

I this is included in my first "yes"

regards

Eliot

  reply	other threads:[~2008-10-21 20:51 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-10-21  1:29 View alsa-lib plugins setup for any app? Eliot Blennerhassett
2008-10-21  6:34 ` Takashi Iwai
2008-10-21 20:55   ` Eliot Blennerhassett [this message]
2008-10-22  3:51     ` Sean McNamara
2008-10-22  6:38       ` Takashi Iwai
2008-10-22  5:58     ` Takashi Iwai
2008-10-22  6:39       ` Takashi Iwai
2008-10-23  4:25         ` Eliot Blennerhassett
2025-12-05  7:56     ` [alsa-devel] " fatmanvincent

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=200810220955.01218.linux@audioscience.com \
    --to=linux@audioscience.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=tiwai@suse.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 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).