From: Chris Carlin <carlin@jlab.org>
To: BlueZ development <bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] Plugz, a2dpd, and a2dpd2 strangeness
Date: Fri, 27 Apr 2007 10:26:25 -0400 [thread overview]
Message-ID: <46320811.10802@jlab.org> (raw)
In-Reply-To: <4631762B.9060704@xmission.com>
Brad Midgley wrote:
>> With pcm_a2dpd2 I have jumpy, very sped up sound from the headphones and
>> plenty of traffic through hcidump. Alsa redirect sounds about the same
>> as the headphones, but the daemon gives the following errors:
>
> I'm not following you here. What's the difference between using
> pcm_a2dpd2 and the "alsa redirect"? I didn't catch what "same as the
> headphones" was referring to either.
In retrospect I think I wasn't clear about pcm_a2dpd and pcm_a2dpd2. By
those I meant the alsa plugins (libasound_module_pcm_a2dpd[2].so) as
opposed to the similarly named daemon and NOT a definition in my .asoundrc.
The "alsa redirect" meant setting enableredirectalsa=1 in .a2dprc. I
gather that this causes the a2dpd system to spit sound back out through
alsa to speakers instead of through a bluetooth connection.
To restate more clearly (maybe) I'll give you a chart:
a2dpd plugin ("type a2dpd" in .asoundrc):
bluetooth headphones (enableredirect=0 in .a2dprc):
occasional chirps
almost no traffic through hcidump
flags=1 only gives info upon occurrance of chirps
normal computer speakers (enableredirect=1):
music sounds fine
a2dpd2 plugin ("type a2dpd2"):
bluetooth headphones (enableredirect=0):
garbled, sped up sound
plenty of hcidump traffic
flags=1 reports once a second or so
normal computer speakers (enableredirect=1):
garbled, sped up sound
ring buffer full messages spew forth
An interesting thing to me is that enableredirect, if it does what I
think it does, seems to show a non-bluetooth problem...
~Chris
-------------------------------------------------------------------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
prev parent reply other threads:[~2007-04-27 14:26 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-27 1:28 [Bluez-devel] Plugz, a2dpd, and a2dpd2 strangeness Chris Carlin
2007-04-27 4:03 ` Brad Midgley
2007-04-27 6:18 ` [Bluez-devel] RE : " Frederic Dalleau
2007-04-27 14:37 ` Chris Carlin
2007-04-27 15:57 ` Frederic Dalleau
2007-04-27 18:49 ` Chris Carlin
2007-04-27 14:26 ` Chris Carlin [this message]
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=46320811.10802@jlab.org \
--to=carlin@jlab.org \
--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;
as well as URLs for NNTP newsgroup(s).