Trying to access/change the Midi Ports for objects like Note in, Note out, midi in, midi out. Could you please help?

doubleclicking should always work when there is no other problem in your midi setup.

but of course doubleclicking stops beeing the solution when you have the object in a subpatcher or when you dont want to show it to the user.

since you cant open the default port window of [midiin] and his sisters by a message, you have to change port by sending "port b".

that is where omsinfo/midiinfo is coming to play, which can fill you a menu with the "real" names of your midi ports.

Thank you!

I can now see all of my midi devices in a menu that is receiving inputs from a midiinfo object. However, there are other menus that also receive inputs from other midiinfo objects in the same patcher that are not showing most of my midi devices and i don't know why. Also, double clicking is still not working for any of the objects in my patcher.

In the screenshot below, i have copy and pasted the examples from the help section for the midi in, note in, and midi info objects. The menu from the midiin object help (towards the left of the patch) example is working perfectly, but the menus from the midiinfo help example (on the right) are only showing a few devices like MaxMSP 1 and 2 and AU DLS Synth 1.

https://www.dropbox.com/s/7cdiczefliq7y5g/Screenshot%202018-04-04%2009.51.38.png?dl=0

but of course doubleclicking stops beeing the solution when you have the object in a subpatcher or when you dont want to show it to the user.
since you cant open the default port window of [midiin] and his sisters by a message, you have to change port by sending "port b".
that is where omsinfo/midiinfo is coming to play, which can fill you a menu with the "real" names of your midi ports.

Can you please explain more about what this means? I don't think that its in a subpatcher- the midi objects are directly in a midi Max for Live device loaded in ableton, not a patch within the patch. I'm not sure why i would not want to show it to the user (or who the user is), but i haven't purposely done anything to do hide it from the user.

I see that the menu that is working has a midiin b (as well as a midiin a) object that prints to port b (and port a). I'm not sure how the ports work though, and i don't see how these are connected to the midi info or how they allow the menu to see all of the midi devices. What do you mean by 'open the default port window of {midiin} and his sisters" and how do i changing the port to port b?

Also, i don't see any object called omsinfo anywhere- was that a typo or am i missing something?

What do i need to do to be able to see all of the midi devices in all of the menus and/or via double clicking the objects?

some of the midiinfo work and others not? are these others eventually in other patcher windows and you turned the midi button off in these windows?

omsinfo is the same thing just the older name. i thought it would still be linked in 7.3

with "default port window" i meant that window which opens when you doubleclick :)

it might be that doubleclicking doesnt work at all in max4live. probably because it all goes automatic anyway nowaday.

You can't change the MIDI port of midiin/midiout in M4L, that is handled by the track the device is on.

There are updates in Live 10 that allow for grabbing midi from other tracks, but its a different process than simply double clicking (iirc).

some of the midiinfo work and others not? are these others eventually in other patcher windows and you turned the midi button off in these windows?
omsinfo is the same thing just the older name. i thought it would still be linked in 7.3

with "default port window" i meant that window which opens when you doubleclick :)

Ok thanks for clarifying. Yes, in the patcher in the last screenshot i posted, one of the midiinfo is working fully and showing all midi devices, and the other two midiinfo objects (on the right) are only showing a couple midi devices (maxmsp1 and 2 and audls synth 1) in the outputted menu. The other midiinfo objects are not in other patcher windows, only this one (and i tried the same thing from the help window example patcher for midi objects too). I don't know how i would turn off the midi button, but i did not do this on purpose if i did.

If i can't access thru my midi devices thru double clicking, thats ok as long i can access them thru the menu or elsewhere.

You can't change the MIDI port of midiin/midiout in M4L, that is handled by the track the device is on.
There are updates in Live 10 that allow for grabbing midi from other tracks, but its a different process than simply double clicking (iirc).

Thanks. I don't think that i need to grab midi from other tracks in ableton and not sure if i should even be accessing this through ableton and max for live. I'm also using Max for Live for several other ableton related purposes (ie floating mixer window device) and that is the only way that i've used Max so far, so thats why i was going through a max for live device originally, but not sure if i should be doing this through a max for live device or a regular max device. However, i just tried changing the midi port in a new patcher that i didn't open through a max for live device in ableton and i'm still having similar issues in seeing my midi devices.

I feel like i should be able to see the midi devices whether i'm in regular max or max for live accessed through ableton, and i must be missing something simple. I'll explain more specifically what im trying to do here, i think that will make this easier:

In this case, i want to use Max to :

A) send midi commands to Keyboard Maestro trigger Keyboard Maestro actions/macros

B) receive midi commands from Keyboard Maestro to monitor the state of Keyboard Maestro actions/macros

Keyboard Maestro is an general purpose app that can create macros that can run actions for basically any type of computer function on whatever application/purpose on my mac and it is capable of both sending out midi commands as part of the macro and triggering macros with midi commands.

I figure that i can use the make note object in Max along with the midi out object to send midi commands to Keyboard Maestro via an IAC Driver Bus trigger these macros, as well as receive midi commands from Keyboard Maestro with a midi in object recieving midi from an IAC Driver Bus to monitor the state of Keyboard Maestro macros. I've never used IAC driver bus before so i'm not sure if this is the right way to do it, but i saw a tutorial that seemed to show that it will work for this purpose .

So i think that all that i need to do is set up Max to send and receive midi commands. I'm just assuming that i need to specify the Midi Device (to a IAC Driver bus) in max in order to send and receive these midi commands, because right now i'm not seeing any outgoing midi notes/commands/signals from Max in my midi monitor at all and I dont think that Max is receiving any midi notes/commands/signals. However, Max isn't allowing me to pick a midi device to send or receive to because its not showing my midi devices.

Does that make sense? Am i thinking this through in the right way or am i missing something? How can i make this kind of workflow/system work correctly? And, with this specific purpose in mind, does it affect the answer to my original question about why Max won't show me all of my midi devices?

Hi, can anybody please help? I'm still having this issue, its been holding me back from using Max and would really appreciate some help!

Post the simple patch that You use for midi send - receive, nothing else.
This is trivial task, something must be wrong in the patch.
And let's keep it Max only-> no Live involved.