dalinnen

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.

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.

large keyboard
black keys: 1-128
white keys: 1-125

small keyboard
black keys: 1-128
white keys: 1-124

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.

kslider-bugs

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)...

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)...

first, I can confirm the bug, though I never touched the highest pixel 

> 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

I don't have these experiences, you descriptions are very vage and sound 

more like things related to other objects, maybe bpatcher quirks (which 

> 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)...

You can switch from monophonic to polyphonic in the inspector...

Don't know if I understood your comment...

first, I can confirm the bug, though I never touched the highest pixel 
in my life before... ;-)

Seejay James wrote:
> 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....

I don't have these experiences, you descriptions are very vage and sound 
more like things related to other objects, maybe bpatcher quirks (which 
have been discussed a lot).

> 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)...

You can switch from monophonic to polyphonic in the inspector...
Don't know if I understood your comment...

-- 
Stefan Tiedje------------x-------
--_____-----------|--------------
--(_|_ ----|-----|-----()-------
-- _|_)----|-----()--------------
----------()--------www.ccmix.com


kslider bug(s)