How cosinekitty/sapphire works
Main Components
a) Core Plugin Infrastructure
• Plugin Registration System (based on plugin.cpp and plugin.hpp)
• Common Utilities (sapphire_globals.cpp, sapphire_vcvrack.hpp)
• Shared Components (sapphire_panel.hpp, sapphire_widget.hpp)
b) Module Categories
Chaos/Vector Modules
• Frolic, Glee, Lark (chaotic oscillators)
• Chaops (expander module)
• Hiss (random vector generator)
• Pivot (vector manipulation)
• Rotini (vector cross product)
Physics Simulation Modules
• Nucleus/Polynucleus (particle physics)
• Elastika (mesh physics simulation)
Audio Processing Modules
• Galaxy (reverb)
• Gravy/Sauce (filters)
• TubeUnit (waveguide synthesis)
Utility Modules
• Moots (connection simulation)
• Pop (trigger generator)
• SplitAddMerge (signal routing)
• Tin/Tout/Tricorder (visualization system)
┌─────────────────────────────────────────────────────┐
• VCV Rack Plugin API │
• ┤
• Sapphire Core Infrastructure │
• (SIMD, Panel System, Widget System, Resampling) │
• ┬──────────────┬────────────┬───────────┤
• Chaos │ Physics │ Audio │ Utility │
• Modules │ Modules │ Modules │ Modules │
• ┴──────────────┴────────────┴───────────┘
Important Elements to Highlight
a) Shared Components:
• SIMD optimization system (sapphire_simd.hpp)
• Panel/widget inheritance hierarchy
b) Module Interactions:
• Expander relationships (Chaops with Frolic/Glee/Lark)
• Signal flow between visualization modules (Tin → Tricorder → Tout)
• Vector data flow between chaos modules
Implementation Details
• Relationship between .cpp and .hpp files
• Test infrastructure (util/unittest)
• Build system integration (.github/workflows)
• Standalone command-line tools (util/cmdline)