Modules are developed under macOS with the help of Erb Eurorack-Blocks. There is also an available Windows compatible version. Erb Eurorack-Blocks allows to test modules in the VCV Rack environment before going to the next stage of development. From idea to final hardware module, via VCV:
| Idea | VCV | Hardware |
|---|---|---|
| FM synthesizer |  |
 |
Pick up your OS compatible module version and past the module directory into the default VCV Rack 2 plugins location wich is /Documents/Rack2/plugins/ by default under macOS and Windows.
As you maybe know, code has to be signed to be distributed and run on macOS and every Apple products. Unfortunately, I'm not part of the Apple developer program, hence I can't sign my code. But, thanks to Raphaël Dingé from Erb who pointed me to the solution, you can run VCV Rack 2 modules if you re-sign them with your OS device certificate and "allow downloaded apps" to run on your device.
Once the module is copied to the default VCV Rack2 plugins location, this alert pops up the first time you launch VCV :
As mentionned earlier, this is a normal behavior, the code is not signed. Follow this procedure:
- Re-sign the code:
For instance, with the FMEinheit module, type those lines in your favorite terminal :
cd ~/Documents/Rack2/plugins/FMEinheit
codesign --force -s - plugin.dylib
- Add a security exception for plugin.dylib :
Go to System preferences > Security & Privacy. You'll notice this message : “plugin.dylib can’t be opened because Apple cannot check it for malicious software.” You just have to "Allow it anyway".
Launch VCV Rack 2 and you now have another security alert in wich you can "Open" the "plugin.dylib".
That's all! 👍
All details about modules are available here: https://omsinserial.com