How bloodbat/sanguinemutants works
Core Architecture Layer
• Core DSP utilities and algorithms
• Plugin infrastructure (plugin.cpp/hpp)
Module Implementation Layer
• Modules by their primary functions:
a. Oscillators (Funes, Nodi)
b. Modulators (Aestus, Incurvationes)
c. Processors (Nebulae, Anuli)
d. Utilities (Explorator, Velamina)
• Alternative firmware variants as branches from their base modules
Common Resources Layer
• Shared components (sanguinecomponents)
• Helper utilities (sanguinehelpers)
• DSP primitives (sanguinedsp)
[VCV Rack Plugin Interface]
• ↑
[Sanguine Plugin Core]
• ↑
• ______________|______________
[Module [Common [DSP [Resource
• Layer] Utils] Layer] Manager]
[Individual Module Implementations with Variants]
Specific Implementation Details:
Specialized subsystems
• DSP processing chains
• Audio buffer management
• Parameter handling
• Resource management
Cross-cutting concerns
• Polyphony handling
• Sample rate conversion
• Parameter interpolation
Key Relationships to Emphasize:
Module Inheritance
• How alternative firmwares (like Etesia, Fluctus) extend their base modules
• Shared resources between variants
Resource Management
• How modules access shared resources
• Resource initialization and cleanup paths
Signal Flow
• Audio and CV signal paths
• Control parameter routing
Implementation Guidelines:
Use standardized symbols
• Rectangles for modules
• Diamonds for decision points
• Top: User interface level
• Middle: Module implementation
• Bottom: Core infrastructure
Technical details
• Sample rates
• Buffer sizes
• Processing modes
• Polyphony capabilities