Javier,
Both SCO and ACL implementations have been done.
Maybe you can add some new feature to the existing A2DP. (a2play or pcm_a2dp).
I think support for the mp3 codec (making a choice at run time between SBC and MP3 codec) could be handy.
Also, the A2DP spec mentions briefly about RTP. Nobody has looked into that till now.
Regards
Mayank
On 5/8/06, javier labella <javi_labella@yahoo.es> wrote:
Fecha: Wed, 3 May 2006 18:18:27 +0200 (CEST)
De: javier labella <
javi_labella@yahoo.es>
Asunto: Re:Advanced Audio Distribution Profile for
Bluez
Para:
bluez-devel@lists.sourceforge.net
>We have implemented some a2dp already. See bluetooth-alsa.sf.net
. There
>is still plenty to do, if you want to help integrate it with gstreamer
>for example.
>I think it's not totally clear how the a2dp profile gets "integrated"
>since it really looks more like a bluez client that belongs in one or
>more multimedia frameworks.
>Brad
Hi,
I've visited bluetooth-alsa.sf.net
and the project is very interesting but I think that the profile's implementation is based on SCO channels. If I'm making a mistake I apologize for it. On the other hand, I've read the A2DP profile specification and I think that an implementation should uses ACL channels: "The Advanced Audio Distribution Profile (A2DP) defines the protocols and procedures that realize distribution of audio content of high-quality in mono or stereo on ACL channels (Introduction of Advanced Audio Distribution Profile Specification)" So I'd like to develop an implementation using ACL channels instead of SCO channels.
I'd like to know if you're interested in include this implementation in the BlueZ stack too.
Thanks.
Javier.