From: Marcel Holtmann <marcel@holtmann.org>
To: bluez-devel@lists.sourceforge.net
Subject: RE: [Bluez-devel] Advanced Audio Distribution Profile (A2DP)
Date: Tue, 21 Jun 2005 19:29:06 +0200 [thread overview]
Message-ID: <1119374946.26772.119.camel@pegasus> (raw)
In-Reply-To: <C70061B183DE09419568AB2060C52A95702C9A@arion.intra.local>
Hi Victor,
> I've tried recently to run a2play on arm (@~380), well no surprise here,
> it looks like there is not enough cpu to deal with fp emulation. Later
> I've modified a2play so it can play pre-encoded sbc (sbcend output) to
> skip encoding part, but it still far from what I get when run it on PC.
> I think there is a synchronization problem somewhere there, hear a lot
> of clicks, drops and repetitions. I've tried it with 2 different pairs
> of headphones, on Bluewalker and on HP's (iPAQ gadget), and while the
> former sound not extremelly bad, the latter sound very crappy (there are
> periods when they sound ok, but mostly they are out of sync?). So it
> looks like it somehow connected with how the headphone handle timing?
the Bluewalker is a GCT based headphone and quite easy to satisfy. You
can also stream SBC directly over RFCOMM with rcplay. The HP is Zeevo
based and you really need to get the timing right to hear good sound.
The same applies for the CSR based headphones.
> I have a couple of questions:
>
> 1) Is there anyone buse with sbc fixed point convertion?
We need an integer only implementation of SBC. I may repeat myself, but
I am not going to code this. This must be done by someone else.
> 2) Is there anyone with similar problems (out-of-synch sound) and knows
> how to solve it (or is it just about tuning the timer?)?
You need to encode the SBC frames in advance and then use a timer for
sending them. I am working on a ALSA plugin that will do exactly this,
but I think that won't help you on your embedded platform.
Regards
Marcel
-------------------------------------------------------
SF.Net email is sponsored by: Discover Easy Linux Migration Strategies
from IBM. Find simple to follow Roadmaps, straightforward articles,
informative Webcasts and more! Get everything you need to get up to
speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
next prev parent reply other threads:[~2005-06-21 17:29 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-21 15:28 [Bluez-devel] Advanced Audio Distribution Profile (A2DP) Victor Shcherbatyuk
2005-06-21 17:29 ` Marcel Holtmann [this message]
2005-06-21 18:02 ` Brad Midgley
2005-06-21 18:28 ` Marcel Holtmann
2005-06-21 19:51 ` Brad Midgley
2005-06-21 21:03 ` Marcel Holtmann
2005-06-22 0:16 ` Brad Midgley
2005-06-22 0:26 ` Marcel Holtmann
2005-06-22 7:56 ` Brad Midgley
2005-06-22 18:50 ` Brad Midgley
2005-06-22 20:23 ` Henryk Plötz
2005-06-22 21:36 ` Brad Midgley
2005-06-22 6:45 ` Peter Robinson
-- strict thread matches above, loose matches on Subject: below --
2005-06-22 15:27 Victor Shcherbatyuk
2005-06-22 16:39 ` Brad Midgley
2005-06-15 17:19 Claudio Takahasi
2005-06-15 17:47 ` wim delvaux
2005-06-15 17:49 ` Brad Midgley
2005-06-15 17:51 ` Henryk Plötz
2005-06-16 12:50 ` Claudio Takahasi
2005-06-22 8:54 ` Peter Robinson
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=1119374946.26772.119.camel@pegasus \
--to=marcel@holtmann.org \
--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.