From: Steven Singer <steven.singer@csr.com>
To: bluez-devel@lists.sourceforge.net
Subject: Re: [Bluez-devel] SCO transparent transmission
Date: Fri, 07 Apr 2006 15:29:03 +0100 [thread overview]
Message-ID: <4436772F.6030300@csr.com> (raw)
In-Reply-To: <fe0a97c20604042223o7c59fb5fq871a004292ac1c55@mail.gmail.com>
Sowmya Gattupalli wrote:
> On 4/4/06, Israel Gu=EDo <israzar@gmail.com> wrote:
>> example, with 0x0063 as voice settings. I have tried it with my Blueto=
oth
> How did u use CVSD when transmitting over sco?? [...]
He was quite clear that he'd used voice settigns 0x0063. The last two
bits indicate transparent coding and not CVSD.
Israel, you need to be sure you're sending data at exactly the right
average data rate. SCO links are synchronous and if you don't provide
data at exactly the right rate then something somewhere in the
system will have to insert or delete samples.
It would also be helpful if you stated what chip and firmware version
you were using.
- Steven
--=20
To access the latest news from CSR copy this link into a web browser: ht=
tp://www.csr.com/email_sig.php
-------------------------------------------------------
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live webcast
and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
next prev parent reply other threads:[~2006-04-07 14:29 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-04 17:44 [Bluez-devel] SCO transparent transmission Israel Guío
2006-04-05 5:23 ` Sowmya Gattupalli
2006-04-07 14:29 ` Steven Singer [this message]
2006-04-08 4:12 ` Sowmya Gattupalli
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=4436772F.6030300@csr.com \
--to=steven.singer@csr.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.