From: Brad Midgley <bmidgley@xmission.com>
To: BlueZ development <bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] org.bluez.Audio
Date: Wed, 06 Dec 2006 14:24:02 -0700 [thread overview]
Message-ID: <457734F2.30204@xmission.com> (raw)
In-Reply-To: <45772B71.5020505@vasmac.com>
Jose
> I think that bt.audiod should only handle the audio control portion.
> The audio plugins should do direct bluetooth I/O.
I'll update the page then. I won't rule out having bt.audiod manage a
file descriptor for the sco channel and pass it around like Fabien did
in his daemon. Only one app could use the sco channel at a time.
In the case of a2dp where we're already dealing with long latencies, I
would like to have bt.audiod mix, encode, and deliver the audio. The
challenge there is to keep the latency consistent so a video player
could accommodate it.
Brad
-------------------------------------------------------------------------
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
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
next prev parent reply other threads:[~2006-12-06 21:24 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-06 5:31 [Bluez-devel] org.bluez.Audio Brad Midgley
2006-12-06 20:43 ` Jose Vasconcellos
2006-12-06 21:24 ` Brad Midgley [this message]
2006-12-10 15:51 ` Fabien Chevalier
2006-12-12 16:45 ` Brad Midgley
2006-12-12 19:53 ` Fabien Chevalier
2006-12-12 20:24 ` Brad Midgley
2006-12-10 15:51 ` 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=457734F2.30204@xmission.com \
--to=bmidgley@xmission.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox