Actually, I should probably be the one apologizing. For some reason I was thinking this was a QuNexus thread! The names are a little too similar for me I suppose. Gets tough when you're constantly going back and forth between the words QuNeo and QuNexus all day. Sorry about that!

i've been thinking more about the aftertouch implementation and believe there would have to be some sort of pressure threshold after you strikes the pad before it kicks in as well...

i've done my own experiments by monitoring midi and noticed that when i strike a pad, varying amounts of pressure data is being transmitted eventhough it feels like i'm not adding any while simply holding the pad to keep the note active...so i would guess we would need to capture the initial pressure data (ipd) when the pad is struck and reject any new pressure data that is not greater than ipd + x before passing the pressure data thru....

also the pressure data would have to be relative to that initial velocity strike too... so, if the velocity was 100 (thus the initial pressure data would also be 100) any new pressure data would have to consider 100 as zero...i can only see this working if the pads can actually receive 254+ levels of pressure (if the pad is struck at a velocity of 127, then the initial pressure that needs to be reject would be 127 so any pressure above 127 would need to be considered)...on a keyboard, i believe there are separate sensors to capture velocity and aftertouch independently so i'm not sure if the pads can measure these separately....anyway, sounds like programming logic i can't fully work out so i'll leave it to the developers ..

interesting to note that maschine and beatstep have the same pressure implementation as the quneo and those manufacturers haven't made aftertouch available either -- just "current touch" pressure...this is why i think it may be a hardware limitation but none of the three (NI, Arturia and KMI) have acknowledge to me if aftertouch is possible or not in the current hardware release...

i just bought my QuNeo today and are working on a personal traktor mapping. When using some knob features (like filter) i'd love to see QuNeo sending a value when i release the slider as setting filter back to value 64 isn't that easy.So sending a specified value on slider release would be a great optional feature for me.