On Sun, 16.08.09 20:12, Jo?o Paulo Rechi Vita (jprvita at gmail.com) wrote: > >> You exposed this as a source. Which makes a lot of sense I > >> guess. However, there is one little problem: we don't allow direct > >> connections between sinks and sources right now, which limtis the > >> usefulness of the a2dp source, because you cannot really use PA as a > >> set of a2dp speakers like this... But I guess this should really > >> convince me to get of my ass and actually implement the necessary code > >> for allowing direct sink/source connections. > >> > > I've been using "parec | pacat" as a workaround for testing, but if > the connection was done inside PA it would be at least more "user > friendly" I guess. Not just that. It will also shortne latency and most importantly can deal with frequency deviations between the sink and the source to connect. > >> One question though: what about support for HSP/HFP? Would it even > >> make sense to make PA behave like a headset to other devices? > > > > I think the use case of having your PC to behave as a headset for your > phone is a good example, but I'm not sure how is the BlueZ support on > this. HSP has two different roles for stream endpoints, Headset and > Audio Gateway. BlueZ implements Audio Gateway, but I haven't checked > about the Headset role. Hmm, implementing the other side of HSP/HFP probably means writing an AT command interpretor. Ugly stuff. > > One more question: the bluez side of this, I assume I can find that in > > the upstream bluez git repo? Would really like to play around with > > this... > > Johan just merged it upstream and is also part of the release 4.48, > released today. Nice, I'll make sure this is in rawhide and toy around with this. Lennart -- Lennart Poettering Red Hat, Inc. lennart [at] poettering [dot] net http://0pointer.net/lennart/ GnuPG 0x1A015CC4
