From: Brad Midgley <bmidgley@xmission.com>
To: bluez-devel@lists.sourceforge.net
Subject: Re: [Bluez-devel] Motorola HT820 audio fidelity
Date: Wed, 03 May 2006 23:31:28 -0600 [thread overview]
Message-ID: <445991B0.9030208@xmission.com> (raw)
In-Reply-To: <1146709233.13358.73.camel@pc7.dolda2000.com>
Fredrik
>>> I have Windows in a VMware exactly for things like these, so I could
>>> test that. However, I could find no such thing on bluetooth.org. In
>>> fact, googling for "sbc site:bluetooth.org" only yielded two
>>> insignificant results, so I'm beginning to wonder if I'm doing something
>>> wrong (whatever that'd be...). Any pointers?
>> You can get it but you probably need to be logged into a (free) account:
>>
>> https://www.bluetooth.org/foundry/adopters/document/A2DP_Bitstream/en/1/A2DP_Bitstream.zip
>
> I could get it without an account. I find it rather weird that google
> didn't find it, but oh well.
google won't necessarily "deep link" into sites like bluetooth.org
> Anyway, I tried it, and it was an *enormous* difference. It is true that
> the file encoded by the encoder from bluetooth.org is almost twice as
> large as that encoded by sbcenc as well, but nonetheless, the difference
> in audio quality was huge.
twice as large? could be they're using 4 subbands.
maybe our defaults are too lossy. after calling sbc_init, you can change
sbc.subbands (default 8), sbc.blocks (default 16), sbc.bitpool (default
32). subbands can be 4,8. blocks can be 4,8,12,16. i need to check the
spec on bitpool ranges.
>> we can also compare with our floating point implementation which we have
>> more faith in.
>
> Is this in the CVS tree? I can't seem to find any other encoder than
> sbcenc. (Speaking of which, what's the difference between the "sbc" and
> "sbc32" directories?)
a lot of this will change, but for now, "sbc" has floating, 64-bit
fixed, and 32-bit fixed and chooses one at compile time. you'll get
floating point implementation if you configure without --enable-fixed.
(heh, maybe that's what you're getting even now)
sbc32 was the precursor to separating out the library and has only the
32-bit implementation. it probably isn't even being built.
a2play "sort of" has a flag for choosing encoder settings (-t for
thrifty) but it is pretty rough.
brad
-------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
next prev parent reply other threads:[~2006-05-04 5:31 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-28 0:24 [Bluez-devel] Motorola HT820 audio fidelity Fredrik Tolf
2006-04-28 3:19 ` Brad Midgley
2006-05-01 14:02 ` Fredrik Tolf
2006-05-01 14:48 ` Brad Midgley
2006-05-02 3:39 ` Mayank Batra
2006-05-02 4:49 ` Brad Midgley
2006-05-02 5:01 ` Mayank Batra
2006-05-04 17:28 ` Shawn Rutledge
2006-05-04 17:58 ` Brad Midgley
2006-05-02 11:02 ` Fredrik Tolf
2006-05-02 16:33 ` Brad Midgley
2006-05-04 2:20 ` Fredrik Tolf
2006-05-04 5:31 ` Brad Midgley [this message]
2006-05-04 9:26 ` Sergey Krivov
2006-05-09 3:20 ` Fredrik Tolf
2006-05-09 15:25 ` Brad Midgley
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=445991B0.9030208@xmission.com \
--to=bmidgley@xmission.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 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.