Guide >
Common problems
Check the module’s prerequisites before retrying. Repeated clicking cannot repair a connection or missing file.
Chat does not reply or cannot control REAPER
- •In Preferences → AI / LLM, test the connection and check address, model, Key, and provider balance.
- •In REAPER Bridge settings, confirm it is connected, not merely deployed.
- •Check host availability. Unreleased Wwise, Pro Tools, and Ableton entries cannot run actions.
- •For selected-track or Item requests, actually select the targets in REAPER first.
No search results or similarity matches
- •Check databases, folder scope, locked terms, and filters. Try clearing restrictions.
- •Confirm scanning completed and source files are accessible. Audio similarity also needs completed analysis.
- •Test AI separately for Smart Search; working text search does not prove AI is configured.
- •Listen to a recorded reference to rule out silence, low level, or an incorrect input.
Playback is silent
- 01Check output in Preferences → Audio, system volume, and app audition volume.
- 02Confirm at least one channel is enabled and the playhead is in a sounding region.
- 03Check the original file in Explorer. Reselect output after changing devices.
A project will not open or its preview fails
- •Rescan after moving projects. Open the .rpp in REAPER to check project and media paths.
- •Set a Time Selection before exporting, and check that Bridge is connected to the correct project.
- •Re-export a stale preview rather than treating old audio as the current project.
Model downloads or plugin capture fail
- •Models: inspect the task error, free disk space, and download availability. Retry as appropriate; end tasks using a model before repairing it.
- •Plugins: check the REAPER path and capture service, recapture, or upload an image manually.
- •If the problem persists, report the module, steps, error, and app version through feedback or Support. Do not include secrets.