From: "Frederic Dalleau" <Frederic.Dalleau@palmsource.com>
To: "BlueZ development" <bluez-devel@lists.sourceforge.net>
Subject: [Bluez-devel] RE : Big patch to a2dpd
Date: Sat, 2 Sep 2006 22:06:35 +0200 [thread overview]
Message-ID: <7A6DA545D7FDCC4B93DB651FDBC1EDDE4E6E91@eumonex01.palmsource.com> (raw)
In-Reply-To: 44F9ABCF.1020706@xmission.com
[-- Attachment #1: Type: text/plain, Size: 1578 bytes --]
Hi Brad,
> It only works if the bdaddr is specified in .asoundrc (the old way) as
> well as in .a2dprc. Specifying it on the a2dpd command line does not
> seem to help.
Now that you tell it, as the .a2dprc is reread for address changes it will overwrite the value set by command line. You can use, enablerereadconfig=0. The .asoundrc is ignored.
> Audio only came out the left speaker using my itech r35 black set. (My
> other sets are up at work)
I have a reversed stereo. It may be related. I haven't found where but it's one of the main problems. Try enablereversestereo=1 and see if audio comes from the right speaker. This would mean the failure came before compression and transmission.
Also try playing with sound balance on xmms and look at alsamixer -D ctl.a2dpd to see if both internal channel values are the same.
Does the standard a2dp plugin work well with that headset?
I have a faulty headset that does that too. When I shoot it it goes ok :D
> How do you switch on the fly to wired audio?
Modify the .a2dprc file, write enablealsaredirect=1 instead of 0 and save. Yes, file ipc :D
> Could we contribute this stuff to a wiki?
Man is to my eyes the standard unix doc format. Even gnu info is nothing :D Why not a manpage stored in cvs, there are certainly php scripts that can render a man page in html.
The wiki is good for writing but having some docs in the project is better. The wiki needs to be watched over and there would be no way to automatically provide docs to a distro... The manpage can be installed with unbuntu packages.
[-- Attachment #2: winmail.dat --]
[-- Type: application/ms-tnef, Size: 3586 bytes --]
[-- Attachment #3: Type: text/plain, Size: 373 bytes --]
-------------------------------------------------------------------------
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
[-- Attachment #4: Type: text/plain, Size: 164 bytes --]
_______________________________________________
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-02 20:06 UTC|newest]
Thread overview: 14+ 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
2006-09-01 18:25 ` Michael Frey
2006-09-02 16:05 ` Brad Midgley
2006-09-02 20:06 ` Frederic Dalleau [this message]
2006-09-06 3:58 ` [Bluez-devel] RE : " 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
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=7A6DA545D7FDCC4B93DB651FDBC1EDDE4E6E91@eumonex01.palmsource.com \
--to=frederic.dalleau@palmsource.com \
--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