All of lore.kernel.org
 help / color / mirror / Atom feed
From: Brad Midgley <bmidgley@xmission.com>
To: BlueZ development <bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] Plugz, a2dpd, and a2dpd2 strangeness
Date: Thu, 26 Apr 2007 22:03:55 -0600	[thread overview]
Message-ID: <4631762B.9060704@xmission.com> (raw)
In-Reply-To: <463151D2.1040805@jlab.org>

Chris

> 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.

Brad



-------------------------------------------------------------------------
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

  reply	other threads:[~2007-04-27  4:03 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 [this message]
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   ` [Bluez-devel] " Chris Carlin

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=4631762B.9060704@xmission.com \
    --to=bmidgley@xmission.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.