J_of_DK, I noted in my post that I'm using Win XP Pro. You don't want to mess around with those drivers. You'll trash your audio on your pc. Freitasm's earlier query on codecs was to get understanding of encoding format (e.g. mp3, wave, etc.). Anyway, codecs are all over the place on your system as part of other a/v apps (WMP, RealOne, QuickTime, etc.).
This piece of code above will work if you're writing an API for speech recognition. It's basically defining mono "telephone" quality. You'd have to reference these parameters within WIN32 files for MS apps.
Just to update, I was able to reproduce your speed problem. I tried a couple of tests with RealOne and recording from BT is accelerated. Tried several formats (mp3, wave) with differing bit rates, even lowest for mono, but speed was still fast. When I used my normal Logitech PC mic, playback speed was normal.
Also, did try the XP sound recorder and playback was also fast. Tried to slow down voice in control panel, but didn't change anything.
My guess is that XP's drivers are optimized for stereo (two channel) rather than mono (1 channel)??
Also, paired Jabra to check out issue earlier in thread on mic, but I had no problems with yahoo, webcam. Did get the same fast playback results with RealOne.
Since current BT headsets are designed and optimized for use with phones, it looks like "hit and miss" with voice on XP.
Thomas_eh, I read through the thread again and noticed that you wanted to use your BT headset with the app. on www.skype.com.
I experimented with using my headset for yahoo messenger and NetMeeting. I've found that spikes in CPU usage causes static and break-up in the BT audio. Voice over the internet adds to the problem. It was just not pratical in my attempts. I've gone back to my Logitech mic.
Chris - guess I missed the fact that you are running on XP on my second read. Excellent.
Chris - you were able to recreate the problem? How?
Chris - are you saying that you have it working with some applications but not with other apps? Please elaborate.
Thomas - those settings look interesting. However, how do you set them up, any idea? Any idea how to test this - with some special settings, a codec perhaps? Any way to set which codec and how it should operate with the Jabra BT200 bluetooth headset?
Thomas_eh, actually finding that piece of code was the key in figuring out the problem. The problem is not Bluetooth per se, but conflicting software (codecs and/or plug-ins) installed on our pc's.
I couldn't figure out why my audio suddenly developed the same problem when Mauricio and I couldn't replicate it two days before. I remembered that I had recently installed RealOne and noticed that after installation, it had added its own codecs and plug-ins so as to handle all media files. When I experienced the BT playback problems, I discovered in its settings (and boy it really can hide things) that it had also changed my settings to handle all audio/video input/output while also defaulting audio recording to mp3.
For a quick check, I rolled back my system prior to installing RO and tested the headset and the speed was back to normal!! Boy, the new version of RealOne gives a new meaning to SpyWare!!
BT's audio codec basically converts audio to digital and back just like the pc speakers and mic. That's when the code above made sense. Audio quality is basically defined by three things: bit (or sample) rate (e.g. 192 kpps for mp3), sample size (8 or 16) and channels (1=mono; 2=stereo). BT's audio sample size is 8 bit (or AM radio voice quality) while mp3 encodes at 16 bit for cd quality. So, double your bit size, double your rate of speed!
You guys probably have RealOne or some other MP3 player installed that has a conflict with the legacy BT (8 bit) audio codecs.
This was definitely a tough one....now for a big drink(s).............
True, I have (had) ReadOne Player installed. I just uninstalled it, but unfortunately it did not fix my problem (could not roll back since its many months since I installed that %&#" piece of software) and of cause all sorts of software.
Bad news - it did not fix the problem just uninstalling RealCrap Player.
Maybe someone has experience with fixing such problems? Figuring out how audio-codecs work and how they are linked to programs/hardware and such? Even better, who might have an idea of how to fix it ;)
I've been participating in several threads on this issue in the handling of audio streams in general. From what I gather, it appears the current BT codec (and maybe the hardware design?) is just not that sophisticated to handle lossy compression types. There are several new profiles spec'd for BT 1.2 to handle audio streams, but they're still on paper and no details on a release date.
Also, a new codec will be required to encode the audio to work with the limited bandwidth issues of the current BT stack.
It seems the headset profile can handle audio recorded in mp3, wma, wav, etc. since no one seems to have a problem with the headset's "speakers". The mystery is when we add recording from the mic and then attempting to playback to the headset.
Apparently, several vendors have attempted to release headsets for lossy compression and/or stereo. To my knowledge, it looks like none have ever made it to market??
BTW, I played around with recording last night and the fast playback has returned!! Could be related to my installation of Rhapsody or Winamp3 when I reverted my drive back.
My situation was unique for my rollback in that I had just re-installed XP and hadn't proceeded very far in re-installing all my "player" software.
Freitasm, do you have any of this software on your pc? Could it be something in W2K that's different in XP?? Maybe, directx, NTFS vs. FAT32, beta BT codecs?? I'd be interested in your inventory of software and format of drive storage??
I had the same problem with audio recording with TDK bluetooth and HBH35.
I have tried the 1.3.2.9 driver on windows 2000 and it worked. But on windows XP (a fresh install, without codec, driver etc), it didn't work. So, in my opinion, it isnt a conflit with a codec or a real-player issue.
I have installed the TDK 1.4.2.10 and now all work fine.
Just wait the end of october !
Hmmm, this would tend to confirm it IS an improvement in the BT audio codec in Build 10 or a related driver.
The BT audio codec is a part of the Widcomm software to support the headset and audio gateway profiles for D to A & A to D.
I read somewhere where Phillips was getting close to releasing a universal codec for better audio handling, but doubtful if it's included in Widcomm's package??
I'm on the 1.4.1 Build 6 and I believe that Freitasm has been beta testing Build 10 for TDK as yourself. Looks encouraging. Won't know for sure until released for D-Link in my case or as we see other vendors roll out the new version.
Just wondering, you didn't notice any new profiles (i.e. local services or client applications) in this build? Would be interesting if some of the initial BT 1.2 profiles were released.
A real long shot and I think Freitasm would have mentioned, but curious just the same.
Freitasm, do you have any of this software on your pc? Could it be something in W2K that's different in XP?? Maybe, directx, NTFS vs. FAT32, beta BT codecs?? I'd be interested in your inventory of software and format of drive storage??
I have a Windows 2000 SP4 (NTFS) machine, Windows Media Player, DivX, RealOne Player and QuickTime. No other players installed. I'm running TDK 1.4.1 beta. Can't reproduce the problem here (no I don't have the 1.4.10 yet and was told by TDK yesterday they're planning to release the drivers end of this month - still fixing problems with HID and PAN).
Thanks, Mauricio for the info. It appears the problem is 1.4.1.6 running on XP, since users on W2K aren't having the problem or Jeremie using 1.4.2.10 on XP informs us that the issue is remedied.
I had a look at the BT audio configuration file to check on the settings. It looks like it uses the Microsoft WDM Virtual Wave Driver (WDM) as the basis for its headset service. Obviously, this would optimize for wave which requires a much smaller bandwidth for transmission than mp3.
Just a educated guess, but perhaps a start to the underlying issue.
It will be interesting to see what 1.4.2.10 employs?
This is excellent news, cant wait to try it out with 1.4.2.10. Anyone know where to get this driver? (D-Link)
I am flabbergasted about how the driver-system is working with this WIDCOMM. Its the same driver for all, but there is a license? This sounds totally crazy and it has wasted a lot of my time figureing out how to upgrade. Finally had to download a cracked version of Dell drivers, working fine BTW since the one at download some time ago on the D-Link website did not work and/or requested a key. Excuse me, what :) Why on earth do they make all this trouble?
Now some people have 1.4.2.10 that would seem to fix a real problem. I am on the lookout for this driver. It is mind-boggling that it is not just available for download.
Don't blame the security or the need for hacking on Widcomm or "how the driver-system is working". Vendors such as D-Link & TDK provide great support to their user base by keeping their driver releases current. It requires money and resources to support each new release (e.g. testing with the hardware, documentation, tech. support, etc.).
Many vendors don't provide this commitment. D-Link and a few others are protecting their investment. Why should they support their competition's user base??
Don't fault the "good guys"! If your vendor isn't providing support, buy the hardware that you know is well supported.
So, let's be fair. People didn't do their research on the product they bought or decided to go for the bargain deal. "Caveat emptor" in this case.
The reality is that TDK's 1.4.2.10 release will be secured and D-Link's/Dell's subsequent releases, etc. will be secured.
And, since they know how users cracked the last round, TDK and D-Link will "plug the holes" and roll out a more complex security solution each time.
Are you subscribed to our RSS feed? You can download the latest headlines and summaries from our stories directly
to your computer or smartphone by using a feed reader.
Administrator
ID Verified
Trusted
Geekzone
Lifetime subscriber
