Skype and Bluetooth audio – very weird behavior

audio-outputbluetoothskype

I'm having a very curious problem with Skype audio that has me
stumped. Here's the setup:

  • I am on my desktop system, which is Intel Core i7, Win7x64, lots
    of memory and disk.
  • I use a Bluetooth headset along with an IOGear Bluetooth USB dongle

In all usage scenarios except Skype, two-way audio via the BT headset
works flawlessly. In Skype, however:

  • Audio out works while "testing" sounds (in the Options/Sounds panel)
  • Audio out does NOT work when placing a call
  • Audio out does NOT work while displaying the Options/AudioSettings
    panel.

The strangest part of this is that it was working this morning. Nothing
has changed, and now it's not working in a call or on the AudioSetting
panel 100% of the time. When I switch to AudioSettings, or when initiating a call, I hear a slight crackling in the headset speakers, which sounds the same as when the audio output routing is being changed.

I have already tried:

  • Shutting down and restarting Skype
  • Multiple system reboots
  • Uninstalling and reinstalling Skype
  • Deleting and re-pairing the headset device

I suspect either Skype or Windows is getting confused when Skype
grabs "exclusive" use of the audio out channel, which it does not
seem to do when just testing sounds. I've tried disabling the
Windows option "Allow applications to take exclusive control of this
device" (in the control panel Sound applet, Speaker Properties) but
this has no effect.

Can anybody suggest anything else to try?

Best Answer

By bluetooth... which profiles are you implying "works" and "doesn't work". Typically, if you're using "A2DP" for your audio output, your microphone won't work. A2DP requires a significant amount of bandwidth that will not allow for a "Hands Free" profile while transmitting audio. Most headsets (that I've used) require you to switch to a "hands free" profile that sounds like garbage (mono, low-quality, etc...) but will allow you to use the microphone. Sometimes, that "switch" must be done manually... by disabling the a2dp profile and enabling the hands-free profile. Windows sees the "output device" for a2dp and hands free separately... so if you have a program playing music... and you switch to hands free... the music will keep playing on the a2dp interface (going nowhere essentially) and your hands-free output device is the only thing that will work.

Related Question