From: Takashi Iwai <tiwai@suse.de>
To: Jaroslav Kysela <perex@suse.cz>
Cc: Marcel Holtmann <marcel@holtmann.org>, alsa-devel@lists.sourceforge.net
Subject: Re: External PCM plugin SDK
Date: Wed, 09 Feb 2005 16:39:41 +0100 [thread overview]
Message-ID: <s5hll9xspxe.wl@alsa2.suse.de> (raw)
In-Reply-To: <Pine.LNX.4.58.0502091622080.1891@pnote.perex-int.cz>
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
next prev parent reply other threads:[~2005-02-09 15:39 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-08 21:30 External PCM plugin SDK Takashi Iwai
2005-02-09 14:14 ` Marcel Holtmann
2005-02-09 14:20 ` Takashi Iwai
2005-02-09 14:37 ` Marcel Holtmann
2005-02-09 15:19 ` Takashi Iwai
2005-02-09 17:27 ` Marcel Holtmann
2005-02-09 17:32 ` Takashi Iwai
2005-02-09 17:48 ` Marcel Holtmann
2005-02-10 11:51 ` Takashi Iwai
2005-02-10 12:29 ` Marcel Holtmann
2005-02-10 17:29 ` Takashi Iwai
[not found] ` <1108057507.15974.97.camel@pegasus>
2005-02-10 17:51 ` Takashi Iwai
2005-02-10 18:06 ` Marcel Holtmann
2005-02-10 18:21 ` Takashi Iwai
2005-02-10 18:30 ` Takashi Iwai
2005-02-10 19:04 ` Marcel Holtmann
2005-02-11 10:50 ` Takashi Iwai
2005-02-11 12:15 ` Marcel Holtmann
2005-02-11 13:28 ` Takashi Iwai
2005-02-11 17:26 ` Takashi Iwai
2005-02-12 2:18 ` Marcel Holtmann
2005-02-14 15:33 ` Takashi Iwai
2005-02-09 17:38 ` Thierry Vignaud
2005-02-09 17:35 ` Takashi Iwai
2005-02-09 15:25 ` Jaroslav Kysela
2005-02-09 15:39 ` Takashi Iwai [this message]
2005-02-09 17:36 ` Thierry Vignaud
2005-02-09 17:38 ` Marcel Holtmann
2005-02-09 15:28 ` Alexander E. Patrakov
2005-02-09 15:29 ` Takashi Iwai
2005-02-09 17:40 ` Thierry Vignaud
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=s5hll9xspxe.wl@alsa2.suse.de \
--to=tiwai@suse.de \
--cc=alsa-devel@lists.sourceforge.net \
--cc=marcel@holtmann.org \
--cc=perex@suse.cz \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.