From owner-freebsd-bluetooth@FreeBSD.ORG Fri Sep 17 09:39:14 2010 Return-Path: Delivered-To: freebsd-bluetooth@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 5B1C91065670 for ; Fri, 17 Sep 2010 09:39:14 +0000 (UTC) (envelope-from plunky@rya-online.net) Received: from smtp02.one2one.net (smtp02.one2one.net [149.254.192.174]) by mx1.freebsd.org (Postfix) with ESMTP id 172848FC19 for ; Fri, 17 Sep 2010 09:39:13 +0000 (UTC) Received: from localhost ([127.0.0.1]) by localhost with esmtp (Exim 4.69) (envelope-from ) id 1OwX2l-00041N-4U; Fri, 17 Sep 2010 10:15:43 +0100 X-Virus-Scanned: Debian amavisd-new at smtpbeckt01.t-mobile.co.uk Received: from localhost ([127.0.0.1]) by localhost (localhost [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id h6BE9y3tQaHT; Fri, 17 Sep 2010 10:15:42 +0100 (BST) Received: from customer44214.102.kt.cust.t-mobile.co.uk ([178.102.172.189] helo=rya-online.net) by localhost with smtp (Exim 4.69) (envelope-from ) id 1OwX2j-00041B-AX; Fri, 17 Sep 2010 10:15:42 +0100 Received: (nullmailer pid 579 invoked by uid 1000); Fri, 17 Sep 2010 09:18:48 -0000 Date: Fri, 17 Sep 2010 10:18:48 +0100 (BST) To: Federico Lorenzi In-Reply-To: References: <4C876C14.2030300@FreeBSD.org> User-Agent: Alpine 2.00 (NEB 1167 2008-08-23) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Message-Id: <1284715128.901194.134.nullmailer@galant.ukfsn.org> From: Iain Hibbert X-SA-Exim-Connect-IP: 127.0.0.1 X-SA-Exim-Mail-From: plunky@rya-online.net X-SA-Exim-Scanned: No (on localhost); SAEximRunCond expanded to false Cc: freebsd-bluetooth@freebsd.org Subject: Re: A2DP ? X-BeenThere: freebsd-bluetooth@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Using Bluetooth in FreeBSD environments List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 17 Sep 2010 09:39:14 -0000 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