6/19/2023 0 Comments Keyboard maestro forumSo if it tries to simulate the same key that you are holding down, in a password field, it will still simulate the press and release, but because the key is already held down, the press will not do anything and the keystroke will be lost. Because of this, Keyboard Maestro does not know that you are still holding down a key and therefore cannot know to release it. However, in a password field (or any time Secure Input is enabled), Keyboard Maestro and other applications cannot see the state of the keyboard (for obvious security reasons). If the key is already being held down by you (eg because you pressed the key as a trigger), then Keyboard Maestro notices this, and first releases the key, and then presses and releases the key. Can anyone make sense of this?Ĭonst logic = sf.ui.app('10') const pluginPath = Ĭonst inspectorBtn = .is('Control Bar').('Inspector').When Keyboard Maestro simulates a keystroke, it simulates both the press and the release. For example, this one inserts a plugin (in this case, Fabfilter Pro-Q3) in the first available channel slot. The Soundflow forum contains a lot of shared scripts and I'm wondering if any of them could be triggered by KM. If anyone actually wants to see it (lol) let me know and I'll repost the link. And combining Keyboard Maestro with a Stream Deck is pure joy.ĮDIT: felt spammy so I removed the link to my video on the 'template builder'. There's all kinds of 'logic' operators, if/then statements, switches, variables, multiple clipboards, user input fields, it's pretty crazy awesome. Bringing up snippets of code, building banks, setting fall-offs, etc. I also use KM when doing game audio implementation all the time. Say doing 2,000 lines of VO that need to be cleaned up, and named properly according an excel sheet. I also use KM when doing game audio VO all the time. Just yesterday I built a pretty big macro for Pro Tools when bouncing out stems (for audio post work) where I can choose what kind of stems/mixes I need (radio, broadcast, web, VO stem, SFX stem, etc.), what kind of format/file type, and it does it all for me, places everything in a folder with the correct name, places the stems in a "STEMS" folder, zips it up for delivery, etc. So I don't need a dedicated button for SCS, another button for Ark1, another for BWW, etc. And all done from one single command/button. Really nice when you just want to see all short notes from a particular library. So I can look for say just violins, or just SCS violins, or JUST staccatos, or just SCS staccatos, etc. Also, HUGE time saver for finding tracks. I also use KM for what is essentially an 'inception template', where it's basically a template within a larger template of just the tracks/favorites I want to use for the current track I'm working on. I also use KM to build macros when ever I need to set a value, so instead of having 20 commands for say Velocity = 10, Velocity = 20, etc., I just have one button and then tell it what velocity I want it to be. Names tracks, colors them, routes them to specific stems and reverbs, connects to VEPro, creates new Kontakt instances, assigns automation parameters, etc. For example I built what I call a "template builder" (I can post a link to the video if you want) where it essentially builds my template for me. I've made some pretty massive macros with it for Cubase. It really doesn't matter what application you're using, or whether it's even a DAW, etc. Yeah Keyboard Maestro is an amazing tool.
0 Comments
Leave a Reply. |