How distrho/cardinal works
Main Components
a) Core Plugin Architecture:
• Host Interface Layer (AU/CLAP/LV2/VST2/VST3 support)
• Cardinal Plugin Core (handling audio, MIDI, and CV processing)
• Remote UI System (for DSP/UI separation in Mini variant)
• Module System (handling the virtual modular environment)
b) Module Categories:
• Cardinal Internal Modules (DAW automation, hosting, etc.)
• Third-party Modules (organized by vendor/category)
• Core Replacement Modules (Cardinal equivalents of Rack Core)
c) Audio Processing:
• Audio I/O Management
• MIDI Processing
• CV Processing
• DSP Engine
Relationships
• Data flow between host DAW and plugin
• Signal routing between modules
• UI interaction with the module system
• Communication between DSP and UI components
• Plugin variant differences (Main/Synth/FX/Mini)
Design Elements
Use the following visual elements:
• Rectangles: Major system components
• Rounded rectangles: Plugin variants
• Diamonds: Decision points for signal routing
• Host integration (blue)
• Audio processing (green)
• UI components (orange)
• Module system (purple)
Specific Implementation Details
a) Plugin Host Integration:
[Host DAW] <-> [Plugin Format Layer (AU/VST/LV2/CLAP)] <-> [Cardinal Core]
b) Core Architecture:
[Cardinal Core]
• [Audio Engine]
• [DSP Processing]
• [Module System]
• [UI System]
• [Module Browser]
• [Patch Management]
• [Parameter Control]
c) Module System:
[Module System]
• [Internal Modules]
• [DAW Automation]
• [Host Integration]
• [Third-party Modules]
• [Categories...]
Additional Details
Annotations for:
• Thread management
• Resource handling
• Platform-specific implementations
• Plugin variant differences
• Module compatibility