CC 129 - aftertouch seems to be behaving oddly

[Lindon]

Maybe its my keyboard , but it seems to work fine in Kontakt - so maybe not. But I cant get aftertouch to work properly in HISE - it seems to be "jumping" to one value when I'm expecting it to (reasonably) smoothly move between the values as I "aftertouch" my keyboard, and it seems to be restricted to a very small range of (low) values. Anyone else getting this?

HiseSnippet 818.3oc6W00SaCCE0tsYB1XH1DZZOlG1angHarA6IJTZQHnPURGauwLItsVywtKwIr9ub+T3ev10IsjDsrRqD6CMHOT06w9Ze78dO23zIP5RCCkAH7hcGMjhvKY3LRnFzX.gIPGtOBurQaRnhFXlBs2ngjvPpGBiqdfF.uXMTxyU6rGgSDtzLHD5LIykdLymoxP6T+HFm2h3Q6x7yM6MqenqTzPxkQ.epZrAZHw8yj9zSH5oUw.gePSOlRF3nHJZHBWaOo2HmAxKEoy+LVH6BNUaXgbfEJEtkj6oYr9+nFCXbuNSN2gHD1nSVTnZZTXUi1LO103YQiURFvLyi7wCbkoQOq7zaiRomUIzCkic0RYGPBoWDmnJxLc5X7.LYwL0gBEUDxTixmt9qR2mXzgobGTNeqTBegD0ua9NN4+Xil85QcUYjslQqO9mMSuvuPMtjQCoPAVz.qaCs3vYVKhqdu16ds2cAs2xoT4QFNfLKQ+kPjmkXa9ARL07.JH.0A0oIB+1suH7TWEr8cCHhvgxvBKrC0m0UJzQjLv2GRaEP+hsNKmGugjDT5PWsSK3PVpONDUTPR4xt9xHgpP4Q0YNmju4PQUSt4WRmhZ22oXdBs2Pe2Jc9oa9sBTe6OjSaJhobIfn46SGCZNAsXAeaoPNbfTvbyWMXSUAr98oA4OGkd31Uofq3kgrZcaJmRxWY+h5GCUjj.HlQmVbo5rEWJIVfmwb2yMRoqoVkZ9OU29GdMsg5d8MDBjbND+SSgIhgLTqalvPeitjDFkOAFSCTZmx2GYxhdRj+E4S3eptiuTpFTriFq99zdjHt5LBOhl+SBxVojMdehhfvMM1b60K9De5kwwwuItmcysZjXaaau9Z8ThiFaC+zaM8TeWpM5VqR4V48qUua99UaYjhI52l.sF9JbuOndwAdslKEXhPP4vFYfqnKoRs2Pam9dMgWhw2gmwCZoswiGzZxf+2rG9D2.44toJBcGpERPfXqH4KgWD9jbv1zBEmJizweePjetqqNg9RHCTtGuZt830ysGaN2d7l41i2N2dr0b6w1SwCcG0ciTR+T4M.zoYZKKbSgt+UhRB8CXLbGNL

MIDI CC 129 seems to do nothing at all.

Yep just checked CC 129 is working as expected in Kontakt.

so in Kontakt:

on controller 
    message("CC Number:" & $CC_NUM  & " value:" & %CC[$CC_NUM] )
end on

gives me a stream of CC_129 messages with changing values....

[Christoph Hart]

Yes I‘ll check that. 129 is pitchwheel though - As a matter of fact this isn‘t official MIDI, I just stole this from KONTAKT to make the transititon smoother - and apparently that didn‘t went well ;)

[Lindon]

@Christoph-Hart well.. pressing hard(er) on my keyboard produces a stream of midi values (assigned to CC129 ) when using Kontakt - I dont really mind what we decide to use, I'd just like it to work...right now aftertouch doesnt seem to work at all in HISE.

[Lindon]

Further investigation reveals: HISE is getting and knows its getting CC129 -

function onController()
{
Console.print("on Controller:" + Message.getControllerNumber() );	
}

BUT BUT BUT...

the time variant midi controller isnt handling it - I've set the CC Number = 129 but nothing is happening in the modulator...

..and this:

function onController()
{
Console.print("on Controller:" + Message.getControllerNumber() + " " + Message.getControllerValue() );	
}

I would expect to see a constantly changing set of values showing up, but its not. Its a singel (arbitary - based on the first press) value.

[Lindon]

any action on this?

[Christoph Hart]

Sure I‘ll take a look. Unfortunately handling aftertouch is not as trivial as it seems - there is monophonic and polyphonic aftertouch, the latter one is reused as MPE pressure gesture and there has to be a sensible solution for every use case. Also my main keyboard doesn‘t send out aftertouch which isn‘t exactly helpful when working on the aftertouch implementation.

[Lindon]

@Christoph-Hart yeah not having ANY aftertouch on you input might be a bit limiting

Just to be clear its monophonic aftertouch I'm talking about here. Sure a poly/MPE solution is nice, but I suggest a walk before run type approach...

[ustk]

Bump bump
Did someone find a solution for this aftertouch?
I'm running in the same issue (CC129 and erratic values)
MPE is not a viable solution in my case...

[Lindon]

@ustk said in CC 128 - aftertouch seems to be behaving oddly:

Bump bump
Did someone found a solution for this aftertouch?
I'm running in the same issue (CC129 and erratic values)
MPE is not a viable solution in my case...

bump again -this seems to be still unresolved....

[Lindon]

@Lindon bump bump bump... getting serious now...