rusty_esp_audio-core

The pure half of the audio package: WAV, FLAC and ADPCM framing, a linear resampler, voice activity detection, and the fixed-block pipeline they feed — with no drivers, no allocator and no product types in it. no_std + alloc, forbid(unsafe).

Every codec path here is gated byte-identical against FFmpeg in both directions: our decode of their blocks equals their decode, and their decode of our file equals ours.

Where the evidence is

This crate is part of rusty_esp_audio. The hardware results, the method lines and the open defects live in that package's README and in docs/LEDGER.md, where no number appears without the run that produced it.

On an ESP32-S3

Turn on pie-s3 and the elements run the chip's 128-bit vector twins instead of their scalar arms — same bytes out, gated byte-identical, and on any other target the scalar IS what runs, so the feature is safe to leave on.

rusty_esp_audio-core = { version = "0.1", features = ["pie-s3"] }

Measured through the element, on a Seeed XIAO ESP32-S3 Sense:

call site	scalar	vector
`peak_abs_i16`	78,259	10,272	−86.9%
`mix_i16`	108,364	16,783	−84.5%
`Convert` integer pairs	193,418	29,240	−84.9%
`rms_dbfs_i16`	215,142	38,312	−82.2%
`Gain::process`	134,920	27,896	−79.3%
`StereoToMono::process`	96,008	42,897	−55.3%
`MonoToStereo::process`	55,259	27,165	−50.8%

(picoseconds per sample; lower is better)

rms_dbfs_i16 is the one that pays for itself: a capture loop calls it once per block, right after Pipeline::process.

Two arms are deliberately NOT accelerated, and the source says why rather than leaving it to inference. Biquad, DcBlock and the AGC filter are sequential — y[n] depends on y[n-1] — and LinearResampler gathers at fractional positions, which this unit has no instruction for.

Part of Janus

Janus rebuilds the Espressif ESP32 and Arduino application portfolio as independent, memory-safe Rust packages — so a hardware maker can ship a device that the MATA home computer discovers, catalogs honestly, adopts under its own identity, and pays for. Ten packages, three layers, and the dependency direction never reverses.

layer	packages
0 — the vocabulary	`rusty_esp_core` · `rusty_esp_dsp`
1 — the functions	`rusty_esp_image` · `rusty_esp_video` · `rusty_esp_audio` · `rusty_esp_signal` · `rusty_esp_mid` · `rusty_esp_iroh`
2 — the surfaces	`rusty_esp_arduino` — the sketch facade · `espino` — the maker's CLI (not published)

Every package is host-verified against an external oracle and keeps a ledger in which no number appears without the run that produced it. Five of seven device profiles have now run their kill tests on real silicon, three of them over a Wi-Fi network the board hosts itself.

Also check out the rest of Remade With Rust — including rusty_alloc, the pure-Rust rebuild of mimalloc that these firmwares run on, and rusty_jpeg, the JPEG engine behind the camera path — and our sister project remade_ffmpeg_rs, a ground-up Rust rebuild of FFmpeg.

About Mata Network

Mata Network builds sovereign, self-hostable infrastructure. Remade With Rust is our open-source home for the permissively-licensed building blocks that work depends on.

License