Launchpad latency on session mode (Update: youtube link)

[iloyd2]

( that's too bad, I would love to hear from some another Novation Launchpad user that the thing works as intended, if I would considered the APC better

Anyway, I think is not hardware related, beacause the other modes in my launchpad work flawless without any noticiable latency, I think it is a software issue with the way Live and the Launchpad talk to each other on the session mode.

I have contacted Novation but they doesn' answer neither

I hope it's not an hardware issue and they have a solution. On my side I can also notice a lag when I press the mute button on/off in Mixer mode.

I don't have that lag at all as I recall, I would have to do the test and come back to tell you.

I am now emailing with novation support, but I think the problem I have is with the ableton mapping of the launchpad.

Cool! I never checked it as a regular midi controller I always used it with Ableton mapping. So looks like there is hope that they can fix the problem!

[soddell]

I had the same latency problem. I've just switched from internal soundcard to external card with ASIO driver ==> problem solved.

Jacques

[FinlayB]

I am having the exact same problem except on a PC laptop with the APC20. Is anyone else experiencing this. Any solutions?

I'm still awaiting a response from Ableton about this.

What's going on:

Running Ableton on XP laptop.
Latency is fantastic. 3ms or less.
Triggering in session mode works well with QWERTY or midi keyboard in remote setup.
Latency is great when using APC20 as a standard midi controller in remote setup.
Latency is TERRIBLE when APC20 is setup as 'Control Surface'.

What gives?

FinlayB

[pedroschki]

Apologies for dragging up such an old post, but did anyone solve this?

When controlling clips in Live's session view, I have the same problem. Pretty sure it's not a latency issue as, using MLRV, Launchpad responds how I'd expect....

[vs]

I have the same issue with apc20. Latency only in session controller mode. With ordinary midi mappings there is no latency, but there is no light feedback too. Did anybody found the solution?

[yur2die4]

On pc, download asio4all. Configure properly and it should work. That is if you are using a standard pc or laptop soundcard. If you have an audio interface and still have problems, best of luck, I can't help you haha

[vs]

Problems described in this thread are not due to audio latency. I have perfect latencies with ~3mS with external asio compatible card. But apc20 latency in session controller mode is still there...

[luisarm]

try this*** I noticed that on your live screen shot next to OVR (ovedub button, located next to the play and stop and all that jazz) you? have it set to 1bar, choose the sample you dabbling with and change that to 1/8t or lower on the scale to say 1/32 to get the results you want. Happy sampling fellow Launchpadder

[vs]

There is no latency of my sound card. and there is no quantization problems, my ASIO latency is only 3mS. and I have quantization settings set to none on those clips.

Based on what I read on posts on this website Ableton is incapable to launch clips (Gate/No quantization) without noticable latency when you use dedicated controller with ligt/led feedback.
The only way to launch those clips correctly is to set manual midi mapping but you will not have a LED feedback.
Unfortunately LED feedback is a significant feature of Launchpad and APC controllers.

I understood that APC Launchpad and Maschine all had similar problems. and maybe the problem is in ableton.

[Morphido]

Same problem
I can map the slots in user2 page and launch clips without any lag, like single shots from a drum rack... but in Session View, with none quantization, I have a kind of latency (lag) which is impossible to perform any rhythm synced with the tempo.
Launchpad is great for its dedicated Session Mode, Ableton is able to play clips without any tempo grid, so the problem is the native communication between Launchpad and Ableton Live.
I'll try to contact both companies in order to receive any answer about this big issue.

[jpodtbc]

hi guys.

i've done some experimentation with custom control surface scripts and i've noticed the same thing. previously i used my MPD midi controller with direct mappings and it responded very quickly. i wanted to expand my ability to control ableton so i wrote a custom midi remote script and used the MPD as a control surface. enter delay.

midi remote scripts are written in python. i believe that the delay comes from the communication between python and ableton. direct midi mappings don't use python script to my knowledge. to fix this ableton would have to address the way that the midi remote scripts trigger ableton functions and optimize it for speed. this is probably why they're not responding to questions about it.

as a side note, i get very frustrated with companies that don't respond to these kinds of problems. i have had several with ableton and they pretty much ignore them all.