From: "Brad Midgley" <bmidgley@gmail.com>
To: "BlueZ development" <bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] SBC optimizations
Date: Thu, 21 Feb 2008 18:58:26 -0700 [thread overview]
Message-ID: <d89ddf300802211758x4a8e9991t868cfe5081523803@mail.gmail.com> (raw)
In-Reply-To: <50282bd30802211429h419f6342qb6ab4ac62cd20a69@mail.gmail.com>
Cidorvan
How significant is the volume drop in 4 subbands? Should we just leave
the decoder at 64 bit mults so we don't needlessly suffer quality
issues on faster platforms?
Brad
On Thu, Feb 21, 2008 at 3:29 PM, Cidorvan Leite <cidorvan@gmail.com> wrote:
> Hi!
>
> I replaced the 64bits multiplies by 32bits and fixed the volume, now
> the encode and decode are >10% faster.
> Unfortunately, I couldn't keep the same volume for decode with 4 subbands...
>
> -------------------------------------------------------------------------
> This SF.net email is sponsored by: Microsoft
> Defy all challenges. Microsoft(R) Visual Studio 2008.
> http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
> _______________________________________________
> Bluez-devel mailing list
> Bluez-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/bluez-devel
>
>
--
Brad
-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
next prev parent reply other threads:[~2008-02-22 1:58 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-21 22:29 [Bluez-devel] SBC optimizations Cidorvan Leite
2008-02-22 1:58 ` Brad Midgley [this message]
2008-02-22 14:00 ` Cidorvan Leite
2008-02-22 14:19 ` Cidorvan Leite
2008-02-22 15:46 ` Brad Midgley
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=d89ddf300802211758x4a8e9991t868cfe5081523803@mail.gmail.com \
--to=bmidgley@gmail.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