Date: Fri, 17 Sep 2010 10:18:48 +0100 (BST) From: Iain Hibbert <plunky@rya-online.net> To: Federico Lorenzi <florenzi@gmail.com> Cc: freebsd-bluetooth@freebsd.org Subject: Re: A2DP ? Message-ID: <1284715128.901194.134.nullmailer@galant.ukfsn.org> In-Reply-To: <AANLkTinpGP%2BKjQo5BB0mpPhpk0g5dB1ntLPmcTkbG-0n@mail.gmail.com> References: <4C876C14.2030300@FreeBSD.org> <AANLkTi=HKrAckHUvL9ehWvWq5NhB40QkfNABSfNQ5Xet@mail.gmail.com> <AANLkTinpGP%2BKjQo5BB0mpPhpk0g5dB1ntLPmcTkbG-0n@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, 8 Sep 2010, Federico Lorenzi wrote: > I seem to recall that getting it to work in userspace wouldn't be "much" > effort. Last I heard, the code for SCO sockets was a bit unstable, but > worked. You could in theory hook this up to something like gstreamer with > its sbc codec built in, or write your own program that encodes and send the > audio data. The SCO sockets are not required, since A2DP uses RFCOMM to transport data that I recall I'm not sure how audio management works in FreeBSD, wether just feeding the data to /dev/audio is enough or really if you need to make it available some other way. I have thought of doing something on NetBSD using the pad(4) driver[*] which would enable a daemon to provide a system standard audio interface (eg on /dev/audio2) that you can use with your favourite music player but have been distracted by other things. I have a pair of A2DP headphones that I can use to listen to music from my phone and it is kind of nice but I guess that there needs to be remote control interfaces with different music players too, perhaps they have them already..? iain [*] http://www.freebsd.org/cgi/man.cgi?query=pad&apropos=0&sektion=4&manpath=NetBSD+5.0&format=html
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1284715128.901194.134.nullmailer>