Alsa-Devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Christopher Arndt <chris.arndt@web.de>
To: alsa-devel@alsa-project.org
Subject: Re: pyalsa: synchronizing queue with MIDI clock events
Date: Tue, 21 Jul 2009 18:20:46 +0200	[thread overview]
Message-ID: <4A65EADE.70007@web.de> (raw)
In-Reply-To: <4A65C370.3030205@ladisch.de>

Clemens Ladisch schrieb:
> Christopher Arndt wrote:
>> What is a sensible number of ticks to take
>> into account for measurement?
> 
> Large enough that you get a stable average, but small enough that you
> can detect actual changes.

I figured out that much on my own :) I was just wondering if anybody had
already experimented with this...

> You can tell ALSA to timestamp all events that are received; just call
> the snd_seq_port_info_set_timestamping() function and set a queue that
> is running, then you'll get the queue's current time in each event.
> This isn't implemented in pyalsa, but you can set this for a specific
> connection with the queue, time_update, and time_real parameters of the
> connect_ports function.

I'll look into this.

Many thanks for your comments!

Chris

  reply	other threads:[~2009-07-21 16:20 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-07-17 12:54 pyalsa: synchronizing queue with MIDI clock events Christopher Arndt
2009-07-20 12:31 ` Christopher Arndt
2009-07-21 13:32 ` Clemens Ladisch
2009-07-21 16:20   ` Christopher Arndt [this message]
2009-07-31 18:26     ` pyalsa: SeqEvent.time strangeness (Was: synchronizing queue with MIDI clock events) Christopher Arndt
2009-08-02 15:42       ` Christopher Arndt
2009-08-03 11:55       ` Clemens Ladisch
2009-08-03 12:21         ` pyalsa: SeqEvent.time strangeness Christopher Arndt
2009-08-04  9:45           ` Clemens Ladisch
2009-08-04 11:10             ` Christopher Arndt
2009-08-04 13:03               ` Clemens Ladisch
2009-08-05 13:18                 ` [PATCH] alsa-python: Add support for setuptools Christopher Arndt
2009-08-05 13:30                   ` Clemens Ladisch

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=4A65EADE.70007@web.de \
    --to=chris.arndt@web.de \
    --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