Oct 25, 2006 at 2:58pm
i just noticed that kslider will send a maximum velocity value of 128 when you click on the black notes. this is consistent in both the large and small keyboard versions. to prove it you need only open the help file and start clicking on each keyboard.
after some quick empirical testing as described above i find these velocity ranges:
i understand the resolution issues of big white keys vs. little black keys. in my estimation it would be more expected if the output ranges were each scaled from 1 at the lowest point to 127 at the highest.
and if someone does open up the code to fix this, i would request while you are there that the ‘clear’ message be made to work in monophonic or polyphonic mode. would be a nice simple way to reset the display.
many thanks to cyclists everywhere.
Oct 25, 2006 at 7:06pm
To add to those bugs, I have definitely noticed quirkiness regarding changing colors — often messages sent won’t change highlight etc. colors when they are sent, only after unlocking and re-locking the patch. Not quite what was intended….
Maybe there should be a dedicated monophonic and polyphonic kslider, might this resolve some of the programming problems? (not being a C programmer I’m out of my element here)…
Oct 28, 2006 at 7:37am
first, I can confirm the bug, though I never touched the highest pixel
Seejay James wrote:
I don’t have these experiences, you descriptions are very vage and sound
> Maybe there should be a dedicated monophonic and polyphonic kslider,
You can switch from monophonic to polyphonic in the inspector…
You must be logged in to reply to this topic.