From: "guang" <m9187@cn.ee.ccu.edu.tw>
To: <bluez-users@lists.sourceforge.net>
Subject: [Bluez-users] SCO question ?
Date: Thu, 22 Apr 2004 00:31:22 +0800 [thread overview]
Message-ID: <003501c427be$15781fc0$7b6b7b8c@yaya> (raw)
[-- Attachment #1: Type: text/plain, Size: 2354 bytes --]
Hi all:
I have a apinion about voice data, but I don't know whether it is correct or not.
Please give me some comments.
If we type "hciconfig hci0 voice" and it will appear this on my PC:
[root@bluez root]# hciconfig hci0 voice
hci0: Type: USB
BD Address: 00:09:DD:xx:xx:xx ACL MTU: 192:8 SCO MTU: 64:8
Voice setting: 0x0060 (Default Condition)
Input Coding: Linear
Input Data Format: 2's complement
Input Sample Size: 16 bit
# of bits padding at MSB: 0
Air Coding Format: CVSD
And my viewpoint is as below:
1. Input Coding : Linear --> quantification and frequency are a ratio of equality.
2. Input Data Format: 2's complement --> ???? I don't know what's mean.
3. Input Sample Size: 16 bit --> per sample is used 16 bit to indicate.
4. Air Coding Format: CVSD --> Voice is sampled by soundcard , then Baseband covert these data using CVSD codec and translate these data on air.
As above, I give a conclusion:
I can extract voice datas from SCO socket, and these data are coded by PCM (linear, 16 bit/per sample, sample rate = 8k).
ex:
outgoing voice data:
soundcard sco socket Baseband
| | |
| 8k sample rate | |
| ,16bit/sample | |
voice --->|-------------------->|----------->|---->CVSD data
| | |
| | |
incoming voice data:
Baseband sco socket soundcard Application
| | | |
| linear PCM | | 8k sample rate |
| ,16bit/sample | | 16 bit/sample |
CVSD ---->|------------------->|---------->|------------------->|---->analogy voice
| | | |
| | | |
As above , that are my concept, Is my concept correct?
Please give me some comments.
Thank you .
[-- Attachment #2: Type: text/html, Size: 6693 bytes --]
reply other threads:[~2004-04-21 16:31 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='003501c427be$15781fc0$7b6b7b8c@yaya' \
--to=m9187@cn.ee.ccu.edu.tw \
--cc=bluez-users@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