Bring an existing project
Import a JUCE, NIH-plug, iPlug2 or other CMake or Cargo plugin project into Freqlab Studio or Freqlab Express, and get it building, previewing and ready to release.
Your project stays where it is: importing doesn't copy or move it.
1. Check it builds with CMake or CargoLink to this section
- JUCE: it needs a
CMakeLists.txt. A Projucer-only project doesn't import until you add one (JUCE's CMake guide shows how). - NIH-plug, or any Rust plugin: a Cargo project.
- iPlug2 or any other C++ plugin: a CMake project.
If it uses git submodules, have them checked out, or let the app set them up when it asks.
2. Import itLink to this section
Click Import Project (under +), Browse… to the folder, check what Studio detected, and click Import Project. See Import or clone a project.
For a CMake project, your CMakeLists.txt decides which formats are built. With Update CMakeLists.txt when build formats change on, changing the formats in the app edits that line for you.
3. Make sure it builds a CLAPLink to this section
Studio's preview and Real-time Check play the CLAP, and the Freqlab Standard checks it with clap-validator. Studio's import tells you if your project doesn't build one. To add it:
| Framework | Add |
|---|---|
| JUCE | clap-juce-extensions |
| iPlug2 | CLAP in its FORMATS list |
| NIH-plug | nih_export_clap! |
4. Build and check itLink to this section
Build it, then (in Studio) start the preview to hear it. Before you release it, pass the Freqlab Standard.
5. Build it in the cloudLink to this section
A cloud build makes macOS and Windows versions in one go, signed once you've set up signing. Leave big folders out of the upload, like sample libraries or test assets (Studio: Project Settings, Cloud Build; Express: Cloud excludes): the free plan's limit is 10 MB. See Studio cloud builds or Express cloud builds, then From plugin to freqlab.co.