Ableton Forum

please add a toggle for drum racks to switch into 64 pad control. used to be able to do this by loading drum racks into instrument racks, but that went away in the latest version of live. Also, there is most definitely a slight delay when triggering clips from the session view. This is really awful as the promise of push implied a super powered mpc-like workflow and the session view is intuitive for an mpc style workflow.

thanks!

Change the launch quantization of your clips for session view. (It is one bar by default)

im not using quantization at all.
I've been a live user since version 1 and i know my way around the program. this is a very slight latency (under 1/36th of tempo), but enough to have a serious impact on rhythmic, mpc type pad triggering. the problem is with push specifically, and does not repeat on other kntrol surfaces like Korg padkontrol or my midi keyboard. it seems push has a problem with session clips. once the clips are in a drum rack or instrument rack, there is no latency. i'm fairly sure this must be a known issue to abelton.

Re: latency in session view
I posted about this over at the beta forum but it sank without a trace. Nice to see im not the only one.
I used to midi-map unquantized clip slots in Session and trigger them with my padkontrol. Tried to replicate with Push, this time midi-mapping unnecessary. Alas, the timing is all over the place with random latency. Crappy issue but no-one seems to be arsed about it at Ableton. Midi-mapping in Push's user mode works fine though...

jmeginsk wrote:im not using quantization at all.
I've been a live user since version 1 and i know my way around the program. this is a very slight latency (under 1/36th of tempo), but enough to have a serious impact on rhythmic, mpc type pad triggering. the problem is with push specifically, and does not repeat on other kntrol surfaces like Korg padkontrol or my midi keyboard. it seems push has a problem with session clips. once the clips are in a drum rack or instrument rack, there is no latency. i'm fairly sure this must be a known issue to abelton.

When I got Push I stumbled over this too. There is a setting in the Options menue that reads: Reduced Latency when Monitoring. You have to turn it off.
It was especially noticable when you changed between tracks.
This should be better documented!

that setting makes no difference in this case, tom. sure you're talking about the same issue?

related: velocity sensitivity for clips doesnt work either

I've def tried both latency and velocity. It seems the push was engineered to be specifically aligned with the midi instruments, but has some issue with actual clip triggering. The ideal for me, would be to have a whole live session packed with audio clips, quantization off, and the ability to use push to trigger the clips with no latency.

fyi: the latency in session is now tracked internally as a bug.

n/m, it's not

Any news on this issue?

Loaded clips into RAM. Still plays like shit.

:/

The unplayable session view is a problem for me too. The clips launch fine when I map them to my QWERTY keyboard but not when I play them from Push. It's a pretty serious issue for Push to not work in this way. I hope we get a fix soon. I considered using drum racks and the 64 pad improvement in the Beta is good but I like to also have midi clips and colour the buttons so drum rack isn't the answer.

Balchie wrote:The unplayable session view is a problem for me too. The clips launch fine when I map them to my QWERTY keyboard but not when I play them from Push.

What "unplayable session view" specifically? You want sample precision launches without any regard for if clips will match?

Stromkraft wrote:

Balchie wrote:The unplayable session view is a problem for me too. The clips launch fine when I map them to my QWERTY keyboard but not when I play them from Push.

What "unplayable session view" specifically?

add a few drum sounds as clips in session view, set global clip Quantize value to None and try to 'finger-drum'. the timing is all over the place.

Yep, garryboozy is describing it exactly. If you switch from using push and map the clips to a midi keyboard, Live plays them perfectly in time. It looks like there is a bug in the way the Push interfaces in session view. It's not something that Live is incapable of doing in the way I'm expecting. I've reported it as a bug and the support team confirmed it is one and they are looking into it. No promise of fix of course but it's real and verified by them.