MIDI port problem

    Jul 30 2013 | 1:42 am
    Hi! I'm testing the demo of Max (4 and 6) on Windows 7 and I'm very happy so far. I want to use Max for controlling and sequencing some MIDI gear and it works fine so far, but now I'm running into some trouble selecting MIDI ports... I can select the ports when the patcher is locked by double-clicking the object, no problem, but what I'd like to do is giving the objects a [port( message like [port a( and so on... In Max 4 it works for all devices like MIDIyoke e.g. except the one of my cheap interface (I'll need a better one soon, but for now it's ok) which would be port k now. If a [port k( message is sent, the object doesn't select it, port a-j work fine.. So, hm, then I tried the current Max and it's even worse because the objects in v6 don't recognize any of the port messages...

    • Jul 30 2013 | 6:09 am
      Max's MIDI stuff understands a port message.
    • Jul 30 2013 | 7:21 am
      Thanks, I know it understands port messages, but not mine :) - that's the problem, when I open your patch and select a device I get "bad arguments for message port"-error
    • Jul 30 2013 | 4:59 pm
      How does midiinfo populate the menus? Do the menus look similar to the list that is presented by double-clicking on notein and note out?
    • Jul 30 2013 | 5:01 pm
      Also, there was a missing patch cord from the message box that held 1 and the midiinfo in my above patch: