From: Marcel Holtmann <marcel@holtmann.org>
To: BlueZ Mailing List <bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] A2DP vs. microphone
Date: Wed, 19 Jan 2005 17:25:37 +0100 [thread overview]
Message-ID: <1106151937.8190.126.camel@pegasus> (raw)
In-Reply-To: <41EE770F.8030302@xmission.com>
Hi Brad,
> i just added this to our docs and I want to bounce it off you guys to
> make sure I'm reading things right:
>
> A2DP provides a way to send stereo high-quality audio to some of the
> newer headsets. This is one-way audio, so if you were expecting to get
> something like a gaming headset (talking to other players, getting
> stereo sound back from the game) I guess the spec is lacking. It might
> be theoretically possible for a headset to accept simultaneous SCO and
> A2DP connections to do this but even if it's possible, no headset
> allows it.
SCO is bidirectional and thus using a Bluetooth headset for gaming is
possible. The A2DP is a distribution service and you can have multiple
sink and source combination. So a headphone can also have a microphone
channel to send high quality voice (for voice recognition) back. However
I haven't seen such a product so far, but it seems that the Toshiba SR-1
may is capable of something like that. Check my webpage.
Regards
Marcel
-------------------------------------------------------
The SF.Net email is sponsored by: Beat the post-holiday blues
Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek.
It's fun and FREE -- well, almost....http://www.thinkgeek.com/sfshirt
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
prev parent reply other threads:[~2005-01-19 16:25 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-19 15:04 [Bluez-devel] A2DP vs. microphone Brad Midgley
2005-01-19 16:25 ` Marcel Holtmann [this message]
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=1106151937.8190.126.camel@pegasus \
--to=marcel@holtmann.org \
--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