The Arctis Sound Manager has been released in version 1.6.6.

The tool manages audio settings of SteelSeries Arctis headsets on Linux, such as microphone EQ, filter chains and the GameDAC display. After version 1.6.5, this release contains only bug fixes.

Key changes: ASM no longer crashes on quit when PipeWire stops answering, and no longer re-sends the same move to idle apps every 5 seconds. The Arctis Pro (2019, wired) gets its own profile, and the on-device EQ of the Arctis Nova 5 / 5X is no longer stuck at -10 dB.

Fixed

• Quitting ASM no longer crashes when PipeWire stops answering (#349). The tray’s last default-sink switch could time out and the error killed it before it finished; a unit that ignored the stop was then sent a second polite signal instead of being killed. Both are handled now. Thanks @ziggityzack for the reproduction and the analysis.
• ASM no longer re-sends the same move to an idle native app every 5 seconds (#349). An app pinned to an output but not playing has no link, so ASM never saw it as already there and asked PipeWire again and again for the whole session. It now asks once per stream.
• Arctis Pro (2019, wired) gets a profile of its own, audio only. It was handled as a wireless Arctis 7, whose commands it does not have, so its battery, ChatMix and headset settings never worked. Like the Arctis 5 (2018), it now gets the audio features (channels, Sonar EQ, spatial audio) and no controls that would do nothing.
• Nova 7 Gen 2 / 7P Gen 2: the start-up sequence no longer loses commands after saving. After a save to the headset’s memory, its firmware ignores every command for 1.5 seconds, and ASM sent the next ones straight away. It now waits, as GG does.
• Arctis Nova 5 / 5X: the on-device EQ is no longer stuck at -10 dB (#347). This headset encodes each band’s gain its own way, 2 × (10 + dB) with 20 for 0 dB, and ASM sent the signed form the other headsets use. In Sonar mode, where ASM flattens the headset’s EQ so only Sonar’s curve applies, every band went to -10 dB; in Custom mode the curve came out shifted. Thanks @gouwschristo, whose read-back of the stored curve showed it.

Source: GitHub