alnico 0.0.1

An audio framework for Rust: DSP, device I/O, plugin formats and a GUI toolkit for building and shipping audio plugins. Placeholder — under active development.
Documentation
  • Coverage
  • 100%
    1 out of 1 items documented0 out of 0 items with examples
  • Size
  • Source code size: 17.0 kB This is the summed size of all the files inside the crates.io package for this release.
  • Documentation size: 104.5 kB This is the summed size of all files generated by rustdoc for all configured targets
  • Ø build duration
  • this release: 1s Average build duration of successful builds.
  • all releases: 2s Average build duration of successful builds in releases after 2024-10-23.
  • Links
  • Homepage
  • NotTheDj/alnico-audio
    0 0 0
  • crates.io
  • Dependencies
    • —
  • Versions
  • Owners
  • NotTheDj

Alnico

An audio framework for Rust — the whole path from "I have a filter" to "signed plugin that loads in your DAW", built on what audio development actually looks like in 2026, and permissively licensed.

⚠️ This release reserves the name. Nothing is implemented yet. Development is tracked at https://github.com/NotTheDj/alnico-audio.

Alnico — aluminium-nickel-cobalt, the magnet alloy in speaker drivers and guitar pickups.

What it will be

  • DSP — filters, FFT, convolution, oversampling, dynamics, analysis
  • Device I/O — CoreAudio, WASAPI, ASIO, ALSA, JACK, PipeWire; CoreMIDI, Windows MIDI Services, ALSA seq
  • Plugin export — CLAP-native, with VST3, AU and standalone as adapters
  • GUI — our own retained toolkit on our own GPU and CPU rasterizers
  • The development loop — hot-reloadable DSP, a harness that runs your processor with no DAW anywhere, golden-audio and property testing, and one command to sign, notarize and package

The focus is developer experience. Today, changing one line of DSP typically means recompile, relaunch the DAW, rescan, reload, re-navigate, re-trigger. That is the problem this project exists to delete.

Status

Pre-alpha, solo-developed, no usable code yet. See the development plan for scope, architecture decisions and roadmap.

Licence

Licensed under either of

at your option.

Unless you explicitly state otherwise, any contribution intentionally submitted for inclusion in this work by you, as defined in the Apache-2.0 licence, shall be dual licensed as above, without any additional terms or conditions.