Surge XT: one CMake build produces VST3, LV2 you must switch on, and VST2 you may not redistribute
Synthesizer plug-in (previously released as Vember Audio Surge)
At a glance
- What is it?
- Surge XT is a hybrid synthesizer written in C and originally sold as a commercial product, released under GPL3 in September 2018 as a partially finished 1.6. The plugin formats are not equal citizens: VST3 builds by default, LV2 needs a CMake flag, and VST2 builds only against your own copy of the SDK because of licensing.
- Who is it for?
- Build Surge XT from source if you are a musician who wants the binaries the team ships, or a developer who needs the Python bindings, and download from the project website otherwise. Check which format your host loads before you start: VST3 and AU are what a normal build produces, while LV2 needs -DSURGE_BUILD_LV2=TRUE and VST2 needs the SDK pointed at by VST2SDK_DIR and may not be redistributed.
- Can I use it commercially?
- Yes, with conditions. GPL-3.0 is a copyleft licence: if you distribute software that includes it, you must release that software's source code under the same licence. Running it internally without distributing it does not trigger that obligation.
- Is it still maintained?
- Yes. The repository last received commits 2 days ago.
- What is it written in?
- Mainly C, according to GitHub's language statistics.
Answers come from the project's GitHub data, last synced on November 15, 2026, and from our analysis. They are not legal advice.
Star history
- surge-synthesizer/surge4,135 ★ · +109
| Repository | 2026-09-24 | 2026-11-15 |
|---|---|---|
| surge-synthesizer/surge | 4k | 4.1k |
109 Stars in the last 52 days, measured from the daily GitHub snapshot. Compare with other projects
Editorial analysis
VST2 is the format the licence will not let you hand on
Three formats, three different statuses. VST3 is what a normal build produces and the readme even gives you a shortcut for it alone, telling you to replace the final build command with:
cmake --build build --config Release --target surge-xt_VST3LV2 is available but off. Surge XT 1.3 moved to JUCE 7, which brought LV2 support with it, and for a variety of reasons the project does not build LV2 by default or in its CI pipeline. You switch it on yourself:
cmake -Bbuild -DSURGE_BUILD_LV2=TRUEVST2 is the awkward one. Due to licensing restrictions, VST2 builds may not be redistributed, though building one for your own personal use is possible. That distinction is the reason the section exists at all, and it is why the only format in this repository that requires you to supply a third party SDK is the oldest one.
The VST2 build needs your own copy of the SDK
Because you cannot get the SDK from this project, the readme tells you to obtain a local copy of the VST2 SDK and unzip it somewhere of your choice, then point an environment variable at it.
On a shell:
export VST2SDK_DIR="/your/path/to/VST2SDK"On the Windows command prompt:
set VST2SDK_DIR=c:\path\to\VST2SDKThen you configure into a separate build directory and build the two targets by hand:
cmake -Bbuild_vst2
cmake --build build_vst2 --config Release --target surge-xt_VST --parallel 4
cmake --build build_vst2 --config Release --target surge-fx_VST --parallel 4Note that this uses a different build directory from the main build, so a VST2 build does not clobber your VST3 one. The outputs land under `build_vst2/surge-xt_artefacts/Release/VST` and `build_vst2/surge-fx_artefacts/Release/VST`, and the readme points out that the `--parallel` value is what sets how many cores the build uses.
The staged-assets target is what makes a build usable
The main build recipe is five commands: clone the repository, change into it, update the submodules recursively, configure with CMake, then build one target.
git clone https://github.com/surge-synthesizer/surge.git
cd surge
git submodule update --init --recursive
cmake -Bbuild -DCMAKE_BUILD_TYPE=Release
cmake --build build --config Release --target surge-staged-assetsThe target name matters. A plain build gives you compiled objects, but the binary assets land in `build/surge_xt_products` and they are staged by that specific target. The readme describes this as often enough of a formula to do a build, which is the giveaway that the rest is optional.
There is a detail that costs people an afternoon. The configure line says `-DCMAKE_BUILD_TYPE=Release` and the build line says `--config Release`, and the readme adds a parenthetical instruction to replace Release with Debug or RelWithDebInfo consistently in both lines as you need. Get that wrong and you get a Release configure with a Debug build, or a configuration the generator ignores.
Submodules are a required step, not an optimisation
The third command in the recipe is `git submodule update --init --recursive`, and the repository carries a `.gitmodules` at the root with a `libs/` directory beside it. The recursive flag matters: the submodules have their own submodules.
Skipping this step gives you a tree that configures and then fails, which is a worse outcome than a build that never starts, because you have already spent the CMake step. The readme's ordering puts the submodule step before the configure step deliberately, and following the order as written is the cheapest way to avoid the problem.
The root also shows what else a build of this project touches: `src/` for the synthesizer source, `resources/` for the assets that get staged, `cmake/` for build modules, `scripts/`, `doc/` for the developer guide and the Git how to, plus `azure-pipelines.yml` and `.clang-format`. That last one means there is a defined C style, applied by a tool rather than by convention.
Python bindings need a separate build directory named for gitignore
Surge XT exposes its internals to Python through pybind, and the readme describes this as mostly useful for developers, pointing at the separate surge-python repository for examples.
The binding is off by default and needs its own configure:
cmake -Bignore/bpy -DSURGE_BUILD_PYTHON_BINDINGS=ON -DCMAKE_BUILD_TYPE=Release
cmake --build ignore/bpy --parallel --target surgepyThat directory name is not arbitrary. The readme says it could be anything you want, and then explains why `ignore` is handy: that directory is ignored via `.gitignore`. So the convention is to build Python into a path the repository already excludes from version control, which keeps a large build tree out of your status output.
The result is a native extension with a platform specific name. On macOS you look in `ignore/bpy/src/surge-python/` for a `.so`, on Windows in `ignore/bpy/src/surge-python/Debug/` for a `.pyd`. The readme shows a Python 3.11 interpreter on darwin producing `surgepy.cpython-311-darwin.so`, and a Windows example named `surgepy.cp312-win_amd64.pyd`.
ASIO is in the box because Steinberg changed its licence
On Windows, building with ASIO is often preferred for the standalone, since it lets users reach the ASIO low-latency audio driver instead of the default Windows audio path.
The reason there is no build procedure for it is stated plainly: the project is grateful to Steinberg Media Technologies for updating their licensing to include GPL3 as a option, which allows ASIO support to be provided out of the box with no special build steps.
That is worth understanding as a mechanism. Low-latency audio on Windows is gated behind a proprietary SDK whose terms originally excluded GPL software, and the fix was not a workaround or a replacement driver but a licence change at the vendor. The readme gives no CMake flag for ASIO because there is nothing to pass.
The readme says it is the developer docs and hands the rest to two documents
This readme states that it serves as the root of developer documentation, and then it is careful about where that documentation stops. Contributor workflow revolves around GitHub issues in this repository and the Discord server. The developer guide lives at `doc/Developer Guide.md`, and the readme notes it covers testing and debugging in particular hosts on particular platforms. A separate `doc/How to Git.md` covers the Git workflow, described as tailored at Surge XT development, and there is a separate section for developing from your own fork.
The fork section is short by design. You press the Fork button, clone your fork instead of the main repository with `git clone [email protected]:youruserid/surge.git`, and the rest of the steps are unchanged.
What the readme does not carry is any user documentation. Musicians are sent to the website for binaries, and the readme notes the team makes regular releases for all supported platforms. The only GitHub release in the repository's history is a single tag named Nightly from 7 August 2024, so the releases musicians install are the ones the website distributes.
CMake generates the IDE files, and macOS needs a flag to get Xcode
Running the configure step is enough to produce IDE project files, which is the mechanism behind the claim that CLion, Visual Studio, vim, emacs and VS Code all work. On Windows CMake generates Visual Studio files. On Mac it generates makefiles by default, and adding `-GXcode` gives you an Xcode project instead.
That is a small flag with a real consequence for anyone who opens the tree in an IDE expecting to build from the GUI. Without it, a Mac developer gets makefiles, and the run configuration in the IDE is not there.
The CI configuration reflects the same split into platforms. Three Azure Pipelines badges sit at the top of the readme, one for CI against main and two for releases against master, labelled Release and Release-XT. Two branch names for the same project in three badges is a small detail that says releases are cut from a different branch than development.
Editorial conclusion
Build Surge XT from source if you are a musician who wants the binaries the team ships, or a developer who needs the Python bindings, and download from the project website otherwise. Check which format your host loads before you start: VST3 and AU are what a normal build produces, while LV2 needs -DSURGE_BUILD_LV2=TRUE and VST2 needs the SDK pointed at by VST2SDK_DIR and may not be redistributed. Keep Release, Debug and RelWithDebInfo consistent between the configure and build commands, since the readme asks you to replace the value in both lines.
Frequently asked questions
how to use surge xt
Musicians should download the appropriate binary from the Surge Synth website rather than building, since the team makes regular releases for all supported platforms. To build from source instead, clone the repository, update the submodules recursively, configure with `cmake -Bbuild -DCMAKE_BUILD_TYPE=Release`, then build the `surge-staged-assets` target.
how do I build the LV2 version of Surge XT
LV2 is not built by default and is not in the CI pipeline. Surge XT 1.3 moved to JUCE 7, which added LV2 support, and you activate the build by adding `-DSURGE_BUILD_LV2=TRUE` on your initial CMake configure.
can Surge XT VST2 plugins be redistributed
No. VST2 builds may not be redistributed because of licensing restrictions, though building one for your own personal use is allowed. You need your own local copy of the VST2 SDK, point `VST2SDK_DIR` at it, then configure a separate build directory and build the `surge-xt_VST` and `surge-fx_VST` targets.
Official sources
Add this badge to your README
If you maintain this project, the badge below links readers to this analysis and shows its maintenance status from the daily GitHub snapshot. Paste the markdown into your README; add ?metric=license or ?metric=stars to the image URL for a different field.
[](https://hysenlabs.com/projects/surge-synthesizer-surge)Star history chart for your README
[](https://hysenlabs.com/projects/surge-synthesizer-surge)Was this useful?