From: Brad Midgley <bmidgley@xmission.com>
To: BlueZ Mailing List <bluez-devel@lists.sourceforge.net>
Subject: [Bluez-devel] a2play live streaming
Date: Fri, 13 May 2005 20:12:05 -0600 [thread overview]
Message-ID: <42855E75.6000003@xmission.com> (raw)
Hi
a2play now takes args. they're possibly overly complicated, but here it is:
use: a2play [options] <bdaddr> [filename]
Where bdaddr is the bluetooth address of an A2DP headset and
filename is an audio file or device, or stdin if not specified.
Options:
-h print this usage and exit
-v print verbose output
-d process input as raw audio or an audio device
-m use mono instead of the default stereo; implies -d
-s skip over backlogged data to try to eliminate latency; implies -d
-r rate (hz): use rate, default 44100, for raw audio or device; implies -d
so i stream directly by running:
a2play -s 00:0D:3C:30:32:AD /dev/dsp
unfortunately, latency is still pretty significant (~400ms?)
any ideas on how to reduce latency? i still use the ring buffer but skip
to the last frame in the ring when using "-s" so it should never get
behind there. the problem seems to be somewhere else anyway.
i disabled the stream close command because it locks up the itech. i got
tired of powercycling it. let me know if it causes problems with the
other sets.
brad
-------------------------------------------------------
This SF.Net email is sponsored by Oracle Space Sweepstakes
Want to be the first software developer in space?
Enter now for the Oracle Space Sweepstakes!
http://ads.osdn.com/?ad_id=7393&alloc_id=16281&op=click
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
reply other threads:[~2005-05-14 2:12 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=42855E75.6000003@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox