From mboxrd@z Thu Jan 1 00:00:00 1970 From: Brad Midgley Subject: Re: alsa-lib plugin devel Date: Mon, 24 Jan 2005 09:49:49 -0700 Message-ID: <41F5272D.9060101@xmission.com> References: <41F522DE.30702@xmission.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: Sender: alsa-devel-admin@lists.sourceforge.net Errors-To: alsa-devel-admin@lists.sourceforge.net List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , List-Archive: To: Takashi Iwai Cc: Clemens Ladisch , alsa-devel@lists.sourceforge.net List-Id: alsa-devel@alsa-project.org Takashi, > We can create a new API to list up the available PCMs. > It will help applications, I guess. > > The problem is that plugins which aren't bound to drivers like btsco > are hard to detect whether they really work in advance. > Do we need a probe callback for such a plugin? I suppose there are problems listing things because the plugins behave differently. I don't fully understand the problem. But... it would be a big inconvenience for the user to be told to know the device name or go look it up in .asoundrc and/or /etc/asound.conf. The {linphone,xine,gnomemeeting} gui should be able to discover and list the plugin devices. Brad ------------------------------------------------------- This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting Tool for open source databases. Create drag-&-drop reports. Save time by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc. Download a FREE copy at http://www.intelliview.com/go/osdn_nl