OPINIONATED OMARCHY
TROUBLESHOOTING CORPUS
790
RECORDS
790
AUDITED
0
UNCHECKED
2388
SOURCES
LIVE
audio-input high very-common DISPUTE

Fix a microphone PipeWire never lists as an input source

omarchyarchendeavouroscachyosmanjarohyprlandwaylandpipewirelaptopintelamd
CORRECTED An auditor found the fix wrong or incomplete and rewrote it.
AUDIT NOTE

The profile advice, the monitor.alsa.properties = { alsa.use-ucm = true } drop-in and the context.objects api.alsa.pcm.source declaration are all verbatim-correct against Arch PipeWire/Troubleshooting lines 57-66 and 116-120 and PipeWire lines 432-436. Two real defects. (1) The ALSA test line hardcodes --device=hw:0,0, but card 0 device 0 is a playback PCM on most machines and hw: refuses the dat format/rate that internal mics do not natively support. The user gets a confusing failure that looks like broken hardware. It also omits that PipeWire holds the device, so the recording will usually just return 'Device or resource busy'. (2) The UCM drop-in is named alsa-config.conf, the exact same filename the crackling/underrun record tells users to create in the same directory. Applying both records silently destroys the first one.

The cause above was not rewritten and may still contain the error described. The fix below is the corrected version.

Symptom

No microphone anywhere: wpctl status has an empty Sources: list or only shows a monitor source, and browsers/Discord say no input device. arecord -l may still list the capture hardware. On laptops the internal mic and the headset mic on the combo jack are both missing.

Cause

Either the card is on a playback-only profile (no Analog Stereo Duplex), or WirePlumber's ALSA monitor is using the ACP card profile instead of the UCM profile that modern laptop codecs need to expose their capture path.

Fix

First check whether ALSA sees the capture device at all. Read the real card/device numbers, do not assume 0,0, and stop PipeWire so the device is free:


arecord -l    # note "card N ... device M" of the CAPTURE device; it is rarely 0,0
systemctl --user stop pipewire.socket pipewire-pulse.socket pipewire.service pipewire-pulse.service wireplumber.service
arecord -f cd -d 5 -D plughw:N,M /tmp/test-mic.wav   # plughw, not hw: hw rejects rates/formats the codec lacks
systemctl --user start pipewire.service wireplumber.service pipewire-pulse.service
aplay /tmp/test-mic.wav

If ALSA records fine but PipeWire has no source, fix the profile in pavucontrol -> Configuration (Analog Stereo Duplex, or a profile containing + Analog Stereo Input), or from the CLI:


wpctl status                 # note the Devices: ID of the card
wpctl set-profile <device-id> <profile-index>

If the input still never appears, force UCM. Give the file a distinct name. Do NOT reuse alsa-config.conf if you already created that file for the period-size/headroom fix, or you will overwrite it:


mkdir -p ~/.config/wireplumber/wireplumber.conf.d

# ~/.config/wireplumber/wireplumber.conf.d/60-alsa-ucm.conf
monitor.alsa.properties = {
  alsa.use-ucm = true
  # if UCM alone does not help, also try turning ACP off:
  # alsa.use-acp = false
}

systemctl --user restart wireplumber.service

The manual context.objects declaration and the alsamixer/wpctl unmute steps are correct as written. Just substitute the card/device numbers you got from arecord -l into api.alsa.path.

Verify

wpctl status lists a Source with a *, and pw-record --target <source-id> /tmp/t.wav followed by pw-play /tmp/t.wav plays back your voice.

Sources

microphone-not-detected-pipewire