How ahornberg/ahornberg-vcv-modules works
Main Components
a. Module Layer
• Modules into functional categories:
• Audio Processing (TapeRecorder, CVFreqShift)
• MIDI Modules (MIDIController, MIDIOverAudio, MIDIPolyExpression)
• Utility Modules (Metronome, CopyPastePreset)
• Musical Tools (EqualDivision, Harmonizer)
• UI/Control Modules (FlyingFader, Tracker)
b. Core Infrastructure Layer
• Base plugin infrastructure (Ahornberg.cpp/hpp)
• Utility services (src/util directory)
• External window management system
c. Resource Layer
• Assets management (res directory)
• Presets system
• Font management
Component Relationships
[VCV Rack Host Application]
• ↑
• [Plugin Interface]
• ↑
┌─────────┴─────────┐
• Module Layer │
• ┤
• Infrastructure │
• ┤
• Resources │
• ┘
Specific Implementation Details
• Rectangles: Individual modules
• Hexagons: Core services
Module Architecture Pattern
For each module, show the consistent pattern:
[ModuleWidget (UI)] ←→ [Module Logic]
• ↓
[Port Connections]
Key Technical Elements to Highlight
• The separation between UI (.hpp) and logic (.cpp) files
• Resource management system
• Test infrastructure
Implementation Notes
• Each module follows a consistent pattern with separate Widget and Logic classes
• Common utilities are shared across modules
• Resource management is centralized
• External window support is available for certain modules
This architecture reflects a plugin-based system with multiple independent modules sharing common infrastructure, which is typical for audio processing applications.