How polymeilex/neothesia works
Main System Components
a. Core Application Layer:
• neothesia (main application)
• neothesia-core (core rendering and functionality)
• neothesia-cli (command-line interface)
• neothesia-ai (AI-related functionality)
b. Input/Output Layer:
• midi-file (MIDI file parsing and playback)
• midi-io (MIDI I/O operations)
• mpeg_encoder (video encoding capabilities)
c. UI/Rendering Layer:
• neothesia-iced-widgets (custom UI widgets)
• wgpu-jumpstart (GPU rendering utilities)
• nuon (UI widget system)
• piano-layout (piano visualization)
Component Relationships
a. Data Flow:
• MIDI File → midi-file → neothesia-core → Rendering Pipeline
• User Input → neothesia → neothesia-core → Output Manager
• Video Export → neothesia-cli → mpeg_encoder
b. Dependencies:
• How neothesia-core is the central component that other modules depend on
• Relationship between UI components and the core rendering system
Architectural Patterns
a. Scene Management:
• Menu Scene
• Playing Scene
• Settings Management
b. Rendering Pipeline:
• Background Animation
• Waterfall Effect
• Keyboard Visualization
• Glow Effects
Technical Implementation
• Blue rectangles: Core components
• Green rectangles: I/O handling
• Purple rectangles: UI components
• Orange rectangles: Rendering components
┌─────────────────────────────────────────────┐
• User Interface │
• (neothesia-iced-widgets, nuon) │
• ┤
• Core Application │
• (neothesia-core, scene management) │
• ┤
• Rendering Engine │
• (wgpu-jumpstart, waterfall, keyboard) │
• ┤
• I/O Handling │
• (midi-file, midi-io, mpeg_encoder) │
• ┘
Important Details
• Configuration management (settings.ron)
• Platform-specific implementations (Flatpak, Windows, macOS)
• Audio output options (MIDI backend, synth backend)
• Resource management (SF2 files, assets)