From: Fabien Chevalier <fabchevalier@free.fr>
To: BlueZ development <bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] RE : RE : SCO on bluez : some architectural tips
Date: Sun, 19 Nov 2006 17:54:24 +0100 [thread overview]
Message-ID: <45608C40.3050307@free.fr> (raw)
In-Reply-To: <7A6DA545D7FDCC4B93DB651FDBC1EDDE4E6EAE@eumonex01.palmsource.com>
Hi Frederic,
> =
> We won't be able to use +/- in a game or system sound!
Of course we can't :-). But a2dp has never been designed for that =
either. It has been designed so that handset makers be able to stream =
music over headsets.
> =
>> 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 !! ;-)
> =
> Did you mean Unix socket have a fixed queue length? =
Yes they did. I had to dig into kernel sources to find that :-)
> If buffering takes place
> inside the SCO socket, then work is due to the socket itself. In both cas=
es,
> I would be surprised if this wasn't tunable.
SCO socket queue is tunable, provided you use my flow control patch... =
otherwise it's not.
> =
> Nevertheless, there is no need to know the buffer size : if the buffer was
> 1 Mb long would you wait for it to be full before reading data? =
Frederic, this is not the point. Of course we won't wait the buffer to =
be full before sending audio data to the remote device.
But if buffer is 1 MB long, then the application that plays sound will =
fill up the buffer faster that the device reads. Which means at one =
point or another, the buffer will be full, thus introducing audio =
latency equal to the time it takes to empty the buffer
> =
> Last, benchmarks on the net measure unix socket latency using =B5s unit.
> =
That easy to say. Just give it a try and you might have some surprises :-)
> =
> Probably the best way to figure out the best architecture is to have both=
and
> measure.
I 100% agree with that. :-)
I can provide wome source code that doe just that to whoever is =
interested in testing this daemon approach.
Cheers,
Fabien
-------------------------------------------------------------------------
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=3Djoin.php&p=3Dsourceforge&CID=3DDE=
VDEV
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
prev parent reply other threads:[~2006-11-19 16:54 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
2006-11-18 11:44 ` [Bluez-devel] RE : " Frederic Dalleau
2006-11-19 5:30 ` Brad Midgley
2006-11-19 16:54 ` Fabien Chevalier [this message]
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=45608C40.3050307@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.