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: Sun, 12 Aug 2007 12:22:25 +0200 [thread overview]
Message-ID: <46BEDF61.2020401@free.fr> (raw)
In-Reply-To: <1186855275.6698.10.camel@violet>
Hi Marcel,
> Hi Fabien,
>
>> I recently purchased a new combo A2DP/HFP headset from Sony Ericsson.
>> This was the first time i was able to try Frederic's a2dpd daemon. :-)
>
> you might wanna focus on the Bluetooth audio service in bluez-utils (the
> code got committed today) which now has A2DP support.
Ho good, i'm gonna start having a look at it then !
>
> Parts are based on the work from bluetooth-alsa, but the overall design
> concept is a little bit different. For example is the SBC encoding done
> inside the ALSA plugin and not inside the daemon.
That's *great* news !! That always shocked me to have the sound data go
through the sound daemon :-)
This allows us to
> avoid any unnecessary copying of data between processes. My laptop
> showed xmms running at 5% CPU and that includes MP3 decoding and then
> SBC encoding.
Agreed. + reduced latency :-)
>
> I have seen some weird behavior with this when the playback speed is way
> to fast. This might be related or totally unrelated. I simply don't
> know.
I'm gonna start to play with it then.
I was planning to start some a2dp related work myself on it... if only
it wasn't already done. :-)
Could you tell me who's working on the audio service ?
How should i submit patches / possible functionnal improvements to it
(are the people working on it on the list)?
Cheers,
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-12 10:22 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 [this message]
2007-08-13 9:59 ` Frederic Dalleau
2007-08-13 10:05 ` Marcel Holtmann
2007-08-13 15:54 ` Fabien Chevalier
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=46BEDF61.2020401@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.