Ableton Forum

Hello respected board users,

I'm a good old ableton user, who recently decided to try on Live7 and though it has some features i'd been dreaming for ages, I personally found it unusable immediately.

The main problem is, compared to Live 6.0.9 (the latest i've been using up to date) 7th midi input has an AUDIBLE delay. This makes it absolutely impossible to play directly from my midi-keyboard (which is basis of my work). I've already tried all possible audio buffer settings, all possible driver error compensation, different asio latencies and in/out sample rates. It may be linked with delay compensation, but turning it off renders my past projects severely out of sync which is not acceptable. Live 6.0.9 on the other hand has no problems like this.

Does anyone one have the same problem? Is there something that can be done?
Thank you!

Live 7 introduced support for the DirectMusic API for MIDI functions. You can now choose between DM or MME, with DM as the new default. Try switching back to MME. At least at one point, there was a cumulative delay problem with the DM system (growing delay the longer the program runs)

I don't mean to sound stupid, but where do I do that ^^;;
Thanks.

I'm experiencing the same problem...the longer the program runs, the more delay gets built up. But it is only for the USB controller...my other controller connects to the audio interface using a 9-pin midi cable. Interesting.

Oh...and switching between MME and DirectMusic does not correct the problem. What say you, Abes??

I am using an Alesis QS8.1 and was getting about a 15-20 second delay from the time I pressed the key. I changed to MME under the preferences and that took care of the midi delay. Also, on my keyboard, I changed keyboard mode to "solo". Midi is working fine now.

Wes

Same here...thanks to timur I finally switched everything to MME, and everything is groovy. Whew...I was starting to worry there...

solovox wrote: Oh...and switching between MME and DirectMusic does not correct the problem.

??

I know, I know...

I think it worked the second time because I closed and the re-opened the app!