Alsa-Devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Gerald Grabner <gerald.grabner@tugraz.at>
To: alsa-devel@lists.sourceforge.net
Subject: queue synchronization to external clock?
Date: Wed, 01 Jan 2003 23:10:23 +0100	[thread overview]
Message-ID: <3E13674F.6010604@tugraz.at> (raw)

Hi,

is there any way to synchronize an alsa midi queue to an external midi
source, of which I know the tempo and receive clock events? Of course
I can start my alsa queue after getting a start event, but how can I
avoid a drift over time?

As I also want to do midi recording, it would be nice to have an
offset between external and internal clock of say half a tick, so that
events that come a bit too early are correctely quantized. Is that
possible?

The mail archive of alsa-devel features some related postings, but
being rather new to alsa, it is quite tough to pick the right things.
Therefore I'd be very grateful for hints and help!

Thanks a lot,
Gerald



-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf

                 reply	other threads:[~2003-01-01 22:10 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=3E13674F.6010604@tugraz.at \
    --to=gerald.grabner@tugraz.at \
    --cc=alsa-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