On Thu, 2017-02-16 at 21:26 -0300, Fatima Castiglione Maldonado å?? wrote: > > To narrow down the problem further, you could try recording from the > > microphone at the same time when chrome is supposed to be recording > > from it. You can use this command: > > parecord --device=alsa_input.pci-0000_00_1b.0.analog-stereo test.wav > > When you play back that test.wav file, does it contain better > > microphone audio than what chrome produces? > > Not better at all. It contains the same cracking noise that chrome > produces. Maybe even worst, because the signal (cracking voice noise) to > noise (ambient noise) ratio appears worst than the signal-to-noise ratio > from "live experience" (while running Chrome). Ok, that suggests that the problem is not with chrome specifically. But in your first mail you said that firefox works fine... If you record with parecord without having chrome running at the same time, is the sound still bad? If it is, you can check if the audio is better without pulseaudio in the middle with this command: pasuspender -- arecord --device=plughw:0 --format=cd test.wav If that produces bad audio too, then it's a kernel driver problem. -- Tanu https://www.patreon.com/tanuk
