Keyboard shortcuts do not work at all in SoundFlow 6 on macOS Sonoma
Keyboard shortcuts do not work at all in SoundFlow 6 on macOS Sonoma
System Information
SoundFlow 6.0.5
OS: darwin 23.6.0
ProductName: macOS
ProductVersion: 14.7.5
BuildVersion: 23H527
Steps to Reproduce
- Install SoundFlow 6.0.5 on macOS Sonoma (MacBook Air M2)
- Gave SoundFlow all permissions (Accessibility, Input Monitoring, Full Disk Access)
- LaunchAgent org.soundflow.sfsx is running correctly
- SoundFlow Editor opens normally, macros run
- UI-based actions (like calling Playback Engine window) work
- But ANY keyboard-related command does NOT work:
- sf.keyboard.press({ keys: "opt+shift+3" }) → nothing happens
- built-in "Send Keystroke" action → nothing
- Tried full uninstall: removed all SoundFlow folders & LaunchAgents
- Reinstalled SoundFlow 6.0.x → same issue
- Helper/Agent apps are not created in Applications folder
- Keyboard shortcuts never send to Pro Tools or any app
Expected Result
Running any keyboard-related action (e.g., "Press Keys: option+shift+3") should send the keyboard event to Pro Tools or the frontmost application. Consolidate Clip command should execute via SoundFlow action.
Actual Result
Keyboard events are never sent.
No reaction in Pro Tools or any other app.
UI-based actions work (e.g., opening Playback Engine window).
But:
• sf.keyboard.press() does nothing
• Built-in “Press Keys” action does nothing
• No errors are logged except “TypeError: no method 'shortcut'” when using sf.ui.proTools.shortcut()
Helper/Agent apps are not created after reinstall.
launchctl shows only: org.soundflow.sfsx (no helper/agent processes)
Workaround
No workaround found. Reinstalling, deleting LaunchAgents, giving full permissions, rebooting did not fix the issue.
Other Notes
This issue happens on a clean installation of SoundFlow 6 on macOS Sonoma.
Keyboard permissions and accessibility permissions are fully granted.
Issue persisted even after deleting all SoundFlow folders and LaunchAgents.
Suspect: Helper/Agent apps are not being installed or started.
Links
User UID: HayKtnRXB7Sg8KQ710FWeC8LZIk2
Feedback Key: sffeedback:HayKtnRXB7Sg8KQ710FWeC8LZIk2:-OfZEo5uDixqZZnknbBi
Feedback ZIP: vN7OfN45MOqN82kcwOT/FOq21kWKLWKxITTAiwrbPCzyvr1L4qkdQkyv8pXl06VElnQTgNWjJi1bbYxV8ZA+iT6jfYz7/Imh/I67qOiPNVKCWIHTszD1rWWLHDIL98hzf3AhJJU1OgCVEAmUQGRGztc8ZBFylokOofrTbqch7aVB+7ZZ1LxsCFDW4dg7v8CnONoeXv4CQFEh75DaTisagpDTpmoKCLdbv6+lVhhfxDvje3GNEaqUdK0hsw1dz7L11i76ENdhrXw+MsIhtZLyO1XLUdBdoKGwdA2XJJsJRsi62wFp4mPQlT2CUm35GV3xBJvU6eY5op6sqEmjfP3vuw==
Chad Wahlbrink @Chad2025-12-03 20:15:51.340ZHi, @Moriyuki_Minami5,
Thanks for the questions!
I believe everything should be set up correctly on your machine, provided that UI-based commands are working correctly. I think these issues can be resolved with some scripting changes or by using a macro to simplify everything.
I would suggest creating a new macro and adding an "App Activate" action for Pro Tools, and then adding a "Press Keys" action to press "⌥⇧3" like this:
From here, you can either copy these actions as JavaScript by clicking on the "..." button on each action and selecting "Copy as Javascript":
Or you can use the "Convert to Script" function to convert this macro to a script:
This would give you the script:
sf.ui.proTools.appActivate(); sf.keyboard.press({ keys: "alt+shift+3", });I think the reason your script didn't work as expected was that you used
option+shift+3instead ofalt+shift+3. The press keys action expects the following syntax for modifiers:sf.keyboard.press({ keys: "ctrl+cmd+alt+shift+3", });- ctrl - control
- cmd - command
- alt - option
- shift - shift
Let me know if adding an
appActivate()call and usingalt+shift+3works correctly for you. App activation is important for keyboard simulation to be sent to the correct application.A better and more stable approach would be to use the menu item like this:
if (sf.ui.useSfx) sf.ui.useSfx(); sf.ui.proTools.menuClick({ menuPath: ["Edit","Consolidate Clip"], });↑ This can be run in the background without focusing Pro Tools.
Finally, here's a quick video explaining all of this:
- MMoriyuki Minami @Moriyuki_Minami5
Hi Chad,
Thanks so much for the detailed explanation and video.
I tried the menuClick version and also tested the macro with
Activate App+Press Keys (alt+shift+3)— both are working
perfectly on my system now.It seems the issue is resolved on my end.
Thank you again for your quick support and clear instructions!Moriyuki