From: "Frédéric DALLEAU" <frederic.dalleau@palmsource.com>
To: BlueZ development <bluez-devel@lists.sourceforge.net>
Subject: [Bluez-devel] Sonorix Headset works with modification + sbc questions
Date: Wed, 02 Aug 2006 11:19:36 +0200 [thread overview]
Message-ID: <44D06E28.1000909@palmsource.com> (raw)
Hi all,
I've got a Sonorix (openbrain?) Headset OBH-100.
As it is a bluetooth.org certified A2DP device, it should have worked =
flawlessly at 44100hz. Maker says a failsafe value is 32000hz bitpool 44.
It had to patch a little bit to make it work :
At 44100 hz, sbc bitpool of 32, music is recognizable but too slow, and =
full of gaps.
At 32000 hz, sbc bitpool of 32, music is good, but 32000hz really loses =
quality. However, all my headsets have worked, but the audio player must =
support the conversion.
At any rate sbc bitpool of 44, music is recognizable but ways ways too =
slow, and full of gaps.
My question is : Are there restriction on using sbc encoder with bitpool =
values other than defaults?
Does anyone know if this formula is right to calculate packet length to =
give to sbc encoder? Should I take bitpool into account?
/// 16 bits * 2 channels * 16 blocks * 8 subbands =3D 4096bits =3D =
512 o/
codesize=3Da2dp->sbc.subbands*a2dp->sbc.blocks*a2dp->sbc.channels*2;
Thank you,
Fr=E9d=E9ric
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys -- and earn cash
http://www.techsay.com/default.php?page=3Djoin.php&p=3Dsourceforge&CID=3DDE=
VDEV
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
reply other threads:[~2006-08-02 9:19 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=44D06E28.1000909@palmsource.com \
--to=frederic.dalleau@palmsource.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.