From: Brad Midgley <bmidgley@xmission.com>
To: bluez-users@lists.sourceforge.net
Subject: Re: [Bluez-users] bluetooth-alsa: a2recv stuttering sound from WM5.0 AKU2.0
Date: Wed, 24 May 2006 09:51:09 -0700 [thread overview]
Message-ID: <44748EFD.2060000@xmission.com> (raw)
In-Reply-To: <96B7A15232D6CF42836BFD428AD6B6034E4F41@deexmb01.de.icap.com>
Guido
> But the sound is stuttering like hell. It is played at half to quater of
> normal speed in very small sound blocks.
>
> Can someone help me? Has somebody got this working on a WM 5.0 Device as
> a sender?
You will be the first. :)
Did you configure with --enable-fixed? Fixed point decoding is more
efficient but it may not behave as well for some codec settings.
Can you figure out what codec settings the wm5 device is using? Maybe
they are not getting set in our decoder properly.
Brad
-------------------------------------------------------
All the advantages of Linux Managed Hosting--Without the Cost and Risk!
Fully trained technicians. The highest number of Red Hat certifications in
the hosting industry. Fanatical Support. Click to learn more
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=107521&bid=248729&dat=121642
_______________________________________________
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-24 16:51 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-24 16:09 [Bluez-users] bluetooth-alsa: a2recv stuttering sound from WM5.0 AKU2.0 Guido Reimer
2006-05-24 16:51 ` Brad Midgley [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-05-25 6:31 Guido Reimer
2006-05-25 15:12 ` Brad Midgley
2006-05-25 15:34 ` Brad Midgley
2006-05-26 5:56 Guido Reimer
2006-05-26 14:11 ` Brad Midgley
2006-05-26 14:14 Guido Reimer
2006-05-29 6:21 Guido Reimer
2006-05-29 6:46 ` Brad Midgley
2006-05-29 6:58 Guido Reimer
2006-05-29 7:15 ` Brad Midgley
2006-05-29 7:21 ` Brad Midgley
2006-05-29 7:25 Guido Reimer
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=44748EFD.2060000@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 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.