From: Brad Midgley <bmidgley@xmission.com>
To: bluez-devel@lists.sourceforge.net
Subject: Re: [Bluez-devel] sbc synthesis inconsistencies
Date: Mon, 05 Sep 2005 07:42:15 -0600 [thread overview]
Message-ID: <431C4B37.4030004@xmission.com> (raw)
In-Reply-To: <Pine.LNX.4.33.0509051123130.25062-100000@redbean.intranet.gw-instruments.de>
Peter
> outer loop goes from i=0 up to i=4 -> 5 times * 8 * 2 = 80
Yes, thanks... I missed the <= (working too late).
I also remembered that Henryk was always testing the decoder against sbc
files on the filesystem which simplifies testing. I'm going to have
another whack at the simplification step and then try unrolling things.
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
prev parent reply other threads:[~2005-09-05 13:42 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-04 5:07 [Bluez-devel] sbc synthesis inconsistencies Brad Midgley
2005-09-05 9:24 ` Peter Wippich
2005-09-05 13:42 ` 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=431C4B37.4030004@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.