From: Marcel Holtmann <marcel@holtmann.org>
To: BlueZ development <bluez-devel@lists.sourceforge.net>
Cc: 'Frans de Bont' <frans.de.bont@philips.com>
Subject: Re: [Bluez-devel] Bad encoding performance of Linux SBC audio codec
Date: Mon, 27 Oct 2008 19:03:43 +0100 [thread overview]
Message-ID: <1225130623.7157.10.camel@californication> (raw)
In-Reply-To: <001501c9381a$022b7f40$06827dc0$@de>
Hi Christian,
> I have made some extensive study on the compression performance of Linux's
> SBC audio codec in comparison to the reference implementation.
>
> I am sorry to say that the audio quality of the open source version of SBC
> is far worse than the reference implementation.
>
> Can anybody confirm these results?
> Do you have any idea why the performance is so worse?
are you talking about the encoder or the decoder. For the encoder, I
can't see the big difference. For the decoder you can clearly hear that
we get the volume wrong.
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 18:03 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 [this message]
2008-10-27 19:13 ` Brad Midgley
2008-10-27 19:41 ` Marcel Holtmann
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=1225130623.7157.10.camel@californication \
--to=marcel@holtmann.org \
--cc=bluez-devel@lists.sourceforge.net \
--cc=frans.de.bont@philips.com \
/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.