Re: C API:s
Re: C API:s
- Subject: Re: C API:s
- From: Eric Brown <email@hidden>
- Date: Sun, 19 Jan 2003 18:59:34 -0800
On Sunday, January 19, 2003, at 06:20 PM, Ragnar Sundblad wrote:
--On den 19 januari 2003 21:34 +0100 Andri Alm <email@hidden>
wrote:
Please add me too! I'd also be happy to test any SCO beta stuff
you might have or get. We want to make software phones.
I have seen several requests for using a Bluetooth headset for audio
input and output. Here is one I happened to see the other day. And of
course add me to the list who needs to get a SCO link working.
I have heard about others using for example an ipaq with windows ce,
bluetooth, wavelan and SIP phone software make wireless
(bluetooth+wavelan) phone calls with good results.
I could almost see it work for myself today. I tried out the beta
of the TDK windows driver that is supposed to work OK with their
pcmcia card, but not yet so good with the USB dongle I have.
I can confirm the latter, something chops up the audio in both
directions with the same interval as the dongle blinking, some 2Hz.
I suspect the dongle firmware.
Anyway, what was nice was that when audio comes through it sounds
almost about as good as a POTS phone call (with the old first
generation ericsson HBH-10) and the latency (I tried a DVD movie)
was seemingly pretty good (not all that easy to tell when the
audio is chopped up, but I think so).
I have no idea which of the three audio formats, ulaw, alaw or
adpcm, that the headset supports that the driver choosed to use.
I don't think the problem you see with the audio is due to firmware.
That sounds similar to what I've seen with a couple of different pieces
of hardware. The problem I suspect is due to the way that the SCO
connection works. It was designed with no retry mechanism. This
unfortunately leads to various problems such as glitches, stutters and
dropouts in different environments given that the 2.4GHz band is in
such high use. In my personal experience, I haven't found a headset
that worked well enough for my everyday use.
Given that a lot of the requests we've had for headset support is for
speech recognition use, in my opinion, there's no way that the hardware
that I've tested would have good enough sound quality for that use.
Now that IP telephony is starting to become more popular, it seems like
more uses for the technology are opening up. Are there any decent IP
telephony solutions for Mac OS X currently?
Also, I'd love to hear from somebody who has a Bluetooth headset really
works well.
I do think that Apple should get support for it asap, and
preferably make the sound manager glue for it too.
People are already using their bluetooth headsets for telephony,
and I doubt that interrest will decline any time soon. It would
be sad if it couldn't be (easily) done on a Mac OS X machine.
If it was just a little programming to do I could try out my
ericsson rok101007-based dongle (with BT 1.1 firmware) on
Mac OS X, I am pretty sure that one works ok with SCO, but
emulating the entire stack, if so only for one single purpose,
seems a little bit heavy for just testing purposes considering
the time I currently have available for this project.
Whom at apple should we talk to to get more SCO support in the
Mac OS X bluetooth stack sooner rather than later?
The best place for non developer-related feature requests is the
Bluetooth feedback e-mail address: <email@hidden>.
However we do hear the requests being made on this list (even if we
can't always respond or talk about everything going on).
- Eric
_______________________________________________
bluetooth-dev mailing list | email@hidden
Help/Unsubscribe/Archives:
http://www.lists.apple.com/mailman/listinfo/bluetooth-dev
Do not post admin requests to the list. They will be ignored.
| References: | |
| | >Re: C API:s (From: Ragnar Sundblad <email@hidden>) |