David Heinemeier HanssonandClaude Opus 5
aa9f0c54c5
Laptop speakers ship voiced by the vendor's Windows DSP layer, which Linux does not get. A tuning restores that as a PipeWire filter-chain in front of the internal speaker sink, matched to the machine by DMI string and expected sink. Adding a laptop is a directory under default/audio/tunings with two files and no new code: matching is data. The XPS 14 DA14260 tuning included here was derived by measuring the xps-audio-linux EasyEffects profile (MIT) and fitting a biquad chain to it, so no impulse response or other upstream asset is redistributed. It measures 1.24 dB RMS against that reference, and matches its dynamic range within 0.1 LU -- the reference's multiband compressor turned out to contribute nothing, so a linear chain replaces it. Bass Q is capped deliberately: a closer magnitude fit swung group delay 31 ms across 63-80 Hz, which smears bass transients. The graph runs as its own PipeWire client under its own config name rather than loading into the audio daemon. The daemon only reads its config at startup, so a daemon-loaded tuning could only be switched by restarting PipeWire -- which drops every PulseAudio client's connection, and applications that do not reconnect (Spotify) then have to be restarted by hand. Hosting it separately also contains failure, since a malformed tuning breaks only that service. Three things about the surrounding audio graph needed fixing for this to behave: - Volume must live downstream of the tuning. omarchy-audio-output-sink is now the single definition of which sink an output's volume really uses, shared by the volume keys, the output switcher's OSD and the audio panel, so they cannot disagree. It resolves the current default output, which keeps it correct when headphones are selected while a tuning exists. - The tuning's own output is a movable sink input, so rerouting "all streams" to a newly selected output would drag the processing onto headphones, or into the tuning's own sink, which is a cycle. It is pinned, and stream moves are limited to streams carrying an application.name. - The physical sink a tuning fronts is not independently selectable, since picking it would only bypass the tuning, so it is kept out of the output list. Applying happens at first-run, not finalize-user, because finalize-user also runs in the ISO chroot where there is no audio server and nothing would retry. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
41 lines
1.3 KiB
Plaintext
41 lines
1.3 KiB
Plaintext
# Host config for the Omarchy speaker tuning.
|
|
#
|
|
# This exists so the tuning gets its own PipeWire client rather than sharing
|
|
# PipeWire's stock filter-chain.conf. That config merges every fragment in
|
|
# ~/.config/pipewire/filter-chain.conf.d/, so hosting the tuning there would load
|
|
# any unrelated filter a user keeps in that directory -- duplicating filters
|
|
# already hosted elsewhere, and stopping them all when the tuning is switched off.
|
|
#
|
|
# Installed as ~/.config/pipewire/omarchy-speaker-tuning.conf with the tuning
|
|
# graph merged from omarchy-speaker-tuning.conf.d/, and run with
|
|
# pipewire -c omarchy-speaker-tuning.conf
|
|
#
|
|
# The contents are the minimum a filter-hosting client needs, taken from
|
|
# /usr/share/pipewire/filter-chain.conf.
|
|
|
|
context.properties = {
|
|
log.level = 0
|
|
}
|
|
|
|
context.spa-libs = {
|
|
audio.convert.* = audioconvert/libspa-audioconvert
|
|
support.* = support/libspa-support
|
|
}
|
|
|
|
context.modules = [
|
|
# Boost the audio thread priority.
|
|
{ name = libpipewire-module-rt
|
|
args = { }
|
|
flags = [ ifexists nofail ]
|
|
}
|
|
|
|
# The native communication protocol.
|
|
{ name = libpipewire-module-protocol-native }
|
|
|
|
# Lets this process provide nodes to PipeWire.
|
|
{ name = libpipewire-module-client-node }
|
|
|
|
# Wraps nodes in an adapter with a converter and resampler.
|
|
{ name = libpipewire-module-adapter }
|
|
]
|