Install & first-time setup
SlipTap needs two macOS permissions before it can work. It usually takes just a few minutes, and you normally only do it once — though you may need to set the permissions again after moving or updating the app.
Move to Applications Open SlipTap Allow Accessibility Allow Input Monitoring Re-check
System requirements
- macOS 13.5 (Ventura) or later
- Apple Silicon or Intel Mac (universal build)
- Avid Pro Tools with AudioSuite
- About 30 MB of disk space
Trial & license
- A 14-day free trial — no license needed to start
- One license activates up to two Macs
- After activation it keeps working offline, with no time limit
Why two permissions?
SlipTap runs Render, Learn or Send in AudioSuite windows you already have open, from a panel button or hotkey. To do that it has to read Pro Tools windows (Accessibility) and notice the hotkeys you assign (Input Monitoring).
SlipTap only watches for the key combinations you assign — it does not record or transmit what you type. It connects to the internet only for things like license activation and update checks.
Setup steps
1. Move SlipTap to Applications first
Open the downloaded .dmg and drag SlipTap into the Applications folder, then eject the disk image. Do this before you launch it: macOS ties permissions to where the app lives, so if you move the app afterwards macOS may ask for the permissions again.
2. Open it from Applications
The first time you open SlipTap, click Open in the macOS confirmation dialog. macOS may then automatically show two permission prompts: keystroke access (Input Monitoring) and Accessibility. SlipTap also shows “Get started with SlipTap”, listing both permissions.
3. Allow Accessibility
Next to Accessibility, press Request Access if shown. In the macOS prompt, click Open System Settings and turn on SlipTap. If you denied or missed the prompt, macOS may not ask again: use Open Settings or follow the manual path, System Settings → Privacy & Security → Accessibility. If SlipTap is not listed, click + and pick it from Applications.
4. Allow Input Monitoring
For Input Monitoring, use Request Access → Open System Settings and turn on SlipTap too. If you missed the prompt, use Open Settings or go to System Settings → Privacy & Security → Input Monitoring. After ticking Input Monitoring, quit SlipTap completely (⌘Q) and reopen it — the change only takes effect on relaunch.
5. Back in SlipTap, press Re-check
Back in SlipTap, press Re-check. When both permissions register, both rows turn to Granted. If either still does not register, remove SlipTap from that list with − and add it back with +. Then press Start using SlipTap, open your AudioSuite windows in Pro Tools, and use Assign Plug-in to link them to buttons.
If something does not work
SlipTap is not in the Accessibility or Input Monitoring list
macOS only adds an app to those lists when the app asks for the permission, so it can be missing — for example if you dismissed the request earlier. Click the + button under the list, choose SlipTap from your Applications folder, and switch it on.
It is switched on, but SlipTap still says the permission is missing
The list entry can go stale — most often after an app update. Select SlipTap in the list and remove it with the − button. Then click + to open a file picker, press Shift-Command-A to go to Applications, select SlipTap and click Open. Switch it on in the list, then press Re-check in SlipTap.
I closed the setup window by accident
Reopen it any time: click a SlipTap window, then choose Help → Setup Guide… in the menu bar at the top of your Mac screen. The permission status is shown there, so you can finish the setup from the same place.
Hotkeys do nothing, but panel buttons work
That is the signature of missing Input Monitoring — the two permissions do different jobs and SlipTap needs both. Also remember hotkeys fire only while Pro Tools is the front app: that is deliberate, so a render never happens while you are typing somewhere else.
I moved SlipTap after granting the permissions
Permissions follow where the app lives, so macOS may ask for them again after you move it. Keep SlipTap in the Applications folder, then remove and re-add it in both lists.
Both permissions are on, but hotkeys still do nothing
Check the status dot at the top right of the panel. Yellow means another app has turned on Secure Input — a macOS feature that blocks every third-party app from detecting keystrokes, usually because a password field is open somewhere. Close that field or app. Red means the hotkey engine stopped: press Restart Hotkeys.
To find out what is intercepting your keys, click [Check] under Check Keyboard Conflicts in Preferences → Diagnostics. It lists the apps that can capture keystrokes right now; quitting one of them restores your hotkeys.
If the dot is green and both permissions are on but nothing happens, the list entry itself may be stale. In System Settings, select SlipTap and remove it with the − button, then add it back with + by picking SlipTap from your Applications folder, switch it on, and press Re-check in SlipTap.
Nothing happens when I trigger a button
If the assigned window is closed, SlipTap tries to open that plug-in from the AudioSuite menu and then runs the action — so nothing happening usually means the button has no plug-in assigned yet, or the plug-in could not be found in the menu. Open Plug-in Check in SlipTap to see which assigned plug-ins in the current profile aren't open, and open them from there.
The permission prompt keeps appearing
Usually one of the two permissions — often Accessibility — is still off, so its prompt may appear each time you open SlipTap. In System Settings → Privacy & Security, check that SlipTap is on in both Accessibility and Input Monitoring, then quit SlipTap completely (⌘Q) and reopen it.
Still stuck?
Right after the problem happens, open Preferences → Diagnostics → Export Diagnostics in SlipTap and send us the file. It records the app and macOS versions, permission state, hotkey engine, Secure Input, recent actions and errors, and crash information. It does not include Pro Tools session names, file names, clip names, or your license key.
The same tab also offers an AX Snapshot, which we may ask for when window detection behaves differently on your setup. That file can contain session, track, clip or file names — have a look before you send it.