SmartEQPresetSwitcher is a cross-platform EQ preset switcher for managing, editing, applying, importing, exporting, and backing up EQ presets. It is built with SvelteKit, TypeScript, Rust and Tauri 2.
On Windows it integrates with Equalizer APO, can install or repair it, and can open the official Device Selector. On Linux it provides GUI, tray, TUI, boot-sync and Linux EQ export workflows for PipeWire-oriented systems.
Current source version: 0.3.0. This source tree is prepared for GitHub push and source packaging. Generated dependency/build folders are intentionally excluded from the archive.
- Organizes presets into groups with drag-and-drop ordering.
- Applies presets from the main window, the system tray or the TUI.
- Edits preset
.txtfiles in-app and exports them back to disk. - Imports Equalizer APO preset files and convolution
.wavfiles. - Keeps convolution file references synced and can reveal linked files with the native file manager.
- Imports and exports full app-data backups as JSON.
- Imports AutoEQ presets.
- Stores readable local-timestamped logs and can open the logs folder directly from the app.
- Supports launch-on-startup on Windows and Linux.
- Supports a Linux headless boot-sync mode.
- Exports active presets to Linux EQ files for PipeWire-oriented workflows.
- Main GUI and tray mode.
- Equalizer APO install/reinstall helper.
- Equalizer APO Device Selector launcher.
- Per-user autorun through the Windows Run registry key.
- NSIS installer build.
- Main GUI and tray mode when a desktop is available.
- TUI mode through
--tui. - Headless boot-sync mode through
--boot-sync. - Desktop autostart through
~/.config/autostart. - User systemd boot-sync service through
~/.config/systemd/user. - Linux EQ export files under
~/.config/SmartEQPresetSwitcher/linux-eq. - Native Arch package, Debian package and optional AppImage build scripts.
Equalizer APO itself is Windows-only. Linux support is implemented as compatibility/export tooling for compatible EQ preset syntax, not as a native Equalizer APO port.
The project was previously named SmartEqualizerAPOPresetsManager. Runtime folders, executable names, package names, desktop files and docs now use SmartEQPresetSwitcher.
On first start, the app migrates the old per-user data folder when possible:
SmartEqualizerAPO -> SmartEQPresetSwitcher
Existing managed config markers from the old app name are still recognized and replaced with the new SmartEQPresetSwitcher markers when the active config is rebuilt.
AutoEQ import now supports target-aware variants instead of assuming GraphicEQ only:
- Auto target: prefers ParametricEQ /
Filter:output for Linux PipeWire/EasyEffects and Windows Equalizer APO/Peace, then falls back to GraphicEQ. - ParametricEQ / Filter: best for PipeWire filter-chain
param_eq, EasyEffects-style PEQ workflows, Equalizer APO and Peace. - GraphicEQ: fallback for simple graphic equalizers and manual editing.
This matters because AutoEq itself produces settings for many equalizer apps and says the user must apply them with the selected equalizer app. The app therefore should not hard-code one AutoEQ format forever.
The GUI now starts with the tray enabled again. On KDE/Wayland/NVIDIA the launcher forces the GTK/WebKit process to X11/XWayland first; if a distro-specific tray problem appears, run:
SMART_EQ_DISABLE_TRAY=1 smart-eq-preset-switcher --guiLinux system EQ setup exports the active preset, generates a PipeWire filter-chain config, reloads the user audio services on Apply, and uses pactl to set/move streams to the generated EQ sink when available. Parametric AutoEQ presets are used directly. GraphicEQ-only presets are converted into a conservative 31-band parametric approximation so PipeWire param_eq can still load them.
The main window now has an EQ backend status button in the header. It tells the user whether the app is only managing presets locally or whether the OS audio backend is ready to consume the active preset.
- Windows: reports Equalizer APO detection and whether APO
ConfigPathpoints at the managed SmartEQPresetSwitcher config folder. - Linux: reports PipeWire / EasyEffects export readiness, the active export path, and the generated PipeWire filter-chain setup file.
- Linux setup exports the active preset to
~/.config/SmartEQPresetSwitcher/linux-eq/active-equalizerapo.txtand writes a PipeWire filter-chain snippet at~/.config/pipewire/pipewire.conf.d/99-smart-eq-preset-switcher-parametric-eq.conf.
On Linux, system-wide EQ is not called "connected" unless the PipeWire setup file exists. The GUI opens a setup gate when the Linux backend is missing, while still allowing an explicit local-only bypass for first-run preset creation or troubleshooting. The Linux setup panel detects common package-manager families and can open a visible terminal with the matching PipeWire/WirePlumber install command. EasyEffects is optional GUI workflow guidance, not a required app-managed backend package. The setup action writes the user PipeWire filter-chain file and, when a valid parametric preset exists, runs systemctl --user try-restart pipewire.service pipewire-pulse.service wireplumber.service.
%APPDATA%\SmartEQPresetSwitcher
%APPDATA%\SmartEQPresetSwitcher\presets
%APPDATA%\SmartEQPresetSwitcher\config
If Equalizer APO is still pointing at a protected config directory, the app prompts to move its ConfigPath to the writable app-managed folder. Changing ConfigPath or updating protected Equalizer APO files can trigger a Windows UAC prompt.
~/.config/SmartEQPresetSwitcher
~/.config/SmartEQPresetSwitcher/presets
~/.config/SmartEQPresetSwitcher/config
~/.config/SmartEQPresetSwitcher/linux-eq
~/.config/pipewire/pipewire.conf.d/99-smart-eq-preset-switcher-parametric-eq.conf
Interactive TUI:
smart_eq_preset_switcher --tuiSingle command mode:
smart_eq_preset_switcher --tui list
smart_eq_preset_switcher --tui apply MyGroup MyPreset
smart_eq_preset_switcher --tui autorun statusBoot sync:
smart_eq_preset_switcher --boot-syncAutorun CLI:
smart_eq_preset_switcher --autorun status
smart_eq_preset_switcher --autorun enable
smart_eq_preset_switcher --autorun disableUse the Troubleshoot button in the main window on Windows to:
- Download and silently install Equalizer APO with the official
/Sinstaller. - Re-run the same install chain if the install needs repair.
- Open the official Device Selector so playback and capture devices receive APO processing.
On Linux these Windows-only actions are hidden from the main UI and return clear unsupported-platform errors if called directly.
Detailed build instructions are in docs/BUILDING.md. Linux runtime diagnostics are in docs/TUI_AND_LINUX.md.
scripts/bootstrap-linux.sh # automatically installs build deps
scripts/bootstrap-linux.sh --cross-windows # also install cross-build deps (NSIS AUR, LLVM, etc.)
scripts/build-linux.sh # auto: Arch -> pacman, Debian -> deb
scripts/build-linux.sh --arch # native Arch package
scripts/build-linux.sh --deb # Debian package (via build-deb.sh)
scripts/build-linux.sh --appimage
scripts/build-linux.sh --windows # cross-build Windows NSIS from Linux, best-effort
scripts/build-linux.sh --all
scripts/build-arch-package.sh # direct Arch pacman builder
scripts/build-deb.sh # direct Debian .deb builder
scripts/build-windows-from-linux.sh # direct Windows cross-build scriptOn Arch, use the default scripts/build-linux.sh or force --arch. The output
is a native pacman package and can be installed with:
sudo pacman -U dist/arch/smart-eq-preset-switcher-*.pkg.tar.zst.deb is for Debian/Ubuntu users, not for installing on Arch. The Arch package is generated through tauri build --no-bundle plus makepkg, not by manually tarring a package root, so the binary embeds production assets and pacman -U can validate the metadata.
AppImage remains optional, but it uses Tauri/linuxdeploy and can fail on some distro/runtime
combinations. On Arch the native .pkg.tar.zst path is preferred.
On Arch, rust and rustup conflict. The bootstrap script keeps an existing
Rust toolchain by default. Use scripts/bootstrap-linux.sh --rust if you use
the repository rust package, or scripts/bootstrap-linux.sh --rustup if you
want rustup.
On KDE/Wayland, the installed Arch launcher forces conservative XWayland/WebKitGTK environment variables by default. Native Wayland can be tested with:
SMART_EQ_USE_WAYLAND=1 smart-eq-preset-switcher --guiExpected Linux outputs:
dist/arch/*.pkg.tar.zst # Arch pacman package
dist/deb/*.deb # Debian/Ubuntu package
src-tauri/target/release/bundle/appimage/*.AppImage # optional
src-tauri/target/x86_64-pc-windows-msvc/release/bundle/nsis/*.exe # optional Linux -> Windows NSIS
The app writes its own log file here:
cat ~/.config/SmartEQPresetSwitcher/logs/application.logFor desktop-launch or crash diagnostics on systemd desktops:
journalctl --user -b --grep='SmartEQPresetSwitcher|smart-eq-preset-switcher|smart_eq_preset_switcher' --no-pager
journalctl -b _COMM=smart-eq-preset-switcher --no-pager
coredumpctl list smart-eq-preset-switcher smart_eq_preset_switcher
coredumpctl info smart-eq-preset-switcherTo run it in foreground and capture stderr/stdout:
smart-eq-preset-switcher --gui 2>&1 | tee /tmp/smarteq-run.logA GTK/WebKit tray app can appear as multiple processes in KDE process dialogs. That is normal unless memory usage keeps climbing over time.
On Linux the app defaults to the X11/XWayland GTK backend for GUI launches because WebKitGTK/AppIndicator combinations can hit Gdk-Message: Error 71 (Protocol error) dispatching to Wayland display on KDE/Wayland/NVIDIA setups. To explicitly test native Wayland:
SMART_EQ_USE_WAYLAND=1 smart-eq-preset-switcher --gui
# or
smart-eq-preset-switcher --wayland --guiThe normal GUI path initializes the tray on Linux. Start background/tray-only mode explicitly with:
smart-eq-preset-switcher --trayIf a distro-specific AppIndicator issue appears, disable the tray for one launch with:
SMART_EQ_DISABLE_TRAY=1 smart-eq-preset-switcher --guiWindows installers are best built on Windows, but the Linux build flow can now cross-build an NSIS installer as a best-effort path:
scripts/build-linux.sh --windows
# or directly
scripts/build-windows-from-linux.shThis path uses cargo-xwin and the MSVC Rust target. It needs rustup, cargo-xwin, NSIS, LLVM/LLD and llvm-rc. On Arch, nsis is in the AUR (paru -S nsis); official packages (llvm lld clang) come from pacman. MSI/WiX installers still require Windows; Linux cross-build is NSIS-only.
Expected output:
src-tauri/target/x86_64-pc-windows-msvc/release/bundle/nsis/*.exe
scripts\bootstrap-windows.bat
scripts\build-windows.batExpected Windows output:
src-tauri\target\release\bundle\nsis\*.exe
npm ci
npm run check
npm run check:project
npm run tauri -- dev
npm run tauri -- buildCommitted on purpose:
- Application source code
package-lock.jsonsrc-tauri/Cargo.lock- Tauri icon assets in
src-tauri/icons/ - Bootstrap/build scripts
- Documentation
Ignored on purpose:
node_modules/.svelte-kit/build/src-tauri/gen/src-tauri/target/.cargo-target/dist/
This repository is prepared for source upload, not binary distribution.
MIT. See LICENSE.


