funny that I should see a "nanoKontrol not working" post at exactly the same time I go to post about a nanoKontrol problem!
Just got it yesterday. The device connects to Max without problems. When I am moving two or more CC's at once (problem is the same for knobs and faders), the lowest CC number is the only CC that responds smoothly. The other CC's only send a value when there isn't a stream of changes happening on the lower CC. In other words, if I try moving a few faders slowly, they all seem to be working okay, but once I reach a certain speed (that's not unreasonable), all CC's but the lowest wait and may never send their value if movement is continuing on the lowest CC.
So not only is the performance unacceptable whenever I'd want to move more than one fader/knob at the same time, but CC values easily get stuck at values far from where the knob may finally rest.
I've tested this by hooking up a few ctlin's to cycle~'s to listen for the zippering, to make sure it's not a strange UI update issue.
Other MIDI controllers work fine in Max. Tested Doepfer pocket dial and Faderfox LV2 (both working over standard MIDI, though, not USB).
I've tested the nanoKontrol in Live and Logic, and no such issue occurs.
Has anyone experienced anything like this, either with this controller or USB MIDI drivers in general?
Running OS X 10.5.6 on a Macbook 2nd gen. Max 5.0.7 and 4.6.3. Issue persists before and after installing Korg USB MIDI drivers.
Works perfectly in Windows XP. Any OS X 10.4 users?