From: Brad Midgley <bmidgley@xmission.com>
To: bluez-devel@lists.sourceforge.net
Subject: Re: [Bluez-devel] Comments about the Logitech/HP stereo headphones
Date: Sun, 24 Apr 2005 08:28:52 -0600 [thread overview]
Message-ID: <426BAD24.1030507@xmission.com> (raw)
In-Reply-To: <20050424134746.GA31151@externe.net>
Guylhem
> IMHO a2dp will be mostly useful for embedded system or in specific
> applications on desktop systems (xmms, etc). Having to use alsa is at
> best useless and at worse a potential showstopper.
we will keep and update the standalone streamer. it doesn't integrate
well with other apps but you can deal with that when embedding.
> - on desktop systems a2dp could also be managed by a standalone
> application, which could be an audio out plugin for xmms/mplayer etc.
> This plugin would also manage sbc encoding and a2dp streaming until
> some dedicated tool manage a2dp streaming.
We can write one plugin for alsa and get support for
xmms/mplayer/xine/etc. if someone else wants native plugins for all
those apps, that's great.
> So my suggestion, at least until a good strategy has been defined, would
> be to use a2play as a work base, and add mp3/ogg decoding - the "all
> in one" approach. Quite easy to test, enhance, fix, finetune, etc -
> better IMHO that separate tools for the moment.
i think this could be an attractive utility for embedded work, but i
would be careful how you add mp3 decode. my gumstix has analog audio
out. I wouldn't want to use the space for an app that can decode mp3
(new a2play) but can't also send it to analog out.
> Later on, like rfcomm manages rfcomm0 etc. entries, some a2dp tool
> could bind a2dp peripherals to /dev/a2dpN where SBC audio would be
> expected and streamed to the a2dp peripheral bound there.
managing connections is kind of a pain. it can't be done entirely in
kernel space. you can see how this gets spread into the btsco daemon.
Brad
-------------------------------------------------------
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
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
next prev parent reply other threads:[~2005-04-24 14:28 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-24 12:18 [Bluez-devel] Comments about the Logitech/HP stereo headphones Marcel Holtmann
2005-04-24 13:47 ` Guylhem Aznar
2005-04-24 14:28 ` Brad Midgley [this message]
2005-04-24 15:23 ` Marcel Holtmann
2005-04-24 15:16 ` Marcel Holtmann
2005-04-24 17:11 ` Guylhem Aznar
2005-04-24 18:09 ` Marcel Holtmann
2005-04-24 20:28 ` Brad Midgley
2005-04-24 16:19 ` Henryk Plötz
2005-04-24 16:48 ` Guylhem Aznar
2005-04-24 18:15 ` Marcel Holtmann
2005-04-24 18:12 ` Marcel Holtmann
2005-04-24 14:04 ` Brad Midgley
2005-04-24 14:34 ` Brad Midgley
2005-04-24 15:30 ` Marcel Holtmann
2005-04-25 17:39 ` Brad Midgley
-- strict thread matches above, loose matches on Subject: below --
2005-04-24 15:16 Mayank Batra
2005-04-24 15:35 ` Marcel Holtmann
2005-04-26 12:46 Mayank Batra
2005-04-26 13:28 ` Marcel Holtmann
2005-04-28 12:10 Mayank Batra
2005-04-29 9:51 ` Marcel Holtmann
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=426BAD24.1030507@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox