From: "Brad Midgley" <bmidgley@gmail.com>
To: "BlueZ development" <bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] SBC optimizations
Date: Fri, 22 Feb 2008 08:46:29 -0700 [thread overview]
Message-ID: <d89ddf300802220746l72e55ba9lfa3b5b3aff2227b0@mail.gmail.com> (raw)
In-Reply-To: <50282bd30802220619v2eb77bafx86973131b65c3d19@mail.gmail.com>
Cidorvan
> "I am not sure if last version(64bits) of decode with 4 subbands is
> correct about overflows."
Some volume reduction is ok, especially if it means we avoid another overflow.
Anyway, it looks like the commit is in.
Thanks again.
--
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
prev parent reply other threads:[~2008-02-22 15:46 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
2008-02-22 14:00 ` Cidorvan Leite
2008-02-22 14:19 ` Cidorvan Leite
2008-02-22 15:46 ` 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=d89ddf300802220746l72e55ba9lfa3b5b3aff2227b0@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