From mboxrd@z Thu Jan 1 00:00:00 1970 From: Takashi Iwai Subject: Re: External PCM plugin SDK Date: Wed, 09 Feb 2005 16:39:41 +0100 Message-ID: References: <1107958458.13863.43.camel@pegasus> Mime-Version: 1.0 (generated by SEMI 1.14.5 - "Awara-Onsen") Content-Type: text/plain; charset=US-ASCII 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: Jaroslav Kysela Cc: Marcel Holtmann , alsa-devel@lists.sourceforge.net List-Id: alsa-devel@alsa-project.org At Wed, 9 Feb 2005 16:25:57 +0100 (CET), Jaroslav wrote: > > On Wed, 9 Feb 2005, Takashi Iwai wrote: > > > > We also talked about making these IO plugins visible when ALSA is > > > listing its hardware devices. Is this possible now? > > > > No, it's still in planning. > > We'll need to define a usable API first... > > Yes, I'll try to prepare something. The general question is, if we should > describe variable parameters (like card number, device number etc. with > this API) or if we put only (probably very long list) of available strings > (device specifications) to applications. > > Both ways have own problems (parsing of parameter description) and > the second case might cause that the list will be completely unuseable for > GUI apps. I prefer a single list. Suppose that at most one or two devices per card are provided as default, the total size wouldn't be so big. In addition to the API to return the list, we can create an API function to return the description of the given PCM (or whatever). For hw pcm, longname can be used. For external I/O plugin, a new description field can be added. For user-defined things, it parses the definition and extracts the "comment" field, for example. Takashi ------------------------------------------------------- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click