Troubleshooting

Plugin doesn’t appear in DAW

• Verify the plugin files are in the correct directory for your OS (see Installation)
• Rescan plugins in your DAW’s preferences
• On macOS, you may need to bypass Gatekeeper: right-click the .vst3 → Open, or go to System Settings → Privacy & Security → Allow

Plugin crashes in Ableton (SIGKILL / Code Signature Invalid)

If building from source: when reinstalling the plugin, you must delete the old .vst3 bundle before copying the new one. Overwriting corrupts macOS’s kernel code signature cache, causing Ableton’s Rosetta plugin scanner to kill the plugin.

DAW keyboard shortcuts stop working after Save/Load Set

After using the Save Set or Load Set file dialogs, keyboard shortcuts like Space (play/stop) may stop reaching the DAW. This is a known limitation of WebView-based plugin UIs — the file dialog can leave keyboard focus in the plugin’s WebView.

Workaround: click the DAW’s main arrange/session window once to return keyboard focus to the host.

No MIDI output

• Confirm Tabbal is routed to a MIDI-receiving instrument in your DAW
• Check that at least one cell is active and the row is not muted
• Verify the MIDI OUT selector is set to “DAW: Tabbal” (or the correct external device)
• In standalone mode, make sure you’ve pressed Play

Clips not loading

• Check that the clip files exist in ~/Library/Tabbal/Clips/ (macOS) or %APPDATA%\Tabbal\Clips\ (Windows)
• Factory clips are copied on each plugin load in development builds; for release builds they are placed by the installer