All of lore.kernel.org
 help / color / mirror / Atom feed
From: Brad Midgley <bmidgley@xmission.com>
To: BlueZ Mailing List <bluez-devel@lists.sourceforge.net>
Subject: [Bluez-devel] sbc synthesis inconsistencies
Date: Sat, 03 Sep 2005 23:07:23 -0600	[thread overview]
Message-ID: <431A810B.2060705@xmission.com> (raw)

Guys,

Have any of you looked closely at this? It comes straight from the spec 
for a2dp on page 66:


	/* Build a 80 values vector U */
	for (i = 0; i <= 4; i++) {
		for (j = 0; j < 8; j++) {
			state->U[ch][i * 16 + j] = state->V[ch][i * 32 + j];
			state->U[ch][i * 16 + j + 8] = state->V[ch][i * 32 + j + 24];
		}
	}

But isn't this code only populating u[ch][0..63] and not through 79 like 
the comment suggests? So the u[ch][64..79] terms are always 0 right?

This isn't the only thing that looks wrong in the spec. We also have a 
sliding window of v[] values that moves 16 values in each pass. The 
vector is 160 elements long even though the code above never accesses 
anything beyond the 128th value!

It's amazing this stuff even works as poorly specified as it is :(

BTW, in our code it looks like sbc_synthesize_eight was multiplying 
sbc_proto_8_80 by -4 where it should be -8. I changed that in cvs.

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

             reply	other threads:[~2005-09-04  5:07 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-09-04  5:07 Brad Midgley [this message]
2005-09-05  9:24 ` [Bluez-devel] sbc synthesis inconsistencies Peter Wippich
2005-09-05 13:42   ` 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=431A810B.2060705@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.