public inbox for linux-bluetooth@vger.kernel.org
 help / color / mirror / Atom feed
From: Frederic Dalleau <frederic.dalleau@access-company.com>
To: BlueZ development <bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] CVS audio-api.txt : 1st question
Date: Thu, 05 Jul 2007 16:12:17 +0200	[thread overview]
Message-ID: <468CFC41.8090404@access-company.com> (raw)
In-Reply-To: <468CE233.8000909@free.fr>

Hi,

>    - Either perform the audio routing at the system level (desktop PC 
> case), the best candidate today being a sound server like pulseaudio.
>   
In the smartphone scenario, there are some streams that are not handled 
by the processor. This is typically the case if you have a phone module 
wired to the bluetooth pcm. Today's smartphones even have a hardware 
routing chip capable of mixing and routing streams. Example inputs are 
radio and phone module, example outputs are speaker, loudspeaker, 
earphone and bluetooth.

The audio router should be able to take these streams into account. 
Having a separate global audio routing would be very flexible. This 
would allow to fit a large number of hardware platforms.

Last, there should be a way to distinguish between different streams 
natures : for example an alert should not interfere with a voip call .

BR,
Frederic



-------------------------------------------------------------------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel

  parent reply	other threads:[~2007-07-05 14:12 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-06-29 15:21 [Bluez-devel] CVS audio-api.txt : 1st question Fabien Chevalier
2007-06-29 18:10 ` Luiz Augusto von Dentz
2007-06-29 20:38   ` Brad Midgley
2007-07-02 17:03   ` Fabien Chevalier
2007-07-03  3:31     ` Brad Midgley
2007-07-03  8:04       ` Fabien Chevalier
2007-07-03 19:54         ` Luiz Augusto von Dentz
2007-07-03 21:08           ` Brad Midgley
2007-07-03 22:25             ` Luiz Augusto von Dentz
2007-07-04  1:57             ` Marcel Holtmann
2007-07-05 12:21               ` Fabien Chevalier
2007-07-05 13:53                 ` Luiz Augusto von Dentz
2007-07-05 15:48                   ` Fabien Chevalier
2007-07-05 14:12                 ` Frederic Dalleau [this message]
2007-07-05 15:55                   ` Fabien Chevalier
2007-07-05 16:40                 ` Brad Midgley
2007-07-06  7:43                   ` Fabien Chevalier
2007-07-06 13:12                     ` Luiz Augusto von Dentz
2007-07-06 13:32                       ` Fabien Chevalier
2007-07-06 13:43                         ` Frederic Dalleau
2007-07-06 15:01                           ` Luiz Augusto von Dentz
2007-07-06 17:07                             ` Fabien Chevalier
2007-07-06 23:44                               ` Brad Midgley
2007-07-07  6:29                                 ` Luiz Augusto von Dentz
2007-07-11 17:33                                   ` Fabien Chevalier
2007-07-11 21:56                                     ` Brad Midgley
2007-07-06 15:24                           ` Fabien Chevalier
2007-07-06 15:38                             ` Frederic Dalleau
2007-07-06 16:56                               ` Fabien Chevalier
2007-07-05 12:53           ` 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=468CFC41.8090404@access-company.com \
    --to=frederic.dalleau@access-company.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