linux-bluetooth.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Anil Sasidharan <anilvpr@gmail.com>
To: Marcel Holtmann <marcel@holtmann.org>
Cc: linux-bluetooth@vger.kernel.org
Subject: Re: A2DP multiple sink support
Date: Mon, 18 Jan 2010 11:09:04 +0530	[thread overview]
Message-ID: <f6c5b8d91001172139q5f23201fnd2ab2193ebc9a33f@mail.gmail.com> (raw)
In-Reply-To: <1263760863.5591.59.camel@localhost.localdomain>

Hi Marcel,

             Thank you so much for the prompt reply. The following are
the conclusions made from your reply.
1. It is possible to support multiple sources and multiple sinks in A2DP co=
ntext
2. There can be 2 separate streams of audio between 2 sets of sources and s=
inks
3. However there might be bandwidth issues and other paging related issues

However I did not get the last point mentioned in your mail i.e. "So
expect some cracks in the audio until both connections are setup
properly".....

Could you please elaborate on this.

Once again, thanks for your time...

Warm Regards,
Anil

On Mon, Jan 18, 2010 at 2:11 AM, Marcel Holtmann <marcel@holtmann.org> wrot=
e:
> Hi Anil,
>
>> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 We are trying to use Bluecore BT module =
(from CSR) for
>> A2DP profile support. In the present use case, our device acts as a
>> A2DP SRC. We are able to stream 44.1kHz stereo audio to a A2DP
>> headset. Now the next use case scenarios that we would like to try out
>> in A2DP context are the following:
>
> look at /etc/bluetooth/audio.conf for settings. You can configure it for
> multiple sources.
>
> The difference between same audio stream and different audio stream is
> not really for bluetoothd itself to make. If it goes to a different
> remote it has to transmit it separately anyway.
>
> If you wanna optimize this, then using GStreamer and some kind of
> mulitplexing magic of the stream could for same stream on different
> targets to reduce the SBC encoding. Otherwise you have to encode the
> stream twice.
>
> This whole thing with one source adapter works, but during inquiry and
> page it is almost impossible for a Bluetooth chip to transmit any data.
> So expect some cracks in the audio until both connections are setup
> properly.
>
> Regards
>
> Marcel
>
>
>

  reply	other threads:[~2010-01-18  5:39 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <f6c5b8d91001170441m1d0d8755x15147f92b85b477f@mail.gmail.com>
2010-01-17 12:50 ` A2DP multiple sink support Anil Sasidharan
2010-01-17 20:41   ` Marcel Holtmann
2010-01-18  5:39     ` Anil Sasidharan [this message]
2010-01-23 15:45       ` Iain Hibbert
2010-02-05 15:59         ` Anil Sasidharan
     [not found]           ` <1265396410.615373.5159.nullmailer@galant.ukfsn.org>
2010-02-27 19:42             ` Anil Sasidharan

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=f6c5b8d91001172139q5f23201fnd2ab2193ebc9a33f@mail.gmail.com \
    --to=anilvpr@gmail.com \
    --cc=linux-bluetooth@vger.kernel.org \
    --cc=marcel@holtmann.org \
    /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;
as well as URLs for NNTP newsgroup(s).