From: Reiner Klenk <pdq808@t-online.de>
To: BlueZ development <bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] RE : Quality of a2dp sound
Date: Mon, 13 Nov 2006 19:37:02 +0100 [thread overview]
Message-ID: <1163443022.7965.30.camel@grappa> (raw)
In-Reply-To: <200611121938.39415.marcel@hilzinger.hu>
On Sun, 2006-11-12 at 19:38 +0100, Marcel Hilzinger wrote:
>
> Thanks a lot for these explanations. I knew, that sco and a2dp are different
> profiles, but I didn not know, that the kernel module handles "only" sco,
> because the command to play is called a2play...
>
??
snd-bt-sco and running btsco => SCO (bi-directional)
a2play, a2dp alsa plugin, a2dpd => three different possibilities for
a2dp (one-way)
> Btw. is there a possibitily to use the micro under Linux or is a2dpd a
> one-way-connection?
>
It can be used in SCO connections, for example with ekiga.
> > To use "old-style" a2dp with amarok:
> > .asoundrc like this:
> >
> > pcm.headphone {
> > type a2dp
> > bdaddr "00:13:17:71:58:F6"
> > }
> >
> > Note the a2dp in the second line (not a2dpd). Replace the address with
> > the one of your headset. Do _not_ run the a2dpd daemon.
> But load the kernel module?
>
Can be loaded, but is not required for a2dp.
--
debb1046 (gmail.com, gtalk, jabber.org, ekiga.net, last.fm, skype)
-------------------------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
next prev parent reply other threads:[~2006-11-13 18:37 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-09 10:02 [Bluez-devel] Quality of a2dp sound Marcel Hilzinger
2006-11-09 10:42 ` Adrian Glaubitz
2006-11-09 10:07 ` Reiner Klenk
2006-11-10 8:01 ` Marcel Hilzinger
2006-11-10 8:41 ` [Bluez-devel] RE : " Frederic Dalleau
2006-11-10 9:46 ` Marcel Hilzinger
2006-11-10 9:59 ` Mayank BATRA
2006-11-10 10:04 ` Marcel Hilzinger
2006-11-11 8:21 ` Reiner Klenk
2006-11-12 18:38 ` Marcel Hilzinger
2006-11-12 20:31 ` Brad Midgley
2006-11-13 9:39 ` Frédéric DALLEAU
2006-11-13 18:26 ` Reiner Klenk
2006-11-13 18:37 ` Reiner Klenk [this message]
2006-11-10 10:06 ` Marcel Hilzinger
2006-11-10 10:17 ` Marcel Hilzinger
2006-11-13 13:24 ` Marcel Hilzinger
2006-11-14 12:19 ` [Bluez-devel] python a2dp Sergey Krivov
2006-11-14 14:40 ` Frédéric DALLEAU
2006-11-14 15:25 ` Sergey Krivov
2006-11-14 15:34 ` Frédéric DALLEAU
2006-11-14 15:40 ` Sergey Krivov
2006-11-13 15:32 ` [Bluez-devel] Quality of a2dp sound Brad Midgley
2006-11-09 17:43 ` Marcel Hilzinger
2006-11-09 19:31 ` Thomas Kear
2006-11-10 8:24 ` [Bluez-devel] RE : " Frederic Dalleau
2006-11-10 13:50 ` Adrian Glaubitz
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1163443022.7965.30.camel@grappa \
--to=pdq808@t-online.de \
--cc=bluez-devel@lists.sourceforge.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox