I'm new to KM and I'd like to use it to automate some tasks in Logic Pro.
My goal is to automate the activation/deactivation (toggle) of a specific plug in in the master channel.
I think the best way is to use an action that could find the plug in name and click on it, but I don't figure out how to achieve it.
Note that the plug in can be in different positions (even outside the visible space of the monitor) because of the number of tracks present in the mixer.
I've tried with the action "find and click image" but it doesn't work because the plug in can be active or not in a certain moment, and the color of the button could be different (grey or blue).
The easiest way to do this would be to use a midi command to trigger the plugin bypass. If you wish to use KM for this, rather than a dedicated controller, it's quite simple.
In Logic, go to Prefrences, click on Midi and then Inputs. Make sure Keyboard Maestro is checked.
Bypass or enable the plugin, then open Controller Assigments and trigger your new midi macro. This will associate that command with bypassing the plugin.
Actually, it is pretty easy to take pictures of both states and put them in the "If-Then" action... I use the same method for Bypassing logic's plugin.
If I'm not mistaken, it appears that you're using that to bypass plugins when their GUI is open. In which case, you don't need found images, as the bypass button is always in the same location relative to the front window position.
I did the same, but I felt it was worth changing to avoid the lag induced by searching for the found image.
The only drawback is that if you click away from the plugin GUI, it is no longer the front window. However, I got around this by automating it's selection as part of the bypass macro, using window titles. Still much more snappy than using found images. I only use the Tracks and Mixer windows in my main screenset, so this works fine for me. However, if you habitually change screensets, you could easily create a window name whitelist that includes all your main Logic windows; any other window whose name does not appear on the whitelist would be the plugin window. It's slightly convoluted because Logic, unlike other DAWs, doesn't title plugin windows in an identifiable way.
I added to my previous reply, apparently after you began your latest one. You can see how I got around it, using window names, in this macro: Bypass:Mute:Solo:Clear Solo.kmmacros (73.2 KB)