From: "Mayank Batra" <mayankbatra@gmail.com>
To: bluez-devel@lists.sourceforge.net
Subject: Re: [Bluez-devel] Re:Advanced Audio Distribution Profile for BlueZ
Date: Tue, 9 May 2006 09:09:52 +0530 [thread overview]
Message-ID: <6297d67c0605082039jd29956bne749c08ef86fbfae@mail.gmail.com> (raw)
In-Reply-To: <20060508153458.88001.qmail@web26908.mail.ukl.yahoo.com>
[-- Attachment #1: Type: text/plain, Size: 2135 bytes --]
Javier,
I think that you did not read the page bluetooth-alsa.sf.net completely.
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.
>
>
> ------------------------------
>
> LLama Gratis a cualquier PC del Mundo.
> Llamadas a fijos y móviles desde 1 céntimo por minuto.
> http://es.voice.yahoo.com<http://us.rd.yahoo.com/mail/es/tagline/messenger/*http://es.voice.yahoo.com/>
>
>
[-- Attachment #2: Type: text/html, Size: 3566 bytes --]
next prev parent reply other threads:[~2006-05-09 3:39 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-08 15:34 [Bluez-devel] Re:Advanced Audio Distribution Profile for BlueZ javier labella
2006-05-09 3:39 ` Mayank Batra [this message]
2006-05-09 5:29 ` Brad Midgley
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=6297d67c0605082039jd29956bne749c08ef86fbfae@mail.gmail.com \
--to=mayankbatra@gmail.com \
--cc=bluez-devel@lists.sourceforge.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox