public inbox for linux-bluetooth@vger.kernel.org
 help / color / mirror / Atom feed
From: James Courtier-Dutton <James@superbug.demon.co.uk>
To: Mauro Tortonesi <mtortonesi@ing.unife.it>
Cc: BlueZ Mailing List <bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] sco link help needed
Date: Wed, 25 Feb 2004 14:22:56 +0000	[thread overview]
Message-ID: <403CAFC0.50807@superbug.demon.co.uk> (raw)
In-Reply-To: <200402251359.00791.mtortonesi@ing.unife.it>

Mauro Tortonesi wrote:
> 
> i have been trying to transfer pcm data over a sco socket both using scotest 
> and other similar apps of mine, but the actual data tranferred were only a 
> bunch of random bytes, completely unrelated to the data sent. moreover, the 
> behaviour of sco links is very unreliable. in my tests i have used several 
> usb dongles with CSR chips (firmware versions ranging from HCI 15.3 to HCI 
> 16.4) and kernel versions from 2.4.22 to 2.4.25-pre7.
> 
> you have told us many times that there are strong limitations in what you can 
> do with sco sockets, but i still can't understand what are these limitations. 
> i have tried searching trough the archives but i couldn't find anything 
> interesting about this.

The standard SCO link takes data from the user app. The CSR chip (any 
bluetooth device in fact) will take that data and treat it as Audio PCM 
samples. the CSR chip will then use a LOSSY codec called CVSD and 
transmit those samples over the air. Due to interference, some of the 
samples in the air get lost. At the receiving end, CVSD is converted 
back into PCM audio. If any samples have been lost in the air, they are 
replaced with duplicate of the previous sample.
Due to the lossy nature of the CVSD codec, the actual PCM values will be 
different at the destination end as they were at the source end. But the 
differences will be such that they are mostly unnoticeable to the human 
ear. So, if you are wishing to transfer anything other than Sound across 
a SCO link, change your mind. If you look at the video streaming 
bluetooth profiles, you will see that they all use Bulk transfers.
Some CSR chips try to include a "Transparent" feature, which disables 
the CVSD codec, and passes samples directly onto the air, but that also 
has problems associated with it.

If your usb device can do Interrupt OUT, use that instead if you need 
low latency output. Some USB dongles can do it, some cannot.

Cheers
James


-------------------------------------------------------
SF.Net is sponsored by: Speed Start Your Linux Apps Now.
Build and deploy apps & Web services for Linux with
a free DVD software kit from IBM. Click Now!
http://ads.osdn.com/?ad_id=1356&alloc_id=3438&op=click
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel

  parent reply	other threads:[~2004-02-25 14:22 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-02-19 14:36 [Bluez-devel] sco link help needed Simon Vogl
2004-02-19 15:29 ` Fred Schättgen
2004-02-21 14:37   ` James Courtier-Dutton
2004-02-22 12:27     ` Marcel Holtmann
2004-02-22 20:53       ` James Courtier-Dutton
2004-02-22 21:30         ` Marcel Holtmann
2004-02-22 22:04           ` James Courtier-Dutton
2004-02-22 22:09             ` Marcel Holtmann
2004-02-22 23:37               ` James Courtier-Dutton
2004-02-23  7:55                 ` Marcel Holtmann
2004-02-25 12:59                   ` Mauro Tortonesi
2004-02-25 13:25                     ` Marcel Holtmann
2004-02-25 14:04                       ` Mauro Tortonesi
2004-02-25 14:23                         ` Marcel Holtmann
2004-02-25 15:35                           ` Mauro Tortonesi
2004-02-25 15:37                             ` Marcel Holtmann
2004-02-25 15:46                               ` Mauro Tortonesi
     [not found]                           ` <1077728432.6021.522.camel@localhost>
2004-02-25 17:16                             ` Marcel Holtmann
2004-02-25 17:27                               ` Nils Faerber
2004-02-25 14:30                         ` James Courtier-Dutton
2004-02-25 14:59                           ` Dr. Simon Vogl
2004-02-25 15:09                             ` Marcel Holtmann
2004-02-25 14:22                     ` James Courtier-Dutton [this message]
2004-02-23 16:35               ` libs2 and utils2 Aaron Klish
2004-02-23 17:19                 ` [Bluez-devel] " Marcel Holtmann
2004-02-22 21:54         ` [Bluez-devel] sco link help needed Fred Schättgen
2004-02-22 22:00           ` Marcel Holtmann
2004-02-22 22:35             ` Fred Schättgen
2004-02-22 12:44     ` Dr. Simon Vogl

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=403CAFC0.50807@superbug.demon.co.uk \
    --to=james@superbug.demon.co.uk \
    --cc=bluez-devel@lists.sourceforge.net \
    --cc=mtortonesi@ing.unife.it \
    /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