Arctis Sound Manager has been released in version 1.4.21.

The update removes the node.passive setting that was introduced in version 1.4.1 to enable the headset’s auto-off timer, but which created a dependency chain where audio in one channel relied on another actively playing. This design flaw caused recurring audio dropouts and contributed to underlying PipeWire stability problems. As a trade-off, the headset will no longer auto-power off from inactivity while the application runs - issue #180 is being reopened to track this.

What’s Fixed

The primary update addresses a critical audio issue by removing the node.passive setting that had been causing channels to go silent unexpectedly.

Key Changes:

• Reverted node.passive from all loopback and output-chain templates
• Removed it from the self-heal function that was silently reapplying it to existing configurations
• This resolves issues #223 (channels going silent) and significantly reduces triggers for #230 (system crashes)

Trade-off Accepted: The headset will no longer auto-power off from inactivity while the application runs. Issue #180 is being reopened to track this change.

Update, version 1.4.20: The previous update reverted the changes from version 1.4.19: the fixes for issues #223 and #230 had made filter-chain crashes more frequent on some hardware, not less. The fix for #223 pinned loopback playback nodes active via node.pause-on-idle=false, while the fix for #230 added cross-process locking around daemon and GUI link rewrites - together, these kept the audio chain continuously active, which triggered an underlying PipeWire concurrency bug more often. Reverting both restored the original idle-suspend behavior.

The release reverted fixes from version 1.4.19 that addressed issues #223 and #230. According to the notes, those previous changes “made filter-chain crashes more frequent on some hardware, not less.”

Key details:

• Issue #223’s fix had pinned node.pause-on-idle=false on loopback playback nodes
• Issue #230’s fix added cross-process locking around daemon and GUI link rewrites
• Together, these changes kept the audio chain continuously active, triggering an underlying PipeWire concurrency bug more frequently
• The removal of both fixes and associated safety measures restores the original idle-suspend behavior
• The maintainers acknowledged this reopens #223’s symptom (intermittent silence) but considered it preferable to crash loops
• Issue #230 remains open for a proper resolution

Source: GitHub