public inbox for linux-bluetooth@vger.kernel.org
 help / color / mirror / Atom feed
From: "Brad Midgley" <bmidgley@gmail.com>
To: "BlueZ development" <bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] gstreamer regressions
Date: Mon, 28 Jan 2008 20:28:31 -0700	[thread overview]
Message-ID: <d89ddf300801281928t52a561bdye4f72bdb0e5dd1d7@mail.gmail.com> (raw)
In-Reply-To: <d89ddf300801261924t311981depb26f0c90f4bbaed9@mail.gmail.com>

Hey

This isn't really a problem in the gstreamer plugin at all. It
appeared with a gstreamer change in cvs but that was linked to
changing a default encoding parameter. The real issue is our decoder
is overflowing for higher bitpool values. It shows up sooner for 4
subbands and/or mono.

The encoder seems to all be fine but I'll need help straightening this
out. There's no way we can get decent regression testing if our
decoder falls apart.

On Jan 26, 2008 8:24 PM, Brad Midgley <bmidgley@gmail.com> wrote:
> I wrote it up in the wiki (http://wiki.bluez.org/wiki/SBC)

-- 
Brad

-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel

      reply	other threads:[~2008-01-29  3:28 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-01-27  3:24 [Bluez-devel] gstreamer regressions Brad Midgley
2008-01-29  3:28 ` 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=d89ddf300801281928t52a561bdye4f72bdb0e5dd1d7@mail.gmail.com \
    --to=bmidgley@gmail.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