FAQ

SYNAPSE or SYNAPSE FX?

• SYNAPSE: instrument track, MIDI input
• SYNAPSE FX: audio track / insert

Difference between Mode A and Mode B?

• Mode A Bridge: controls plugins already in the session
• Mode B Host: plugin loaded inside SYNAPSE

Both modes can coexist.

Plugin not visible in the browser?

• Relaunch Scan Plugins
• Check VST3/AU paths
• Restart SYNAPSE after installing new plugins

Fast Mode or State Chunk Mode?

• Fast Mode: recommended mode, fast and stable in real time
• State Chunk Mode: useful for plugins with complex internal state

Sanity Mode blocks some parameters, is this normal?

Yes. It protects critical parameters (bypass, mute, output gain, sensitive routing).

Can I work offline?

Partially yes. Local control is possible. Cloud providers require internet.

How many snapshots?

The current spec documents 12 slots.

How do I configure the MCP server?

1. Start SYNAPSE in your DAW.
2. Retrieve the token: ~/Library/SYNAPSE/mcp_token.txt
3. Configure your MCP client (e.g. Claude Desktop):
   • URL: http://127.0.0.1:52100/mcp
   • Header: Authorization: Bearer <token>
4. Use list_hosted_params to discover parameters, then set_param / set_params_batch to control them.

MCP — what is the difference between set_param and trigger_ai?

• set_param / set_params_batch: applies values directly, instant, no network call.
• trigger_ai: sends a natural-language instruction to cloud AI (Claude/OpenAI/etc.) — slower (1-10 s), non-deterministic.

Use set_param for direct control. Reserve trigger_ai for creative AI assistance.

Are macros saved?

Yes. Macro bindings are serialized in getStateInformation and restored from setStateInformation — they are preserved when the DAW project is saved and reloaded.

Where are logs and data stored?

macOS

• ~/Library/SYNAPSE/
  • mcp_token.txt — MCP authentication token (rotated on each plugin load)
• ~/Library/Application Support/SYNAPSE/
  • known_plugins.xml — plugin scan cache
  • ai_settings.json — AI configuration
  • ui_prefs.json — UI preferences (including window size)
  • synapse_knowledge.db — VST plugin knowledge database (SQLite)
• ~/Library/Logs/SYNAPSE/

Windows

• %LocalAppData%\SYNAPSE\

Some parameters are not affected by AI — why?

SYNAPSE excludes certain parameters from AI writes to protect the audio signal:

• Non-automatable params (isAutomatable() == false in VST3): preset selectors, program change, wavetable browser, engine type, OSC routing. These are UI-only states the VST3 protocol does not expose.
• AlwaysCritical params: preset/program/bank, MIDI routing, voice count, arp/sequencer mode, OSC enable/disable (on/off toggles).
• SanityCritical params (when Sanity Mode is ON): bypass, mute, solo, output gain, master volume, wet/dry.

Use list_hosted_params_ai_ready via MCP to see exactly which parameters are available for AI control.

Common plugin limitations:

Full compatibility matrix: docs/plugin-compatibility-matrix.md §9

Limits of the LE version?

According to the spec: limited targets/snapshots, Mode B disabled, Creative Engine unavailable.