From: Brad Midgley <bmidgley@xmission.com>
To: Marcel Holtmann <marcel@holtmann.org>, bluez-users@lists.sourceforge.net
Subject: Re: [Bluez-users] News: Stereo BT Headset from BlueTake
Date: Thu, 14 Oct 2004 14:28:19 -0600 [thread overview]
Message-ID: <416EE163.1050605@xmission.com> (raw)
In-Reply-To: <1097762684.4640.49.camel@notepaq>
Marcel,
I must not have understood the distinction. I've seen stuff
(http://www.ericsson.com/bluetooth/files/newsletter5_0403_lores.pdf)
that suggests 1.2 brings with it higher-quality audio through new
profiles (A2DP, AVRCP, GAVDP) and stuff
(http://www.wordiq.com/definition/Bluetooth#Bluetooth_1.2) that says it
gives us better transfer heuristics (eSCO).
Are the profiles purely a function of the software stack? What about eSCO?
I'd love to hear that the 1.1 adapter hardware is not being obsoleted by
1.2. I don't mind having to get a new headset like the bluetake.
Brad
Marcel Holtmann wrote:
> Hi Brad,
>
>
>>I'm not saying bt1.2 is required to use the new headsets, but I'd want
>>to experiment with the a2dp profile for higher-fidelity audio.
>
>
> you don't need Bluetooth 1.2 for A2DP either.
>
> Regards
>
> Marcel
>
>
next prev parent reply other threads:[~2004-10-14 20:28 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-13 19:42 [Bluez-users] News: Stereo BT Headset from BlueTake Matthias Thomae
2004-10-13 22:03 ` Brad Midgley
2004-10-14 8:14 ` Marcel Holtmann
2004-10-14 13:55 ` Brad Midgley
2004-10-14 14:04 ` Marcel Holtmann
2004-10-14 15:01 ` wim delvaux
2004-10-19 13:20 ` Marcel Holtmann
2004-10-19 14:02 ` wim delvaux
2004-10-19 14:53 ` Marcel Holtmann
2004-10-19 15:00 ` wim delvaux
2004-10-19 14:20 ` wim delvaux
2004-10-19 14:53 ` Marcel Holtmann
2004-10-19 14:59 ` wim delvaux
2004-10-14 20:28 ` Brad Midgley [this message]
2004-10-16 11:59 ` Marcel Holtmann
2004-11-05 7:28 ` Brad Midgley
2004-11-05 9:00 ` Matthias Thomae
2004-11-05 16:11 ` 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=416EE163.1050605@xmission.com \
--to=bmidgley@xmission.com \
--cc=bluez-users@lists.sourceforge.net \
--cc=marcel@holtmann.org \
/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