From: "Luiz Augusto von Dentz" <luiz.dentz@gmail.com>
To: "BlueZ development" <bluez-devel@lists.sourceforge.net>
Cc: Frans de Bont <frans.de.bont@philips.com>
Subject: Re: [Bluez-devel] REALLY Bad encoding performance of Linux SBC audio codec
Date: Wed, 29 Oct 2008 19:27:44 -0300 [thread overview]
Message-ID: <2d5a2c100810291527w6d5c4615udcb450d49e68702@mail.gmail.com> (raw)
In-Reply-To: <004e01c939db$5c241760$146c4620$@de>
Hello,
Thanks for doing those tests, we never really have a method for
testing the sbc codec, so PEAQ could be a good start. By looking the
results it seems that our decoder is not really in good shape, which
is not a surprise since we normally only use the encoder part. As for
comparison with the reference implementation, bluez sbc codec does not
use floating point as the reference codec seems to be using, so this
may well be impacting on quality, although we probably gain some
speed.
Other points we might need to consider:
- Test with different audio source/parameter. (48000hz/mono/28
bitpool is not that common to be used as reference)
- Mono seems to surfer from quality problems which may cause the problem.
- Consider working on a gstreamer element for doing live tests based
on ITU BS.1387 (PEAQ)
- Also consider using liboil as alternative for using floating point.
BTW, don't assume something is bad just because it produces different
results than the reference, as far I can tell you one cannot really
notice _any_ difference between bluez sbc codec and logitech freepulse
e(enhanced)sbc, so on real world we are not that _bad_.
-- =
Luiz Augusto von Dentz
Engenheiro de Computa=E7=E3o
-------------------------------------------------------------------------
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
prev parent reply other threads:[~2008-10-29 22:27 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
2008-10-29 15:30 ` [Bluez-devel] REALLY " Christian Hoene
2008-10-29 22:27 ` Luiz Augusto von Dentz [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=2d5a2c100810291527w6d5c4615udcb450d49e68702@mail.gmail.com \
--to=luiz.dentz@gmail.com \
--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