Skip to content

Build with us

Mixar is a Rust audio engine with a Flutter front end. Clone the repo, run it on Linux, and change what gets in your way.

01 / Stack

Stack

Engine-first boundaries between audio, library, and UI.

Rust engine

Real-time audio and mixing in Rust. The audio callback allocates nothing, so timing stays predictable under load.

Flutter UI

Decks, waveforms, and mixer chrome in one UI codebase for desktop today and mobile targets next.

Async buses

The UI talks to the engine, library, and controllers over async message buses, so engine code never runs on the UI thread.

Stem separation

HTDemucs splits a track into drums, bass, other, and vocals offline. GPU (WebGPU) when available, CPU otherwise, with no cloud round-trip.

Offline analysis

BPM, key, loudness, artwork, and waveforms are computed locally and cached in a SQLite library.

Pluggable backends

CPAL/PipeWire on Linux, or a null backend for tests, chosen at runtime behind one trait.

02 / Architecture

Architecture

UI, controllers, and engine stay in sync over cmd/evt buses. One typed event enum moves both ways, with a focused Rust crate per domain.

Mixar architectureFlutter opens one event stream from BusTransport and sends commands over three FRB transports; every engine, library and controller event is one typed enum on a single bus, and MIDI hardware drives the controller crate.HOST-FLUTTER1 STREAMCMDMIDIALL EVENTSCMD/EVTCMD/EVTCMD/EVTCMD/EVTAPPFlutter UIgui-flutterEXTMIDI Hardwareexternal deviceBRGBusTransportone stream · fan-outBRGDomain transportsengine · library · controllerBUSEvent busevent-bus · bus-apiCOREEngineengine-core · engine-dspLIBLibrarylibrary-core · analyzerCTLControllercontroller · midirLEGENDFocal hubTransportRust domainApp / UIExternalcmd/evt

Get involved

Setup lives in the README. Contribution guidelines live on GitHub. Pick a bug or a rough edge you care about and start there.