Mar 03 2009 | 5:34 am
    Hello I recently bought a small midi controller called the korg nano kontrol, to integrate into my live set. It has many knobs and sliders and some buttons. I have been trying to figure out how to use it with max and I feel like my brain is melting. I read several of the MSP midi tutorials as well as the Max Midi basics tutorial and I'm still really in the dark. It's especially bad because someone just showed me how to use the controller with Reason and it took less than 30 seconds to be assigning knobs and sliders to devices. Of course I realize MAx is a different beast .... but I feel Like I'm reading VCR instructions in German.
    Basically how do I assign all the different knobs and sliders to different buttons and number boxes. When I open the Midi set up It seems like my entire device is represented by one name and I can give it one letter and ....... help. thanks jjr

    • Mar 03 2009 | 9:03 am
      Well, of course, Max is not Reason, wich is great in its category btw.
      In fact you are adressing several points:
      _What are the basics of MIDI protocol? _How do I monitor my midi controller inside a max patch? _Do I really need Max/MSP? Maybe Reason is better suited to your project.
      You should have a look at "MIDItester" in the menu "Extra" then tweak the knobs on your controller and see what happens.
    • Mar 03 2009 | 2:00 pm
      Something like Reaktor (or any end-user application) has made a whole bunch of decisions for you already. The MIDI standard itself has its own ways of dividing up what kinds of input gets sent from a knob or fader, and so on. That's all hidden from you by programmers. In this case, you'll need to know two things:
      1. Where do the MIDI messages come from and what does a MIDI message look like?
      You should spend some time looking at the MIDI tutorials 1 and 3 in Max 5. They should be greatly useful to you.
      2. What is it you want to control, and what's the data range of that stuff?
      MIDI kicks out streams of numbers in the range 0-127 for nearly everything, and it's doubtful that 0-127 is going to work well for things like, say, volume (which might be 0. -1.0 if you're working with the *~ object or 0-157 if you want to use a gain~ slider. So I would suggest that you spend some time looking at the Max Data Tutorial 2, which will teach you about scaling data.
      Once you've got that, it's really a matter of connecting outputs to inputs.
    • Mar 03 2009 | 2:04 pm
      And never hesitate to send a small patch if a precise question arises.
    • Mar 03 2009 | 11:44 pm
      i also have a korg nanoKontrol, i hope yours is mapped the same as mine because here's all the inputs from mine. you then just patch the sliders and dials and toggles to anything you want.
      NB this is only one way of doing it - check the ctlin helpfile! NB2 this is while the nanokontrol is set to "scene 1" - you can work out the rest of the scenes for yourself in the ctlin helpfile.
      hope that's a help! nick
    • Mar 04 2009 | 5:08 am
      Thanks a lot ! to you for this great patch, and everyone else for helping, really I just think that the intro to midi tutorials are confusing but now I have figured out basically how to do it.
      One question though with the patch you sent me would you just hide that in a sub patcher of the patch in which you wanted to use it? thanks best jjr
    • Jun 19 2009 | 1:24 am
      hey there.. i think i'm trying to do the same thing as you were back in March with the Nanokontrol.. How'd you go? I COMPLETELY identify with your "reading a vcr manual in german".. But I htink I'm slowly getting it too..
      How did that patch work out for you? Any tips you'd give?
    • Jun 19 2009 | 7:35 am
      Hi - I posted that patch and BaltimoreMAX seemed to find it useful. However, a little while later there was another nanokontrol thread on here, about it dropping MIDI messages when using ctlin. someone called Lewis came up with an abstraction (and a helpfile for it) that got around the problem - it's here: