Hi Brad, > I put some junk in the btsco cvs: > > alsa-lib.patch > bt/ > > if you apply alsa-lib.patch and put bt inside alsa-lib/src/pcm then the > idea is that you can build a userspace alsa driver. > > currently it doesn't even compile... it's just based on the jack plugin > and not yet reworked for bluetooth. nice start. Actually I tried this by myself some time ago, but haven't got any further than a skeleton. The main problem I see at the moment is that we have to develop this inside the ALSA lib source and that is bad. The reason for this is "pcm_local.h" and its definitions that are not installed system wide. I don't think that SND_PCM_TYPE_BLUETOOTH is needed, but I can be wrong of course. The other thing is that this stuff should belong to the pcm/ext/ directory. My skeleton is attached and I used these extra lines in ~/.asoundrc pcm.aiptek { type a2dp bdaddr "00:0B:xx:xx:xx:xx" } Assuming that /usr/lib/alsa-lib/libasound_module_pcm_a2dp.so exists this works as it should. So we have PCM at the input side of this plugin and we send SBC over AVDTP to our headphone. > anyway, this is my next project. it depends on a couple of things in > other parts of the project: Actually I think this is the way we should go. Using a2play is great, but this will open it up to any tool that can play music using the ALSA library. > it would be nice if 'make install' inside sbc/ would install the sbc > includes and library (static libs would be ok) This is the whole goal, but for now I think we should copy the source and simply link it. My plan is to combine sbclib.c and sbc.c and include sbc_internal.h into sbc.c then. Also sbc_tables.h is not really useful as a separate include. > the avdtp library is just a skeleton right now... should I just ignore > it for now and hardcode what is currently in a2play? It is more than a skeleton, but I haven't committed the other code and I don't think that I will have much time to work on it. Ignore it for now, because we can catch up with that later. Regards Marcel