From: Brad Midgley <bmidgley@xmission.com>
To: bluez-devel@lists.sourceforge.net
Subject: Re: [Bluez-devel] sbc and fixed-point progress
Date: Tue, 06 Sep 2005 21:24:29 -0600 [thread overview]
Message-ID: <431E5D6D.20901@xmission.com> (raw)
In-Reply-To: <002001c5b32d$7c610340$0201a8c0@NBVICTOR>
Victor
> I've checked in code for 4-subbands encoder. I've tried it only on x86,
> but I do not expect any surprises on arm.
Again, this is very cool...
> It turned out (probably I should read the specs more carefully) that
> 4-subbands with the same bitpool are actually superior to 8-subbands in
> sound quality, producing 2 times higher bitrate
wow, I hadn't understood that. I always thought 4 subbands sounded
better just because my stereo headset is the sort of tinny in-the-ear
type and I figured 4 subbands was truncating high-end frequencies just
enough to make the sound less shrill.
> I've added the options to specify the number of subbands and use of
> joint stereo to sbcenc.
ok, good.
> Things to do (I'll spend some time on it):
> 1. Check if joint stereo works
> 2. Add command line arguments for bitpool, subbands, joint stereo,
> other? (thrifty flag is a bit obscure)
yes, "thrifty" was a quick hack
> 4. Check/tune the error introduced by fixed point conversion (this can
> be done comparing to old floating point implementation, cause current is
> using int32_t for subbands, which might introduce some error in the
> output stream)
how is 32 bit maths selected? I assume we have to tweak the source to
try it...
> 5. There are still some optimizations regarding memcopies....
yes... I've been struggling with this in the decoder...
Brad
-------------------------------------------------------
SF.Net email is Sponsored by the Better Software Conference & EXPO
September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices
Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA
Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
next prev parent reply other threads:[~2005-09-07 3:24 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-28 13:14 [Bluez-devel] sbc and fixed-point progress Victor Shcherbatyuk
2005-07-28 14:59 ` Brad Midgley
2005-07-28 18:41 ` Victor Shcherbatyuk
2005-07-28 19:21 ` Victor Shcherbatyuk
2005-07-28 21:09 ` Brad Midgley
2005-08-21 18:47 ` Victor Shcherbatyuk
2005-08-21 21:56 ` Roberto
2005-08-21 22:24 ` Victor Shcherbatyuk
2005-08-22 6:15 ` Brad Midgley
2005-08-22 7:22 ` Brad Midgley
2005-09-03 15:33 ` Victor Shcherbatyuk
2005-09-03 16:05 ` Brad Midgley
2005-09-06 21:53 ` Victor Shcherbatyuk
2005-09-07 3:24 ` Brad Midgley [this message]
2005-09-03 19:36 ` [Bluez-devel] bcm2035 Oliver Ruiz Dorantes
2005-09-04 12:09 ` Paul Webster
2005-09-04 14:02 ` Oliver Ruiz Dorantes
2005-09-05 4:03 ` Paul Webster
-- strict thread matches above, loose matches on Subject: below --
2005-09-07 7:14 [Bluez-devel] sbc and fixed-point progress Victor Shcherbatyuk
2005-09-07 21:18 ` Victor Shcherbatyuk
2005-08-26 8:07 Victor Shcherbatyuk
2005-08-26 8:02 Victor Shcherbatyuk
2005-08-27 3:01 ` Brad Midgley
2005-08-24 12:18 Victor Shcherbatyuk
2005-08-24 16:40 ` Brad Midgley
2005-08-24 21:06 ` Victor Shcherbatyuk
2005-08-26 5:10 ` Brad Midgley
2005-08-27 22:54 ` Victor Shcherbatyuk
2005-08-28 5:44 ` Brad Midgley
2005-08-28 22:26 ` Victor Shcherbatyuk
2005-08-23 20:42 ` Roberto
2005-08-29 17:08 ` Brad Midgley
2005-08-23 21:10 ` Roberto
2005-08-29 20:18 ` Brad Midgley
2005-08-29 21:04 ` Roberto
2005-08-23 15:00 Victor Shcherbatyuk
2005-08-01 8:20 Victor Shcherbatyuk
2005-08-01 8:41 ` Brad Midgley
2005-07-04 4:03 Brad Midgley
2005-07-04 11:11 ` Marcel Holtmann
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=431E5D6D.20901@xmission.com \
--to=bmidgley@xmission.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.