No internet connection
  1. Home
  2. How to
  3. Pro Tools

Change behaviour of hotkey using Soundflow?

By Joachim Jorddal @Joachim_Jorddal
    2024-03-11 14:14:38.266Z

    Is there any way I can change the behaviour of hotkeys in Pro Tools using Soundflow?
    I sometimes hit the incredibly annoying Enter hotkey by accident, taking me to 00:00:00:00 which I never ever need as my projects never start at 00:00:00:00. Disabling the hotkey or changing the behaviour to something useful would be a huge relief. Is this possible? If not, are there other solutions?

    • 3 replies
    1. Chad Wahlbrink @Chad2024-03-11 16:12:26.532Z

      Hey @Joachim_Jorddal!

      There are a few options for this. First, Pro Tools has a keyboard shortcuts manager built-in to the latest versions of Pro Tools. You can open this from the Menubar via Setup > Keyboard Shortcuts... or ⇧⌃K. From there, you can click "Search By Key" and hit "Return" to see all shortcuts that are tied to "Return."

      From there, you can hover your mouse over the Key Combination for "Return to Zero" and click the little "X" to remove that key command.


      Alternatively, you can also create any SoundFlow command to be triggered from the "Return" key by setting up a keyboard trigger. SoundFlow Commands will take precedence over default commands in Pro Tools, so they can be used to change default keyboard commands to anything you'd like.

      1. MMatt Friedman @Matt_Friedman
          2024-03-23 19:08:44.575Z

          I have a follow up question to this.

          Say you set a trigger in SF to take precedence over a Pro Tools kybd shortcut. Can you still use that keyboard shortcut in your script and will that work as expected or create some kind of SF error/loop?

          For a silly example, say you make a SF script to save the session using Command-S as the trigger. In your SF script could you use sf.keyboard.press({ keys: "command+s" }); to trigger the save (or must go through selecting Save via menus)?

          1. @Matt_Friedman, using a keyboard shortcut in a script assigned to a command's trigger in SoundFlow will not trigger that command, instead, it will pass it off to Pro Tools.

            In your example, using sf.keyboard.press({ keys: "command+s" }); in a script will do a save in Pro Tools. If you have a SoundFlow command with command+s as the trigger, that command will not fire.