FAQ & troubleshooting

Releases are code-signed (Azure Trusted Signing), so the installer shows a verified publisher. SmartScreen reputation still builds up over the first downloads, so it may warn for a while on a fresh release — click More info → Run anyway.

1. Check the control surface is loaded in Ableton: Preferences → Tempo & MIDI → Control Surface → Protocol 0.
2. Confirm the binding exists in the web UI at http://127.0.0.1:9010/shortcuts — it should be in the bindings table.
3. Make sure Ableton is the foreground window. Shortcuts are intentionally ignored everywhere else.

The UI is served by the agent — the background app on your machine, not Ableton. If http://127.0.0.1:9010/shortcuts doesn't load:

• Make sure the agent is running — look for the "P" icon in the system tray (left-click it to open the UI). If it's gone, launch Protocol 0 from the Start Menu.
• Check the agent log at %APPDATA%\Protocol0\logs\agent.log for a startup error (e.g. port 9010 already in use).

The agent couldn't reach the in-Ableton action API. Make sure Ableton is open and the control surface is enabled; then check the agent log for details.

If your Live install is in a non-standard location, the wizard offers a step to point at the MIDI Remote Scripts folder manually — typically:

C:\ProgramData\Ableton\Live 12 Suite\Resources\MIDI Remote Scripts

Autostart is a shortcut in your Startup folder (only created if you kept "Start at login" ticked during install). You can see and toggle it in Task Manager → Startup apps (look for "Protocol 0"), or open the folder directly:

%APPDATA%\Microsoft\Windows\Start Menu\Programs\Startup

If it's missing, reinstall with "Start at login" ticked, or launch Protocol 0 from the Start Menu whenever you need it.

They shouldn't — bindings live in %APPDATA%\Protocol0\shortcuts.json, which installs and uninstalls leave alone. If the file got hand-edited into invalid JSON, the agent treats it as empty (no shortcuts) rather than crashing. Open the web UI and re-add the binding, or fix the JSON.