From: andy@samuri.demon.co.uk
To: "BlueZ development" <bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] Big patch to a2dpd
Date: Fri, 1 Sep 2006 13:57:36 +0100 (BST) [thread overview]
Message-ID: <41749.212.58.233.129.1157115456.squirrel@samuri.demon.co.uk> (raw)
In-Reply-To: <44F7088F.6090606@palmsource.com>
Hi Fr=E9d=E9ric,
Whoo some patch cant wait to give it a whirl..
On the subject of your DOC nice work very concise
You might like to add
------------------
If you create an ~.asoundrc as follows
pcm.a2dpd {
type a2dpd
}
Then you can directly add the headphone device (pcm.a2dpd) to any app that
supports alsa plugins correctly, Without affecting the default Gnome/X/KDE
sounds
Known working Apps
Xmms
alsaplayer
VLC (you have to manualy add it to the conf file as the gui wont allow
adding non visible plugins (bug)).
cheers Andy
--------------------------------------
Hi Brad,
>>
>> I looked over Matthew's patches and applied them. I applied your "small
>> patch" which turns out to be bigger than it sounds :)
>>
> This one is more than bigger!
> Reindent,
> Alsa output redirection,
> New on-the-fly in-play switch from bt to alsa and reverse
> Changing bdaddr in play too.
> More options described in sample.a2dprc
>
> I removed the line LIBS=3D from Makefile.am as suggested. This line was
> making tons of compilation problems. As a2dpd finally links to alsa, it
> is no longer needed.
> Please give it a try before submitting (Matthew and RUI if you read that).
>
> Wrote a doc : http://fdalleau.free.fr/a2dp_doc.pdf ideas welcome!
>
> Fr=E9d=E9ric
>
>
-------------------------------------------------------------------------
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 easi=
er
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=3Dlnk&kid=3D120709&bid=3D263057&dat=3D1=
21642
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
next prev parent reply other threads:[~2006-09-01 12:57 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-23 16:55 [Bluez-devel] Small patch to a2dpd Frédéric DALLEAU
2006-08-23 17:53 ` Brad Midgley
2006-08-24 8:44 ` Frédéric DALLEAU
2006-08-30 14:45 ` Brad Midgley
2006-08-31 16:04 ` [Bluez-devel] Big " Frédéric DALLEAU
2006-09-01 12:57 ` andy [this message]
2006-09-01 18:25 ` Michael Frey
2006-09-02 16:05 ` Brad Midgley
2006-09-02 20:06 ` [Bluez-devel] RE : " Frederic Dalleau
2006-09-06 3:58 ` Brad Midgley
2006-09-06 8:52 ` Frédéric DALLEAU
2006-09-07 23:00 ` Brad Midgley
2006-09-02 16:08 ` [Bluez-devel] " Brad Midgley
2006-09-02 17:01 ` Brad Midgley
-- strict thread matches above, loose matches on Subject: below --
2006-09-02 6:04 Li, Lea
2006-09-02 13:02 ` Michael Frey
2006-09-02 6:21 Li, Lea
2006-09-06 3:06 ` Brad Midgley
2006-09-06 3:12 Li, Lea
2006-09-06 3:38 ` Brad Midgley
2006-09-06 9:33 ` Frédéric DALLEAU
2006-09-07 16:48 ` Andrew Waldram
2006-09-07 19:47 ` Brad Midgley
2006-09-07 20:36 ` Michael Frey
2006-09-07 22:46 ` Brad Midgley
2006-09-07 21:06 ` Andrew Waldram
2006-09-07 22:52 ` Brad Midgley
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=41749.212.58.233.129.1157115456.squirrel@samuri.demon.co.uk \
--to=andy@samuri.demon.co.uk \
--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