From: Brad Midgley <bmidgley@xmission.com>
To: BlueZ development <bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] A2DP and Alsa Plugin
Date: Tue, 30 May 2006 14:28:20 -0600 [thread overview]
Message-ID: <447CAAE4.3040202@xmission.com> (raw)
In-Reply-To: <447C1C70.1030309@palmsource.com>
Fr=E9d=E9ric
>>Ideally it's a system function, but I'm not seeing a way to pull that off.
>> =
> gstreamer makes it easy to write applications, but application writer =
> can choose whatever sink he wants. We cant rely on application being =
> a2dp aware.
I just read this more carefully... so the system would do things like
discover headsets, pair, update .asoundrc (or equivalent). The app
should only have to search for a plugin and let the user choose it.
Brad
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
next prev parent reply other threads:[~2006-05-30 20:28 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-11 9:15 [Bluez-devel] A2DP and Alsa Plugin Frederic Dalleau
2006-05-12 17:10 ` Brad Midgley
2006-05-17 16:51 ` Frédéric DALLEAU
2006-05-17 17:40 ` Brad Midgley
2006-05-29 7:02 ` Brad Midgley
2006-05-30 10:20 ` Frédéric DALLEAU
2006-05-30 16:38 ` Brad Midgley
2006-05-30 20:28 ` Brad Midgley [this message]
2006-08-02 14:08 ` Brad Midgley
2006-08-02 14:54 ` Frédéric DALLEAU
-- strict thread matches above, loose matches on Subject: below --
2006-05-10 8:17 Frederic Dalleau
2006-05-10 17:49 ` Brad Midgley
2006-05-05 12:38 Frederic Dalleau
2006-05-05 17:24 ` Brad Midgley
2006-05-04 15:58 Frederic Dalleau
2006-05-04 17:19 ` Brad Midgley
2006-05-04 15:34 Frederic Dalleau
2006-05-04 13:30 Frederic Dalleau
2006-05-04 14:36 ` Brad Midgley
2006-05-04 14:50 ` Brad Midgley
2006-05-04 15:20 ` Brad Midgley
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=447CAAE4.3040202@xmission.com \
--to=bmidgley@xmission.com \
--cc=bluez-devel@lists.sourceforge.net \
/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.