Setting a filter for a custom velocity curve

[jahngra]

Hi all -

I recently purchased a new controller (Arturia Keylab Essential 61) and find the velocity curve very problematic. On other controllers there are often several different curves to choose from. This one just has log and linear, and neither works well for me. I've previously had M-Audio controllers which I've found give me a better range of control for my playing style. Has anyone had any luck setting up a velocity input filter to overcome such a problem? Or must I ditch this controller?

[stubbsonic]

I'll bet you can find a remap velocity curve plugin.

For temporary purposes, you could insert DP's Change Velocity, and choose Compress/Expand. Which can let you tweak the response a little bit. Not a full curve, though.

As I understand it, remap will just be an input/output transfer curve, and you will sacrifice some range and resolution in order to achieve your result. This is probably the case with most keyboards. However, some might have a higher internal velocity resolution, so that even after a curve is applied, you still get a full 127 values of velocity.

Budget controllers all cut corners. I recently discovered that many of them don't use 14-bit pitch benders. Not surprising, but the MIDI 1.0 spec only has ONE high-res control source. The manufacturers said, "Counter proposal: How about none?"

[bayswater]

There are apps. This one is not cheap, but there is a demo that won’t let you save a preset.

https://springbeats.com/2021/12/15/velp ... composers/

I’ve had a lot of cheap keyboards, and most had some setting to change the velocity curve. Odd that this is not a more common function.

[stubbsonic]

Seems like making an input/output transfer curve for MIDI velocity SHOULD be trivial.

But it is a stinkin' shame that Arturia didn't put more thought & effort into a controller keyboard. I should qualify that it seems like lots of controller brands spend lots of effort adding bells and whistles related to DAW and VI integration, but drop the ball when it comes to the actual qualities that matter most.

[HCMarkus]

The more expensive Aruria keyboards have more options. I use the custom curve available in the Keylab Mk3 to adjust aftertouch to my preferred response.

[stubbsonic]

Even if it is an entry-level keyboard, if you can have "log & linear", does it cost that much to add a few more choices? This is the way the keyboard feels under the fingers.

I'm usually happy if the linear (non)curve has the right range; i.e., that I hit it hard and get 127, and when I play what I consider to be my softest, I can get the lowest velocities like 2-15. The rest of the curve stuff can usually be handled by the receiving synth.

[HCMarkus]

Even if it is an entry-level keyboard, if you can have "log & linear", does it cost that much to add a few more choices? This is the way the keyboard feels under the fingers.

I'm usually happy if the linear (non)curve has the right range; i.e., that I hit it hard and get 127, and when I play what I consider to be my softest, I can get the lowest velocities like 2-15. The rest of the curve stuff can usually be handled by the receiving synth.

+1

[stubbsonic]

There are a few keyboards that use higher scan rates for velocity-- 10KHz-- to measure the timings between the first & second contacts within the velocity mechanism. I think this should be the new de facto minimum standard for all keyboard going forward-- but it won't be.

Supposedly, one of my cheapo controller keyboards (I'm not naming it for reasons) has a 10K scan rate. Its velocity response is excellent, and is the best part of that otherwise mediocre keyboard.

[stubbsonic]

We've not heard from the OP since this thread started. But just to add one more data point, I forgot about Bome Translator Pro. However, I don't have this software, and I don't know if it will specifically allow you to create a custom curve to remap velocity.

Also, not exactly cheap.

https://www.bome.com/products/miditranslator

[jahngra]

Thanks all for your thoughts. I will try the springbeats plug-in and see if I have any luck with that. It’s truly annoying that my more basic (and smaller) M-audio keyboard has a better response than the Arturia. there’s another cheapo one I used recently that had like seven curves to choose from and I found one that would work.

With the Arturia I’m finding it’s either real loud or real soft- I can’t control of the middle velocity range properly- which is most important when I’m using piano instruments.

[stubbsonic]

Yea, I'm totally with you on this. I don't mind adapting to a slightly different response, but when it's wrong it's just wrong. And there's no excuse for it, really.

Unfortunately, if the linear response is how you describe, then the velocity remap might not really be a very good solution. For example, if you have a hard time producing velocities between say 50-90 and the keyboard somehow doesn't scan in a way that makes those velocities be represented properly, then remapping won't really help that much. yes, you can make it so that 95 is more like 80 and 45 is more like 60, but it won't really feel like super controllable response. Give it a try, though.

Is your purchase recent enough that you can exchange it for something more to your liking?

[HCMarkus]

With the Arturia I’m finding it’s either real loud or real soft- I can’t control of the middle velocity range properly- which is most important when I’m using piano instruments.

I hope you can find a suitable setup for what you've got on hand, but must throw in my recommendation that, if at all possible, you purchase a weighted, hammer action 88 for piano and other velocity-sensitive visual instruments like Rhodes, Clav, Wurli and many synths. You will find such a keyboard is extremely helpful in getting inspired performances recorded. I use a Yamaha P255 in my studio; I got it for $600 used. There are many less-expensive weighted-action controllers that would be great, too! Might be worth keeping an ear to the ground on Craigslist to see if something fun shows up locally.

And though I love a weighted action keyboard, the synth action is definitely preferred for organ and certain other VI parts. The difference in response expands the variety of results one can expect, something I find inspiring, and the availability of other physical controls compliments a digital piano (which is typically lacking things like mod and pitch wheels) nicely. If you run DP in regular MIDI record mode (as opposed to Multi Record), MIDI data coming from all sources is merged in DP, so you can control VI parameters with one keyboard while performing on another.