Re: exports for pulseaudio

Hi Brad,

> I've been looking over the pulse integration problem. I'd like to help
> get issues out of the way for João Vita to make some good headway.
> 
> Maybe the biggest issue is we need to export some functions for
> getting the audio stream socket. It would also make a lot of sense to
> provide access to the sbc codec at the same time. A native pulse
> plugin will need direct access to do its own sbc encoding. Hopefully
> Lennart will be ok with the idea of some minimal codec handling in a
> plugin--I can't see any other way around it.

the agreement from the mailing list or IRC (can't remember) was that we
have ipc.[ch] and these files have LGPL license so they can be copied
out of the side bluez-utils source code and used by other libraries or
systems. Nothing has changed here. It is the job of the external plugin
developers to keep this in sync with bluez-utils. No API guarantee.

For SBC the same thing applies at the moment. Unless we really do freeze
the API (and that only happens if an audio experts from a project like
GStreamer or similar tells me it is a good API), external plugins have
to copy the whole thing and sync it with bluez-utils.

Regards

Marcel



-------------------------------------------------------------------------
This SF.net email is sponsored by the 2008 JavaOne(SM) Conference 
Don't miss this year's exciting event. There's still time to save $100. 
Use priority code J8TL2D2. 
http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone
_______________________________________________
Bluez-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/bluez-devel