All of lore.kernel.org
 help / color / mirror / Atom feed
From: Fabien Chevalier <fabchevalier@free.fr>
To: BlueZ development <bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] RE :  SCO on bluez : some architectural tips
Date: Sat, 18 Nov 2006 11:27:23 +0100	[thread overview]
Message-ID: <455EE00B.80504@free.fr> (raw)
In-Reply-To: <7A6DA545D7FDCC4B93DB651FDBC1EDDE4E6EA7@eumonex01.palmsource.com>

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

Hi Frederic

> Hi Fabien,
> 
>> 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. :-)
> 
> A2DP data are certainly not sensitive, but having the sound of your movie playing
> with delay is really unpleasant. So in the end the need for low latency is probably
> the same in SCO and A2DP.

Yes and No :-)
I agree having the sound of your movie played with delay is unpleasant.

However even if it takes one second between the moment the player sents
audio data and the moment it is heared by you, it is this possible to
have audio and video in sync if the player sends desyncs audio and video
 of one second. For instnace, mplayer + and - keys allows you to do just
that.


> 
>>>From my point of vue, having the SCO socket inside application is not needed.
> The benefit is one single unix socket transfer. In a typical video conferencing
> application used on the internet, the delay used for transmitting data will probably
> be by far more important than the delay induced by this transfer. So any gain
> on the SCO side would be made negligible against what is lost during transmission.

I don't agree with that. It's not uncommon these days to have ~ 50 ms
latency between one point fo the internet and the other. (ok not at the
other side of the planet tough :-) )
Let' say you use a unix socket. Sco sockets have a fixed queue length
(something like 1 kb if i remember : this should be checked). Each SCO
packets is 48 bytes, with 'lasts' 3 msec. Which means we can fit
20 packets, or 60 ms data.
Congratulations, we just added more delay that the network itself !! ;-)

Cheers,

Fabien


[-- Attachment #2: 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 #3: 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-18 10:27 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-11-16 20:32 [Bluez-devel] SCO on bluez : some architectural tips Fabien Chevalier
2006-11-16 20:38 ` 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 [this message]
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=455EE00B.80504@free.fr \
    --to=fabchevalier@free.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.