[Bluez-devel] fleshing out audio daemon scenarios

[Bluez-devel] fleshing out audio daemon scenarios

[Brad Midgley]

[-- Attachment #1.1: Type: text/plain, Size: 740 bytes --]

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

[-- Attachment #1.2: Type: text/html, Size: 900 bytes --]

[-- Attachment #2: Type: text/plain, Size: 286 bytes --]

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

[-- Attachment #3: Type: text/plain, Size: 164 bytes --]

_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel

Re: [Bluez-devel] fleshing out audio daemon scenarios

[Marcel Holtmann]

Hi Brad,

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

please stop worrying so much about the combo headsets and the
complicated cases. We can fix them later. The goal should be to get
simple headsets working.

This means for me we have no ALSA plugin configuration option right now.
Let the ALSA plugin connect to the audio service and use whatever
headset or headphone it has available. Currently it is really not
important to get all possible scenarios covered.

Regards

Marcel



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

Re: [Bluez-devel] fleshing out audio daemon scenarios

[Brad Midgley]

[-- Attachment #1.1: Type: text/plain, Size: 361 bytes --]

Marcel

So I think next step will be to tell the audio daemon to put a headset in
connected state and then with a basic plugin (no options) put it in
streaming state and send some audio to it.

What does the command-line dbus injection stuff look like to get the audio
daemon to connect to a set?

I'll start documenting the minimal approach on the wiki.

Brad

[-- Attachment #1.2: Type: text/html, Size: 394 bytes --]

[-- Attachment #2: Type: text/plain, Size: 286 bytes --]

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

[-- Attachment #3: Type: text/plain, Size: 164 bytes --]

_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel

Re: [Bluez-devel] fleshing out audio daemon scenarios

[Marcel Holtmann]

Hi Brad,

> So I think next step will be to tell the audio daemon to put a headset
> in connected state and then with a basic plugin (no options) put it in
> streaming state and send some audio to it.
> 
> What does the command-line dbus injection stuff look like to get the
> audio daemon to connect to a set? 
> 
> I'll start documenting the minimal approach on the wiki.

no idea. Simply start playing with the code. A lot of stuff will fall
into place automatically and some other stuff needs more thinking, but
without actually trying to do it, we don't know what works and where we
have to fix stuff.

Regards

Marcel



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