Controlling keyboard velocity accurately

ajaym
Posts: 11
Joined: Sat Jun 07, 2014 10:22 am

Controlling keyboard velocity accurately

Postby ajaym » Sun Jun 29, 2014 6:24 am

It's taken me a while to figure out how to configure the Qunexus in order to get some reasonable control over keyboard velocity.

I've found the following process to work fairly well

1. Reset all the key gains to normal
2. Set the note gain to 1.00, curve=linear, and set min = 0, max = 127 and offset = 20
3. Set the overall sensitivity to 0.75, on threshold = 2, off threshold = 1

Now try a patch (like a piano) with a reasonably wide dynamic range where you can also hear the timbre change with velocity. You should find the keyboard fairly controllable. The trick here is the offset value which ensures that a minimum velocity is obtained from light touches. Without this, I found the keyboard almost impossible to control accurately, with missing notes regularly occurring. A real physical keyboard actually has a minimum velocity, anyway, so this is a good compromise.

A few notes may now be under or over-sensitive. Try correcting this with the individual key gain settings but be prepared for disappointment. Some keys, particularly under-sensitive ones, simply can't be corrected for.

But don't worry. I know how to resolve this, though it will require some more work with a Reaper JS plugin. This will allow under-sensitive notes to be scaled appropriately to resolve the issue. I'll post some code and instructions shortly.

Once I've gotten all the quirks resolved, I intend to propose to KMI that some kind of VST plugin to process MIDI events from the Qunexus might be the easiest way to resolve some of the current issues. (since many of you, of course, will be using other hosts than Reaper, where the problems are so easily fixable).

In addition, I'm hoping I can persuade the engineers to produce a version of the firmware where the initial tilt timeout is either disabled or minimised. At present this delay seriously compromises the use of keyboard tilt for bend or modulation, because the delay is so long in musical terms. I appreciate it was added to attempt to mitigate the tilt control problems that the engineers must have seen during product development, but the flaw lies in the algorithms chosen, not the hardware, so with the changes I've implemented, the delay is no longer required and if eliminated will allow a lot more flexibility in playing styles.
Guzumaki
Posts: 1
Joined: Mon Jun 30, 2014 11:29 am

Re: Controlling keyboard velocity accurately

Postby Guzumaki » Mon Jun 30, 2014 11:31 am

Thank you so much for your work on this. I just received a newer replacement unit that still is very frustrating to play keys/drums on. Crossing my fingers for a vst fix! Love this controller..I just wish I could use it to it's full potential.

These settings did help some with piano samples. Thanks!
ericzang
Posts: 40
Joined: Sat Feb 12, 2011 6:15 am

Re: Controlling keyboard velocity accurately

Postby ericzang » Wed Jul 02, 2014 12:12 am

Good news, JS plugs can be run as vst in other hosts, download:
http://www.reaper.fm/reaplugs/
ajaym
Posts: 11
Joined: Sat Jun 07, 2014 10:22 am

Re: Controlling keyboard velocity accurately

Postby ajaym » Fri Jul 04, 2014 10:59 am

You're correct; I did not know that. ReaJS is a wrapper that should allow any JS plugin to run as a VST. Ok, well in that case I'll finish off the JS code and post it here, since it's obviously gonna be more useful to others than I had originally thought.

Return to “QuNexus General Discussion”

Who is online

Users browsing this forum: No registered users and 2 guests

cron