From: "Brad Midgley" <bmidgley@gmail.com>
To: "BlueZ development" <bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] FW: Loss concealment with SBC codec
Date: Tue, 12 Feb 2008 12:39:32 -0700 [thread overview]
Message-ID: <d89ddf300802121139p12c7e8d4y73e6d1cd995a0075@mail.gmail.com> (raw)
In-Reply-To: <Pine.LNX.4.64.0802121001010.3841@xena.cft.ca.us>
Hey
> I'm not a codec guru, but my experience with SBC has not been wonderful.
the codec settings may make a difference here. 4 subband-encoded audio
sounds better. There are also parts of the code we will target for
better numerical accuracy once some bugfixes are complete.
for devel-related issues, see http://wiki.bluez.org/wiki/SBC
> (Does the Bluetooth stack have a feature to swallow SBC coded material
> directly, rather than insisting that the client decode SBC to raw, then the
> audio service re-codes raw to SBC?)
yes. If you use gstreamer, you can separate a2dp transmission from the
codec. It can accept sbc coded material and with a gstreamer patch it
can accept mp3 material (provided your headset has an mp3 decoder).
> > If the CRC8 is wrong, does sbc_decode function conceals the lost frame? If
> > not, did you hear anything about a packet loss concealment algorithm for
> > SBC? Any work on that?
there is no attempt at packet loss concealment, but we're not opposed
to the idea :)
--
Brad
-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
prev parent reply other threads:[~2008-02-12 19:39 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-12 16:01 [Bluez-devel] FW: Loss concealment with SBC codec Christian Hoene
2008-02-12 18:21 ` Jim Carter
2008-02-12 19:39 ` Brad Midgley [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=d89ddf300802121139p12c7e8d4y73e6d1cd995a0075@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