Repository navigation
Sonero 0.1.5 — Harmonic bass, and an interface you can repaint
Two features you can see, and one change underneath them that you cannot: every
output channel now runs Sonero's own processing instead of the daemon's. That is
what made the bass stage possible, and it is also the reason this release touches
everyone's audio and not only the people who switch the new things on.
Read that last part twice before upgrading. 0.1.4 built each channel out of a
PipeWire module-filter-chain and let the sink's own volume control do the fader.
0.1.5 replaces both with a pair of nodes Sonero owns and one chain running between
them. Routing, the stream mix for OBS and the device handling are unchanged and
still go through the same code as before — but the path your audio actually takes
is new, and it has run on one person's machine.
For the microphone, the Arch package and the update check, see the
0.1.4 and
0.1.3 notes — all three are
unchanged here.
What's new
- Harmonic bass synthesis, on every channel. A small driver cannot move enough
air to reproduce 40 Hz, and asking it to with an equalizer does not produce bass —
it produces excursion, and distortion of everything else playing at the same time.
So Sonero synthesises the harmonics of the bass instead, in the range the driver
does reproduce, and your hearing reconstructs the fundamental that is not there.
Crossover, level, how many orders, the balance between even and odd, and the
envelope timing are all yours, with aReplace lowsoption that filters the
original out rather than adding to it — the setting that earns its keep on small
drivers and Bluetooth. - The harmonics come from Chebyshev polynomials, not from clipping or
tanh.
T_n(cos x) = cos(n x)is an identity, so feeding a sinusoid through the n-th
polynomial produces exactly its n-th harmonic — per-order control rather than a
waveshaper's mush. The low band is normalised by its own envelope before shaping
and scaled back by it afterwards, which is the difference between harmonics that
breathe with the bass line and a constant buzz under the music. - Themes, as files you can write. Thirteen colours and a font in a JSON file.
Every shade in between — a hover against its surface, a slider groove, the tint
behind a soloed channel — is derived from those thirteen, so a coherent interface
costs thirteen decisions instead of thirty-six. Import, export and switch from the
Profiles page. Six examples ship: Nord, Gruvbox, Cyberpunk, Phosphor and two
light ones. - The built-in theme cannot be broken. It is compiled into the binary and is
only ever applied over, never replaced, so a theme file that is wrong, truncated
or written for an older version changes colours and nothing else — and selecting
the built-in one in Profiles is always a way back. An optional style-sheet block
covers what colours cannot say; Export stylesheet… writes out the whole sheet
with your colours already resolved, as the reference for writing one. - Themes reach the parts that are painted, not styled — the equalizer curve, the
VU meters, the channel strips' accents and the app chips, none of which a style
sheet can touch. Channel colours keep their own hue so green still means Game, but
take their saturation and lightness from the theme. - Battery without a list of blessed products. Read from the kernel's own
power_supplyclass, which publishes a charge level for any HID device whose
driver knows one. A vendor protocol is now one source behind a shared interface
rather than the feature itself — SteelSeries base stations still use that path
because they report battery no other way, and adding another vendor costs one file. - Devices behind a receiver are handled. For anything on a dongle the USB
descriptors describe the dongle — a Logitech Lightspeed receiver reports itself as
"USB Receiver" — so the power supply's own model name is matched as well. This was
found by probing real hardware, where matching on the USB strings alone silently
reported no battery.
Fixed
- Bluetooth battery never worked. PipeWire publishes the same Bluetooth sink
under two names, one with the MAC's colons intact, and a D-Bus object path may not
contain a colon. Every lookup was rejected withInvalid object path— five times
per device per refresh, filling the log — and no percentage ever arrived. It reads
now. - A device plugged in while the Channels page was open stayed invisible until you
switched channels or restarted Sonero. The page built its output list once and
never watched for changes, although the backend has published a revision counter
all along and the Mixer and Devices pages both use it. - The Channels page showed "Default output" for every channel, whatever it was
actually routed to. Rebuilding the list dropped the selection and nothing put it
back. - Qt failed to register Sonero with the desktop portal on every launch. The
desktop file name was set after the application object was constructed, by which
point the Wayland plugin had already registered the process — so the registration
that stuck was the one made before the name was known, and the window icon and
notifications were not tied toSonero.desktop.
What is finished and what is not
Working:
- The bass stage runs on all six output channels, with its own settings per channel,
remembered across restarts. The equalizer, the limiter and the fader are Sonero's
own code now, and the equalizer behaves exactly as it did in 0.1.4 — band gains
clamped to ±12 dB and the curve's boost compensated ahead of the filters. - Themes apply live, with no restart, and are remembered.
Not finished:
- The bass crossover is per channel, not per device. It should follow the
transducer — it is the frequency where your driver stops delivering — so
switching a channel from headphones to speakers means setting it again. Making it
a property of the device is the obvious next step and is not in this release. - A theme's optional style-sheet block can break its own layout. Nothing
validates it. The thirteen colours are the supported surface; the sheet is an
escape hatch, and the built-in theme behind it is why a bad one is recoverable. - There is no preview. You apply a theme to see it.
- Noise suppression still needs RNNoise at build time, exactly as in 0.1.4. It is
in the.deband the AppImage; from source it ispackaging/build-rnnoise.sh
everywhere except Arch.
What "tested" means here: 42 new automated cases across five suites, 139 in total,
and the bass measured rather than described. A pure 50 Hz sine has no harmonics in
it, so anything at 100 or 150 Hz was synthesised — and halving the input halves them
again, within a decibel of a factor of two, which is what separates this from a
distortion pedal. The same measurement through the running graph matches the offline
model within about 1 dB per frequency. The limiter never passes its ceiling whatever
is driving it, and the chain's output does not change with the block size PipeWire
happens to hand over.
What has not happened is other people listening to it, on other headphones. The
numbers say the algorithm is doing what it claims; whether the settings suit your
hardware is a judgement no test makes. If it sounds wrong, that is worth an issue.
Requirements
- PipeWire 0.3+ with WirePlumber — already running on every current desktop.
- Qt 6.2+ (the AppImage carries its own).
- RNNoise 0.2, for the microphone's noise suppression only. In the
.deband the
AppImage already;rnnoiseon Arch;packaging/build-rnnoise.shelsewhere. - x86-64.
Which file to download
| File | For |
|---|---|
| none — build the package | Arch, Manjaro, EndeavourOS (see the command below) |
Sonero-0.1.5-x86_64.AppImage |
Anything. Portable, built on the oldest glibc, carries its own Qt. |
sonero_0.1.5-ubuntu2204_amd64.deb |
Ubuntu 22.04, Linux Mint 21.x |
sonero_0.1.5-ubuntu2404_amd64.deb |
Ubuntu 24.04, Linux Mint 22.x |
sonero_0.1.5-ubuntu2604_amd64.deb |
Ubuntu 26.04 |
sonero_0.1.5-debian13_amd64.deb |
Debian 13 (trixie) |
Sonero-0.1.5-arch-x86_64.AppImage |
Arch, if you would rather not build |
Sonero-0.1.5-fedora-x86_64.AppImage |
Fedora, or a distribution at least as new |
The last two exist because CI builds on those distributions to catch bundling
regressions. They link a newer glibc and offer nothing the portable one does not.
# Arch, Manjaro, EndeavourOS — builds a real package and installs it with pacman
git clone https://github.com/Tatsu21/sonero.git
yay -B sonero/packaging/aur/sonero
# without an AUR helper: makepkg -si -D sonero/packaging/aur/sonero
# and packaging/aur/sonero-git builds main as it stands
# AppImage — needs FUSE 2, or run with --appimage-extract-and-run
chmod +x Sonero-0.1.5-x86_64.AppImage
./Sonero-0.1.5-x86_64.AppImageUpgrading
Your settings carry over. The bass stage starts switched off on every channel, so
0.1.5 sounds like 0.1.4 until you turn it on — which is the point: if something
sounds different immediately after upgrading, that is the rewritten channel path and
not a setting, and it is worth an issue.