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] a2dpd produces choppy audio with Digitus dongle, OK with D-Link
Date: Fri, 09 Mar 2007 11:13:41 -0700	[thread overview]
Message-ID: <45F1A3D5.7010801@xmission.com> (raw)
In-Reply-To: <45F18755.7040307@exon.dyndns.org>

hey

> Does anyone know what causes the choppiness?

did you try turning off all your other bluetooth equipment? if you have 
a headset or a pc that is switching between piconets then that comes 
through as gaps in the audio.

i also had some similar trouble with the cvs code about 3 weeks ago but 
now it seems to be fine.

brad



-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel

  reply	other threads:[~2007-03-09 18:13 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-03-09 16:12 [Bluez-devel] a2dpd produces choppy audio with Digitus dongle, OK with D-Link bluez.mexon
2007-03-09 18:13 ` Brad Midgley [this message]
2007-03-09 19:13   ` [Bluez-devel] a2dpd produces choppy audio with Digitus dongle, (bluez: message 14 of 20) " bluez.mexon
2007-04-07 17:12     ` [Bluez-devel] a2dpd produces choppy audio with Digitus dongle, " bluez.mexon
2007-04-09  3:18       ` 王晋伟
2007-03-10 16:38   ` Robert Huitl

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=45F1A3D5.7010801@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.