Yahoo Groups archive

Emu XL-7 & MP-7 User's Group

Index last updated: 2026-04-29 00:09 UTC

Message

Re: [xl7] jittery midi clock?

2006-09-25 by Zsolt Szabó

I usually experience a drift too, but I think that's normal.
Since MIDI is serial I think there's no way to avoid it, even
if clock messages are system realtime commands.
Simply you have to wait to finish transmitting a message before can
initiate the next and once a message is in the queue there's
no way to remove it.

In my setup using AMT8 with USB I experience for example
a drift of max. -2/+1 BPM when tempo is 130.
Slower tempos will do better, of course as you are slowing down.
At higher tempos there's not much difference.

Really MIDI clock is OK for live act but I wouldn't use for studio
work. In that case you can make Live the master and drive the
PX7 from there. PX7 will drifet of course here too, but maybe
the glitches will go in Live.

Regards,

    Zsolt




----- Original Message ----- 
From: "milesegan" <milesegan@...>
To: <xl7@yahoogroups.com>
Sent: Monday, September 25, 2006 8:05 AM
Subject: [xl7] jittery midi clock?


> I've been using Live as an effect rack and driving it from the PX-7
> using the PX-7 as the master clock.  Today I froze a couple of synth
> tracks to free up some CPU and was surprised to hear them glitching
> heavily.  Since the problem seemed to go away when external sync was
> disabled in Live I fired up Logic and watched the Logic midi clock
> bounce all over a three bpm range while syncing to the PX-7.
> 
> Is this normal?  I seem to be getting a very unstable clock signal
> from the PX-7.  I tried a separate midi cable to rule that out and
> also an empty pattern with no midi data at all on the PX-7 to make
> sure it wasn't just a case of choking on too much data.  Neither of
> these fixes made any difference.
> 
> 
> 
> 
> 
> 
> Yahoo! Groups Links
> 
> 
> 
> 
> 
> 
> 
> 
> 
>

Attachments

Move to quarantaine

This moves the raw source file on disk only. The archive index is not changed automatically, so you still need to run a manual refresh afterward.