IN DEVELOPMENT — REAL SCREENSHOTS, LIVE BUILD

The DAW that remembers everything.

Waveqi is a DAW and DJ engine on a real-time Rust core, where every session is a journal of commands — edit, mix, perform, then replay the whole thing exactly, forever.

waveqi — session: demo_live — 48 commands

Waveqi arrangement view: playheads with waveforms, markers, chord lane, and journal feed over a live session

ARRANGEMENT — LIVE SESSION, SCREENSHOT OF THE ACTUAL BUILD

{"op":"media.register","args":{"id":"m0","path":"media/kick_124.wav"}}{"op":"tempo.set","args":{"beat":0.0,"bpm":124.0}}{"op":"playhead.create","target":"ph_kick","args":{"media":"m0","gain":0.9,"start_beat":0.0}}{"op":"playhead.create","target":"ph_vox","args":{"media":"m5","gain":0.75,"start_beat":24.0}}{"op":"bus.set_gain","args":{"id":"b_drums","gain":0.9}}{"op":"note.add","target":"ph_bass","args":{"pitch":36,"start_beat":16.0,"length_beats":2.0}}{"op":"chord.set","args":{"beat":16,"root":2,"quality":"maj"}}{"op":"marker.add","args":{"id":"mk_drop","beat":16.0}}{"op":"scene.create","args":{"name":"drop","playheads":[...]}}{"op":"playhead.fade","target":"ph_pad","args":{"fade_in_beats":2.0,"fade_out_beats":2.0}}{"op":"playhead.set_pan","target":"ph_hats","args":{"pan":-0.25}}{"op":"playhead.route","target":"ph_vox","args":{"bus":"b_vox"}}{"op":"media.register","args":{"id":"m0","path":"media/kick_124.wav"}}{"op":"tempo.set","args":{"beat":0.0,"bpm":124.0}}{"op":"playhead.create","target":"ph_kick","args":{"media":"m0","gain":0.9,"start_beat":0.0}}{"op":"playhead.create","target":"ph_vox","args":{"media":"m5","gain":0.75,"start_beat":24.0}}{"op":"bus.set_gain","args":{"id":"b_drums","gain":0.9}}{"op":"note.add","target":"ph_bass","args":{"pitch":36,"start_beat":16.0,"length_beats":2.0}}{"op":"chord.set","args":{"beat":16,"root":2,"quality":"maj"}}{"op":"marker.add","args":{"id":"mk_drop","beat":16.0}}{"op":"scene.create","args":{"name":"drop","playheads":[...]}}{"op":"playhead.fade","target":"ph_pad","args":{"fade_in_beats":2.0,"fade_out_beats":2.0}}{"op":"playhead.set_pan","target":"ph_hats","args":{"pan":-0.25}}{"op":"playhead.route","target":"ph_vox","args":{"bus":"b_vox"}}

THE PRODUCT IS THE JOURNAL

Every session is a recording of commands.

Append-only. Human-readable. Machine-drivable. Load a session and the engine rebuilds it exactly — the same way, every time.

THE COMMAND SURFACE

Everything speaks JSON-RPC.

The interface emits journal commands. So does anything else you point at the engine — scripts, controllers, agents. What you see here is a real excerpt from the session in the screenshot.

journal.jsonl — demo session

{"op":"media.register","args":{"id":"m0","path":"media/kick_124.wav"}}
{"op":"playhead.create","target":"ph_kick","args":{"media":"m0","gain":0.9,"start_beat":0.0}}
{"op":"tempo.set","args":{"beat":0.0,"bpm":124.0}}
{"op":"chord.set","args":{"beat":16,"root":2,"quality":"maj"}}
{"op":"scene.create","args":{"name":"drop","playheads":[...]}}

Every surface, one engine

DECKS · MIXER · PIANO ROLL

DECKS view of the Waveqi interface — DECKS
Rate, gain, keylock, and beatgrid controls over live playheads.

MIXER view of the Waveqi interface — MIXER
Buses, sends, and gain staging driven by the same commands.

PIANO ROLL view of the Waveqi interface — PIANO ROLL
Notes on instrument playheads — journal commands like everything else.

One engine, built differently

WHAT MAKES IT WAVEQI

Journal sessions

Every action is a command in an append-only journal. Sessions are text: diff them, branch them, replay them.

Deterministic replay

The same journal always renders the same audio. Enforced by a measurement harness, not promised by a spec sheet.

One command surface

The interface, the CLI, and scripts drive identical commands. Automate anything — the engine can't tell the difference.

Rust RT core

A real-time audio path with a proven zero-allocation callback, and offline rendering that matches it bit for bit.

Plugin hosting

CLAP in-process. VST3 and AUv2 out-of-process with latency reporting. Your plugin library works here.

Performance deck

Beatgrids, keylock, stems, and quantized scene launch. Production and performance share one engine, not two products.

Under the hood

ENGINE FACTS — CURRENT BUILD

Real-time core: Rust engine, zero-allocation callback, offline rendering with bit parity to the live path
Audio path: 48 kHz engine core — any import rate or channel count converts on the way in
Plugin hosting: CLAP in-process; VST3 and AUv2 out-of-process with latency reporting
Sync: MIDI clock in and out, MTC generation, Ableton Link (optional)
Deck: Beatgrids, keylock, stems, quantized scene launch
Metering: BS.1770-4 loudness, true peak, SHA-256 render hashes
Automation: JSON-RPC and MCP over the one command surface the UI uses
Verification: 510 engine tests, 277 UI tests, soak and loopback rigs

510

engine tests

277

UI tests

allocations in the RT callback

command surface for UI, CLI, and scripts

Not yet available.

Waveqi is pre-release. The engine, interface, and agent surface are under daily construction — no downloads, no pricing, no waitlist. This page is the honest status.

IN DEVELOPMENT