From: Brad Midgley <bmidgley@xmission.com>
To: BlueZ users <bluez-users@lists.sourceforge.net>
Subject: Re: [Bluez-users] bluetooth-alsa: a2recv stuttering sound from WM5.0 AKU2.0
Date: Mon, 29 May 2006 00:15:21 -0700 [thread overview]
Message-ID: <447A9F89.9070002@xmission.com> (raw)
In-Reply-To: <96B7A15232D6CF42836BFD428AD6B6034E5073@deexmb01.de.icap.com>
Guido
> No problem, but what can we do now? For me it looks like, a2recv will
> not grab the packets at the right speed, or something like this.
maybe wm5 reports the wrong rate to us. you could try hardcoding in
adjustsound() the value that is used. the legal values are 16000, 32000,
44100, 48000.
we print out the rate that the sender reports. what rate are you getting
printed out?
> The timeline on my sending media player will also run very slow, so it
> seems, that it notices, that something is not realy ok.
>
> Does a2recv confirms the packages back to the sender?
short answer yes. it runs the data over l2cap which is reliable and uses
flow control as long as you're not doing anything fishy in the lower layers.
it sounds like wm5 is encoding at a higher rate than we expect.
brad
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users
next prev parent reply other threads:[~2006-05-29 7:15 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-29 6:58 [Bluez-users] bluetooth-alsa: a2recv stuttering sound from WM5.0 AKU2.0 Guido Reimer
2006-05-29 7:15 ` Brad Midgley [this message]
2006-05-29 7:21 ` Brad Midgley
-- strict thread matches above, loose matches on Subject: below --
2006-05-29 7:25 Guido Reimer
2006-05-29 6:21 Guido Reimer
2006-05-29 6:46 ` Brad Midgley
2006-05-26 14:14 Guido Reimer
2006-05-26 5:56 Guido Reimer
2006-05-26 14:11 ` Brad Midgley
2006-05-25 6:31 Guido Reimer
2006-05-25 15:12 ` Brad Midgley
2006-05-25 15:34 ` Brad Midgley
2006-05-24 16:09 Guido Reimer
2006-05-24 16:51 ` 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=447A9F89.9070002@xmission.com \
--to=bmidgley@xmission.com \
--cc=bluez-users@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).