linux-bluetooth.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Fabien Chevalier <fabchevalier@free.fr>
To: BlueZ development <bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] experimental ALSA/A2DP plugin patch
Date: Thu, 01 Nov 2007 15:19:38 +0100	[thread overview]
Message-ID: <4729E07A.3070809@free.fr> (raw)
In-Reply-To: <719D5CCC2F6E3644B0A9F5C9B1D00088038C8C83@esebe104.NOE.Nokia.com>

Hi Kai,


> Hi,
> 
> On 23 Oct 2007,  Fabien Chevalier wrote:
>> Except for the timing part, i'm not really sure the receiver 
>> is that clever. I guess at least some of them will expect to 
>> receive data with at their local clock speed...
> 
> hmm, based on further reading of the spec, I think the receivers
> must be that clever. And this makes sense, as it's basicly RTP, 
> so an off-the-shelf RTP receiver implementation would work
> for the headsets.

There is a major difference between Internet RTP and Bluetooth RTP.
AFAIK the senders and the receivers' clocks are not syncrhonized on the 
Internet, while using bluetooth technology all slaves devices have an 
estimate of the master clock.

As for off the shelf implementations, i guess everybody just rewrites an 
  RTP implementation for it's own device, as we have done for the Bluez 
project :-)

> 
> And that assumption leads to an experimental patch (patch plus
> patched pcm_bluetooth.c for convenience):
> 
> http://sofia-sip.org/~vehmanek/bluez-patches/patch-pcm_bluetooth-kv-2007
> 1025-works.txt
> http://sofia-sip.org/~vehmanek/bluez-patches/pcm_bluetooth.c
> 
>  - send errors are now ignored (packets dropped), seems
>    to have no bad side effects on the headsets I've tested
>    with
>      -> the positive impact is that we can more easily keep
> 	  up the correct timing even with bigger period sizes
>  - a2dp_write() now loops'n'sends until all data submitted by
>    the app is  encoded (needed to work with MMAP using clients)
>  - allowed period sizes defined as set of values (vs range), 
>    this works with for example pcm.c (seems to be an alsa-lib bug,
>    but didn't have time to track it down)
>  - period count fixed to 3 (seems to work best and still 
>    doesn't confuse ALSA apps)
> 


I'm gonna have a look to that :-)

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

  reply	other threads:[~2007-11-01 14:19 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-10-17 16:31 [Bluez-devel] PATCH1/2: bluez-utils - fix-a2dp-buffer-constraints Kai.Vehmanen
2007-10-18  8:42 ` Johan Hedberg
2007-10-18 10:08 ` Fabien Chevalier
2007-10-18 17:33   ` Jim Carter
2007-10-22 12:28     ` [Bluez-devel] PATCH1/2: bluez-utils -fix-a2dp-buffer-constraints Kai.Vehmanen
2007-10-22 20:15       ` Luiz Augusto von Dentz
2007-10-23 16:58       ` Fabien Chevalier
2007-10-26 13:31         ` [Bluez-devel] experimental ALSA/A2DP plugin patch (was: RE: PATCH1/2: bluez-utils -fix-a2dp-buffer-constraints) Kai.Vehmanen
2007-11-01 14:19           ` Fabien Chevalier [this message]
2007-11-01 14:40           ` [Bluez-devel] Kai's experimental ALSA/A2DP plugin patch review Fabien Chevalier
2007-11-01 15:11             ` Kai.Vehmanen
2007-11-01 17:28               ` Fabien Chevalier
2007-11-02 12:05                 ` Kai.Vehmanen
2007-11-02 12:28                 ` Kai.Vehmanen
2007-11-08  9:58                 ` [Bluez-devel] new not-so-experimental ALSA plugin patch (was: RE: Kai's experimental ALSA/A2DP plugin patch review) Kai.Vehmanen
2007-10-23 14:12   ` [Bluez-devel] PATCH1/2: bluez-utils-fix-a2dp-buffer-constraints Kai.Vehmanen
2007-10-23 16:53     ` Fabien Chevalier

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=4729E07A.3070809@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;
as well as URLs for NNTP newsgroup(s).