KeyLab MK3 max velocity issue

Lab KeyLab
#1

Hi everyone, I’m running a KeyLab MK3 on Logic and for some reason no matter how hard/fast I hit the keys my max velocity seems to tap out at around 116. All software updated.
I have tried using the different velocity curves but it doesn’t seem to help.

Any ideas on how to solve this would be awesome :slight_smile:

Thank you in advance:)

#2

Hi @viktorl. Welcome to the community.

I think this might be by design. But i suggest you contact Arturia support through your account and ask.

I do wish the keylab MK3 beside the mod curve also had a parameter to set the sensitivity of the mod needed to reach the max value.

1 Like
#3

have you tried using MCC and selecting the ⌘M to bring up the midi console? do you get the same results from your key presses in console? if you can get to the 7F hex (127) via this method then the limitation is some form of limit inside of LogicPro.

#4

Hi and thank you both for responding :slight_smile:

I tried the MCC but this is the only messages I get with it all enabled:
In: 90 41 72 | Ch 1 Note On F3
In: 80 41 4B | Ch 1 Note Off F3

This is with me pressing fairly hard.

I wonder if I’m missing something here…

#5

I had the same problem and contacted Arturia support. Their response seemed to indicate that this is by design. I ended up returning.

#6

Maximum value should only be reached at the hardest/ fastet hits/ presses. That’s individual so it could be nice if it could be personalized in controllers. But in anyy case it should not be very easy/ too easy to reach maximum value.

1 Like
#7

the 72 is hex for 114, so you’ve hit it technically faster in logic than you did in the mcc app, the next line is the release speed that you let go of the key.

don’t confuse how you get the max value, its not pressure… that it how aftertouch works. The initial midi value is the speed that the button is pressed. I don’t have the KeyLab anymore. it took mine back as I didn’t like the layout of the controls and the options for moving in daw mode along the track timeline. (and the control screen on mine kept locking up in daw mode and not displaying the menu items it should).

But I did try using the MCC on my minilab and get the 7F (or 127 midi velocity) value. so I would as the others have said… Ask Arturia directly if this is a known function of the keyboard or if your unit is defective

#8

In testing a new KL 61 Mk3 I’m seeing the exact same issue, and it’s frustrating.

Arturia might feel that having the headroom available to literally take a hammer to keys to get max velocity (127) is what is deemed correct but there have been a fair number of disgruntled customers (since the Mk2) who do not want this ‘dead zone’ due to their lighter playing style and would much prefer being able to have a preference to scale the velocity to be able to have greater control over of the velocity range in their playing style.

As others have mentioned, this has nothing to do with selecting a linear/log/exp/custom curve as none of those will ever reach 127 velocity under ‘normal’ playing conditions. Yes, you can abuse the custom curve and set the last two values to 127 and you will get max velocity, but this absolutely kills any ability to have control over the mid to lower velocity range while playing.

It can’t be difficult to add one simple preference which allows you to configure a ‘velocity scaling’, where if the user set it to 120% and would normally get a value of 100 on say linear curve, then it would instead output 120 instead due to the scaling. For a velocity normally output as 15 it would instead output 16 (or 17).

Please Arturia, this is a new controller and your dev team is clearly still tweaking the firmware at the moment, and a LOT of people would be very grateful if you could add this very simple quality of life improvement.

(knowing my and others requests, this will be just ignored as per Arturia usual practices - customers first right? :weary: I could also go on about how it’s missing a decent custom velocity curve setting with at least 7 setpoints with Bézier curves to smooth the abrupt slope changes around velocity set points… and why on earth did you get rid of quick-change banked encoders/faders? and… :confounded: )

1 Like