ENGINE01
Real-time audio engine
DSP and routing form a native foundation rather than depending on a separate host as the real product.
Dyne
A completely independent Rust-based audio production environment and instrument.
active development Rust · independent audio environment · instrument-first architecture
PB-08 active development
SYS/WAVE 04 CHANNELS PALOMA BB
- Foundation
- Rust
- Product model
- Instrument-first
- Environment
- Independent
- Domain
- Recording + DSP
01
02
03
04
What is real today
The workstation is treated as an instrument in its own right.
Dyne is an independent Rust-based audio production environment and instrument. Recording, processing, sequencing and performance are being designed as one coherent system rather than a conventional desktop shell built around a pile of unrelated plugin windows.
The project starts from musical interaction: what should remain immediate, what deserves a physical-feeling control surface and how the engine can expose depth without making every action feel like software administration.
Dyne is in architectural development. Its public description therefore separates the instrument-first direction from features that are not yet ready to claim as finished.
System shape
One engine, multiple musical timescales.
Immediate performance, detailed editing and signal processing are designed to feel like views of one instrument.
TIME02
Recording + sequence
Linear capture and authored musical structure share a common temporal model.
PATCH03
Signal architecture
Processing is connected as understandable musical structure instead of scattered configuration.
PLAY04
Instrument surface
Performance interaction remains a first-class design problem alongside editing and production.
Current evidence
The current proof is architectural coherence.
Dyne is not presented as a finished DAW. The work is in defining a native system that can grow without reproducing the same fragmented interaction model.
01
Implementation
Rust-native
The environment is designed as its own audio system rather than a themed wrapper.
02
Scope
Full environment
Recording, DSP, sequencing and playing are considered together.
03
Interaction
Instrument-first
Musical immediacy is a governing constraint, not a late usability pass.
04
Status
Active architecture
Direction is public; unfinished features are not represented as complete.
Operating principles
Constraints that keep the work honest.
Musical time first
The system should respond like an instrument, not office software.
One coherent environment
Recording, processing and performance share a foundation.
Depth without fragmentation
Advanced control should not require window-management choreography.
Claims follow implementation
The page distinguishes active architecture from completed capability.
Connected work