|
The interface descriptions for audio-api.txt appear
to be somewhat stagnant (for one area, you are probably waiting for
me).
That said: is it still your intent (or that of the
development group) that the Object Path for audio-connected devices will
be /org/bluez/audio/device<n> (where "n" is
0-based)?
I assume that one would have to do any/all pairing
against the org.bluez.Adapter object (e.g., object path /hci0), creating a
Device object (e.g., /hci0/dev_00_02_5B_01_A4_74) before connecting to the audio
Service and creating the audio Device (using the BT Address of the remote
device, e.g., 00:02:5B:01:A4:74). Do I have this right?
How much of what is in audio-api.txt is or
will be obsolete under 4.x?
David Stockwell
|
------------------------------------------------------------------------- Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://sourceforge.net/services/buy/index.php
_______________________________________________ Bluez-devel mailing list Bluez-devel@xxxxxxxxxxxxxxxxxxxxx https://lists.sourceforge.net/lists/listinfo/bluez-devel
