From: Jon Smirl <jonsmirl@gmail.com>
To: alsa-devel mailing list <alsa-devel@alsa-project.org>
Subject: Synchronizing multiple machines
Date: Wed, 27 Jan 2010 20:52:54 -0500 [thread overview]
Message-ID: <9e4733911001271752r4b9f77e2kef54d720ede5a704@mail.gmail.com> (raw)
What's the best strategy for synchronizing alsa between multiple
machines within earshot of each other? I can synchronize the CPU
clocks to microsecond accuracy. But how do I deal with drift in the
audio clocks? Can I periodically stop the stream and restart it using
CPU clock? That would compensate for the audio clock drift.
--
Jon Smirl
jonsmirl@gmail.com
reply other threads:[~2010-01-28 1:52 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=9e4733911001271752r4b9f77e2kef54d720ede5a704@mail.gmail.com \
--to=jonsmirl@gmail.com \
--cc=alsa-devel@alsa-project.org \
/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;
as well as URLs for NNTP newsgroup(s).