PlanetZ forums - scopeusers.com

hi..

if i use the scope midi port in my win 8 64bit system with ableton64 (9.1) i got strange MIDI problems.
The first i discovered was that the midi clock timing was total unusuable.
So i have used one of my usb midi interfaces.

now i was playing around with push and my xbase09. i mapped the controllers via scope midi.
the result was there was a very high latancy of the parameter changes on the xbase to the ableton macros.
And it crashes ableton after some minutes. If i connect it to my USB midi interface it is working without latency and i have no crashes.

is there any known problem ?

cheers

PS;

the system is running fine in all other cases .. only wavedevice problem with more then 4gb ram and the MIDI problem.

Hardware
AMD A8
1x Pulsar2
2x 6DSP board.

usb is not without latency, but it should be very, very short.

it sounds like you are not using the ASIO drivers, but are connected to the wave driver, and/or there may be a feedback loop.

ableton is running in asio mode.
Are there asio midi drivers?

the xbase is connected on the usb interface in the same way as i connected it with scope.
I dindt see any loopback in ableton, the midi indicator was only blinking if i move a knob on push.
aslo the midi monitor in SFP was not fraking out.

the timing ptroblem is existing with only midi sync and one cable connected. i had massive tempo changes in live. if i do the same over the usb device it was in sync.

cheers and thanx

there isn't a problem with the midi driver.
i don't know why you have this behavior.

1.) Make sure you don't have sync setup in Ableton for both inputs & outputs (or from multiple devices!!!!)

I have found SCOPE to be incredibly rock-solid for MIDI clock generation. And any Ableton after 8.4 will "lock" onto an external clock and smooth it out. Makes sudden tempo changes impossible, but works pretty well at limiting system jitter.