Signed-off-by: falkTX <firstname.lastname@example.org>
|2 months ago|
|.github/workflows||2 months ago|
|.kdev4||7 months ago|
|carla @ 93d3fff123||2 months ago|
|deps||2 months ago|
|docs||3 months ago|
|dpf @ ee94ba0cae||2 months ago|
|include||2 months ago|
|jucewrapper||2 months ago|
|lv2export||2 months ago|
|patches||3 months ago|
|plugins||2 months ago|
|src||2 months ago|
|utils||3 months ago|
|.gitignore||6 months ago|
|.gitmodules||3 months ago|
|LICENSE||11 months ago|
|Makefile||2 months ago|
|README.md||3 months ago|
Cardinal, the Rack!
Cardinal is a free and open-source virtual modular synthesizer plugin,
available as JACK standalone and AU, LV2, VST2 and VST3 audio plugin for FreeBSD, Linux, macOS and Windows.
It is based on the popular VCV Rack but with a focus on being a fully self-contained plugin version.
More specifically, this is a DPF-based
plugin wrapper around VCV Rack,
using its code directly instead of forking the project,
with the target of having a proper, self-contained, fully free and open-source plugin version of Rack.
See the why section below for the reasons Cardinal exists, also for frequently asked questions check this FAQ document.
Cardinal contains Rack, some 3rd-party modules and a few internal utilities all in a single binary.
All “Core” modules from Rack have been replaced by Cardinal equivalents, simplified to better work for an audio plugin.
Cardinal does not load external modules and does not connect to the official Rack library/store.
All VCV branding has been removed (to the best of our knowledge) in order to avoid any trademark issues.
The VST3 version is in progress, already part of the build but still experimental.
Prefer to use other formats if you can.
Cardinal should be considered stable, if you spot any bugs please report them.
Currently the following should be noted:
Cardinal releases have official builds for Linux, macOS and Windows.
You can find these under https://github.com/DISTRHO/Cardinal/releases.
There are Linux builds for various architectures (armhf, arm64, i686 and x86_64), macOS “universal” (arm64 + intel) and Windows 32 and 64bit builds.
Both macOS and Windows builds have an installer.
Install instructions are available here.
Note: Neither the macOS or Windows builds are signed, so expect warnings saying they are from an “untrusted developer”.
You can find builds for pretty much any recent Cardinal commit here.
Just click on any successful build, and scroll to the bottom to find the builds.
(note the canvas-like area in the middle prevents mouse wheel scrolling)
A GitHub account is required in order to download these builds.
Basic building instructions are available in BUILDING.md.
Cardinal provides 3 plugin variants - “main”, Synth and FX.
They are all equivalent in performance and behaviour, with only the IO and metadata that changes.
This is because some hosts are very strict on which plugins are allowed as instruments vs FX, so separate variants of the same plugin are needed.
FX and Synth variants both have 2 audio outputs, while “main” has 8.
All variants have MIDI input and output support.
This variant provides 8 audio inputs and outputs and 10 CV inputs and outputs.
NOTE: Due to AU and VST2 formats not supporting CV ports, this variant is not available for those formats.
This variant provides 2 audio outputs but no audio inputs or CV ports.
Plugin type is set as “instrument”.
This variant provides 2 audio inputs and outputs, but no CV ports.
Plugin type is set as regular “effect”.
Because people will ask for it. It is, well... Rack.
But a couple of modules background's have their colors flipped, because damn we want proper dark mode!
At the moment the following 3rd-party modules are provided:
Additionally Cardinal provides its own modules for DAW/Host automation, time position, audio to CV pitch conversion and internal plugin hosting.
Install new modules on a Cardinal build is not possible, but we can add new modules to the build.
Details on this are available here.
Also check this wiki page where we discuss possible modules to include.
All included modules are open-source and have a GPLv3+ compatible license. (GPLv3-only modules are not allowed)
It is a requirement that the final Cardinal binary is GPLv3+ licensed.
Module dependencies should be kept at a minimum, as otherwise it quickly grows the complexity of the build.
Online access (such as phone-home) is not allowed.
Worth noting that a few modules have artwork licensed separately from their code.
These licenses range from CC-0 to CC-NC-ND to custom (used with permission).
An overview of the included artwork licenses can be seen here.
Even though CC-NC is problematic for packaging (some linux distributions are commercial in nature),
Cardinal allows their use because of how prevalent they are across many Rack modules.
Even the Rack “Component Library” (which can be considered the base widget elements) is CC-NC licensed.
Any artwork that uses a custom license has had explicit permission to be used in Cardinal.
Cardinal was created first and foremost as a way to have Rack as a proper open-source audio plugin.
A proper audio plugin should be self-contained as much as possible, as to not interfere with the DAW/Host. Loading external modules clearly goes against this idea.
Not to mention being open-source, otherwise we are at the mercy of the wishes of a company for what we can and cannot do, which is not something Cardinal's authors wish to abide by.
A self-contained plugin can't be overstated, as DLL/shared-object symbol conflicts can trigger hard-to-debug crashes.
While Rack tries to mitigate this as much as possible, crashes due to conflicting modules have already been seen in v2 builds.
On the other side, Cardinal redefines class and function names as needed to avoid as many conflicts as possible.
Support for ARM and non-mainstream platforms (for example BSD) has also always been missing from the official Rack since the start.
While we can patch the Rack free version to support these, same can't be done with Rack Pro with it being a closed-source product.
The online library/store only supports a very specific set of platforms too, so non-supported platforms would need any 3rd-party modules to be manually compiled to make them usable.
Unhappiness with the audio threading behaviour of Rack also plays a role.
Both audio and MIDI should be locked to the host audio thread as to minimize (or even altogether remove) latency and jitter.
The use of separate threads for MIDI is bad design, one that has been corrected in DAWs and JACK-MIDI for several years...
But Rack's use of RtMidi requires separate threading, so Cardinal does not use it.
Other relevant reasons include:
It needs to be said that Cardinal project and its author(s) do not wish anything bad to the original/official Rack project.
In fact, Cardinal wouldn't exist if not for Rack v2 release. (which has many needed things to make a plugin version work)
Cardinal and Rack should be able to co-exist friendly and peacefully, as they clearly have different targets.
It is likely most people will prefer to use Rack Pro for its official support and its big module collection (including commercial ones).
A feature comparison between Cardinal and Rack Pro can be seen here.
Currently we are all on #cardinal IRC room in irc.libera.chat server.
Come join us in your favorite IRC client or through a Matrix bridge.