public inbox for linux-bluetooth@vger.kernel.org
 help / color / mirror / Atom feed
From: Lars Grunewaldt <lgw@dark-reality.de>
To: bluez-devel@lists.sourceforge.net
Subject: Re: [Bluez-devel] more encoder stuff
Date: Fri, 26 Nov 2004 01:14:00 +0100	[thread overview]
Message-ID: <41A67548.90805@dark-reality.de> (raw)
In-Reply-To: <1101425014.6465.39.camel@pegasus>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Marcel Holtmann wrote:
| Hi Henryk,
|
|
|>>The MAD library (www.underbit.com/products/mad/) is using fixed-point
|>>integer computation. Do you think it is possible to do the same thing
|>>for SBC? Will it give us some extra performance?
|>
|>Unfortunately I'm not familiar with fixed-point arithmetics, especially
|>with how to handle multiplication. So if anyone who has done this before
|>would step forward ...
|>
|>Well, I did some naive tests: I probably did something wrong, but I'm
|>not seeing any significant difference between floating point and fixed
|>point (that is: integer). For multiplication the difference is not
|>noticeable (1.38s vs. 1.36s in my test program) and for addition it is
|>not that big (0.77s vs. 0.47s).
|>
|>I guess we'll be fine using floating point as long as there is an FPU.
|
|
| we can optimize at any time if needed, because the SBC API should hide
| this stuff. For me this sounds perfect for a diploma thesis for someone
| interested in audio codec stuff and Bluetooth.

*raising hand*

thing is, on modern CPU you won't get much speedup with fixed point
stuff, because the main advantage was eliminated by Intel when they
build the pseudo-pipes into their FPU's. That's why id used floating
point operations for gfx for the first time, making life for non-Pentium
owners really hard. AMD also has the pseudo-pipes, and modern
multiplication/devision on FPU is very fast.

But of course there are still some cycles to kill in audio processing
always. I'll advertise this project to my professor...

cu,
~  Lars
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.3 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org

iD8DBQFBpnVHQWC6DTWkDAoRAgkgAKDAZ9hRDYGRP4sNtuJKFFu/0zcomQCgmG8v
UoPSMR/LGba03dC7OsdwkUM=
=vL5b
-----END PGP SIGNATURE-----


-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now. 
http://productguide.itmanagersjournal.com/
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel

  reply	other threads:[~2004-11-26  0:14 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-11-25  5:02 [Bluez-devel] more encoder stuff Brad Midgley
2004-11-25  6:02 ` Marcel Holtmann
2004-11-25  6:14 ` Henryk Plötz
2004-11-25  6:51   ` Marcel Holtmann
2004-11-25 14:35     ` Lars Grunewaldt
2004-11-25 23:06     ` Henryk Plötz
2004-11-25 23:23       ` Marcel Holtmann
2004-11-26  0:14         ` Lars Grunewaldt [this message]
2004-11-26  0:44           ` Marcel Holtmann
2004-11-26  0:57             ` Lars Grunewaldt

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=41A67548.90805@dark-reality.de \
    --to=lgw@dark-reality.de \
    --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