Fix a USB webcam or USB mic that records pure silence until it is replugged
Read the creaseygit/c920-mic-wake README, its 51-c920-soft-mixer.conf and install.sh, and issue #12047 in full. The cause (C920 046d:082d firmware keeps streaming zeros if capture starts while hardware mute is on, PipeWire maps desktop mute onto that control) and the fix match the repo exactly: the WirePlumber rule is byte-for-byte the repo's, and awk '/C920/{print $1; exit}' /proc/asound/cards plus amixer -c "$CARD" sset Mic cap mirror install.sh. alsa-utils and pipewire are in Omarchy's base packages, and Omarchy 4.0.4 applies its own alsa-soft-mixer.conf only on ASUS machines (install/user/hardware/asus/fix-audio-mixer.sh), so the per-device rule is still needed elsewhere. One defect: the symptom says it often starts after pressing mute and lumps the Blue Yeti into that. Issue #12047 reports the Yeti going silent after a reboot with no mute involved, the hardware capture clock at zero, recovered only by a firmware reset or replug, and the C920 author's link to it is only a suggestion. The symptom now separates the two. Not exercised: no USB microphone here.
Symptom
A Logitech C920 webcam microphone is listed in wpctl status, is the default source, shows unmuted with sane levels, and apps see it, but every recording is digital silence (every sample exactly zero). Restarting PipeWire does not help, unplugging and replugging the USB cable does. On the C920 it starts when the mic was muted (the bar's mute icon, a mute key, pactl set-source-mute) before an app opened it and was then unmuted. A Blue Yeti (046d:0ab7) has been reported in the same detected-but-silent state right after a reboot, with no mute involved.
Cause
For the C920 (046d:082d) the cause is a firmware bug: if a capture stream starts while the webcam's hardware mute is on, it keeps streaming zeros after unmute and still reports itself unmuted, until re-enumerated. PipeWire maps the desktop mic mute onto that hardware mute control, so a mute toggle before an app opens the mic triggers it. The Blue Yeti report has the same shape (capture clock stuck, recovered by a firmware reset or replug) but the C920 mechanism is not confirmed for it.
Fix
Make PipeWire do mute and volume in software for that device, so the buggy hardware mute is never touched. No root needed:
mkdir -p ~/.config/wireplumber/wireplumber.conf.d
# ~/.config/wireplumber/wireplumber.conf.d/51-c920-soft-mixer.conf
monitor.alsa.rules = [
{
matches = [
{
device.name = "~alsa_card.usb-046d_HD_Pro_Webcam_C920*"
}
]
actions = {
update-props = {
api.alsa.soft-mixer = true
}
}
}
]
For another device, take its card name from wpctl status / pw-cli ls Device | grep device.name and adjust the match. Set the hardware capture switch on and restart WirePlumber, then replug once to clear the current silent state:
CARD=$(awk '/C920/{print $1; exit}' /proc/asound/cards)
amixer -c "$CARD" sset Mic cap
systemctl --user restart wireplumber
For a Blue Yeti where this does not help, the reporter's fix was a firmware reset at boot with the third-party blue-yeti-autoreset tool, or a physical replug.
Verify
Mute and unmute the mic from the bar, then record: timeout 3 pw-record /tmp/mic.wav and play it back with pw-play /tmp/mic.wav. Your voice is audible.