Stuttering audio via Bluetooth headset due to audio init bug

[directhex]

I've spent the past few hours trying to coerce Windows into using a Bluetooth headset as a sound device. However, there appears to be a bug in Teamspeak:

• Headset acts fine as a microphone, whatever happens (i.e. recording from headset, playing on speakers, no problems)
• Headset is fine for general use in Windows, e.g. playing music, games, flash animations, etc
• Headset produces horrible, stuttering audio when being used to play back from Teamspeak - i.e. in local test mode, or connected to a server, the headset cannot be used to listen as audio is stuttering.

This could well be a problem with the API in use, as windows sound recorder shows the same problem (note that games and music are fine, so it's DEFINITELY a problem with whatever mechanism teamspeak & sndrec32 use to output their audio, possibly missing out on some change in Hz that the other "normal" apps are doing, or somesuch).

Any ideas?

[directhex]

I've spent the past few hours trying to coerce Windows into using a Bluetooth headset as a sound device. However, there appears to be a bug in Teamspeak:

• Headset acts fine as a microphone, whatever happens (i.e. recording from headset, playing on speakers, no problems)
• Headset is fine for general use in Windows, e.g. playing music, games, flash animations, etc
• Headset produces horrible, stuttering audio when being used to play back from Teamspeak - i.e. in local test mode, or connected to a server, the headset cannot be used to listen as audio is stuttering.

This could well be a problem with the API in use, as windows sound recorder shows the same problem (note that games and music are fine, so it's DEFINITELY a problem with whatever mechanism teamspeak & sndrec32 use to output their audio, possibly missing out on some change in Hz that the other "normal" apps are doing, or somesuch).

Any ideas?

this is DEFINITELY down to some kind of initialization bug - if I set WMP to use the headset for output, and start some music playing - then teamspeak is fine as long as i have music playing. As soon as I close WMP, teamspeak goes screwy - but leaving WMP open, after it has played some music, acts as a fix. The very first half-second of the music is played at the wrong speed, so it *seems* to be sample-rate-related.

teamspeak 2.0.32.60
XP home SP2
motorola h3 headset, via MSI BToes dongle, with WIDCOMM 1.4.3.4 driver (plus Audigy 2ZS, 5.12.2.444)