Return-Path: Date: Sat, 23 Jan 2010 15:45:18 +0000 (GMT) To: Anil Sasidharan Cc: linux-bluetooth@vger.kernel.org Subject: Re: A2DP multiple sink support In-Reply-To: References: <1263760863.5591.59.camel@localhost.localdomain> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Message-Id: <1264261518.596186.16656.nullmailer@galant.ukfsn.org> From: Iain Hibbert Sender: linux-bluetooth-owner@vger.kernel.org List-ID: On Mon, 18 Jan 2010, Anil Sasidharan wrote: > 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. Anil you should be aware that Marcel will rarely respond to top posting.. > On Mon, Jan 18, 2010 at 2:11 AM, Marcel Holtmann wrote: > > 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. 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. regards, iain