Trigger Key Command Won't Record
I'm trying to set Command-Option-Cntrl-L as a key command and when I type it in it won't record. Other key commands will work.
I assume there's a conflict with another app but how do I find out what app is causing the conflict?
Nothing happens when I enter this command.
Chris Shaw @Chris_Shaw2020-12-12 23:48:31.537ZI'm not 100% sure but it may be reserved for the SoundFlow editor/app. For instance, opt-cmd-k is used to assign a keyboard shortcut to a script/macro in the SF editor so it can't be used as a keyboard shortcut trigger.
Christian Scheuer @chrscheuer2020-12-13 00:19:30.315ZThe most likely case is that it gets caught by some other app.
The first place to check is System Preferences -> Keyboard -> Shortcuts. Walk through there and double check it's not already assigned. If there is something assigned there, macOS won't let SoundFlow know about the keypress.
If you can't find it there, then the chances are you have another piece of software interfering. It could be anything, really. The easiest way to find out is to shut down your other apps one by one. Most likely candidates would be apps that are running as icons up by the clock – but it could also be stuff like custom mouse software, video recording software etc.
Chris Shaw @Chris_Shaw2020-12-13 01:03:28.207ZOddly enough I can’t assign that either. Have dig in to find it.
- Christian Scheuer @chrscheuer2020-12-14 16:32:51.568Z
It seems to work fine here. Hope you can narrow it down :)
- Chris Shaw @Chris_Shaw2020-12-14 17:21:00.623Z
It's not a system key command as I am able to assign it to a system function. Must be a menu item or something else
- Christian Scheuer @chrscheuer2020-12-14 17:28:37.759Z
I think it's more likely a 3rd party app. Logitech for example
Phil McGowan @Phil_McGowanUnfortunately I still haven't figured it out but I just added shift to the key command and it's similar enough that I've gotten used to it.
Too bad there isn't some sort of OS level tool that tells you what applications a key command is triggering at any certain time....
- In reply tochrscheuer⬆:
Raphael Sepulveda @raphaelsepulveda2020-12-15 01:13:13.694ZI can confirm that, in fact, the Logi Options Daemon process for my Logi mouse was not letting me use the ctrl+opt+cmd+L as a trigger. If you quit the process you can use that key command, but unfortunately, that means not being able to use your Logitech peripheral as it's supposed to.
It seems to cause a direct conflict with SoundFlow since I'm still able to assign that key combination as an OS shortcut as well as a trigger in Keyboard Maestro while the Logitech Daemon is running.
- Chris Shaw @Chris_Shaw2020-12-15 02:30:55.007Z
That’s why I can’t use it either: I have to use the Logitech daemon for my webcam.
- Christian Scheuer @chrscheuer2020-12-15 15:07:04.725Z
Yea.. Good thing that there's 1000's of other potentially available shortcuts then :)
SoundFlow specifically doesn't use kernel extensions to keep the platform more stable across OS upgrades. Spending hundreds of hours on upgrading a kernel extension for every OS release is a bad way to spend our time, at least while we're still in this stage of the company's journey. One of the downsides is that we have to accept what macOS filters before it reaches SoundFlow. This works for 99.9% of cases, in my experience, but there are corner cases like this one.- Chris Shaw @Chris_Shaw2020-12-15 17:07:59.664Z
There’s at least 360 with f keys and modifiers alone.
Plus not using a kernel extension makes studio more receptive to outside engineers installing SF on their rigs. - In reply tochrscheuer⬆:Raphael Sepulveda @raphaelsepulveda2020-12-15 17:09:03.892Z
Completely understandable!