From: Marcel Holtmann <marcel@holtmann.org>
To: BlueZ development <bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] Bad encoding performance of Linux SBC audio codec
Date: Mon, 27 Oct 2008 20:41:56 +0100 [thread overview]
Message-ID: <1225136516.7157.22.camel@californication> (raw)
In-Reply-To: <d89ddf300810271213w53d8d179gc3af2f89c37bea47@mail.gmail.com>
Hi Brad,
> > I am sorry to say that the audio quality of the open source version of SBC
> > is far worse than the reference implementation.
>
> If you are using the standalone "sbc" project at sourceforge, then you
> should try the version inside bluez. The standalone used to simply be
> slower, but we identified & fixed some quality issues too that should
> be backported.
the standalone version should not be used at all at the moment. All
efforts should go into the version included in bluez-4.x.tar.gz.
Regards
Marcel
-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
next prev parent reply other threads:[~2008-10-27 19:41 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-27 9:54 [Bluez-devel] Bad encoding performance of Linux SBC audio codec Christian Hoene
2008-10-27 18:03 ` Marcel Holtmann
2008-10-27 19:13 ` Brad Midgley
2008-10-27 19:41 ` Marcel Holtmann [this message]
2008-10-29 15:30 ` [Bluez-devel] REALLY " Christian Hoene
2008-10-29 22:27 ` Luiz Augusto von Dentz
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=1225136516.7157.22.camel@californication \
--to=marcel@holtmann.org \
--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.