linux-bluetooth.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Victor Shchebatyuk <victor@win.tue.nl>
To: bluez-devel@lists.sourceforge.net
Subject: Re: [Bluez-devel] Nokia 770 and bluetooth audio
Date: Sun, 09 Oct 2005 14:25:08 +0200	[thread overview]
Message-ID: <1128860708.8700.12.camel@localhost.localdomain> (raw)
In-Reply-To: <1128849280.15821.7.camel@blade>

Hi all,

It would be nice to have at least a piece of advise from those
mysterious people who tell all those things about the optimization :)

I belive that 32-bit is enough (I saw it working in some other
implementations with excellent sound quality), but it shouldn't be done
in the straight forward way as it is done now. I'm going to look at it
in the nearest future anyway...

I've looked only at the filter-bank code, what is outside probably can
me improved...

Regards,
    Victor.

On Sun, 2005-10-09 at 11:14 +0200, Marcel Holtmann wrote:
> Hi Brad,
> 
> > > if I am not mistaken, then the integration into GStreamer will solve all
> > > the problems. However we need a good SBC encoder for this first. May you
> > > wanna give an update on its current status.
> > 
> > Victor's changes to our encoder give reasonable performance on arm (<10% 
> > of cpu on an arm9 400mhz I think). It uses 64-bit integer math and we 
> > expect there is room for even more optimization using a lossier 32-bit 
> > version (the 32-bit stuff is stubbed out but disabled for now since it's 
> > incomplete)
> 
> from what other people told me about SBC, a 32-bit version will be
> enough for good quality audio.
> 
> > In addition to switching to integer ops, Victor unrolled loops and 
> > reworked some of the tables so less stuff has to be computed at runtime.
> 
> I also heard that there are a lot of possible optimizations, because the
> example code in the specification sucks totally.
> 
> Regards
> 
> Marcel
> 
> 
> 
> 
> -------------------------------------------------------
> This SF.Net email is sponsored by:
> Power Architecture Resource Center: Free content, downloads, discussions,
> and more. http://solutions.newsforge.com/ibmarch.tmpl
> _______________________________________________
> Bluez-devel mailing list
> Bluez-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/bluez-devel



-------------------------------------------------------
This SF.Net email is sponsored by:
Power Architecture Resource Center: Free content, downloads, discussions,
and more. http://solutions.newsforge.com/ibmarch.tmpl
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel

  reply	other threads:[~2005-10-09 12:25 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-10-07 22:35 [Bluez-devel] Nokia 770 and bluetooth audio Brad Midgley
2005-10-08 12:33 ` Marcel Holtmann
2005-10-09  5:48   ` Brad Midgley
2005-10-09  9:14     ` Marcel Holtmann
2005-10-09 12:25       ` Victor Shchebatyuk [this message]
2005-10-09 13:22         ` Marcel Holtmann
2005-10-09 15:49         ` 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=1128860708.8700.12.camel@localhost.localdomain \
    --to=victor@win.tue.nl \
    --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;
as well as URLs for NNTP newsgroup(s).