From: Tim Chick <chick@computergeek.freeserve.co.uk>
To: bluez-devel@lists.sourceforge.net
Cc: Frederic Dalleau <Frederic.Dalleau@access-company.com>
Subject: Re: [Bluez-devel] Success with current cvs and amarok
Date: Wed, 7 Mar 2007 00:42:13 +0000 [thread overview]
Message-ID: <200703070042.14210.chick@computergeek.freeserve.co.uk> (raw)
In-Reply-To: <CE5216C10C83944D9FD37B65CD33F3970CF481@mplex01.mpl.access-company.com>
On Wednesday 07 March 2007 00:24, Frederic Dalleau wrote:
> > > I just wanted to report a near 100% success with amarok and the
> > > current cvs bluez, to the point where its working to switch songs and
> >
> > If you are using a CSR based headset it will bend the pitch if the input
> > queue is getting too full or empty. So the headset doesn't like the data
> > timing.
>
> Hi, I believe (I hope) Mike is talking about a2dp which is digital and so
> the pitch can not be modified. But it is possibly a bug in the timing. Are
> there some traces that could be related to the moment where you feel the
> pitch change?
I was talking about a2dp as well - the headset will shift the pitch to correct
buffer problems, using the built in dsp!
Cheers,
Tim
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
prev parent reply other threads:[~2007-03-07 0:42 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-06 22:50 [Bluez-devel] Success with current cvs and amarok Mike Hodson
2007-03-06 23:08 ` Tim Chick
2007-03-07 0:24 ` Frederic Dalleau
2007-03-07 0:42 ` Tim Chick [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=200703070042.14210.chick@computergeek.freeserve.co.uk \
--to=chick@computergeek.freeserve.co.uk \
--cc=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 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).