Scriptnode Midi CC Node Bug

[crd]

The value in the edit box is show + 1 in the midi cc knob.

[ustk]

@crd is it intended that your max is 130?
Shouldn't be 127? I don't think it is related to the issue though …

[Christoph Hart]

@ustk I stole KONTAKT's way of slapping the pitch bend and aftertouch at the end of the list, but yeah, that offset by 1 is a bit annoying, better fix it now before people actually use it :)

[d.healey]

@christoph-hart So after touch is working now in HISE?

[Christoph Hart]

@d-healey it depends :) I actually don't have a MIDI device that produces (monophonic) aftertouch so there might be something obvious I'm missing, but the polyphonic MPE keyboard produces aftertouch.

[ustk]

@christoph-hart Speaking of offset issues, there's another one (not that problematic though)
the display buffer starts at 1 but the script index starts at 0...

[Christoph Hart]

@ustk Do you mean this:

Yeah, that's me basically not liking #0 (there's even not a name for this abomination, #1 is first, #2 is second, but #0 does not exist) so I incremented the display value, but the actual system is zero-based like everything that is good and logical.

[ustk]

@christoph-hart said in Scriptnode Midi CC Node Bug:

Yeah, that's me basically not liking #0

Feeling the same... demons from school I guess

[crd]

@ustk I was referring to the value of the knob. In the edit window it is 74 and on the knob it is 75. Not a huge deal but worth fixing... and it looks like it's already fixed :)

[ustk]

@crd yeah that’s how I understood it but I just noticed this aside the main issue

[d.healey]

@christoph-hart said in Scriptnode Midi CC Node Bug:

I actually don't have a MIDI device that produces (monophonic) aftertouch so there might be something obvious I'm missing

@Lindon What was the issue you were having with aftertouch?

[Lindon]

@d-healey - so basically when you applied mono aftertouch (pressed harder on a keY) all that HISE responded with was the MIDI's initial velocity value....