From: Marcel Hilzinger <mhilzinger@linuxnewmedia.de>
To: BlueZ development <bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] RE : Quality of a2dp sound
Date: Mon, 13 Nov 2006 14:24:05 +0100 [thread overview]
Message-ID: <200611131424.06615.mhilzinger@linuxnewmedia.de> (raw)
In-Reply-To: <200611101117.30944.mhilzinger@linuxnewmedia.de>
Am Freitag, 10. November 2006 11:17 schrieb Marcel Hilzinger:
> Am Freitag, 10. November 2006 09:41 schrieb Frederic Dalleau:
> > Hi,
> >
> > > a2dpd produces some noise in the background. If there is silence, you
> > > can hear it. With a2play there is no noise. I will checkout cvs again
> > > and have a look.
>
> One more (maybe last :-) feedback
Never say never again...
I'm now testing the 3th day, whole day with bt phones on my head. A new =
problem, which appears at least with amarok, maybe also with xmms: The spee=
d =
of the played sound is not constant. It's like augmenting the speed on a =
oldstyle turntable from 33 1/2 to 35, back to 31 and back to 33 1/2 again. =
First I thought it's due to heavy CPU load, but it seems to appear randomly=
. =
I decreased the sbcbitpool=3D value from 64 to 32 and it's seems to be bett=
er, =
but perhaps it's only because I restartet a2dpd. =
It seems to be a caching problem.
In my first tests I had the same, when I went far away from the dongle, so =
playback stopped and then came back. Sound was played very quickly, and the=
n =
normal again. But I then had no up-and-down-effects like today.
-- =
Mit freundlichen Gr=FC=DFen,
Marcel Hilzinger
Linux New Media AG
S=FCskindstr. 4
D-81929 M=FCnchen
Tel: +49 (89) 99 34 11 0
Fax: +49 (89) 99 34 11 99
-------------------------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easi=
er
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=3Dlnk&kid=3D120709&bid=3D263057&dat=3D1=
21642
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
next prev parent reply other threads:[~2006-11-13 13:24 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-09 10:02 [Bluez-devel] Quality of a2dp sound Marcel Hilzinger
2006-11-09 10:42 ` Adrian Glaubitz
2006-11-09 10:07 ` Reiner Klenk
2006-11-10 8:01 ` Marcel Hilzinger
2006-11-10 8:41 ` [Bluez-devel] RE : " Frederic Dalleau
2006-11-10 9:46 ` Marcel Hilzinger
2006-11-10 9:59 ` Mayank BATRA
2006-11-10 10:04 ` Marcel Hilzinger
2006-11-11 8:21 ` Reiner Klenk
2006-11-12 18:38 ` Marcel Hilzinger
2006-11-12 20:31 ` Brad Midgley
2006-11-13 9:39 ` Frédéric DALLEAU
2006-11-13 18:26 ` Reiner Klenk
2006-11-13 18:37 ` Reiner Klenk
2006-11-10 10:06 ` Marcel Hilzinger
2006-11-10 10:17 ` Marcel Hilzinger
2006-11-13 13:24 ` Marcel Hilzinger [this message]
2006-11-14 12:19 ` [Bluez-devel] python a2dp Sergey Krivov
2006-11-14 14:40 ` Frédéric DALLEAU
2006-11-14 15:25 ` Sergey Krivov
2006-11-14 15:34 ` Frédéric DALLEAU
2006-11-14 15:40 ` Sergey Krivov
2006-11-13 15:32 ` [Bluez-devel] Quality of a2dp sound Brad Midgley
2006-11-09 17:43 ` Marcel Hilzinger
2006-11-09 19:31 ` Thomas Kear
2006-11-10 8:24 ` [Bluez-devel] RE : " Frederic Dalleau
2006-11-10 13:50 ` Adrian Glaubitz
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=200611131424.06615.mhilzinger@linuxnewmedia.de \
--to=mhilzinger@linuxnewmedia.de \
--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