From: Frederic Dalleau <frederic.dalleau@access-company.com>
To: BlueZ development <bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] bluetooth-audio and bug in a2dpd (Patch included)
Date: Mon, 28 May 2007 09:44:53 +0200 [thread overview]
Message-ID: <465A8875.9090801@access-company.com> (raw)
In-Reply-To: <4658C395.6010908@jlab.org>
Mathias,
Thanks for the patch,
I forgot that DBG was erasing errno, irk...
I integrated it in order to get a working solution but as you said, this =
is not a solution.
> With my patch it is: 4 seconds filling the buffer, waiting up to 500ms
> (spectrum analyzer in XMMS stops), 2-3 seconds filling the buffer
> (spectrum analyzer runs smoothly), waiting again for 500ms, and so on.
This behavior is strange, a2dpd calculate delays precisely ;) Can you =
send me on my private email a whole .a2dprc and logfile, done with =
enabledebug=3D255 in .a2dpdrc?
a2dpd > logfile
press play, wait something like 10 secs then press stop on xmms.
Don't wait too much as this is very verbose (+/- 10mb).
Thanks,
Fr=E9d=E9ric.
-------------------------------------------------------------------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
prev parent reply other threads:[~2007-05-28 7:44 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-26 17:15 [Bluez-devel] bluetooth-audio and bug in a2dpd (Patch included) Matthias Hensler
2007-05-26 23:32 ` Chris Carlin
2007-05-28 7:44 ` Frederic Dalleau [this message]
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=465A8875.9090801@access-company.com \
--to=frederic.dalleau@access-company.com \
--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.