v1.4.1

Added

• A channel's volume can be bound to a key. Sonar on Windows let you bind a key to a channel — turn a dial on a macropad, and Chat goes up or down by a fixed step without alt-tabbing. ASM cannot claim a key for itself on Wayland (the compositor owns that, and the mechanism that hands keys out is neither available everywhere nor able to grant a specific key like F20), so the action is a command your desktop binds instead: asm-cli volume game +5, chat mute, media 40, or several at once with game +5 chat -5. Bind it in your desktop's keyboard settings like any other shortcut. It goes straight to PipeWire, so a bound key works whether or not the window is open, and the new level is remembered exactly as the sliders' are. (#193)
• The clips folder can be changed. Under the gear in the Clips page, next to the capture settings: pick any folder you can write to, and new clips go there. Clips already recorded stay where they are — moving a library means moving each clip's trim, mix and track files with it, possibly across drives and possibly while a capture is running, and a library you want moved is one you can move yourself. "Default" returns to your desktop's video folder. (#192)

Fixed

• The USB permissions popup at every boot. Reported in July, fixed once, and still happening on clean installs a month later. Your dongle is usually enumerated early in the boot, before udev has applied its rules to it, so ASM's first attempt to open it fails even though the rules on disk are perfectly valid. A retry was added for that — but it gave up after ten seconds, and the only things that ever refilled its budget were a successful connection or unplugging the dongle. On the ordinary setup where the dongle never leaves its port, one slow boot meant the dialog stayed until you physically replugged it, no matter how correct your system was. ASM now keeps checking for a full minute before saying anything, and then goes on checking every thirty seconds instead of giving up — so rules that land late, or a fix applied from anywhere else, are picked up on their own. And if access comes back while the dialog is open, the dialog closes itself rather than asking you to fix something that is no longer broken. (discussion #140, discussion #190)

• The uninstaller now finds the installs it used to walk past. Two of them. A pip install --user copy in ~/.local was printed as a note and then ignored — so someone who had removed their distro package and still found ASM starting at every boot was told "No Arctis Sound Manager installation detected — nothing to do", three lines after the script had listed the offending file. And on Nobara and Ultramarine, where the package comes from Terra under the name python3-arctis-sound-manager, nothing was detected at all, because only our own package name was checked. Both are now found and removed, with --pip-user to target the ~/.local copy alone. A removal that fails also says so instead of reporting success. (discussion #190)

• Clips now go to your actual video folder. The save location was the literal path ~/Videos/ASM Clips — but "Videos" is the English name of a folder every desktop translates: ~/Vidéos, ~/Videók, ~/ビデオ. On any system not running in English, ASM quietly created a second video folder beside the real one, and clips landed somewhere the file manager never points at. The folder is now read from your desktop's own configuration, so it follows whatever your system calls it. If you already have clips in ~/Videos/ASM Clips, that stays your folder — nothing is moved out from under you. (#192)

• The headset can finally fall asleep. With ASM running, a headset set to power off after N minutes of inactivity simply never did — stop ASM and it powered off normally. The cause was in every audio chain ASM builds: none of its nodes declared node.passive, so each one kept pushing its chain even with nothing playing. The physical device sat in RUNNING permanently, the firmware never saw an idle moment, and its auto-off timer never started counting. All six output chains and the three channel loopbacks are now passive: they follow the audio instead of driving it, so once applications stop, the whole graph — loopback, EQ, spatial audio, device — suspends, and the headset powers off exactly as configured. Playback wakes it back up. Confirmed on a Nova Pro Wireless: with auto-off at one minute, the headset powered down in 45 seconds, and all three channels still play normally. Existing configs are repaired in place on the next start, so nobody's EQ is touched. Thanks to @Michsior14 for six rounds of captures on an Arctis 7+, and for the fix to the diagnostic script along the way. (#180)