[08]Blog

One engine, compiled twice

Why Audya's audio engine is written once in Rust and built for both WebAssembly and native code, and what that buys a DJ moving between a tab and a stage.

6 min readBy the Audya team

Most DJ software picks a side. Desktop apps are fast and talk to every controller; web apps are easy to open and easy to share. Audya wants both, without two codebases that sound slightly different.

Write the DSP once

The engine (decks, mixer, EQ, filters, time-stretch, analysis) is one Rust crate. We compile it to WebAssembly for the browser and to native code for the desktop app. The UI talks to both through the same set of commands, so a button does the same thing wherever you press it.

  • Same EQ curves and filter shapes in both apps
  • Same beat and key analysis, so a track keeps its grid when you move machines
  • One set of tests for the sound, run against both builds

Where the hosts differ

The engine is shared, but the host around it isn't. On desktop we can open any audio interface, split master and cue, and talk HID to controllers with jog displays. In the browser we get WebAudio, WebMIDI and a sandbox. The plan is to keep those differences at the edges and keep everything you hear in the middle.

Same sound, same library, same cues, wherever you play.

We'll know this works when one track plays from the same Rust code in both apps. That's the bar for Phase 0, and the next engineering post will be about clearing it.