Page 1 of 1

Akai MPK49, Reason Rewired and Ableton.... Latency Problems!

Posted: Sat Apr 03, 2010 4:15 am
Hey all.

I have a show in two days and occasionally my midi controller (brand new Akai mpk49) will have a latency/delay issue. In other words, I will press a key or pad and the note will play after a half a second or so. Once I restart Ableton the problem is fixed. At first I thought this was because I was overloading the CPU because the set is rather large, but I watched closely last time and Ableton's meter was at 14-20% the entire time.

I'm running Ableton 8 Suite to launch clips and Reason 4 rewired for most of my synths. My interface is an Apogee Duet and I'm running this all on a MacBook w/ 10.5.8 (2G Memory). Akai is brand new. I've ran large sets before on this computer and have never had a problem like this.

If it is a CPU issue- I'm very confused. I've been monitoring via Activity Monitor in my utilities, and Reason takes up about 1% while my Live session takes up about 30-50%. I have no other programs running.

If its not a CPU issue, I'm thinking maybe it could be a problem with the USB port?

Any suggestions would be greatly appreciated! My show is on Sunday night, April 3rd!

Re: Akai MPK49, Reason Rewired and Ableton.... Latency Problems!

Posted: Sun Apr 11, 2010 4:46 pm
by christianwitt
I have the same Soundcard (Duett) & the same Controller Keyboard (Mpk49) & the same Problem!
do you found a way to fix the delay?

best
c

Re: Akai MPK49, Reason Rewired and Ableton.... Latency Problems!

Posted: Tue Jul 20, 2010 9:30 pm
I noticed the problem only occurs after the CPU would spike- so I've done everything I can do prevent those from happening (freezing tracks, flattening when possible, limiting my VSTs). I also increased the buffer again. If the CPU does spike, I usually need to restart my entire system and it clears the problem.

Let me know if you figured out anything too!

Thanks

Dallin

Re: Akai MPK49, Reason Rewired and Ableton.... Latency Problems!

Posted: Wed Jul 21, 2010 11:10 am
by christianwitt
i found out that it was a problem of the old NI Kontakt 4.01 after updating to 4.1 the problem was fixed.