FXRoute is a browser-based control surface for a Linux hi-fi audio box. One small PC or ARM board with a PipeWire user session becomes the source and DSP hub for local music, internet radio, Spotify, Qobuz, and TIDAL — controlled from any phone, tablet, or laptop on the local network.
Radio, the music library, the streaming providers, the native DSP engine, and the room-measurement tools all in one interface. You browse and play from the couch; FXRoute owns the audio session, the DSP chain, the output routing, and the measurement on the audio machine.
Start from FXRoute releases. The release notes list every published artifact and where to fetch it: the Raspberry Pi 4 / Pi 5 SD-card image (GitHub Release) and the x86_64 Ubuntu 26.04 installation ISO (SourceForge). Write the image or ISO to disk, boot it, and finish the web onboarding.
No new hardware? Try the web demo first. Already running Linux on the audio machine? Use the installer instead.
Try the interface without any audio hardware, directly in your browser: https://cobbycode.github.io/fxroute/
The demo is the real FXRoute frontend — same UI — with simulated backend state for playback, DSP, radio, and measurement, so every view is explorable in a normal browser.
Web demo screenshots (simulated playback and measurements). Click an image for full resolution; the manual also illustrates routing, Surround Easy/Expert, PEQ, Convolver, and the room diagram.
Sources (manual §4)
- Local music library with albums, tracks, artists, playlists, favorites, and folders, plus uploads and URL imports; SMB and NFS network shares
- Internet radio with a curated catalog, personal stations, Radio Browser search, and live metadata for Radio Paradise, FIP, SomaFM, and KEXP
- Spotify Connect (desktop client or spotifyd), Qobuz Connect, and TIDAL inside the Library with gapless playback
- Bluetooth, external line, and (on supported boards) USB gadget input, with automatic PCM / Dolby Digital / DTS Core recognition, per-device Custom Mapping, and Auto input switching
- STDIN pipe input for raw PCM from shell pipelines (
decoder | fxroute stdin …), mono to multichannel
DSP and output (manual §5)
- A native DSP engine (
fxroute_dsp_sink) in the same PipeWire session as playback - Stereo, Stereo + Sub, or Surround, with free assignment of speaker roles to hardware outputs
- 2-, 3-, or 4-way crossovers and mono, dual-mono, or stereo subwoofers, derived from the routing
- PEQ and convolver presets per filter bank, A/B compare, preset combining, and REW/IR imports
- Output extras (limiter, headroom, autogain, loudness, bass enhancer, tone effect), a Surround upmixer, and Auto or fixed sample rate up to 384 kHz with selectable SRC quality
Measure and correct (manual §6)
- Room and speaker measurement with a host microphone: single sweeps, L/R Repeat, and a guided multi-position Advanced workflow, also per Surround speaker group
- Electrical-reference timing, Speaker Auto Alignment, and Auto Sub Optimize
- SPL calibration (automatic with UMIK-1, UMIK-2, or Dayton UMM-6), Level Matching, Polarity Check, and AV Sync
- PEQ assistant with automatic filter suggestions, custom house curves, and FIR convolver presets in linear, minimum-phase, and aligned modes
System
- Control from any browser on the LAN, including a TV remote or keyboard (arrows, OK, Back, Home, media keys); optional local HTTPS via Caddy
- A read-only power hint for amplifier smart-plug automation (Home Assistant)
- In-app maintenance updates, plus the downloadable images above
Classic install on a Linux PC or board with PipeWire:
git clone https://github.com/CobbyCode/fxroute.git
cd fxroute
./install.shThe installer prepares the system packages, builds the native DSP engine, creates the Python virtualenv, and enables the fxroute.service user service. Run it as the audio user; from a root shell on a host with several users, pass that user explicitly with ./install.sh --user <name>. Custom install targets must be dedicated directories named fxroute unless --local-project is used (that flag installs in place from the current project directory).
Supported package managers are apt, dnf, zypper, and pacman. Streaming providers are optional and always resolve the current stable upstream release. The provider matrix, first-run authentication, and uninstall behavior are covered in docs/INSTALLER.md.
systemctl --user status fxroute— the service isfxroute.service.- Open the UI from any browser on the network:
http://fxroute.local:8000(mDNS; the name is set in Technical settings → Device Name; the downloadable images install a unique id, e.g.http://fxroute-ab12cd.local:8000)http://<host-ip>:8000http://localhost:8000on the audio PC itselfhttps://<host-ip>orhttps://<device-name>.localwhen the optional HTTPS proxy is enabled (HTTP stays reachable)
- Play something from Radio or Library to confirm audio and DSP routing.
- The music folder is configured in
.env(MUSIC_ROOT); SMB shares and NFS exports are selected or added in Technical settings → Music Library and survive restarts. Details in the manual.
GET /api/power/state is a read-only amplifier power hint: amp_should_be_on is true while FXRoute plays, measures, or has an active input, so an automation can switch a smart plug. POST /api/audio/input-presence is the optional return channel that lets an automation report a source as present. FXRoute does not require MQTT. Payload, rules, and complete configuration examples are in the manual.
- MANUAL.md — the user manual: sources, output modes and routing, crossover, subwoofers, Surround, the measurement assistant, and the settings
- docs/INSTALLER.md — installer, providers, and uninstall details
- docs/INSTALL-ISO.md — the x86_64 Ubuntu 26.04 ISO: install, live session, building it yourself
- docs/INSTALL-ARMBIAN.md — building the ARM64 board images yourself
- docs/usb-audio-gadget.md — USB audio input (UAC2) requirements and setup
- Technical background: Surround path · playback SRC · HDMI profiles · AV Sync accounting · input auto-select
- CHANGELOG.md — release history
- CONTRIBUTING.md — how to contribute
AGPL-3.0 — see LICENSE.


