From: Anil Sasidharan <anilvpr@gmail.com>
To: Iain Hibbert <plunky@rya-online.net>
Cc: linux-bluetooth@vger.kernel.org
Subject: Re: A2DP multiple sink support
Date: Fri, 5 Feb 2010 21:29:42 +0530 [thread overview]
Message-ID: <f6c5b8d91002050759s3968fa13ka3ee4bfaab4b8b4@mail.gmail.com> (raw)
In-Reply-To: <1264261518.596186.16656.nullmailer@galant.ukfsn.org>
On Sat, Jan 23, 2010 at 9:15 PM, Iain Hibbert <plunky@rya-online.net> wrote:
>
> This means that when a Bluetooth device is performing a device inquiry, or
> setting up a connection (paging) to another device, it will usually pause
> data transfer over other baseband connections that it already holds.
>
> This means that if you set up an audio stream, then try to start another
> stream or perform a device inquiry at the same time the first stream may
> become broken (cracks) as no data is being transferred.
>
> Actually, since A2DP is not necessarily low-latency, you may find that
> forward buffering is adequate to cover small temporary lapses in data
> transfer.
>
Hi Iain,
Thanks a lot for the inputs. Based on this I've tried some experiments.
1. A2DP src has been paired and connected to the A2DP sink
2. While the connection with first SINK is active, I've tried to pair
and connect to another A2DP sink
3. Pairing with the second SINK gets done, however while trying to
connect I'm encountering an error from D-Bus "Stream Setup Failed".
What could be wrong
It would be really great if you could throw some light on this. BTW
I'm using Bluez v3.36
Warm Regards,
Anil
next prev parent reply other threads:[~2010-02-05 15:59 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
2010-01-23 15:45 ` Iain Hibbert
2010-02-05 15:59 ` Anil Sasidharan [this message]
[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=f6c5b8d91002050759s3968fa13ka3ee4bfaab4b8b4@mail.gmail.com \
--to=anilvpr@gmail.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=plunky@rya-online.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;
as well as URLs for NNTP newsgroup(s).