From: Brad Midgley <bmidgley@xmission.com>
To: bluez-devel@lists.sourceforge.net
Subject: [Bluez-devel] encoding delay, librarifying a2play
Date: Sat, 27 Nov 2004 19:24:06 -0700 [thread overview]
Message-ID: <41A936C6.70209@xmission.com> (raw)
Hey guys
I was able to encode audio in real time with:
arecord -c 2 -r 44100 -f S16_BE -t au /dev/stdout | ./sbc/sbcenc - |
./a2play 00:08:F4:30:05:BB
But I estimate the delay is about 300ms. The bluetake encoder dongle was
bothering me with its delay which is probably under 200ms... I really
want to get our encoder under 100ms. I read somewhere that 60ms is
achievable.
I think the place to start to get shorter latency is to write something
that reads audio itself, uses the encoder library and writes out to the
headset. Context switches between the 3 userland apps could be wiped
out. I imagine the app will have command-line args for rate and mode,
will open/ioctl the audio device appropriately, and then write to the
headset.
What's the ultimate destination for a2play? A library somewhere? I need
to break a2play into at least 3 files: headers, library, and a fairly
simple main(). Is this a good time?
BTW, I did try a class 1 adapter this time and the usable range
increased from about 8 meters to about 16... it will be better still
when headsets have class 1.
Brad
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://productguide.itmanagersjournal.com/
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
next reply other threads:[~2004-11-28 2:24 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-28 2:24 Brad Midgley [this message]
2004-11-28 6:56 ` [Bluez-devel] encoding delay, librarifying a2play Marcel Holtmann
2004-11-29 21:14 ` Brad Midgley
2004-11-29 21:45 ` Marcel Holtmann
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=41A936C6.70209@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