From: Brad Midgley <bmidgley@xmission.com>
To: BlueZ development <bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] RE : A2DP plugin success with HP bluetooth headphones
Date: Thu, 13 Jul 2006 06:43:58 -0600 [thread overview]
Message-ID: <44B6400E.9040305@xmission.com> (raw)
In-Reply-To: <20060713105346.GA22651@srcf.ucam.org>
Matthew
>> Could you give it a try with a2dpd plugin and see if these problems remains?
>> You will not have the same audio quality, but those start/stop problems may disappear.
>
> Ok, that seems better, but the audio quality is pretty dreadful - what
> recognisable bits there are are running slightly too slowly, followed by
> a brief burst of static.
fwiw, in my experience, the hp set was the least forgiving of timing
problems in our software. it "pops" when frames are too fast and has
even nastier "snaps" when it's so slow that the stream runs dry.
brad
-------------------------------------------------------------------------
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 easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
prev parent reply other threads:[~2006-07-13 12:43 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-13 6:27 [Bluez-devel] RE : A2DP plugin success with HP bluetooth headphones Frederic Dalleau
2006-07-13 10:53 ` Matthew Garrett
2006-07-13 12:37 ` Frédéric DALLEAU
2006-07-13 12:50 ` Matthew Garrett
2006-07-13 16:37 ` Frédéric DALLEAU
2006-07-13 18:01 ` Brad Midgley
2006-07-13 21:30 ` Matthew Garrett
2006-07-13 23:36 ` Matthew Garrett
2006-07-13 12:43 ` Brad Midgley [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=44B6400E.9040305@xmission.com \
--to=bmidgley@xmission.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 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).