From owner-freebsd-bluetooth@FreeBSD.ORG Fri Sep 17 18:16:17 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 0D1C7106566C for ; Fri, 17 Sep 2010 18:16:17 +0000 (UTC) (envelope-from maksim.yevmenkin@gmail.com) Received: from mail-gw0-f54.google.com (mail-gw0-f54.google.com [74.125.83.54]) by mx1.freebsd.org (Postfix) with ESMTP id B88618FC16 for ; Fri, 17 Sep 2010 18:16:16 +0000 (UTC) Received: by gwb15 with SMTP id 15so1016025gwb.13 for ; Fri, 17 Sep 2010 11:16:15 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:received:in-reply-to :references:date:message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=gs0KXIVw3BNJMYV46MqDgRb/vwcwq2XGq2R/X8X9KHM=; b=fNYUPGwYR1HokrNBuQsOBcJ3X1rD6W/lfAeqykYxh7pEbjbhYlGwhH7+qnnYogWwc6 5qICNFOzJ26Ctc7mzjrjjGRsdsirAXqHY4TJEn1XasD13qFSrnaPl+wXaY6v7hEDoFmM FBlm1xhlhAbgp0PxzT8+QyJNL/zPLIJ0x7AkM= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; b=ZE23O56G+NyfQWTKb6jUJbebgyUwy+GUCsnQ3I1LVuhyocDjc3EQppz58IaQV6YmXF kaKN47lv5Np4BQZukKHI7lGjBr/CFNm/7MT/Po2002kmK7tSJUEvxxEnrivTkg+m7nyH +ZtTRut52x32KjSygkk6X0PPWkV4vCnx6EC4E= MIME-Version: 1.0 Received: by 10.150.190.9 with SMTP id n9mr6220783ybf.34.1284747375716; Fri, 17 Sep 2010 11:16:15 -0700 (PDT) Received: by 10.231.208.1 with HTTP; Fri, 17 Sep 2010 11:16:15 -0700 (PDT) In-Reply-To: <1284715128.901194.134.nullmailer@galant.ukfsn.org> References: <4C876C14.2030300@FreeBSD.org> <1284715128.901194.134.nullmailer@galant.ukfsn.org> Date: Fri, 17 Sep 2010 11:16:15 -0700 Message-ID: From: Maksim Yevmenkin To: Iain Hibbert Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: quoted-printable 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 18:16:17 -0000 On Fri, Sep 17, 2010 at 2:18 AM, Iain Hibbert wrote= : > 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 wit= h >> 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 dat= a > that I recall on later, i believe its l2cap actually :) on former, i agree, the exact quo= te =3D=3D The Advanced Audio Distribution Profile (A2DP) defines the protocols and procedures that realize distribution of audio content of high-quality in mono or stereo on ACL channels. The term =93advanced audio=94, therefore, should be distinguished from =93Bluetooth audio=94, which indicates distribution of narrow band voice on SCO channels as defined in Chapter 12 of Bluetooth Baseband specification. =3D=3D > 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 i doubt it. audio said to be encoded in SBC (mandatory) with optional support for MPEG-1,2 Audio, MPEG-2,4 AAC and ATRAC (whatever that is). so decoding is needed, imo. > 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 syste= m > standard audio interface (eg on /dev/audio2) that you can use with your > favourite music player but have been distracted by other things. yeah, i would do something like this too. no pad(4) on freebsd though :( > I have a pair of A2DP headphones that I can use to listen to music from m= y > 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..? another exact quote :) =3D=3D Note also that the A2DP does not include remote control functions. Devices may support remote control features by implementing both A2DP and the control profile as depicted, for example, in the usage scenario of Audio/Video Remote Control Profile. =3D=3D thanks max