https://bugs.kde.org/show_bug.cgi?id=511276
--- Comment #11 from NeKoconut <[email protected]> --- (In reply to Nate Graham from comment #8) > *** Bug 512963 has been marked as a duplicate of this bug. *** This is in relation to my original report, Bug 512963, which was marked as a duplicate of this issue. I did some additional testing with my Elgato Wave:3 and was able to narrow down what is happening. On a fresh boot or after unplugging/replugging the microphone, the first press of the hardware mute button causes the Wave:3 to report a mute state to Linux. ALSA changes the Mic Capture Switch to off, and PipeWire also becomes muted. Pressing the hardware mute button again unmutes the microphone internally and changes the LED back to white, but the Wave:3 does not send a corresponding USB/ALSA unmute event. ALSA remains muted, so PipeWire remains software-muted as well. The underlying device behavior therefore appears to be part of the problem: the Wave:3 reports the hardware mute transition to the host, but does not report the corresponding hardware unmute transition. As a workaround, I added a WirePlumber rule for the Wave:3 with: api.alsa.soft-mixer = true This prevents PipeWire from tying its software mute state to the Wave:3 hardware mixer state. After applying the rule, the hardware mute/unmute button works normally and PipeWire no longer gets stuck muted. I also confirmed the workaround persists across reboot. I assume this workaround is already known, but I'm mainly leaving this comment so that anyone else who encounters this issue has a working solution. In my time searching for a solution for this bug, I did not find any solutions or workarounds for this. Hopefully this alleviates the problem until an upstream fix is available. -- You are receiving this mail because: You are watching all bug changes.
