Listening to Bluetooth (or at least trying to)
by Dori Smith, coauthor of Mac OS X Unwired03/02/2004
I once read a review of a bug zapper -- a product that killed flying insects. The reviewer concluded that once you took into account the product's pros and cons, your best value for the dollar was to buy one and then give it to your next-door neighbor. You ended up with most of the pros and none of the cons. Using iChat AV with a Bluetooth-enabled headset has a lot in common with that product, including the way that both of them leave you complaining about bugs.
What you'll need (hardware):
- A Mac running OS X 10.3.2
- A Bluetooth module, either internal (all supported) or external (only some supported)
- A Bluetooth-enabled headset, such as the Jabra BT200
What you'll need (software):
- Bluetooth Firmware Updater 1.0.2
- Bluetooth Software 1.5
- iChat AV 2.1 beta
I've been pairing the Jabra BT200 headset with my Sony Ericsson phone for months now and found it to be very handy. Wearing it at last October's O'Reilly OS X Conference, the most common question I was asked was: does that work with a Mac? I was sorry to disappoint people and tell them no, and I was happy to hear that with the recent release of Bluetooth 1.5 that that answer had changed.
(The second most common question I heard was whether the headset made me look more like a Bajoran or a Borg, but that's another story altogether.)
What You'd Expect
You're a Mac user, so you expect that you can plug things in (or in this case, pair things), and they'll just work. So, you'd expect that a Bluetooth headset pairing would allow you to use your Mac and your headset to do things like voice recognition, listen to iTunes, and in general, use the audio input and output features of the headset to replace the audio input and output of the Mac. Unfortunately, it's not quite that simple.
The Installation Process
There are three separate downloads, all of which are required: the Bluetooth firmware updater, the Bluetooth software, and iChat AV 2.1. The firmware updater has the most ominous warning message I've ever seen in an Apple product, with five separate warnings (as shown in Figure 1).
Figure 1: Apple's Bluetooth Firmware Updater.
|
Related Reading
Mac OS X Unwired |
Even with this many warning messages, things can still go wrong. If you were an early adopter and bought the original Bluetooth adapter sold by Apple (the D-Link DWB-120M), you'll get an error message saying that your adapter isn't suitable and its firmware isn't updateable. The Belkin F8T003 isn't updateable, either, but the current adapter Apple sells (the D-Link DBT-120) works fine.
But if you do have a compatible adapter, even with all those warning messages, Apple missed one: don't try to run the firmware updater with Bluetooth turned off. The updater won't ever find your Bluetooth device, and it won't stop trying -- leaving you with only an option specifically warned against: canceling the update. Thankfully, no harm appeared to be done to my test machine, and the updater ran just fine after Bluetooth was turned on.
If you've gone to Apple's Bluetooth page to download both the Bluetooth software and the firmware updater, you might then think that you have everything that's necessary. After all, the page says "You can also use a Bluetooth headset to talk to your friends and colleagues during an iChat AV session." But the page forgets to mention that the version of iChat AV you probably have (v2.0) only mostly works with Bluetooth headsets.
Save yourself several headaches and gray hairs (it's too late for me) and download iChat AV 2.1 Public Beta. While the only feature Apple documents adding in 2.1 was the ability to video conference with AOL 5.5/Windows users, installing 2.1 fixed a number of hairy Bluetooth chat bugs on my test system, including application freezes and an inability to turn Bluetooth devices off.
Getting Started
As mentioned previously, even though you've installed three different downloads, it's still not quite plug-and-play. Your Sound System Preference and the iChat preferences each have separate settings for sound input and output (see Figures 2 and 3).
Figure 2: Sound System Preference pane.
Figure 3: iChat AV video preferences pane.
While this seems counterintuitive at first (two separate inputs and two separate outputs?), it starts to make sense shortly after you've tried using the headset for all system sounds. For instance, if your Mac hasn't made any sounds in awhile, it drops the connection to your headset. If an application then beeps, the connection has to resume before the beep can be sent, causing a delay that makes you wonder just which recent action went with that beep. And listening to iTunes through the headset is near painful; listeners compared it unfavorably to AM radio through a cheap speaker.
As for setting your System Preferences to use the headset for sound input, there's not really much point, as Apple documents fairly clearly that "Speech recognition is not a supported feature." And despite the Speech System Preferences pane successfully recognizing the headset as a microphone, and then displaying that it's hearing sounds, you can't use it to enter speakable items. The days when we'll be able to wirelessly talk to our Macs is coming, but it's not here yet. Between the issues with system sounds, iTunes quality, and lack of speech recognition, there's no point in setting your Sound preferences (either input or output) to use your Bluetooth headset.
Setting Things Up
After all that negativity, I'm happy to be able to say that setting up a Bluetooth headset was fairly straightforward, although somewhat more than plug-and-play:
- Launch the Bluetooth Setup assistant
- Choose the new-to-Bluetooth 1.5 "Headset" radio button
- Set your headset to be discoverable, and wait for your Mac to find it
- At the prompt, enter the passkey associated with the headset (hint: if you have the Jabra BT200, it's "0000")
- Launch iChat AV
- Go to the "iChat (Beta)" → "Preferences…" → "Video" (because you'd expect to find the audio settings under the video preferences, right?)
- Set the "Microphone" and "Sound Output" pop-up menus to your headset, as shown in Figure 3, above
- Start talking to your buddies
Thankfully, all those steps only have to be done the first time; after that, when necessary, you'll simply be prompted to re-pair the device (as shown in Figure 4).
Figure 4: Pairing the headset.
Don't believe that line about "Passkeys are only used once and do not need to be remembered"; you'll need to repeat this step every time you turn the headset off (which includes recharging it) or go out of Bluetooth range and come back again. And even though your Mac knows that it's a headset and that you can't enter a passkey on a headset, it'll tell you that "[t]he same passkey needs to be entered on both the computer and the remote Bluetooth device" -- so be sure to remember your passkey!
iChatting with Bluetooth
And finally, you've got everything set up, just the way you want it, and you'll find that it works well, although not perfectly. If you've used iChat before, you'll find that the greatest new feature is being able to pace while chatting -- no more having to talk directly into your iSight or PowerBook's microphone. And the combination of iChat, an iSight, and your Bluetooth headset is the virtual equivalent of VOIP calling.
I got mixed reports from the people I chatted with about the relative audio quality. While they all agreed that the headset was considerably better than my 15" PowerBook's built-in microphone, they split just about evenly whether the headset was better or worse than the iSight's mic. The most common evaluation was that the two were fairly even in quality, but their tone was different, and different people preferred one over the other (sometimes strongly).
I was hoping that the headset would clear up what I consider to be iChat AV's greatest failing: the echo effect. It's distracting to hear everything I say repeated on the other end. The good news is that the headset does kill off the echo. The bad news: it kills it off for the person you're chatting with, not you. So you'll still hear an echo, but the person on the other end won't. Consequently, I found that I got the greatest enjoyment from the headset when I gave it to someone else to use while I was chatting with them.
You'll also want to be careful how you seat the headset in and around your ear -- while it's supposed to fit everyone, nothing that's one size fits all ever quite does. Proper positioning of both the earbud and the mic improves the quality of both the sound input and output.
As for talking to Windows AIM 5.5 users, it's obvious why v2.1 is still a beta release. If my iSight was attached, I could audio or video chat with Windows users. Oddly enough, those with audio-only showed as video-capable, but whether audio or video-capable, only video and text appeared as options (never audio). And with my iSight detached, no one showed as having audio capabilities, even though both their computers and mine were capable.
Final Thoughts
If it's important to you (as it is to me) to pace while you talk, you owe it to yourself to get a Bluetooth headset to use with iChat AV. If you don't currently have any audio input to your Mac and you already have Bluetooth, this is a simple way to be able to start audio chatting.
But beyond that, this technology is still not quite there yet. The big benefits, I found, were those available when I gave the headset to others to use instead of me: primarily, the end of the echo issue (on my end), and also that I had access to other sound inputs (internal PowerBook mic, iSight) and the recipient (with a tower) didn't, allowing us to audio chat for the first time.
Eventually Apple will support features like speakable items and voice recognition. In the long run, we'll get functionality that will let your Mac/cell phone/headset inter-operate, such that you can be listening to good quality music on your headset until a phone call comes in. At that point, iTunes will pause, caller ID will show up on your Mac saying who's calling, and you'll be able to take that call via the headset. While we're close, we're not quite there yet.
Thanks to Tom, Matt, Al, Chuq, Steven, Eric, Lynn, Chuck, and Dan for help with the audio tests.
Dori Smith is coauthor of Mac OS X Unwired, JavaScript for the WWW: Visual QuickStart Guide, 4th Edition, author of Java 2 for the WWW: Visual QuickStart Guide, and a contributor to numerous online and print computer industry magazines.
Return to MacDevCenter.com.
You must be logged in to the O'Reilly Network to post a talkback.
Showing messages 1 through 10 of 10.
-
Use Jabra BT200 for non-bluetooth phones
2004-03-05 18:45:11 winkllj@acm.org [Reply | View]
An alternative to using the bluetooth BT200 directly with the Mac's Bluetooth is to use the Jabra BT200 for Non-Bluetooth phones.
What you need
1) Jabra BT200 for Non-Bluetooth phones: comes with its own bluetooth receiver (already matched to the earpiece), outputs as mic with 2.5mm phone plug (stereo -- one side for receiving, one for transmitting).
2) an adapter (Radio Shack) 2.5mm to 3.5mm stereo phone plug adapter (approx $5)
3) Griffin iMic, which takes a Mic In, pushes to USB (powered!) -- you already have one of these -- right?
It may be a little on the Rube Goldberg side, but it works, and if you have a non-bluetooth phone (as I have) I can use it with your phone (no need to rematch bluetooth signals).
The benefits are
a) Because I'm using Mic-in on USB instead of bluetooth, my PB 15" handles speakable items -- I can control Keynote wirelessly now;
b) No need to update firmware as described above.
c) Can use with non-bluetooth cell phones
Negatives:
i) a bit Rube Goldberg
ii) BT200 for non-bluetooth phones is more expensive than bluetooth earpiece alone.
-
Firmware update
2004-03-05 11:36:04 w4lna [Reply | View]
Be aware that the Apple firmware update for the D-Link DBT-120 breaks its compatibility with any Windows machine that you might want to use it with later...
-
A thorough how-to...
2004-03-04 02:31:41 sanfordmay [Reply | View]
Finally somebody wrote a how-to for this process. Amen. I've been trying to help people at Apple's Web site, but I'm not a technician, I'm a writer -- not even a technical writer. The first high hurdle people seem to meet -- other than impossibly incompatible hardware -- is getting their BT headset into headset profile pairing mode as opposed to handsfree. I -- heaven forbid -- read the documentation for my Jabra FreeSpeak; thus I was fortunate enough to know ahead of time that I needed to pair in headset profile with my PowerBook, and handsfree for my mobile phone if I wanted the extra features -- like voice dialing -- of the handsfree profile. The second hurdle is dealing with the fact that the headset can only maintain a connection with one device at a time; if you keep your mobile phone near your Mac, the mobile tends to grab the BT headset connection if the headset is on and you have to power off the phone or manually disconnect to switch to the Mac. The former hurdle is just a matter of education and the latter is, I think, a limitation of the headsets and mobiles, not the Mac.
As to audio fidelity, I often get a clear, excellent signal until I wander to the limits of range -- which in my present apartment is short for my FreeSpeak. The range of my Nokia phone, on the other hand, is good. Sometimes too good, as I use Salling Clicker and on occasion I can go all the way outside without it dropping the connection to my PowerBook and triggering Clicker's "away" features. I'm not sure if this is device-dependent signal strength, random interference (in the case of FreeSpeak static), quirks, or a bit of all three.
At any rate, dozens will appreciate your article. And for my part, I think things like headset support, Salling Clicker (now supporting Ericsson and Symbian mobiles, and Palm OS) and Apple's elegant keyboard and mouse are moving Bluetooth from a potentially useful technology to a tangibly useful one.
-
Caller ID, iTunes Integration and Bluetooth = Salling Clicker
2004-03-03 15:46:33 fasonmobile [Reply | View]
Dori,
I just read your article. Great and descriptive account of how to set this up. I went through all the very same steps myself about 1 month ago... When I got my SonyEricsson HBH 60 Headset. This one is the SMALLest one I have seen that looks good!
Here is a link to the Sony Ericsson website to check it out...
SonyEricsson HBH-60 BT Headset
Also, an added footnote to your ending comments on Caller ID, integration with BT mobile phones and iTunes... Its all working right now... Yes, its true... you can in fact use Caller ID, and control iTunes from a Bluetooth phone... See my notes below...
If you launch your Address Book, and activate its Bluetooth integration (just click on the Bluetooth logo), then if you have a Bluetooth phone paired with OSX, and you get a phone call, it will display the person calling in a large dialog window (Caller ID)... with some additional call management options...
Additionally, if you install Salling Clicker from Salling Software, a VERY handy Bluetooth ap ... this software allows you to remote control your mac (ie. iTunes, Keynote, iPhoto, etc.) as in, from your mobile phones accessory menu you can remote control iTunes volume level, track shuttle, select playlists, edit your library, etc.... and THE MOST compelling add on feature is Salling Clickers ability to integrate with OSX Address Book and further allow you to automatically fade down/up/pause iTunes when a call comes in, as well as displaying the Caller ID on screen... As soon as your finished with a mobile phone call, iTunes resumes playback at the set level...
Here is the link to the Salling Clicker app...
Salling Clicker for Bluetooth Phones and PDAs
PS> I am using Salling Clicker and my Bluetooth enabled OSX Address Book right now and its pretty much the coolest thing on Panther I have seen to date...
Best,
Jason Fields.
AIR-PORT, LLC
Los Angeles, CA
air-port.com -
Not here yet
2004-03-03 16:56:14 dori [Reply | View]
Also, an added footnote to your ending comments on Caller ID, integration with BT mobile phones and iTunes... Its all working right now... Yes, its true..
No, it's not. Or at least not the way I described it in the article. At this point you can't use a headset for both the phone and the Mac simultaneously, and I think that that's an important part of making this all work seamlessly.
Re Salling Clicker (which I also love): you can find my previous article about it here, and I also wrote about it in our book, Mac OS X Unwired.
-
Not here yet
2004-03-04 22:57:51 fasonmobile [Reply | View]
Well... Your request/future suggestion is a tad vague in the last paragraph, as the things you describe are what IS working now... apart from the fact that the headset can only be paired to one device at a time... which you barely mention... you did a better job in your reply to me than in the article... anyhow... as one of the other poster mentioned, probably an artifact of the hardware and not the software...
BUT, regardless, it was a nice and detailed article. Keep on BT'n!
-
video...
2004-03-02 18:49:19 C.K. Sample, III [Reply | View]
'. Oddly enough, those with audio-only showed as video-capable, but whether audio or video-capable, only video and text appeared as options (never audio). And with my iSight detached, no one showed as having audio capabilities, even though both their computers and mine were capable.'
The reason audio only people show up as video in iChatAV beta (and the new AIM) is because you can actually send video one way now (they see and hear you, while you only hear them). If you turn off the iSight it works just like a regular audio chat, even though the connection button shows the video icon.
Also, thanks for mentioning my scripts in your book.
Also, have you ever tried ohphoneX? I used to use it before iChat AV and it worked well. I'm thinking about trying it out with my Jabra... -
video...
2004-08-05 10:06:55 Granny [Reply | View]
I am soon to be a granny and want to be able to see our grandchild who lives 7 horus away. Thought a webcam would be the answer to that question. I am running Mac OS 10.2.8. I have downloaded MacCam, iChat USB Cam v.1.1.2, i Chat Enhancer, Logitech's QuickCam update for OSX. Still no luck with audio. Thought I would try OhphoneX. I'm not real sure how to use it. I have downloaded it, but now what.
The baby is due by the end of August so I am getting anxious. Thanks. -
video...
2004-03-03 15:22:18 dori [Reply | View]
The reason audio only people show up as video in iChatAV beta (and the new AIM) is because you can actually send video one way now (they see and hear you, while you only hear them). If you turn off the iSight it works just like a regular audio chat, even though the connection button shows the video icon.
That was sort of what I was trying to say, that basically, what iChat shows isn't what you actually get (i.e., it'll show video-only even though it's sometimes audio-capable, and some times audio-only). However it's described, it's screwy and Apple ought to fix it before the final release.
Also, thanks for mentioning my scripts in your book.
Thank you for making them available!
Also, have you ever tried ohphoneX? I used to use it before iChat AV and it worked well. I'm thinking about trying it out with my Jabra...
That's a new one on me. I'll go check it out.





I'm surprised you had so much trouble with your BT headset and iChat. I paired by Jabra BT300 headset as soon as the new Bluetooth software came out and I haven't had much trouble. I don't have to re-pair and iChat conversations sound great with no echo to speak of. Listening to music using the headset doesn't sound very good, but that's to be expected. Speech recognition also works as good (or bad, still working on my American accent so my Mac will understand me better) as with the internal microphone.
The only problem I had was that an older version of iChat had a hard time switching and remembering audio in/out settings.
A tip for anyone using iChat's audio chat feature without a Bluetooth headset: by using some regular headphones the Mac won't be hearing it's own speaker output back through the microphone. This allows the sound to flow in both directions at the same time, making everything sound much better.