From: Brad Midgley <bmidgley@xmission.com>
To: bluez-devel@lists.sourceforge.net
Subject: Re: [Bluez-devel] sbc decoder unrolled
Date: Fri, 09 Sep 2005 11:59:04 -0600 [thread overview]
Message-ID: <4321CD68.4070800@xmission.com> (raw)
In-Reply-To: <43217888.9030902@csr.com>
Steven
> output of reference encoder + your decoder (spec requires K > 14)
> output of your encoder + reference decoder
> output of your encoder + your decoder
There is a little gotcha here in that we only have a windows binary for
a reference encoder/decoder. I haven't tried to build our stuff in
cygwin or windows dev tools and there are probably things to fix...
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-09 17:59 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-09 5:37 [Bluez-devel] sbc decoder unrolled Brad Midgley
2005-09-09 11:56 ` Steven Singer
2005-09-09 14:16 ` Brad Midgley
2005-09-09 17:59 ` Brad Midgley [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-09-09 9:31 Victor Shcherbatyuk
2005-09-09 13:15 ` Brad Midgley
2005-09-09 13:56 Victor Shcherbatyuk
2005-09-09 18:13 Victor Shcherbatyuk
2005-09-09 18: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=4321CD68.4070800@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox