From: Marcel Holtmann <marcel@holtmann.org>
To: BlueZ users <bluez-users@lists.sourceforge.net>
Subject: Re: [Bluez-users] A2dp on ARM9- Quality not good
Date: Sat, 11 Aug 2007 20:20:33 +0200 [thread overview]
Message-ID: <1186856433.6698.37.camel@violet> (raw)
In-Reply-To: <d89ddf300708060727r2f2165dawfec381fd3506ec44@mail.gmail.com>
Hi Brad,
> first, try different encoder settings. some settings use more
> bandwidth but less cpu.
>
> also see the todo items from sbc.c:
>
> use a log2 table for byte integer scale factors calculation (sum
> log2 results for high and low bytes)
> fill bitpool by 16 bits instead of one at a time in bits
> allocation/bitpool generation
> port to the dsp
> don't consume more bytes than passed into the encoder
>
> some of these were suggested to me by the guy writing an encoder for
> palm 700p. I didn't dig into the algorithm to see how they would work.
I think that is a job for our friends from Brazil. Ping them and see if
they can work something out.
Regards
Marcel
-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users
next prev parent reply other threads:[~2007-08-11 18:20 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-06 7:38 [Bluez-users] A2dp on ARM9- Quality not good Sumeet VERMA
2007-08-06 14:27 ` Brad Midgley
2007-08-11 18:20 ` Marcel Holtmann [this message]
2007-08-17 14:01 ` Brad Midgley
2007-08-17 14:08 ` Marcel Holtmann
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=1186856433.6698.37.camel@violet \
--to=marcel@holtmann.org \
--cc=bluez-users@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