On Mon, 21 Mar 2022 23:01:51 +0100, cblondin@xxxxxxxx wrote: > > Hi, > I was redirected here by pulseaudio maintainers for an issue I thought was at that layer : > https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/issues/1344 > > After a fresh reboot, arecord / parecord work fine, and the level meters in pavucontrol react normally. > If I start audacity, the card gets in a state where the level meters become sluggish, and recording either drops 90% of samples, or records approximately 10x too fast. > Playback is always ok, unaffected. > > I cannot fix that state other than by a reboot. The obvious "closing audacity", restarting the pulseaudio daemon, have no effect. > Tried kernels 5.15.24 and a recent 5.17; same problem. > > I posted some detailed debugging info on that pulseaudio issue tracker, as well as pastebinned alsa-info.sh output here: > http://alsa-project.org/db/?f=7ee784003379252acfef25de5fecbdfd559fe342 > > The problematic hardware is Card 1, Audio device [0403]: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) HD Audio Controller [1022:1457]. > > Test command : > pasuspender -- arecord -D hw:1,0 -f S16_LE -c 2 -r 44100 arec_pasusp.wav > > Here's an example recording of me saying 'test' : > https://gitlab.freedesktop.org/pulseaudio/pulseaudio/uploads/5a51081fcd55ecd705df258c1a0fd2b6/arec_44k.wav > > I have no ~/.asoundrc or related files. > > Anything I can try to narrow down the cause of this ? Is audacity recording via pulseaudio? And it happens only with audacity? That is, if you keep arecord running (over pulseaudio), and start audacity in parallel, does the problem still appear? In anyway, you need to try different ways to trigger the problem, without the need of complex sound system setup. thanks, Takashi
