From: Brad Midgley <bmidgley@xmission.com>
To: BlueZ development <bluez-devel@lists.sourceforge.net>
Subject: [Bluez-devel] itech r35 supports mp3
Date: Mon, 05 Jun 2006 16:19:54 -0600 [thread overview]
Message-ID: <4484AE0A.8050900@xmission.com> (raw)
Hey
FYI, I found my new r35 headset supports mp3 encoded streams. I changed
a2play to identify (but not use yet) mp3 support and there it is, layer
3 support built in.
too bad about the alsa plugin... audio must be decoded before being sent
to the plugin where it's re-encoded, possibly in the same format we just
decoded :(
gstreamer would realize the stream is already in a supported format and
skip those steps, but we're still stuck without a good ipc/server mixer
for gst.
Brad
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
reply other threads:[~2006-06-05 22:19 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=4484AE0A.8050900@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;
as well as URLs for NNTP newsgroup(s).