Re: [Bluez-devel] CVS audio-api.txt : 1st question

[Fabien Chevalier <fabchevalier@free.fr>]

Hi all,
>> When no device is connected, the plugin will discard or (more
>> preferably) send audio to the wired device. We use connected as a cue
>> that the user wants to use that device for audio.
> 
> no and NO. The Bluetooth plugin is not dealing with any wire connection.
> The plugin has to be simple and can actually be stupid. I don't wanna
> have any intelligence inside the ALSA plugin.
> 

If the ALSA plugin is not dealing with any wire connection, then 
wired/wireless handover has to be performed somewhere else. :-)
Somewhere else should not be the bt audio daemon. Do you imagine what 
will happen when new type of wireless headsets will come out of the hood 
(Wireless USB, Wireless whatever else will happen in the future :-) ) ?
Will we be adding audio daemons on top of each other so that each one 
has the option to perform its on routing business ?

I think we need:
   - Either to let the application perform routing operations (that 
would make sense in Linux Smartphone style devices, where you have a 
very reduced set of applications : phone application, media player)
   - Either perform the audio routing at the system level (desktop PC 
case), the best candidate today being a sound server like pulseaudio.

What do you guys think of that ?
(+1 for pulseaudio for Luiz i think ;-) )

Cheers,

Fabien

-------------------------------------------------------------------------
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