Dejay wrote:The tilt / pitch doesn't work at all like I hoped. First it ALWAYS seems to pitch up to the set value so it's not "analog" at all. I realize this might be impossible with the used sensors but this is what I bought the QuNexus for and what I didn't get.
The delay just adds insult to injury. If I wanted simple to play, I would have bought a standard keyboard.
I just got the QuNexus a couple of weeks ago, and the delay also has been bothering me. I have measured it to be at least 350ms as well which is already bad, but furthermore the response varies based on how lightly you move up and down the keys for some reason and doesn't trigger at all for a very slow glide. I'm sincerely hoping that both of these issues will be fixed in the next firmware update. My cello doesn't suffer from these defects and I'm sure I don't speak just for myself when I say that I would be comfortable with the ramifications of lower delay. :p
There *is* a solution to the skipping tilt, by the way. I thought it was a deal breaker at first and would probably have returned the keyboard, but turns out that if you send the tilt data as CC instead of bend it doesn't skip. I was... confused when I discovered this. Who *wants* their pitch bend to jump to min/max?
Another issue I've noticed is that when tilt data is sent over the keyboard layer -- either as bend or a CC -- you cannot set it to latch. The latch functionality is only available in the controller layer, which makes it essentially inaccessible because AFAIK (correct me if I'm wrong) there's no channel for the octave up/down control, which means that if you were to latch in the controller layer you wouldn't be able to map it to the corresponding key. Once again, this is a design decision I am having great difficulty understanding. Do most performers *want* their pitch to immediately snap back to center during the release phase of their envelope?