I am still in the process of turning the Qunexus into a true musical instrument (i.e, working around some of its current software limitations in order to make it more playable).
I can say that the hardware really is superb, but the software has a few issues that could do with a bit of a tweak - but, props to the engineers, it's pretty cool the way it is!. (I bought two of these devices so you can figure I like the Qunexus very much).
Now, one thing I was disappointed about was the pitch bend 'nub'. It really doesn't seem to offer very precise control. Yesterday I had a look at the MIDI data coming from it and found something interesting. If you set the pitchbend range to 12 semitones, it outputs the full range of data and the control and precision look quite good. Incidentally, the nub is also pressure sensitive, something I have only at this stage had a quick look at, but that's a cool feature too.
But set the range to 2 semitones and the volume of data and the control over the pitch value degrades significantly. What I think is happening is that the software simply clips the values when a lower range is specified. It should, instead, divide the full control range by a constant value to produce a smaller bend range, thus not losing the intrinsic resolution of the physical controller.
I'm gonna try implementing this in the JS plugin I'm already using to fix the tilt pitchbend issues - I'm pretty optimistic this will greatly improve pitchbend accuracy. In the interim if you set bend range to 12 and you have the ability to control bend sensitivity independently at the plugin level, you may find that the pitchbend control experience improves greatly. If this turns out to be the case, I'll add this to a list of firmware issues I'm gonna beg KMI to implement.