Hi list, 

Yesterday I bought a new korg nanoKontrol2. To my surprise, after a few basic testings, i've discovered that when I move as little as three faders sending CC values simultaneously --and not incredibly fast--, pd doesn't receive a big part of the values (with [ctlin]), staying half the way in the midi-value range.

---------For example, moving three faders from minimum to maximum, that is, from 0 to 127, the values in the number boxes connected to [ctlin] end up in random numbers in between (like 63, 74 and 70). Even more weird (or maybe not!) is that when I move any of the faders again, the next value that is thrown out is 126 (as if the object had actually gotten the previous 127 and is going down from there!)---------

Indeed, using a midi monitoring program ('MIDI monitor' on my mac), I can see that the computer receives all the midi values as expected, so I guess that something happens on the [ctlin] level in Pd.

Apparently this is/was also an issue on Max's implementation of [ctlin]: http://cycling74.com/forums/topic.php?id=19562

I have worked with other Midi controllers in Pd and I never had a similar problem.

i've also tried [midiin]->[midiparse], with exactly the same results.

(mac osx 10.6.8, pd-extended 0.42.5, pd-extended 0.43.1, pd 0.43.2)

any light on this??

cheers,

Ángel Faraldo