Channel Aftertouch..still not working
-
@d-healey damit - just tried this and its STILL not working....
-
@Lindon Can you try again? I think the problem is that channel pressure saves the value as first byte (where normally the note number or CC number is stored) and getControllerValue() always returns the second byte value.
I've fixed it by copying the first byte to the second byte for channel pressure messages, but I'm not sure if that applies to your problem.
-
@Christoph-Hart - Thanks yep _I will redownload and try again...could you just load the snippet above and check too?
-
@Lindon Lol I don't have a keyboard with aftertouch...
-
@Christoph-Hart I will tomorrow if the postman doesn't get lost :)
-
I see cc129 showing up in the console when I print from the controller callback. I don't see a way to assign this CC to a knob on the UI though.
-
@d-healey said in Channel Aftertouch..still not working:
I see cc129 showing up in the console when I print from the controller callback. I don't see a way to assign this CC to a knob on the UI though.
Yes you get CC129, which is good, but try printing the controller value, which should change as you (after)press the key....its always returning the note velocity for me...not tried the latest version yet tho..
-
@Lindon It's outputting different values for me :) @Christoph-Hart Could you add CC129 to the MIDI learn and the assign drop down for UI components? Might be better to label it after touch rather than CC129.
-
@d-healey said in Channel Aftertouch..still not working:
@Lindon It's outputting different values for me :) @Christoph-Hart Could you add CC129 to the MIDI learn and the assign drop down for UI components? Might be better to label it after touch rather than CC129.
have you tried the snippet I posted above? (Just to make sure..)
-
-
@d-healey -OK all good then... I will load up the new HISE ...Thanks.
-
@Christoph-Hart -yep all good here.. working fine now.
-
@d-healey said in Channel Aftertouch..still not working:
@Lindon It's outputting different values for me :) @Christoph-Hart Could you add CC129 to the MIDI learn and the assign drop down for UI components? Might be better to label it after touch rather than CC129.
@Christoph-Hart whilst we are here...the MIDI Controller CC Number goes all the way to 129 - but when set to 129 and channel aftertouch is applied I get some action on note down (which I think is probably wrong) but no activity on actual pressure...any chance we can get this fixed?
-
@d-healey said in Channel Aftertouch..still not working:
@Christoph-Hart Could you add CC129 to the MIDI learn and the assign drop down for UI components? Might be better to label it after touch rather than CC129.
Bump bump :D
-
@Lindon Might be of interest - https://github.com/christophhart/HISE/commit/9a7d7b4507bf2ddda83692d653d4a887ffc5ac57
-
@d-healey said in Channel Aftertouch..still not working:
@Lindon Might be of interest - https://github.com/christophhart/HISE/commit/9a7d7b4507bf2ddda83692d653d4a887ffc5ac57
oh yes - very nice....
-
@Lindon what's the best way of setting up after touch these days?
-
@DanH probably;
function onController() { if(Message.AFTERTOUC_CC) { Console.print(Message.getControllerValue()); } }
-
@Lindon that‘s some ChatGPT level quality here :)
- that‘s a constant number (either 128 or 129, don‘t remember that‘s why it‘s a constant)
- is it really spelled wrong or is that a typo from you?
-