From mboxrd@z Thu Jan 1 00:00:00 1970 From: Eliot Blennerhassett Subject: Re: View alsa-lib plugins setup for any app? Date: Wed, 22 Oct 2008 09:55:01 +1300 Message-ID: <200810220955.01218.linux@audioscience.com> References: <48FD3070.7080406@audioscience.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: Received: from smtp3.clear.net.nz (smtp3.clear.net.nz [203.97.33.64]) by alsa0.perex.cz (Postfix) with ESMTP id 60FA5243E5 for ; Tue, 21 Oct 2008 22:51:27 +0200 (CEST) Received: from zaphod (121-72-250-62.cable.telstraclear.net [121.72.250.62]) by smtp3.clear.net.nz (CLEAR Net Mail) with ESMTP id <0K9300AMEWL7CT40@smtp3.clear.net.nz> for alsa-devel@alsa-project.org; Wed, 22 Oct 2008 09:51:07 +1300 (NZDT) In-reply-to: Content-disposition: inline List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: alsa-devel-bounces@alsa-project.org Errors-To: alsa-devel-bounces@alsa-project.org To: Takashi Iwai Cc: alsa-devel@alsa-project.org List-Id: alsa-devel@alsa-project.org 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