public inbox for linux-bluetooth@vger.kernel.org
 help / color / mirror / Atom feed
From: "Cidorvan Leite" <cidorvan@gmail.com>
To: "BlueZ development" <bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] SBC optimizations
Date: Fri, 22 Feb 2008 11:19:58 -0300	[thread overview]
Message-ID: <50282bd30802220619v2eb77bafx86973131b65c3d19@mail.gmail.com> (raw)
In-Reply-To: <50282bd30802220600m73114ba8ya7bdb415d4d6057f@mail.gmail.com>

Hi Brad!

I would say:
"I am not sure if last version(64bits) of decode with 4 subbands is
correct about overflows."

On Fri, Feb 22, 2008 at 11:00 AM, Cidorvan Leite <cidorvan@gmail.com> wrote:
> Hi Brad!
>
>  The volume drop is not significant.
>  Comparing the versions, I didn't see any change in quality with my
>  headphone, so I think that we can change to 32bits.
>  By the way, I am not sure if last version of decode with 4 subbands is
>  correct about overflows.
>
>
>
>  On Thu, Feb 21, 2008 at 10:58 PM, Brad Midgley <bmidgley@gmail.com> wrote:
>  > 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
>  >
>

-------------------------------------------------------------------------
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

  reply	other threads:[~2008-02-22 14:19 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 [this message]
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=50282bd30802220619v2eb77bafx86973131b65c3d19@mail.gmail.com \
    --to=cidorvan@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