Is it possible to nest a MIDI trigger inside an If-Then action?
In other words, if KM receives a specific MIDI trigger, THEN do these actions.
If this isn't possible, please consider it a feature request. I know I can use MIDI triggers to trigger an entire KM workflow, but AFAICT I don't think I can use a MIDI trigger as an "if" trigger.
You can evaluate whether a keyboard key is pressed but you can't evaluate whether or if a user is going to press a key. Similarly you can't evaluate whether someone decides to press a midi key although maybe you could tell if a midi key is currently being pressed.
That's the best i can answer because right now I'm on vacation and accessing this website through my iPhone.
OK, I see what you mean. Sorry I was confusing triggers and conditions.
I guess I can set up an individual macro for every single "when the user hits this MIDI note" that I want; I was just hoping to have them all in one macro to keep things organized.
No matter; I can use folders instead.
Yes, triggers are events, conditions test state.
You can have a generic MIDI trigger using the MIDI packet variant of the MIDI trigger. You can then use the TriggerValue token to determine which actual note was pressed and behave in different ways, and the TriggerValue can be tested in a condition.
Thanks @peternlewis! This opens a whole new way to use my midi devices.
If I wanted to do this, how would I set up the trigger? I can choose a MIDI trigger but don't know how to tell it "any MIDI."
Come to think of it, I generate thousands of MIDI events every hour, so KM will go nuts if I'm not more specific. How would I tell it "any note from a specific device"?
See the MIDI trigger documentation. You will need to understand MIDI packet formats. The trigger can be limited to specific devices.