All of lore.kernel.org
 help / color / mirror / Atom feed
From: Brad Midgley <bmidgley@xmission.com>
To: BlueZ development <bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] SBC codec, joint stereo mode
Date: Thu, 04 Jan 2007 10:38:11 -0700	[thread overview]
Message-ID: <459D3B83.5050701@xmission.com> (raw)
In-Reply-To: <459D3730.6080504@gmx.de>

Siegbert

> Yep, now it makes sense.
> BTW, is this the right list to ask SBC-specific questions? I have some 
> more general questions, e.g. I don't quite understand the rationale 
> behind the codec definition: If you choose joint mode for encoding, it 
> happens that the encoder does not use joint mode for all subbands. But 
> why? Saving bits? If anybody has a pointer to some documentation for 
> SBC, which explains the design decisions I would be really happy.

yes this is the right place.

I haven't worked on it in a while so your question doesn't ring a
bell... I do need to get back into it to re-roll the encoder and
eliminate the inner loop memory move.

Brad

-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel

      reply	other threads:[~2007-01-04 17:38 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-01-04 14:36 [Bluez-devel] SBC codec, joint stereo mode Siegbert Baude
2007-01-04 16:09 ` Frédéric DALLEAU
2007-01-04 17:19   ` Siegbert Baude
2007-01-04 17:38     ` 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=459D3B83.5050701@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.