Audivane DSP documentation
Install the engine, give it your DAC, and send your apps through it. Audivane DSP0.9.3 is a beta for 64-bit Linux with PipeWire.
Requirements
- 64-bit (x86_64) Linux with PipeWire and WirePlumber, the default on current Arch, Ubuntu, Debian and Fedora desktops.
- Arch Linux, Ubuntu 24.04 or newer, Debian 13 or newer, or Fedora 40 or newer.
- A USB or PCI DAC that the engine can open directly. While the engine runs it uses the DAC exclusively.
- Optional:
rtkit, for real-time scheduling of the audio thread.
1. Install
Pick your distribution. Each command downloads the package from GitHub Releases, where you can also check it against the SHA-256 checksums.
curl -fLO https://github.com/audivane/dsp/releases/download/0.9.3/audivane-dsp-0.9.3-1-x86_64.pkg.tar.zst && sudo pacman -U ./audivane-dsp-0.9.3-1-x86_64.pkg.tar.zstcurl -fLO https://github.com/audivane/dsp/releases/download/0.9.3/audivane-dsp_0.9.3-1_amd64.deb && sudo apt install ./audivane-dsp_0.9.3-1_amd64.debsudo dnf install https://github.com/audivane/dsp/releases/download/0.9.3/audivane-dsp-0.9.3-1.x86_64.rpmgit clone https://github.com/audivane/dsp.git && cd dsp2. Start the engine
The package never starts anything by itself. The engine is a per-user service:
systemctl --user daemon-reload
systemctl --user enable --now audivane-dsp
avdsp ctl statusThen open Audivane DSP from your app menu. If the engine is not running, the app offers to start it.
3. Choose your DAC
In the app, open Device and pick your DAC. The engine opens it directly over ALSA and drives PipeWire from the DAC's own clock. Two new outputs appear in your sound settings:
- Audivane DSP: everything sent here goes through the EQ, convolution and upsampler.
- Audivane Direct: bit-perfect, with no processing and no resampling. Point a dedicated music player at it.
4. Route your apps
Routing decides which apps use the DSP. System-wide makes Audivane DSP the default output, so everything goes through it. Selected apps leaves your default alone and lets you send individual apps to it. The Playing now table lists every stream, its format and where it goes.
The engine follows the sample rate of what you play, so a 44.1 kHz album reaches the DAC at 44.1 kHz (times the upsampling ratio). When several apps play at different rates at once, the first one keeps the rate and PipeWire resamples the others. To prefer the highest rate or your default rate instead, change Mixed rates on the Device page.
5. Shape the sound
- Parametric EQ: drag bands on the graph, or import an AutoEQ / Equalizer APO
ParametricEQ.txt. Separate L+R, L and R sections; overlay target curves or a measurement. - Convolution: load impulse responses (WAV), for room correction or crossfeed.
- Upsampling: pick a ratio, filter length and phase. The plots show the measured response of the real filter.
- A/B compare: switch between two settings with matched loudness.
Save your settings as presets from the bar at the top of the window.
Update
avdsp upgrade # check, download, verify, install, restart the engine
avdsp upgrade --check # only say whether an update existsavdsp upgrade asks for your password once, for the package step. Running the install command for a newer version works too: it replaces the old version and restarts the engine. Versions before 0.9.2 do not have avdsp upgrade, so update those with the install command. If the app was open, click Restart in its update banner.
Stop, hand back the DAC, or uninstall
systemctl --user disable --now audivane-dsp # stop and release the DAC
sudo pacman -Rns audivane-dsp # Arch
sudo apt remove audivane-dsp # Ubuntu / Debian
sudo dnf remove audivane-dsp # FedoraYour settings live in ~/.config/audivane-dsp/ and are kept after uninstalling; delete that folder for a clean slate.
Troubleshooting
- No sound, or the DAC is busy: another program may hold the DAC. Close it, then pick the device again in Device.
- Check the engine:
avdsp ctl statusshows its state;journalctl --user -u audivane-dsp -ffollows its log. - Dropouts under load: install
rtkit, or use a shorter upsampling filter.
Still stuck? Open an issue with the output of avdsp ctl status and the log.
Reference
- Architecture: how the engine owns the DAC and drives the graph.
- Control plane: the socket protocol behind the app and
avdsp ctl. - Build from source and the developer notes.
Looking for the listening test? See the ABX documentation.