From: Brad Midgley <bmidgley@xmission.com>
To: Takashi Iwai <tiwai@suse.de>
Cc: Clemens Ladisch <clemens@ladisch.de>, alsa-devel@lists.sourceforge.net
Subject: Re: alsa-lib plugin devel
Date: Mon, 24 Jan 2005 09:49:49 -0700 [thread overview]
Message-ID: <41F5272D.9060101@xmission.com> (raw)
In-Reply-To: <s5hk6q2u659.wl@alsa2.suse.de>
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
next prev parent reply other threads:[~2005-01-24 16:49 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-24 8:17 alsa-lib plugin devel Brad Midgley
2005-01-24 8:36 ` Clemens Ladisch
2005-01-24 16:31 ` Brad Midgley
2005-01-24 16:46 ` Takashi Iwai
2005-01-24 16:49 ` Brad Midgley [this message]
2005-01-24 17:12 ` Takashi Iwai
2005-01-24 17:25 ` Marcel Holtmann
2005-01-24 16:53 ` Marcel Holtmann
2005-01-24 17:09 ` Takashi Iwai
2005-01-24 17:23 ` Marcel Holtmann
2005-01-24 17:41 ` Takashi Iwai
2005-01-24 17:56 ` Marcel Holtmann
2005-01-24 20:08 ` Brad Midgley
2005-01-25 10:19 ` Takashi Iwai
2005-01-25 13:12 ` Florian Schmidt
2005-01-24 9:24 ` Jaroslav Kysela
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=41F5272D.9060101@xmission.com \
--to=bmidgley@xmission.com \
--cc=alsa-devel@lists.sourceforge.net \
--cc=clemens@ladisch.de \
--cc=tiwai@suse.de \
/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.