PlanetZ forums - scopeusers.com

Hi, i've hooked my RS up to my prisma synth and i've got the RS acting as the external clock for delays etc...

I know some users on here have claimed that the RS has rock solid timing...but prisma is telling me otherwise
the timing is close, but not solid. say i have a bpm of 130 on the RS, in prisma the timing will jump between 129 and 130 (since it's accurate to 2 decimal places, i get the BPM jumping between say 129.70 and 130.3)

ok, it's a small difference, but when it changes by 1 bpm (i.e the crossing between 129/130) you can really hear clicking on the delays...

anyone get timing that's actually solid, or is this just an inherent latency with MIDI?

adding to that, is there any 3rd party device that can 'round' the bpm to the nearst whole number?

of course, i can just match the bpm's by hand, but i'm just curious as to whether the latency comes from the RS or scope...

thanks,
mini

<font size=-1>[ This Message was edited by: minipax on 2006-09-21 16:34 ]</font>

that looks like midi....

Midi Clock data is inherently not perfect because the way it is transmitted...

I think your better to set the bpm in prisma, but still control midi notes from RS.

I use the rs the sequence everything, and it's effectively ALOT more tight in timing external midi device than sx for example.

Take eds8i and play really fast snare roll, from SX not a single hit seems tight compare to the previous one, and from RS, the same sequence is tight as a virgin

If you're using the same MIDI port (cable) for your midi clock as well as note & controller data, the slow external datarate of MIDI-DIN (which is MIDI-x1, 31.5 kbaud) means that the 'midi clock' databytes won't necessarily all be sent & receieved at the exact time they should be (they will get shuffled in between other midi messages-as marcus suggests). In the 'old' days you would manually shift notes & controller data around to 'optimize' your midi sequence, insuring that the most important bits are sent at the right time (only the kick on the downbeat with everything slightly offset, etc). RS7000 should do this for your, as should some other hardware & software solutions like Logic.

Also Scope itself runs MIDI in the cpu, which means that a high process load on the cpu can affect midi timing within the software.


btw hi marcus

<font size=-1>[ This Message was edited by: valis on 2006-09-21 23:58 ]</font>

Ok, cheers for the info..

I tried the same thing with SX sending Midi clock, and the bpm jumps from about 110 - 150
what a joke...

MIDI clock sync on Scope unfortunately sucks. Sure, MIDI clock isn't all that tight by definition, but I've seen it working way better than it does on Scope. It would be nice if more devices allowed you to re-sync them with a MIDI note (like Flexor ramp system).