public inbox for linux-bluetooth@vger.kernel.org
 help / color / mirror / Atom feed
From: Fabien Chevalier <fabchevalier@free.fr>
To: BlueZ development <bluez-devel@lists.sourceforge.net>
Subject: [Bluez-devel] [RFC] : Bluez audio routing: introducing switch alsa plugin
Date: Sun, 10 Dec 2006 16:51:59 +0100	[thread overview]
Message-ID: <457C2D1F.1050605@free.fr> (raw)

All,

I got here a suggestion for audio routing.
I take here as assumption that it is a possibility that sco and a2dp
plugins are different.

The idea is to bring in the picture a new plugin that i would call
conveniently the 'switch' plugin.
As its name suggests, its role would be to route to either one PCM
stream or another PCM.

We could imagine that per default the plugin would route audio to wired
PCM IO, and when notified that a alternate PCM is ready, would switch to
this plugin.

This would give sth like that:

audio application --> switch plugin --> wired io PCM
			|
			|
			----> bluetooth plugin --> bt.audiod


This is an audio routing suggestion that could be used for both SCO and
A2DP.

as usual, comments are welcomed,

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=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel

             reply	other threads:[~2006-12-10 15:51 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-12-10 15:51 Fabien Chevalier [this message]
2006-12-11 15:29 ` [Bluez-devel] [RFC] : Bluez audio routing: introducing switch alsa plugin Brad Midgley

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=457C2D1F.1050605@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox