How mrjoy/sparkle_motion works
Main System Components
a) Input Layer
• Novation Launchpad (Control Surface)
• Numark Orbit (Secondary Control)
• Audio Input Systems (experimental)
• Configuration Files
b) Core Processing Layer
• Simulation Engine
• Node Graph System
• Launch Pad Widget System
• Task Management System
c) Output Layer
• Philips Hue Bridge Interface
• Light Management System
Key Architectural Patterns to Highlight
• Blue Rectangles: Core Components
• Green Rectangles: Input Devices
• Yellow Diamonds: Processing Nodes
• Red Rectangles: Output Devices
• Purple Rectangles: Configuration Systems
Component Relationships
Input Devices → Launch Pad Widget System → Node Graph System → Light Management → Hue Bridges → Physical Lights
Detailed Component Breakdown
a) Node Graph System (Central Component):
• Generators (Perlin, Wave, Const)
• Transforms (Contrast, Range, Spotlight)
• As a hierarchical tree
b) Task Management Layer:
• ManagedTask
• UnmanagedTask
• Simulation Tasks (RenderTask, SweepTask, etc.)
• As parallel processing units
Data Flow Indicators
• Control signals (from input devices)
• Processing flow (through node graph)
• Output commands (to bridges)
• Configuration loading
Technical Details
Annotations for:
• Ruby-based implementation
• MIDI interface requirements
• Network protocols (SSDP, HTTP)
• Real-time processing requirements
Subsystem Details
Create insets for:
• Launch Pad Widget System
• Audio Processing Pipeline
• Bridge Communication Protocol
The separation between input processing, simulation, and output handling
Use a hierarchical layout with:
• Top: Input devices and configuration
• Middle: Core processing and node system
• Bottom: Output handling and physical devices
• Node types and their purposes
• Communication protocols
• Control flow patterns
• Task management system
This will create a comprehensive visualization that captures both the high-level architecture and the important implementation details of this real-time lighting control system.