From mboxrd@z Thu Jan 1 00:00:00 1970 From: Clemens Ladisch Subject: Re: Determining the plugins being used? Date: Tue, 13 Sep 2011 08:54:14 +0200 Message-ID: <4E6EFE16.4040902@ladisch.de> References: <4E6E6C28.1070009@ladisch.de> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: Received: from out4.smtp.messagingengine.com (out4.smtp.messagingengine.com [66.111.4.28]) by alsa0.perex.cz (Postfix) with ESMTP id 811DC244D9 for ; Tue, 13 Sep 2011 08:53:56 +0200 (CEST) In-Reply-To: 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: Raymond Toy Cc: alsa-devel@alsa-project.org List-Id: alsa-devel@alsa-project.org Raymond Toy wrote: > On Mon, Sep 12, 2011 at 1:31 PM, Clemens Ladisch 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