From: Fabien Chevalier <fabchevalier@free.fr>
To: BlueZ development <bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] An explanation of a2dpd weird behaviour on high resolution timers enabled kernels
Date: Mon, 13 Aug 2007 17:54:20 +0200 [thread overview]
Message-ID: <46C07EAC.8060407@free.fr> (raw)
In-Reply-To: <1186999538.6698.141.camel@violet>
Hi Marcel & Frederic,
> Hi Frederic,
>
>>> you might wanna focus on the Bluetooth audio service in bluez-utils (the
>>> code got committed today) which now has A2DP support.
>> That's great news !!! I was thinking of this coming out soon, but didn't expect something so early.
>
> the CSR based headphones seem to work pretty good so far. We have some
> minor issues on the AVDTP protocol level, but they are fixable. The
> current big issue are the Broadcom based headphones. While CSR seems to
> be quite forgiving if you send data too fast (actually I think they use
> flow control in the baseband to slow us down), the Broadcom ones are
> not. We have to send the next SBC frame at the exact time slot.
> Otherwise the audio sounds too fast or frames are skipped. If you have
> any ideas on how we can improve pcm_bluetooth.c (yes, that handling is
> inside the ALSA plugin), I would like to know.
The issue you plotted here is a well known issue. Basically a2dp/avdtp
profile does not specify how flow control is supposed to be handled,
which leaves it open to implementation-specific behaviours (play faster,
drop samples, use l2cap flow control...). :-(
The way handset makers have solved the issue is to throttle the data
sending, to avoid triggering moonlight specific headset behaviours.
What i would suggest is to do the same thing using usleep() calls inside
the alsa plugin.
That will trigger another issue which is clock drifting, because the
headset will supposedly consume data at master clock speed, while we
will send data at host clock speed. I think for this one the best is to
calculate and compensate for the drift using OCF_READ_CLOCK_OFFSET hci
command: however it's just my wild guess ... ;-)
I hope that helps...
Fabien
-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
next prev parent reply other threads:[~2007-08-13 15:54 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-11 9:48 [Bluez-devel] An explanation of a2dpd weird behaviour on high resolution timers enabled kernels Fabien Chevalier
2007-08-11 18:01 ` Marcel Holtmann
2007-08-12 10:22 ` Fabien Chevalier
2007-08-13 9:59 ` Frederic Dalleau
2007-08-13 10:05 ` Marcel Holtmann
2007-08-13 15:54 ` Fabien Chevalier [this message]
2007-08-13 17:04 ` Marcel Holtmann
2007-08-13 17:49 ` Frederic Dalleau
2007-08-14 2:39 ` Luiz Augusto von Dentz
2007-08-14 12:51 ` Fabien Chevalier
2007-08-14 14:47 ` Frederic Dalleau
2007-08-14 16:40 ` Marcel Holtmann
2007-08-17 10:42 ` Fabien Chevalier
2007-08-17 11:06 ` Marcel Holtmann
2007-08-18 14:13 ` Fabien Chevalier
2007-08-17 13:41 ` Frederic Dalleau
2007-08-14 12:51 ` Fabien Chevalier
2007-08-14 16:44 ` Marcel Holtmann
2007-08-14 19:31 ` [Bluez-devel] Gnome Protocol Analyzer tjoconno
2007-08-17 11:17 ` [Bluez-devel] An explanation of a2dpd weird behaviour on high resolution timers enabled kernels Fabien Chevalier
2007-08-17 11:32 ` Marcel Holtmann
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=46C07EAC.8060407@free.fr \
--to=fabchevalier@free.fr \
--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