Forums > MaxMSP

KORG nano PAD

September 25, 2009 | 8:41 am

Hi. I’m trying to assign my KORG nano Pad to max. Im using the midiinfo object to report all midi devices connected to Max. But for some reason midiinfo reports a different name on the nano Pad then midiin. Midiin keeps the name "nanoPAD PAD" but the midiinfo object reports the name "nanoPAD CTRL".

And accordingly if I use midiinfo object and umenu to set the midiin, well it cant find the controller.

Anyone experienced the same? Or what am I doing wrong?


September 25, 2009 | 9:05 am

just a few questions to ask.

can you use any of it in max at all?
are you getting signals?
have you tried it with any other max patches that use midi input?

also as well, the help files for all of the [midiin]/[midiout]/[midiinfo] etc, do help in a tremendous way.

aye…


September 25, 2009 | 9:20 am

Yes I’m getting signals. If I doubble click the midiin I can select nanoPAD PAD. But Im using several midi interfaces so I want them in a menu, therefore midiinfo. But midiinfo reports that the controllers name is nanoPAD CTRL and no (as stated by the midiin object) nanoPAD PAD.


September 25, 2009 | 9:41 am

I have a padKontrol, not the nano. But here "padKONTROL CTRL" is the _output_ port (PC->USB). Check the midiinfo help. For building a menu of input devices you need to send -1 to its second inlet.

cheers


September 25, 2009 | 9:54 am

Thanks. now it works


September 25, 2009 | 11:35 am

I use a nanopad and a nanokontrol. Midiin and midiinfo work properly in max 5.0.5, but I had some problems in max 5.0.7: in max 5.0.5 midiin recognizes messages, in max 5.0.7 it doesn’t.
Same problem about the name of the devices (as Ricardo) in max 5.0.7, not in max 5.0.5.
The only way for me is to assign port a and port b to the devices and then to use an argument for midiin.
Everyone has noticed this behavior? Can it be a bug?
What about midiin in max 5.0.8?

thanks!


Viewing 6 posts - 1 through 6 (of 6 total)