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 context
2. There can be 2 separate streams of audio between 2 sets of sources and sinks
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@xxxxxxxxxxxx> wrote:
> Hi Anil,
>
>> 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
>
>
>
--
To unsubscribe from this list: send the line "unsubscribe linux-bluetooth" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
