Analogue-sequencer

> Do you have a clue as to what's happening then - seems to 
> happen at the
> beginning of the loop cycle - not every time, but often. 
> Cubase is sending
> something that the other sequencers are not...

I can't say for sure what's happening with your particular Cubase...

I originally wrote the sync handling in P3 such that if a new clock byte
arrived before the clock pulse handler had finished preocssing the previous
clock byte, the new byte was ignored, since the implication was that the
incoming tempo was so high that P3 couldn't keep up.
As it turned out, some PC sequencers, Cubase being a major culprit, like to
send clumps of MIDI clock bytes very close together, working on the basis
that the tempo is just some arbitrary average of the rate of clock pulses,
and not defined instantaneously by every single pulse.
Essentially they were allowing huge amounts of tempo jitter.

P3 now queues up clock pulses that come in faster than it can handle them,
on the assumption that the tempo isn't too high, and that the clock pulse
rate will drop to a much lower value sometime soon.
So it works better slaved to Cubase, and other PC sequencers with no regard
for the regularity of MIDI clock.

Best regards,
Colin Fraser
Sequentix Music Systems Ltd
http://www.sequentix.com