How hemmer/audibleinstruments works
Project Type and Purpose
• This is a VCV Rack “Audible Instruments” plugin, re-implementing Mutable Instruments Eurorack modules in C++ as a dynamic library loaded by the VCV Rack host.
• README confirms it provides digital versions of modules like Braids, Clouds, Tides, etc., each implemented in its own .cpp file, plus shared DSP libraries and UI assets.
File Structure
Top-level:
• plugin.json – VCV Rack metadata/manifest
• Makefile – build rules (compiles C++ to a plugin .dll/.so)
• src/ – C++ source code
– plugin.cpp / plugin.hpp – plugin initialization & module registration
– XX.cpp (Blinds, Braids, …) – one source file per module
– subdirectories (Ripples, Shelves, Streams) – reusable DSP/filter algorithm headers and sources
• design/ – Adobe Illustrator files (.ai) for panel artwork templates
• res/ – runtime assets (fonts)
• .gitmodules – possibly pulls in external DSP or Rack SDK submodules
README for Insights
• Confirms module list and their origins
• Mentions which modules include “virtual analog models” (alrightdevices DSP code)
Main Components & Their Interactions
a. VCV Rack Host
• Loads plugin.json, locates plugin binary, calls initialization
• Manages audio & CV signal routing between modules
b. Plugin Initialization (plugin.cpp)
• Reads plugin.json metadata
• Registers each Module class (Braids, Clouds, Tides, etc.) with the host
c. Module Factories
• C++ classes derived from rack::Module
• Each owns parameters, inputs, outputs, and DSP processing method
d. DSP Libraries
• Shared code under src/Ripples, Shelves, Streams implements filters, resamplers, engines
• Called by individual modules during process()
e. UI / Panel Artwork
• design/*.ai source templates SVG/PNG assets at build time
• res/ fonts loaded by rack::Widget code in each panel’s .cpp
f. Build & Deployment
• Makefile invokes Rack SDK and compiler to produce plugin library
• plugin.json & res/ packaged alongside binary
Architectural Patterns & Design Principles
• Modular design: one C++ class per synth module
• Shared DSP component libraries for code reuse (Ripples, Shelves, Streams)
• Separation of concerns: plugin init vs. module DSP vs. UI layout
• Declarative registration via plugin.json + plugin.cpp