[alsa-devel] pyalsa: synchronizing queue with MIDI clock events
clemens at ladisch.de
Tue Jul 21 15:32:32 CEST 2009
Christopher Arndt wrote:
> Now to synchronize the queue tempo to incoming MIDI clock events, to be
> able implement synchronized delays or arpeggiators, I use the method in
> the code shown below. This works ok, but I notice that the measured BPM
> oscillates +-1 BPM around the value displayed by the clock source (my
> synth's sequencer) if I measure/average only a few (~10) ticks or do not
> round the result to an integer value.
> Is this the right approach? 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.
> Should I use another reference timer than Python's time.time() function?
That timer probably has a high enough resolution, but you measure the
time when your code is executed, which may be later then when the
event was actually received.
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
> Is pyalsa generally suitable for this kind of application even on
> older/weaker hardware (e.g. a NSLU2)?
The biggest problem is probably scheduling delays, so I guess using
Python instead of C should not add any noticeable delay.
More information about the Alsa-devel