Open-source project
zrythm/zrythm avatar
zrythm/zrythm

Zrythm is still at 2.0.0-alpha, and nineteen v1 features are listed as not yet ported

a highly automated and intuitive digital audio workstation - official mirror

3,206 stars153 forksC++NOASSERTION

At a glance

What is it?
zrythm/zrythm is a C++23 digital audio workstation built on Qt/QML and JUCE, mirrored from GitLab to GitHub. The rewrite is not finished: the README carries a collapsible list of nineteen features from the 1.x line that have not been brought over, and the release tags are still alpha with a missing number in the sequence.
Who is it for?
Zrythm suits someone who wants a workstation with clip looping, adaptive snapping, and a piano roll already built, and the plugin format coverage including VST3, CLAP, LV2, LADSPA, and AudioUnit is broader than most free alternatives. Three things to weigh.
Can I use it commercially?
Check first. The repository uses a licence we do not classify automatically, so read its LICENSE file before any commercial use.
Is it still maintained?
Yes. The repository last received commits 1 day 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.

From daily snapshots

Star history

  • zrythm/zrythm3,206 ★ · +78
Star history
Repository2026-09-242026-11-15
zrythm/zrythm3.1k3.2k

78 Stars in the last 52 days, measured from the daily GitHub snapshot. Compare with other projects

Editorial analysis

The GitHub repository is a mirror and the GitLab directory holds the pipeline

The one-line description for this repository ends with a note: official mirror.

The tree explains what that means in practice. There is a `.gitlab-ci.yml` and a `.gitlab/` directory at the root, and the Conan instructions reference a local package index with `conan remote add conan-local-index ext/conan-center-index`. The primary home of the project is elsewhere and this repository is a copy of it.

A `.github/` directory exists as well, so both forges have configuration, but the continuous integration file is the GitLab one. If you file an issue or want to know whether a pull request was tested, the answer is on the other host.

The build documentation points at a website for downloads rather than to release assets here. Prebuilt installers are available from `zrythm.org/en/download.html`, and the README calls that the recommended way to install. Everything below that line is for people building from source, which is a smaller group than the mirror's traffic suggests.

Nineteen v1 features are listed as not yet ported, including the automation claim

A collapsible section titled Not yet ported from v1 holds nineteen entries. They include clip linking, bouncing anything to audio or MIDI, punch in and out recording, detachable views for multi-monitor setups, searchable preferences, a built-in file browser, optional plugin sandboxing, stem export, automatic project backups, and serializable undo history.

Three of the marketing bullets at the top of the file are contradicted by that list.

One bullet promises limitless automation capabilities. The unported list includes automate anything using automation events or CV signal from modulator plugins and macro knobs. Another promises mixing features; the unported list includes signal manipulation with signal groups, aux sends, and direct anywhere-to-anywhere connections. A third promises undoable user actions with undo history; the unported list includes serializable undo history.

In the undo case both are true at once, because undo works in the current version and cannot be written to a file. In the other two the list is the more specific statement and the bullets are the marketing summary of an intention.

The plugin browser landed and the file browser did not

One pair of entries is worth reading side by side because it shows where the porting effort stopped.

The shipped feature list includes a built-in plugin browser. The unported list includes a built-in file browser. Two adjacent conveniences, one done and one not, which tells you the remaining work was prioritised around audio and MIDI assets rather than around files.

The same asymmetry appears in plugin format support. The current version handles VST3, CLAP, LV2, LADSPA, and AudioUnit, five formats. The unported list names VST2, DSSI, and SFZ and SF2 SoundFont support together with other audio file formats, so the older plugin formats and the sample instruments are all still on the other side.

File handling is narrow in the same way. Import is listed as WAV audio file import, singular, and MIDI file support is listed as Type 0 and 1. Type 2 MIDI, where the tempo map is separate from the note data, is not claimed.

One documented Conan step overwrites three files in your Conan home

The optional Conan path is the most interesting part of the build documentation, because it carries an explicit warning.

The steps begin with a virtual environment and a pinned install:

code
python -m venv venv && source venv/bin/activate
pip install -r requirements.txt

Then comes the step that overwrites things:

code
conan config install conan

The warning attached to it states that this overwrites all files in `~/.conan2/profiles/`, as well as `~/.conan2/settings_user.yml` and `~/.conan2/global.conf`. The suggested remedies are to back up existing configuration or to point `CONAN_HOME` somewhere else.

That is a well-handled hazard, since it is documented rather than discovered. It is still a command in a numbered setup list that silently replaces machine-wide tool configuration, and the backup advice comes after the instruction rather than before it.

The step after it initialises submodules with `git submodule update --init --recursive`, described as including the custom Qt recipe fork, then registers a local index and exports the recipes with `python3 tools/export_conan_recipes.py`.

The macOS profile builds a sanitizer-instrumented Qt by default

The Conan section includes a profile table with five platforms and, unusually, a cross-compile build profile for exactly one of them.

Linux with Clang and Linux with GCC, Windows x64, and Windows ARM64EC all use a host profile and no build profile. macOS is the exception: the host profiles are `appleclang_debug` and `appleclang_release`, and `appleclang_build` is the cross-compile build profile. The note explains why. The macOS host profile builds a sanitizer-instrumented Qt, and building that requires cross-building, because the sanitizer profiles set `cross_build=True` in order to skip running test executables that would otherwise fail under the sanitizer runtime.

So on macOS the default dependency build is instrumented, and the instrumented binary is not the one that ends up in your application. That is a deliberate arrangement to get sanitizer coverage over the whole dependency chain, and it is also the reason macOS is the only platform in the table with a second profile column.

The sanitizer profiles listed for use are `clang_asan_ubsan`, `clang_tsan`, `gcc_asan_ubsan`, `appleclang_asan_ubsan`, and `msvc_asan`.

Windows needs Qt built with the same compiler and the same configuration

The three platform recipes differ in more than generator name, and the differences are the constraints.

Linux installs CMake, Ninja, and Qt, then configures and builds with two commands:

code
cmake -B builddir -G Ninja -DCMAKE_BUILD_TYPE=Release -DCMAKE_PREFIX_PATH=<path to your Qt prefix>
cmake --build builddir --config Release

The result lands at `builddir/src/gui/zrythm`.

macOS swaps the Ninja generator for Xcode, which means the third step is opening the generated project and building it rather than running a command. Windows uses the `Visual Studio 17 2022` generator and has the same open-the-project step, on top of needing the Desktop development with C++ workload installed.

The Windows note is the one to read carefully: Qt must be built with the same compiler and the same Debug or Release configuration used to build Zrythm. A mismatched Qt is the kind of mistake that produces link errors rather than a clear message, which is why the requirement is stated as a note rather than left to the toolchain.

Dependencies are fetched with CMake's FetchContent, so the stated prerequisite is CMake and Qt and nothing else.

The license lives in an HTML comment while the repository records NOASSERTION

The first thing in the README is a comment, and it carries the licensing metadata:

code
SPDX-FileCopyrightText: © 2018-2026 Alexandros Theodotou <[email protected]>
SPDX-License-Identifier: FSFAP

So the copyright holder and license identifier are stated in an HTML comment at the top of the file, and the identifier is FSFAP, an FSF approved license rather than a copyleft source-available one.

The repository itself records no license at all. The tree carries `COPYING`, a `LICENSES/` directory, and a `REUSE.toml`, which is the configuration file for the REUSE licensing specification, so there is a real licensing apparatus in the repository that the license field does not reflect.

Two of the three sources therefore disagree, and picking one would be guessing. What the README does state in prose is that Zrythm is free software, with a link to the GNU page on free software.

Redistribution has its own terms. A callout in the build section says that if you distribute your builds to others you must comply with the license terms of Zrythm and of all the dependencies used, in addition to the project's Trademark Policy, which is a separate file at the root.

The build requirements are 74 pinned Python packages, none of which runs the application

The Conan path installs from `requirements.txt`, and that file is a fully pinned list of 74 Python packages, every one with an exact version.

Read by category, they describe the project's infrastructure rather than its runtime. The build tooling is there: `conan`, `cmake`, and `ninja` as installed Python packages. So is the documentation stack, with Sphinx, the Furo theme, and a set of Sphinx extensions including `sphinx-intl` for translations and `sphinx-copybutton`. The release and inventory side has `PyGithub`, `PyJWT`, and `PyNaCl` for repository automation, `boto3` and `botocore` for uploads, and `cyclonedx-python-lib` with `packageurl-python` for software bill of materials.

Two entries in that list are unusual enough to notice on their own. `license-expression` is a licensing parser, which fits the REUSE and `LICENSES/` arrangement. `gprof2dot` turns profiler output into graphs, which points at the SIMD-optimised DSP work being measured rather than at packaging.

A C++ application with a 74-package Python toolchain is a normal shape for a project that builds, documents, signs, and publishes itself in one place. There is also a `requirements-base.txt` beside it, so the pinning is layered.

Editorial conclusion

Zrythm suits someone who wants a workstation with clip looping, adaptive snapping, and a piano roll already built, and the plugin format coverage including VST3, CLAP, LV2, LADSPA, and AudioUnit is broader than most free alternatives. Three things to weigh. The GitHub repository is a mirror, so continuous integration and issue triage happen on GitLab and a GitHub bug report is not the shortest path to a fix. Nineteen named 1.x features are still missing, including everything the automation bullet advertises. And if you build from source, read the Conan instructions before running them, because one documented step overwrites files in your Conan home.

Frequently asked questions

What is Zrythm and which languages is it written in?

Zrythm is a digital audio workstation written in C++23 using Qt/QML and JUCE, described as free software. It targets both professionals and beginners, with clip looping, adaptive snapping, a piano roll, an audio editor, recording with takes, and a hardware-accelerated interface.

Is Zrythm finished or still in development?

The release tags are still alpha, at v2.0.0-alpha.6 published on 2026-10-04. The README also carries a collapsible list of nineteen features from the 1.x line that have not yet been ported, including clip linking, stem export, automatic project backups, and serializable undo history.

Which plugin formats does Zrythm support?

VST3, CLAP, LV2, LADSPA, and AudioUnit. VST2, DSSI, and SFZ and SF2 SoundFont support appear in the not yet ported list, together with other audio file formats. MIDI file support is listed as Type 0 and 1, and audio import is listed as WAV.

Where should I report a Zrythm bug?

The repository describes itself as an official mirror and carries a .gitlab-ci.yml plus a .gitlab directory, so the primary home is on GitLab. The README asks for bugs through the issue tracker and feedback through a Discussions tab, and points at the website download page for prebuilt installers.

What do I need to build Zrythm from source?

CMake and Qt, with dependencies fetched automatically through CMake FetchContent. Linux uses the Ninja generator, macOS uses Xcode and Windows uses Visual Studio 17 2022. On Windows Qt must be built with the same compiler and the same Debug or Release configuration. Conan is offered as an optional alternative.

Official sources

  1. Issues
  2. Project website
  3. README
  4. Releases
  5. zrythm/zrythm on GitHub
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.

Add this badge to your README

markdown
[![Hysen Labs](https://hysenlabs.com/badge/zrythm-zrythm.svg)](https://hysenlabs.com/projects/zrythm-zrythm)

Star history chart for your README

markdown
[![Star history](https://hysenlabs.com/chart/zrythm-zrythm.svg)](https://hysenlabs.com/projects/zrythm-zrythm)

Was this useful?