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:31:26 -0700 Message-ID: <41F522DE.30702@xmission.com> References: 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: Clemens Ladisch , alsa-devel@lists.sourceforge.net List-Id: alsa-devel@alsa-project.org Hi None of the gui alsa-lib clients I've used allow for a freeform device name to be entered. Should we be telling linphone, xine, gnomemeeting, etc developers to allow a freeform device name? They currently just enumerate the (hw I guess) devices and make you choose from what they found. Can I get around this problem by using esd or arts? brad Clemens Ladisch wrote: > Brad Midgley wrote: > >> aplay -B 1000000 -D pcm.a2dp sound.wav >> >>What I'm struggling with is how to make this driver >>appear to clients that use alsa-lib. In the simplest case, >> >> aplay --list-devices >> >>Does not show my device in its list! > > > "aplay -l" shows only hardware devices, i.e., devices that can be > accessed with the hw plugin. > > There is no simple enumeration function for plugin pcm's. > > > HTH > Clemens > ------------------------------------------------------- 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