I’ve been out of town for a little over a week teaching a seminar, and thus unavailable.
It seems you have asked several questions, but I’ll respond to the simplest and most intriguing one first.
You said you made this macro... and it’s not working. Can you verify that the macro group it’s in is enabled? Because in your screenshot, above the trigger, it says “when macro group is enabled”, which indicates to me that the enclosing macro group is disabled, which would prevent it, and any other macros in it, from working.
@cdthomer wwwwow. yup. how embarrassing. ha. noob problems. i swore i realized that and then enabled it with no effect, but lo and behold, that macro works now. So... it seems that at the very least, i can trigger my articulations in Reaticulate and the focus will shift back to whatever window was last active. then i can hit a key command to return the mouse to an absolute position. Awesome!. 2 things that would be ideal would be 1: doing this all in one fell swoop, and 2: getting the mouse to go to a position relative to the "Last engine window" to which the focus goes after I trigger the articulation. I don't know how that correlates to "front window", but when i tried using front window instead of absolute position, for some reason the mouse jumped over to my 3rd monitor. not sure why as that window was not focused. Nonetheless, that's much more of a minor issue. Thanks for pointing out that i didn't have the freakin macro enabled. good lord. haha.
Just to be clear: the "Last Engine Window" refers to the last Window of Keyboard Maestro (not any other App). "Engine" refers to the Keyboard Maestro Engine App i.e. the App that runs Keyboard Maestro Macros.
We’ve all been there at some point. I’ve been using Keyboard Maestro daily for over 5 years now and still have these moments from time to time.
Now that you tracked down the latest issue, I imagine you will be able to combine the two macros into one. As @Zabobon mentioned, that last engine window action is the wrong action to use. Swap that for the Activate Last Application action, or something similar and go from there. Give me a shout if you still run into trouble however.
Hi @cdthomer and @Zabobon Thanks for the info. I've been messing with this on-and-off and noticed that the macro to change the window focus may have not been doing anything as ,through enabling and disabling the KM macro, I've realized that Reaper is automatically shifting focus from Reaticulate back to whatever screen I was on. So really all i need to do is find a way to trigger the mouse to move back to a position relative to what i think would be the front screen's center. I just assigned "move mouse" to a gotten location relative to the front window's center and it seems like that works... with the hotkey. However, I still can't figure out a way to trigger this from touching the touch screen (or in other tests, clicking in the Reaticulate window on a regular monitor with a mouse). Focus shifts from Reaticulate back to the window i was working in but the cursor remains in the Reaticulate window. If i hit the hotkey, the cursor jumps back to the position i set relative to the center of that window. I just can't seem to get it to happen as a result of touching the touchscreen. here's a shot of my current setup. Do you have any other ideas on ways I might trigger the mouse movement? Reaticulate does send out MIDI feedback, and i tried assigning MIDI to do this, but it seems to create some weird glitchy effects and not work very well.
hi,
i just purchased the keyboard maestro... tonight
this thread got me thinking, as i use reaper & other audio applications... also intend on using ipads as secondary screens.
can the mouse position be captured as a first action(and the x/y coordinates saved)... before the execution of the touchscreen action?
a delay in the touchscreen execution, which is preceeded by the save coordinates?
i havent even made a KeyboardMaestro script yet :-s
but i can see the sense in making the mouse return to its original position after a single tap... afterall achieving a mouseless workflow is why we have these KM scripts in the first place.
hi @777enz I'll be curious to hear your experience! i'm still trying to figure out a few things. Right now I am using a key command to return the mouse to the correct location after using the touch screen, which is not ideal, but it seems like it should be possible to get it to work where touching the iPad triggers everything. Although, i'm not sure about capturing the location of the mouse position. Seems like that could be a separate key command, but once you touch the iPad, the mouse has moved, so capturing the location at that point won't work. Maybe there is some other way. as you probably saw in this thread, I just use my iPad for Reaticulate. So the macro is getting triggered when the Reaticulate screen becomes focused. Let me know about your progress! Hopefully these far more knowledgeable people will be able to help.
i use reaper
Personally if i were using Reaticulate... and wanted to use the ipad to make full use of the articulations...
i would go the route of using Realearn by helgoboss... and tie the midi in that way and like wise for any other midi change type.
Realearn in the reaper context acts as a VST... but you can tie in your ipad in a couple of ways i believe OSC ...IAC midi bus thingy
all that said, there must be another reason why you are using the Ipad the way you do...
personally im using Keyboard maestro for the things that work across applications... Reaper is just one of the applications & it is the things that Realearn cannot do... i need Keyboard maestro for
youll have to forgive me... as im still getting my feet wet with Keyboard Maestro... and im about as useful as a sore thumb atm *smiles
thanks @777enz I'll look into Realearn. I'm using Reaticulate on the iPad to be able to have easy access to all my articulation banks quickly and easily. i don't like have to mouse them into the midi editor. with the iPad i can record articulation changes on the fly. Just can't get the mouse to jump back to where it was before I triggered the articulation.
ha. noob problems. i swore i realized that and then enabled it with no effect, but lo and behold, that macro works now. So... it seems that at the very least, i can trigger my articulations in Reaticulate and the focus will shift back to whatever window was last active. then i can hit a key command to return the mouse to an absolute position. Awesome!. 2 things that would be ideal would be 1: doing this all in one fell swoop, and 2: getting the mouse to go to a position relative to the "Last engine window" to which the focus goes after I trigger the articulation. I don't know how that correlates to "front window", but when i tried using front window instead of absolute position, for some reason the mouse jumped over to my 3rd monitor. not sure why as that window was not focused. Nonetheless, that's much more of a minor issue. Thanks for pointing out that i didn't have the freakin macro enabled. good lord. haha.