09-13-2005, 12:16 PM
|
|
|
Join Date: 04-12-2005
|
| Posts:
17 |
 |
Quote:
Originally posted by sarcasmsra
The biggest problem for A2DP with the MS stack is that there is simply [no] software implementation of the A2DP profile for any Windows CE 4.2 devices running the MS bluetooth stack. And unfortunately, implementing one would be very difficult or impossible. A2DP is a layer on top of AVDTP, a protocol which is not implemented in the Microsoft stack, and which is on top of L2CAP protocol, which is implemented but there is no interface to interact with it in Windows CE 4.2 (not documented interface, but there must be a way).
|
I've been working on A2DP drivers in Linux. We also have no AVDTP protocol in Linux, but we're able to assemble packets and send and receive the AVDTP signals over an L2CAP connection. We can send high-quality audio to every stereo headse we've tried (although the HP headset requires timing tweaks in our sender app)
I'm disappointed to hear there is not a documented way to get at L2CAP... I was going to suggest a ppc developer take our SBC library and AVDTP signaling examples and try them on ppc. One of our developers just optimized the encoder for arm and it runs pretty well now (using 5% of cpu on an arm9/400mhz)
Anyway, our project is at http://bluetooth-alsa.sf.net and the sbc library is licensed under the LGPL. |
|
|
|
|