kocmoc repo has an official v2 branch with some Rack version 2 features already added in:
I finally checked all developers that are currently in the library and reveal their source codes. I discovered a lot of plugins, which also build fine on Linux, just with the change of the version number. Now I have 1193 modules installed. The new additions are: Aaron Static AlliewayAudio_Freebies aridacity Axioma CaptVolt’s VCV Modules Catro/Blanco Catro/Modulo Chord Controller Comfortzone dBiz Dintree Edge Expert Sleepers - Encoders GoodSheperd Hot Bunny huaba Interrobang JLmod Karatesnoopy Kosmodules LabSeven LFSR LOGinstruments Mantra Mental MicMusic Mojo MrLumps NEX NonLinearInstruments noobhour NoraCodes Nozoid OhmerPrems Pfzzz Plurm PS-PurrSoftware QuantalAudio Qwelk RCM ReTunes Free s-ol Sculpt-O-Sound Skylights SLM Stalys stocaudio StochKit Strong Kar SunsetSignals TercerBrazo TriggerFish-Elements Truly Vitamin WeldSplatter
I have built my unless_modules successfully with the latest Rack source (v2.git.042a9ce), haven’t really tested them yet though, only fixed errors and crashing.
Source is here. Soon I’ll implement port labels, test functionality further and update my automated builds to provide v2 versions as well.
The only change so far is that drawing sliders on Towers now works with Ctrl+Alt instead of just Alt (since Rack took over Alt).
I can confirm building on Linux.
ML_Modules (free) and Quantum Multiverse compiled successfully for v2, and should be available when v2 launches. The sequencers still require some work…
Vult free is at V2 too
The Modular Bus Mixers by Glue the Giant were tweaked so they compile for v2 and have some fixes from the migration document, but they haven’t yet been tested. The code can be found here: GitHub - gluethegiant/gtg-rack: Glue the Giant Rack Modules for VCV Rack
BaconPlugs build and run with v2 if you check them out on the v2 branch.
Sorry for a bit of an obvious question but there’s a lot of activity here. What’s the next step? I don’t want to push that branch to main or do I? And when and how do I update the community library? I’m happy to read the ‘steps once you are ported’ doc but i couldn’t find it here.
Just reading between the lines of the dev blog here but I would say recompile your plugins against new Rack v2 betas as they are released (seems to be happening weekly on Saturday’s so far) to check if any new issues arise.
Andrew said the v2 API and ABI will be declared stable on Oct 23 at the earliest. Once it is declared stable then recompile against that (and perhaps then make v2 your default branch if you don’t want to do it before). I know for MindMeld and Impromptu Marc has made v2 the default branch already.
I guess once the v2 API and ABI is declared stable Andrew will give further instructions as to when to submit your plugins compiled against that to the Library.
OK cool so basically “hang out and wait for the community instructions” and “if i want to set up auto builds against v2 do that”. Got it! Appreciated.
I’ve reached out to Jake who did the excellent 21kHz modules to ask permission to have them added to the v2 VCV library when that goes live. I’ve nearly finished them for v2 and there, hopefully, will also be a “Southpole” version which again I’ve nearly finished doing. This will be added to the main Southpole repo for v2. You’ll be able to have both the originals and Southpole versions in your Rack should you wish.
wip/v2 branch currently builds and runs on my Macs (macOS Big Sur) with VCV Rack 2.git.042a9ce0. It also builds and passes tests on Windows and on the wrong version of Linux.
As usual, I’m experimenting with various unwarranted and unwise coding shenanigans, so you never know if any branch will continue to compile. But if you need a commit that builds, you can likely find a “green” one in my repo’s Actions tab.
No word on the Stellare Modular plugin suite & Stellare Link ?
Ahornberg 2.0.0 alpha Windows build compiled and tested against Rack 2.git.042a9ce0
Although Lomas only has 2 modules, I use both of them in pretty much every patch. I messaged the developer a week ago regarding plans for a v2 port but have not heard anything back (and he has no activity on GitHub since Feb 2020) so figured I would have a go at porting them myself, and with some help from Marc when I got stuck, (I got stuck quite a lot…) I have a fork of Lomas that compiles and works in v2. Hopefully we’ll hear from the developer before Rack 2 launches officially (I’ve sent him a pull request) but if not at least they should remain available.
@Ahornberg I uploaded a Mac build to your GitHub issues.
I had to comment out - include “window.hpp” to get PdArray to compile too
try #include window/Window.hpp. I believe that works if it should prove necessary. You can see on gh where Andrew has made this change when the v1 version had include window.hpp.
Including any Rack header file other than
rack.hpp is unsupported/unstable.
rack.hpp includes all of Rack’s plugin API.
was this true in v1 or is this new in v2?