Linux bluetooth development
 help / color / mirror / Atom feed
From: Fredrik Tolf <fredrik@dolda2000.com>
To: bluez-devel@lists.sourceforge.net
Subject: Re: [Bluez-devel] Motorola HT820 audio fidelity
Date: Tue, 02 May 2006 13:02:06 +0200	[thread overview]
Message-ID: <1146567726.13358.40.camel@pc7.dolda2000.com> (raw)
In-Reply-To: <44561FB6.5000306@xmission.com>

On Mon, 2006-05-01 at 08:48 -0600, Brad Midgley wrote:
> Fredrik
> 
> >>It doesn't help that we're typically decoding mp3 and reencoding in sbc.
> >>Loss is really compounded.
> > 
> > 
> > Indeed, that seems to be the problem. I was always under the
> > (uninformed) impression that SBC was lossless, but I just tried
> > re-encoding an MP3 to SBC and playing that SBC with sbcenc and sbcdec,
> > and the exact same audio artifacts are showing themselves when I play
> > back to my normal speaker system as through the headphones.
> 
> You haven't ruled out our implementation of sbc however. We could have
> problems still. Also, there are also some defaults for encoding that
> although set fairly high are not at the max iirc.
> 
> There is/was a reference SBC encoder that is a windows executable
> somewhere at bluetooth.org. Testing with it would let us rule out (or
> implicate) our implementation.

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?

> The spec allows us to negotiate a different codec with the headset. SBC
> is the only required codec. fwiw, I've never seen a headset that accepts
> mp3 or others. I should modify a2play to flag these so they would be
> easier to spot.

Unfortunately, that seems to be no relief in this case. a2play gets only
one acp_seid_info from the headset, so I guess that means that it only
supports SBC, correct?

Fredrik Tolf




-------------------------------------------------------
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

  parent reply	other threads:[~2006-05-02 11:02 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 [this message]
2006-05-02 16:33         ` Brad Midgley
2006-05-04  2:20           ` Fredrik Tolf
2006-05-04  5:31             ` Brad Midgley
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=1146567726.13358.40.camel@pc7.dolda2000.com \
    --to=fredrik@dolda2000.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