From: bluez.mexon@spamgourmet.com
To: bluez-devel@lists.sourceforge.net
Subject: Re: [Bluez-devel] a2dpd produces choppy audio with Digitus dongle, (bluez: message 14 of 20) OK with D-Link
Date: Fri, 09 Mar 2007 20:13:29 +0100 [thread overview]
Message-ID: <45F1B1D9.4080601@yahoo.com.au> (raw)
In-Reply-To: <45F1A3D5.7010801@xmission.com>
Brad Midgley - bmidgley@xmission.com wrote:
> 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.
Oh. There you go. That fixed it. I have a bluetooth mighty mouse:
switched it off and everything's coming through fine. Thanks a lot!
So what's up with that? That's not supposed to happen, right? Is it a
software thing or a hardware thing? I checked the a2dpd stuff out of
CVS only two days ago. And the DBT-120 handles the mighty mouse and
A2DP no problems, I just unplugged one and plugged in the other.
-------------------------------------------------------------------------
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
next prev parent reply other threads:[~2007-03-09 19: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
2007-03-09 19:13 ` bluez.mexon [this message]
2007-04-07 17:12 ` 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=45F1B1D9.4080601@yahoo.com.au \
--to=bluez.mexon@spamgourmet.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.