Yes, I back it up to many local and cloud locations, so I'm not worried about losing it. In short, it's the single most-used app on any of my Macs.įor as much as I love KM, it has one major shortcoming: All of those macros live in one large XML file. I use KM for everything from gathering monthly utility bills to inserting HTML code in blog posts to generating replacement license files for users to controlling iTunes to decrufting URLs when copying (future post coming on that one) to automatically naming and filing documents I scan to storing snippets for insertion into our apps' help files to opening oft-used URLs to adding key functionality to many apps such as Excel, Mail, Messages, Photos, Preview, Safari, etc. (These are not all user-facing many are macros that support other macros.) In terms of actual macros, there are over 425 at present. How much do I rely on it? The shrunken image at right lists all of my macro groups-not macros, just the groups holding the macros. I have not tried in Cubase yet.As much as I rely on our own Many Tricks' apps every day, there's one I rely on more: Keyboard Maestro (KM), the macro app for macOS that can do pretty much anything. for reasons still unknown to me, the macros that didn't fire when set to use keyboard shortcuts (I checked to make sure they weren't duplicates in the system shortcuts - in there almost everything is disabled, though so that wasn't an issue) began working when I decided to change to trigger MIDI note on instead and now it's working.
However I noticed the keyboard maestro error went away in the console so that was promising. After doing that I was able to fire some macros in Pro Tools but others wouldn't fire. Next I disabled IPv6 in the Metaserver app and chose USB connection only since my iPad remains connected via USB constantly.
I'm not sure what changed or which step actually solved the issue but here's what I did:įirst I went to my documents directory (Command+I on the documents folder) and added the Administrators group with read/write access then applied that to all enclosed items just in case the server app was unable to access the cubase XML files.
HOWEVER, after a couple of steps I was able to get metagrid to trigger some macros but I had to change some to trigger via MIDI note on rather than the keyboard shortcuts that have been working for a couple years. Thank you, Przemek, I tried the uncheck and recheck step in the Automation tab of Privacy ad Security but it didn't help.
0 kommentar(er)
