InqScribe lets you create custom shortcuts and assign them to a keystroke (or "trigger") of your choosing. Although you're free to assign a shortcut to any combination of keys, you might run into issues using pre-existing triggers. In this article, we'll go through the "in use" triggers you should avoid as well as which triggers are generally available for assignment.
What shortcuts are already in use?
There are generally 2 types of shortcuts you'll want to keep in mind:
1. Pre-existing InqScribe shortcuts. To avoid overlap, refer to the table of default InqScribe shortcuts below:
Shortcut | macOS | Windows |
---|---|---|
Change Play Roate (-0.1x) | Cmd+9 | Ctrl+9 |
Change Play rate (0.1x) | Cmd+0 | Ctrl+0 |
Advance One Frame | Cmd+] | Ctrl+] |
Rewind One Frame | Cmd+[ | Ctrl+[ |
Cue (2.0x) | Cmd+Shift+] | Ctrl+Shift+] |
Review (2.0x) | Cmd+Shift+[ | Ctrl+Shift+[ |
Skip Back (8 sec) | Cmd+Tab | Ctrl+Tab |
Toggle Pause and Play (0 sec) | Tab | T |
2. Systemwide shortcut. For example, Command+Shift+3 is already assigned as a systemwide shortcut on most Mac computers to take a screenshot. To avoid any problems, refer to the following list of trigger limitations from our shortcut documentation:
Windows Trigger Limitations
- Existing system-wide hotkeys (e.g. print screen) may not be used.
- Avoid key combinations that are already mapped to menu items, like control-; or control-O. Such combinations will trigger both the menu item and the shortcut, which probably isn't what you want.
Mac OS Trigger Limitations
- Existing system-wide hotkeys (e.g. Exposé) may not be used.
- Avoid F1-F4. These are automatically mapped to Undo, Cut, Copy, and Paste.
- Avoid key combinations that are already mapped to menu items, like command-; or command-O. Such combinations will trigger both the menu item and the shortcut, which probably isn't what you want.
- Avoid key combinations that are used to enter accented characters (for example, option-u, option-e, option-a). These combinations are handled by the OS in a special way, and while InqScribe can detect them, InqScribe cannot prevent them from also being typed into your transcript.
What keyboard triggers are not in use?
To avoid inadvertently triggering a shortcut command, we recommend using a modifier such as “Ctrl” (Windows) or “Command” (Mac). As you notice from the above "InqScribe Shortcuts that are in use" chart, many triggers are already assigned. Note that you can also combine the “Ctrl” or “Command” modifier with another modifier, such as the “Shift” key to open up more triggers.
There are many possibilities. If you use video editing programs such as Final Cut Pro or Avid, be sure to check out our blog article “Keyboard Shortcuts for Film Editors” on how to optimize shortcuts across your workflow.
Which keyboard triggers do you use in your workflow? We welcome any feedback on the subject. If you have suggestions for assigning keyboard shortcuts, please contact us at inqscribe.com/support.
What are these mysterious triggers?
Trigger | Definition |
---|---|
undef | If you edit an existing shortcut or snippet and "Clear" the trigger, it is marked as "undef" |
unassigned | If you re-assign an existing trigger to a new shortcut or snippet, the old shortcut or snippet is marked as "unassigned". |