From: "Brad Midgley" <bmidgley@gmail.com>
To: "BlueZ development" <bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] FW: REALLY Bad encoding performance of Linux SBC audio codec
Date: Thu, 30 Oct 2008 12:48:37 -0600 [thread overview]
Message-ID: <d89ddf300810301148s6afa46a0v2bd8ce1ed844a60e@mail.gmail.com> (raw)
In-Reply-To: <1225380052.4626.8.camel@hoene-desktop>
Christian
> the sound quality got better. Still, both encoder and decoder are not as
> good as the reference.
It would be ideal to have automated tests for codec quality that don't
require windows and that we could run before commits to track our
progress. We could prepare some encoding/decoding samples with the
reference codec and store them in the project or somewhere online. The
one test we couldn't do this way is to encode with our codec and
decode with the reference.
Are there free tools for checking the quality and for comparing
signal/noise and overall volume? If you can detail the process you use
that would help.
thanks
Brad
-------------------------------------------------------------------------
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-30 18:48 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-30 14:54 [Bluez-devel] FW: REALLY Bad encoding performance of Linux SBC audio codec Christian Hoene
2008-10-30 15:20 ` Christian Hoene
2008-10-30 15:46 ` Luiz Augusto von Dentz
2008-10-30 16:07 ` Christian Hoene
2008-10-30 18:02 ` Marcel Holtmann
2008-10-30 18:03 ` Marcel Holtmann
2008-10-30 18:48 ` Brad Midgley [this message]
2008-10-31 10:23 ` Christian Hoene
2008-10-31 11:10 ` Craig Southeren
2008-10-31 18:50 ` Marcel Holtmann
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=d89ddf300810301148s6afa46a0v2bd8ce1ed844a60e@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