21–30 of 48 posts
It lacks the VultModulesFree from VCV...
Cardinal is based on open-source modules (compatible with GPL3.0-or-later license) that are all compiled into a single static binary.
This is not possible with proprietary binaries.
Programs like this and VCV Rack are great ways to get started on the road to building your own modular synthesizer [1]. Many of the modules in the program are based on real hardware, and while the hardware versions of these modules can cost hundreds of dollars, the software versions are using the exact same firmware. Whether you stay virtual or go out and build the hardware equivalent of your rack, it's a great way t…
> while the hardware versions of these modules can cost hundreds of dollars, the software versions are using the exact same firmware firmware? so for the modules you are talking about, what you are saying is that they're virtual analog software synths anyway, and the "hardware" aspect simply provides some jacks for patching?
Think the Mutable Instruments modules, many of these are based around STM32 microcontrollers. The firmware is MIT licensed and has simply been ported into Rack modules.
There are a number of Rack modules that started out as pure hardware that now have virtual counter-parts.
It lacks the VultModulesFree from VCV...
These are proprietary so how would you include these? Cardinal is based on open-source modules (compatible with GPL3.0-or-later license) that are all compiled into a single static binary. This is not possible with proprietary binaries.
Also there is now a physical eurorack module where you can load and play VCV modules. https://modulargrid.net/e/4ms-company-metamodule
When can I get this module in VCV? :)
Earlier quoted context omitted.
These are proprietary so how would you include these? Cardinal is based on open-source modules (compatible with GPL3.0-or-later license) that are all compiled into a single static binary. This is not possible with proprietary binaries.
Loading proprietary binaries at runtime is still GPL-compliant.
There is an LV2/VST2/3/CLAP/JSFX plugin loader (Carla or Ildaeil) that can load audio plugins, but these don't sit directly in the Rack DSP graph and do not modify the Rack runtime like its modules do. You could load the VCV-Pro plugin and run it inside one of these if needed ;)
Does this offer anything besides circumventing the little set of features that VCV Rack charges money for? Am I subsidizing the development of this tool with my paid VCV Rack version?
One could argue that a plugin version is more than a minor feature.
Cardinal is not affiliated with VCV in any way. We use the upstream Rack source-code as a base so any support towards VCV will ultimately "trickle down" (in the form of code) back to Cardinal as well.
This only includes a small subset of the VCV Library, some of the best modules aren't included in this and pretty cool. There's also some incredible paid modules in the library worth checking out.
You think over 1200 modules is small? Definitely enough for endless hours of modular patching.
Programs like this and VCV Rack are great ways to get started on the road to building your own modular synthesizer [1]. Many of the modules in the program are based on real hardware, and while the hardware versions of these modules can cost hundreds of dollars, the software versions are using the exact same firmware. Whether you stay virtual or go out and build the hardware equivalent of your rack, it's a great way t…
> while the hardware versions of these modules can cost hundreds of dollars, the software versions are using the exact same firmware firmware? so for the modules you are talking about, what you are saying is that they're virtual analog software synths anyway, and the "hardware" aspect simply provides some jacks for patching?
Does this offer anything besides circumventing the little set of features that VCV Rack charges money for? Am I subsidizing the development of this tool with my paid VCV Rack version?
You can read about all the main differences in this document: https://github.com/DISTRHO/Cardinal/blob/main/docs/DIFFERENC... One could argue that a plugin version is more than a minor feature. Cardinal is not affiliated with VCV in any way. We use the upstream Rack source-code as a base so any support towards VCV will ultimately "trickle down" (in the form of code) back to Cardinal as well.