From: "Christian Hoene" <hoene@uni-tuebingen.de>
To: <bluez-devel@lists.sourceforge.net>
Cc: 'Frans de Bont' <frans.de.bont@philips.com>
Subject: [Bluez-devel] Bad encoding performance of Linux SBC audio codec
Date: Mon, 27 Oct 2008 10:54:27 +0100 [thread overview]
Message-ID: <001501c9381a$022b7f40$06827dc0$@de> (raw)
Hello,
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?
With best regards,
Christian
--------------------------------------------------------
Dr.-Ing. Christian Hoene
Computer Networks and Internet, University of T=FCbingen
Sand 13, 72076 T=FCbingen, Germany, Phone +49 7071 2970532
http://net.informatik.uni-tuebingen.de/~hoene
-------------------------------------------------------------------------
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 priz=
es
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=3D100&url=3D/
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
next reply other threads:[~2008-10-27 9:54 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-27 9:54 Christian Hoene [this message]
2008-10-27 18:03 ` [Bluez-devel] Bad encoding performance of Linux SBC audio codec Marcel Holtmann
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='001501c9381a$022b7f40$06827dc0$@de' \
--to=hoene@uni-tuebingen.de \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox