Development / roadmap

One tested phase
at a time.

The 0.1.0 foundation is implemented. The remaining phases describe future work, not a release schedule or a promise of availability.

ImplementedIn developmentPlannedExperimental

Implemented means documented and tested. In development means work has started. Planned means unavailable. Experimental describes diagnostic functionality with explicit limits.

PHASE 01Implemented

Foundation

CMake project
Qt application
application architecture
audio engine
PipeWire/JACK output
JACK MIDI foundation
settings
logging
error handling

0.1.0 · See test evidence and limitations. The opt-in diagnostic sine remains experimental.

PHASE 02Planned

Rack

Device abstraction
rack UI
processing graph
front/rear views
real cable connections

PHASE 03Planned

Rivet Sub

Subtractive synthesizer
MIDI input to voices
polyphony
real DSP controls

PHASE 04Planned

Effects

Filter
distortion
delay
EQ
compressor
reverb

PHASE 05Planned

Mixer

Mixer channels
master output
actual channel meters

PHASE 06Planned

Sequencer

Transport
timing
tracks
MIDI clips
playback scheduling
loop regions

PHASE 07Planned

Piano Roll

MIDI editing
quantization
note manipulation

PHASE 08Planned

Automation

Automation lanes
parameter playback
interpolation
tempo synchronization

PHASE 09Planned

Drum Machine

Rivet Drum
pattern sequencing

PHASE 10Planned

Sampler

Rivet Sampler
waveform display

PHASE 11Planned

Persistence

.rivet projects
presets
autosave/recovery
missing sample handling

PHASE 12Planned

Export

Offline WAV rendering

PHASE 13Planned

Polish

Undo/redo
shortcuts
browser improvements
performance monitoring
accessibility
UI scaling
crash recovery
documentation
packaging

Next: make routing real.

Phase 2 starts with device contracts and graph validation before rack controls.

Development notes

One tested phaseat a time.