I'm not sure if I'm allowed to repost answers from ChatGPT here, but it said yes to your first question, and gave a qualified/limited yes to your second question (i.e., output only, not input.) Do you have access to ChatGPT?
Keyboard Maestro can send MIDI messages, which effectively come from a device named âKeyboard Maestroâ. The device will be created as soon as you add any MIDI action.
That device does not appear as any sort of object in Audio MIDI Setup, and you should not need to use IAC. It does appear in, for example, the list of available MIDI inputs in Logic Pro.
Logic Pro and, I would expect, just about any other DAW, could be used to route that MIDI input to a hardware output
Pitch bend can be dealt with as a MIDI packet. This Web page goes into detail.
I have just put together a scruffy little macro that sends a Note On message, a few pitch bend messages (separated by pause actions) and then a Note Off message. It looks like this:
With a synthesiser plugin loaded here into Logic Pro (with MIDI input set to either âKeyboard Maestroâ or âAllâ), it sounds something like this... Nope, I canât upload audio here, but it does work..! The pitch bend values just cause a sort of pitch glitching with the way I have done it. I have not taken the time to move smoothly over changing pitch bend values or anything like that.
So Keyboard Maesto might be able to do what you have in mind for it, but you should try KM out before buying (which is officially encouraged anyway, to make sure you will be happy with it) and see if you can implement some of your ideas in macros in a way that suits you. KM is not primarily intended as a MIDI processing application, of course. It is just very versatile, one way and another!
KM can receive cc, note on/off and raw midi from any IAC port, from any hardware port, and from the virtual port called "Keyboard Maestro"
KM can send cc, note on/off and raw midi only to the virtual port called "Keyboard Maestro". It's not possible to send midi messages to IAC ports or hardware ports.
I am not sure if we should start posting vague ChatGPT answers on topics we canât answer by ourselves on this Discourse or if it would be better to wait for someone who just knows.
I didnât address the question of receiving MIDI, did I, but yes a MIDI trigger can indeed be used to listen out for any MIDI data that is being transmitted.
I think itâs true to say that a Send MIDI action acts like an attached MIDI keyboard would: it transmits the MIDI data and it is then up to whatever is receiving MIDI to process it if applicable.
I mentioned that MIDI routing can be handled in the DAW. That would, in general, probably be the easiest way. There are also MIDI routing utilities such as MidiPipe.
No problem; it often happens with longer threads and anyway it must sometimes be useful to see people recommending the same possible solution.
As for forgetting that KM is only for MacOS: I think I did too once, way back, and if not I have certainly made bigger howlers. Anyway, now any casual visitors or AI chatbots should be under no illusion (or hallucination) on that point!
Remember that (see previous replies), although a KM macro can output a MIDI message, it is up to your DAW (or whatever is attached to your MIDI interface) to be listening. âTo my DAWâ does not apply to the output from your KM macro any more than it would to, say, an attached MIDI keyboard. If you move the modulation wheel on the keyboard, you do not expect the keyboard to handle the routing; in the same way, KM can send MIDI messages but it is not a MIDI router. MidiPipe has already been recommended if the routing within your DAW is not sufficient.
You can of course use the hotkeys that you mentioned as macro triggers. Those particular choices might however already be in use by your DAW, so watch out for that. For example, in Logic Pro, â-1 is the default key command for âopen main windowâŚâ and â-2 is the default for âopen mixerâŚâ (although I, as a Logic Pro user, never use those commands!).
Here is a macro that sends âcc1 channel 1 value 127⌠after pressing cmd+1â. Just one action is needed to do that, but of course, if you wanted to send a gradually changing range of modulation wheel values, the macro would become a little more fiddlyâor rather, getting the timings right might take some work. So do not be tempted to think of KM as a MIDI toolbox for anything too sophisticated. It could probably cope if you put enough work into it, but it might not be your best tool for the job, if you have anything ambitious in mind.
Sorry, I think my previous question was not accurate. I will try it again.
I understand that KM is not a midi router and it sends midi messages as a piano keyboard, There is only one output port. That's clear.
I know how to manage the input ports of my DAW and the input ports of my audio device, no problems or doubts here.
I know how to configure the shortcut triggers and the midi actions in KM. No doubts here.
What I don't understand is how to route the ports with MidiPipe, because if I route the "Keyboard Maestro" port to "myDawPort" and also to "myAudioInterfacePort" I will be always sending the same midi message to both ports, and that would be a mess.
So let me change the question to:
I want to send cc1 channel 1 value 127 to "myDawPort" after pressing cmd+1
I want to send cc1 channel 1 value 127 to "myAudioInterfacePort" after pressing cmd+2
Is this possible using MidiPipe? How should I configure MidiPipe to send the midi message only to one port and not to both ports?
Hope my question is more clear now, sorry for the inconveniences!!
It had been quite a few years since I had last experimented with MidiPipe but I have just taken another look at it.
The underlying issue remains that a MIDI message is available to any device that is listening out on the same MIDI network to that port, on the same channel. If a âpipeâ is created to process MIDI in MidiPipe, then we can see in Logic Pro that MidiPipe is available as a MIDI input. If the track in Logic for a virtual instrument is set (within Logic) to listen only to MidiPipe rather than âAllâ inputs, the instrument will sound only to MIDI data from MidiPipe. That actually has no advantage, for our purposes here, to just setting the input to Keyboard Maestro.
So in fact MidiPipe might be a bit of a dead end for this situation (unless someone else here has more experience of it and can correct me on that).
In Logic Pro there are a few ways to limit which of its MIDI inputs it will respond to. I refer to Logic because that is the DAW that I use, and I do not know what DAW you useâbut, in conclusion, it seems to me that it will probably be best to first look into routing possibilities in your DAW, especially if it is the centre of your workflow.
ChatGPT is so inconsistent in its responses, and frequently gives entirely incorrect answers regarding Keyboard Maestro that reposting such answers is not recommended. Only post answers to things you personally have knowledge of (which, if you gain that knowledge by asking ChatGPT and then verifying the answer is correct would be perfectly fine).