Skip to content
DOCS

Troubleshooting

Fixes for the problems people hit most in Studio, and where to find the log.

The preview won't startLink to this section

  • Rebuild required: there's no build of this version yet. Build again.
  • No CLAP build: the project's own files don't build a CLAP. Add CLAP support (JUCE: clap-juce-extensions; iPlug2: CLAP in its formats; NIH-plug: nih_export_clap!).
  • Build required: this version crashed earlier. Fix the code and build again.
  • Unavailable for native plugins: plugins made with No Custom UI have no window, so they can't be previewed. Test them in a DAW.
  • Rebuilds may reload unreliably or Use Freqlab's WebView library (macOS): the project needs a small change so the preview stays reliable after a rebuild. Click the notice beside Start Preview, then Copy the Fix, or, with an agent set up, ask the agent to make it.

A build is stuck on old codeLink to this section

Use Clean Build in the arrow menu beside Build. If it keeps happening, turn on Never cache for this project.

My DAW doesn't see the pluginLink to this section

Publish it with Publish to DAW, then rescan plugins in your DAW. Check the folders in Settings, DAW Paths match where your DAW looks.

The editor shows errors that aren't realLink to this section

For C++ projects, clangd can't see JUCE or SDK headers until the project is built. Build once; the errors refresh. If code help is missing altogether, install the language server in Settings, Intelligence.

macOS keeps asking for accessLink to this section

Turn on Freqlab Studio in System Settings, Privacy & Security, Full Disk Access.

The disk is filling upLink to this section

Clear Studio's caches in Settings, Storage. The Rust cache alone is often 5 to 20 GB.

The log fileLink to this section

Settings, Troubleshooting, Log File: View Log, Show in Folder or Copy, to send with a support request.