From: Brad Midgley <bmidgley@xmission.com>
To: bluez-devel@lists.sourceforge.net
Subject: Re: [Bluez-devel] A2DP sink code finally
Date: Wed, 27 Apr 2005 10:27:54 -0600 [thread overview]
Message-ID: <426FBD8A.8020006@xmission.com> (raw)
In-Reply-To: <20050426123412.48950.qmail@web8310.mail.in.yahoo.com>
Guys,
I updated the docs to reflect the new a2play usage and basic a2snk
operation.
I think the best effort spent on a2play now would be to:
- use the real-time clock for timing
- optionally open and perform ioctls on /dev/dsp to operate directly on it
Both of these should make live streaming tighter.
Timing improvements include both inserting delays and throwing out data
when the link doesn't accept it fast enough (or to take up delay), but
you only need the latter for live streaming.
Brad
-------------------------------------------------------
SF.Net email is sponsored by: Tell us your software development plans!
Take this survey and enter to win a one-year sub to SourceForge.net
Plus IDC's 2005 look-ahead and a copy of this survey
Click here to start! http://www.idcswdc.com/cgi-bin/survey?id=105hix
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
next prev parent reply other threads:[~2005-04-27 16:27 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-26 12:34 [Bluez-devel] A2DP sink code finally Mayank Batra
2005-04-27 16:27 ` Brad Midgley [this message]
2005-05-01 15:16 ` Henryk Plötz
2005-05-03 13:23 ` Mayank Batra
-- strict thread matches above, loose matches on Subject: below --
2005-04-26 12:35 Mayank Batra
2005-04-26 13:10 ` Brad Midgley
2005-04-26 15:50 ` Marcel Holtmann
2005-04-27 19:08 ` Brad Midgley
2005-04-26 12:29 Mayank Batra
2005-04-24 15:09 Mayank Batra
2005-04-25 3:24 ` Brad Midgley
2005-04-25 3:58 ` Brad Midgley
2005-04-25 6:08 ` Henryk Plötz
2005-04-25 14:40 ` Brad Midgley
2005-04-26 12:23 ` Mayank Batra
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=426FBD8A.8020006@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.