From: Luca Pizzamiglio <pizzamiglio@cefriel.it>
To: bluez-devel@lists.sourceforge.net
Subject: Re: [Bluez-devel] SCO & btsco
Date: Wed, 14 Sep 2005 15:21:23 +0200 [thread overview]
Message-ID: <432823D3.3060705@cefriel.it> (raw)
In-Reply-To: <43280B35.1070303@csr.com>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Thanks, Steven.
I'm sorry for confusion I created.
with sox:
sox -t raw -r 8000 -s -w sound.raw pippo.wav
I build a transformation chain that works.
Thank you.
Cheers,
Pizza
Steven Singer wrote:
> Luca Pizzamiglio wrote:
>
>>bt specification says that bluetooth supports three audio formats:
>>- CVSD
>>- u-law
>>- a-law
>
>
> That's not what the BT spec says, you need to read it more carefully.
>
> BT supports 3 *air* formats: u-law, A-law and CVSD, however, that's
> irrelevant as far as interfacing with the chip is concerned as the
> chip will transcode to and from those formats from and to the HCI
> format (aka the input format).
>
> BT supports the following HCI formats:
>
> 2's complement linear
> 1's complement linear
> sign-magnitude
> unsigned (some devices only)
> u-law
> A-law
>
> The linear formats can be 8 bit, 16 bit or 9..15 bit right aligned
> in a 16 bit word.
>
> The default format - 0x0060 - is CVSD on the air and 16 bit 2's
> complement linear signed on the wire as the output of hciconfig
> clearly states.
>
> Always keep the air format set to CVSD (as the two sides need to agree
> on the air format in order to be able to make a connection and most,
> if not all, Bluetooth devices are set up for CVSD). Make the HCI
> format whatever your program supports.
>
> - Steven
- --
- -------------------------------------------
Luca Pizzamiglio
CEFRIEL - Embedded Systems Design Unit
Via Fucini, 2 - 20133 MILANO (ITALY)
Phone: +39 02 23954 343
e-mail: pizzamiglio@cefriel.it
ICQ: 5046978
- -------------------------------------------
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.7 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org
iD8DBQFDKCPTAoUy56ORfbERAv+XAKCjAVKqVVugB0wTSZFMMjQPFGcIQwCgtdr7
XyCn4ayjOeATXi0ckPA0Njk=
=6h94
-----END PGP SIGNATURE-----
-------------------------------------------------------
SF.Net email is sponsored by:
Tame your development challenges with Apache's Geronimo App Server.
Download it for free - -and be entered to win a 42" plasma tv or your very
own Sony(tm)PSP. Click here to play: http://sourceforge.net/geronimo.php
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
prev parent reply other threads:[~2005-09-14 13:21 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-14 7:51 [Bluez-devel] SCO & btsco Luca Pizzamiglio
2005-09-14 11:36 ` Steven Singer
2005-09-14 13:21 ` Luca Pizzamiglio [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=432823D3.3060705@cefriel.it \
--to=pizzamiglio@cefriel.it \
--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