v1.2.27

Added

• Provisional support for an Arctis 7+ hardware revision (0x220c). A dongle reporting this product id was in no device profile, so ASM recognised nothing and sent it nothing at all — no settings, no battery, no ChatMix. Audio worked throughout, because that side is plain USB audio handled by the kernel, which makes the gap easy to miss: everything sounds fine while nothing you set in the app reaches the headset. It also meant no udev rule was generated for it, so the device was denied access even after running asm-setup. This revision exposes a different USB layout from the other 7+ variants (HID interfaces 0 and 1, where they use interface 3), so it gets its own profile rather than a fifth product id on the existing one. Marked provisional: the control interface and command set are inferred from the endpoint sizes and the rest of the family, and not yet confirmed on hardware — if your 7+ behaves oddly rather than simply working, please say so in the issue. Reported by @Michsior14. (#180)

Fixed

• The Channels tab's per-channel output device now actually sticks. Sending a channel to something other than the headset — Media to your speakers, say — appeared to do nothing for any app that also had a saved routing override on that channel. The setting was saved correctly and the move itself worked; two enforcement passes then fought over the stream every few seconds. The per-app override pass resolved to the bare virtual sink and moved the stream back to the headset, the channel-output pass moved it out to the speakers again, forever. Both passes now resolve through the same destination before acting, so the pick holds — and when the configured output isn't currently plugged in, the channel falls back to the headset instead of routing to a sink that doesn't exist. Contributed by @relxek. (#177)
• Arch and CachyOS were stranded on 1.2.25. The v1.2.26 repository publish lost its database upload to a transient HTTP 503 from GitHub. The packages went up, the index did not — and pacman resolves against that index, so the signed repository kept advertising the previous version to everyone while the new package sat there unreferenced. Uploads are now retried, and the database is published after the packages it names, so an interrupted run leaves the previous coherent repository rather than an index pointing at missing files. The release delivery check was also looking the wrong way: it verified the AUR — which nothing on this side can guarantee, since pushing depends on aur.archlinux.org's git being reachable — while never checking the repository Arch users install from. It now reads the actual pacman database, and an AUR outage no longer fails a release or buries a real problem under recurring noise. (#178, #176)
• pacman -S noise-suppression-for-voice was missing from the signed repository. v1.2.26 made the mic noise-cancel plugin an optional dependency shipped alongside ASM, but it had silently stopped building: GCC 15 no longer pulls in a header the plugin's 0.91 release relies on. The build step tolerates failures by design — a broken upstream must not hold back a release — so it only logged a warning, and the repository shipped without it. It builds and is published again. (#175)
• SteamOS, Bazzite and Silverblue could not update. The Distrobox installers built ASM from the AUR, so when aur.archlinux.org went into maintenance there was no supported way forward on an immutable OS — the workaround being shared around was hand-editing a PKGBUILD, re-running checksums and manually installing service files a stale package definition never knew about. They now register the signed repository inside the container and install from there, falling back to the AUR only if it is unreachable. Updating becomes a plain pacman -Syu inside the container. Reported by @baccatuesday, with help from @TheJurassicSnark. (#175)
• The DAC screen no longer flashes the ASM logo when Custom Display is off. Turning Custom Display off means keeping the DAC's own interface, but the startup splash was drawn anyway — at daemon start, and again every time the app was opened or the tray icon clicked. It did more than flash a logo: showing it also paused the refresh loop for its full duration, and that loop is what hands the panel back to the firmware, so the screen sat frozen on the ASM logo for a few seconds before snapping back. Reported on Discord by Messiah Complex on a Nova Pro Wired DAC.