All of lore.kernel.org
 help / color / mirror / Atom feed
From: Fabien Chevalier <fchevalier@silicom.fr>
To: BlueZ development <bluez-devel@lists.sourceforge.net>
Subject: [Bluez-devel] SCO on bluez : some architectural tips
Date: Thu, 16 Nov 2006 21:32:52 +0100	[thread overview]
Message-ID: <455CCAF4.8020007@silicom.fr> (raw)

[-- Attachment #1: Type: text/plain, Size: 1285 bytes --]


Marcel & Brad,

I send you this e-mail to share some of the experience acquired while 
writing bluez-headset.
There is much to share but i'll do it bits at a time, it will be more 
easy to digest than a 300 lines e-mail :-).

So let's talk about SCO today. :-)

SCO is designed for low quality (poor Hz rate). It's only application is 
telephony.
However it requires *really* low latency.

At first hand i tried the same approach as you did, which means route 
audio trough a daemon that could do all kind a of funny and interesting 
stuff in it. This would have been a very interesting approach.
However result was really bad, for two reasons:
 * The unix socket between application and the daemon would queue some 
data, which would add unwanted delay.
 * And moreover, the fact to send the data trough a 3rd party unix 
process (the daemon), resulted in jitter due to scheduling behaviour. Do 
avoid hearing audio cuts in the headset, i had to add run daemon as root 
and decrease its nice value to unsane levels.

Due to this, i had to fall back on having the SCO file descriptor 
available in application process space.

However, due to the fact a2dp is not supposed to be used for delay sensitive
 streams, it is possible to use this architecture for a2dp. :-)

Cheers,

Fabien

[-- Attachment #2: fchevalier.vcf --]
[-- Type: text/x-vcard, Size: 241 bytes --]

begin:vcard
fn:Fabien CHEVALIER
n:CHEVALIER;Fabien
org:SILICOM
adr:;;4 rue de Jouanet;RENNES ATALANTE;;35700;FRANCE
email;internet:fchevalier@silicom.fr
title:Software & Studies Engineer
tel;work:+33 (0) 2 99 84 17 17
version:2.1
end:vcard


[-- Attachment #3: Type: text/plain, Size: 347 bytes --]

-------------------------------------------------------------------------
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=join.php&p=sourceforge&CID=DEVDEV

[-- Attachment #4: Type: text/plain, Size: 164 bytes --]

_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel

             reply	other threads:[~2006-11-16 20:32 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-11-16 20:32 Fabien Chevalier [this message]
2006-11-16 20:38 ` [Bluez-devel] SCO on bluez : some architectural tips Albert Huang
2006-11-17  6:46   ` [Bluez-devel] RE : " Frederic Dalleau
2006-11-18 10:02   ` [Bluez-devel] " Fabien Chevalier
2006-11-16 21:56 ` Brad Midgley
2006-11-18 10:07   ` Fabien Chevalier
2006-11-19  5:45     ` Brad Midgley
2006-11-19 17:02       ` Fabien Chevalier
2006-11-17  6:45 ` [Bluez-devel] RE : " Frederic Dalleau
2006-11-18 10:27   ` Fabien Chevalier
2006-11-18 11:44     ` [Bluez-devel] RE : " Frederic Dalleau
2006-11-19  5:30       ` Brad Midgley
2006-11-19 16:54       ` Fabien Chevalier

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=455CCAF4.8020007@silicom.fr \
    --to=fchevalier@silicom.fr \
    --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.