Analogue-sequencer

> Thanks Colin...I will investigate. I have lodged a question 
> with Steinberg as I cant see any mentions of problems on any 
> notice boards. 
> Also I'll do the simple stuff like buying a higher quality 
> shorter MIDI lead.

The sure way to see what's going in, if you can beg, borrow or steal another
laptop, would be to pass the MIDI from Cubase to the P3 through something
like MIDI-Ox, so you can see exactly when MIDI clock bytes are being sent.
That should clear up very quickly whether there are any missing bytes, clock
bytes bunched tightly together, or a.n.other problem.

> Can I ask a more general question..you 
> mention new modes of working with MIDI clock with Cirklon but 
> from my investigations MTC would seem to be the preferred 
> method of syncing equipment...is there a reason why you are 
> not going this route?

The new timing mechanism in Cirklon is going to allow support for MTC, but I
still prefer MIDI clock.
MTC is a linear timecode. It doesn't carry any information about tempo but
rather provides an absolute timing reference, which a slaved device can then
use to generate a pre-defined tempo clock.
This is primarily aimed at syncing devices where the tempo of a project is
fixed in advance, either at a single value, or at a series of values defined
in a tempo map - essential if you're composing to a film or video source.
And it doesn't make much difference if you are locking MIDI tracks to
recorded audio tracks where the tempo is essentially fixed anyway.
I prefer to use MIDI clock, as I always set the tempo by feel, and wouldn't
like to have a track tied to a certain tempo from the outset.

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