From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Message-ID: Date: Fri, 1 Jun 2007 22:43:31 -0600 From: "Brad Midgley" To: "BlueZ development" MIME-Version: 1.0 Subject: [Bluez-devel] fleshing out audio daemon scenarios Reply-To: BlueZ development List-Id: BlueZ development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============2050881289==" Sender: bluez-devel-bounces@lists.sourceforge.net Errors-To: bluez-devel-bounces@lists.sourceforge.net --===============2050881289== Content-Type: multipart/alternative; boundary="----=_Part_9191_7635848.1180759411129" ------=_Part_9191_7635848.1180759411129 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline Hey I spent some time digging through the alsa api and experimenting with the daemons in plugz. I also looked over the traces as some alsa clients including kphone and twinkle. I came across two problems to the design we've discussed * for combo headsets, we incorrectly assumed we'd get a device open that was either write-only or read-write and use that to decide whether to use a2dp or sco * we didn't have any provisions for two headsets connecting independently which we might as well get right (imagine a voip appliance) So I think a solution is not that complicated, but it gets wordy in explaining it all out. I did a writeup in the wiki http://wiki.bluez.org/wiki/Audio#Requirementsoftheaudioservice-alsaplugininterface Brad ------=_Part_9191_7635848.1180759411129 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline Hey

I spent some time digging through the alsa api and experimenting with the daemons in plugz. I also looked over the traces as some alsa clients including kphone and twinkle.

I came across two problems to the design we've discussed

* for combo headsets, we incorrectly assumed we'd get a device open that was either write-only or read-write and use that to decide whether to use a2dp or sco
* we didn't have any provisions for two headsets connecting independently which we might as well get right (imagine a voip appliance)

So I think a solution is not that complicated, but it gets wordy in explaining it all out. I did a writeup in the wiki

http://wiki.bluez.org/wiki/Audio#Requirementsoftheaudioservice-alsaplugininterface

Brad

------=_Part_9191_7635848.1180759411129-- --===============2050881289== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline ------------------------------------------------------------------------- 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/ --===============2050881289== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Bluez-devel mailing list Bluez-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bluez-devel --===============2050881289==--