From: Brad Midgley <bmidgley@xmission.com>
To: bluez-devel@lists.sourceforge.net
Subject: Re: [Bluez-devel] a2play and Motorola HT820
Date: Fri, 26 Aug 2005 19:33:24 -0600 [thread overview]
Message-ID: <430FC2E4.2000504@xmission.com> (raw)
In-Reply-To: <20050824051102.46AA8A00FC@bostoncoop.net>
Nat
> I tested the bluetooth-alsa software for playing mp3's over a Motorola HT820
> headset. My Thinkpad X40 laptop is running kernel 2.6.12.5, debian unstable.
> Sco works fine through xmms, though the sound quality is poor. A2play with
> -n works fine for ~10s, then cuts out. (It cuts out after ~5s without the
> -n option.) It usually returns, then cuts out again after a similar period.
I am redoing our timing loop with rtc because it is inconsistent between
different computers.
If you're impatient, try it without the -n flag but modify the "magic"
number of 87 to different values to find one that works better.
You can try one or two "-t" flags to change the encoder settings.
It looks like the ht820 has csr chips in it which is a good
sign--they're normally very tolerant of variable timing in the stream.
Brad
-------------------------------------------------------
SF.Net email is Sponsored by the Better Software Conference & EXPO
September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices
Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA
Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
prev parent reply other threads:[~2005-08-27 1:33 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-24 5:11 [Bluez-devel] a2play and Motorola HT820 Nat Butler
2005-08-27 1:33 ` Brad Midgley [this message]
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=430FC2E4.2000504@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.