(06-08-2020, 02:59 PM)tophneal Wrote: You might want to look at the settings in ALSA, then: https://linuxconfig.org/how-to-test-micr...cture-alsa
Okay. I guess I'm confused about how ALSA and PulseAudio might interact here. pavucontrol seems to provide accurate controls for my other input and output devices, just not the headset mic.
On another system, where the headset mic works, it shows up as a selectable input device in pavucontrol (something like "headset microphone (plugged in)")
Thanks for the ALSA test link. I tried it, but arecord -l only shows a single device with the headset plugged in.
**** List of CAPTURE Hardware Devices ****
card 0: rockchipes8316c [rockchip,es8316-codec], device 0: ff890000.i2s-ES8316 HiFi ES8316 HiFi-0 [ff890000.i2s-ES8316 HiFi ES8316 HiFi-0]
Subdevices: 0/1
Subdevice #0: subdevice #0
Attempting to record on that device (which I assume is the built-in mic anyway) gives an error:
arecord -f S16_LE -d 10 -r 16000 --device="hw:0,0" /tmp/test-mic.wav
arecord: main:830: audio open error: Device or resource busy
which is odd because nothing is using the input device (and both the toolbar audio mixer and pavucontrol show no active input).
Any ideas about next things to try? Are we sure that this should work to begin with?
-john