Hello all,
I’ve been through a long struggle, but here is what’s happening:
- when I record with a program like GNOME Sound Recorder from my Line-In, it works fine. (But this is a rather limited tool, so I prefer Audacity)
- when I then start up Audacity and immediately close it again, recording with GNOME Sound Recorder doesn’t work properly: the timer that shows the amount of recorded time runs at about 10x slower speed and the sound recorded thus plays back at 10x normal speed. Also OBS can’t properly record anymore from inputs, exactly the same thing.
- when I try to record with Audacity, the same thing happens (even on a user that never ran Audacity, so not related to any settings)
- I haven’t found any way to recover, except by rebooting the PC. Then I can record normally again, until I start up Audacity.
So, there is something that Audacity does that affects all sound recording programs and I haven’t found a way to recover.
I’m using Debian GNU/Linux testing, with Audacity 3.7.0 currently.
I’m using pipewire as audio service.
The way I tried to recover: systemctl --user restart wireplumber pipewire pipewire-pulse pipewire.socket (so was not effective).
For now I’ve reverted to use kwave, but it would be nice to have this issue fixed…
I’ve also used arecorder and after I have started and closed Audacity, I can’t even use that command anymore (it says the resource is in use). E.g.: arecord -f dat -D hw:1,0 -vvv test.wav
Sound hardware:
$ arecord -l
**** List of CAPTURE Hardware Devices ****
card 1: Generic_1 [HD-Audio Generic], device 0: ALC1220 Analog [ALC1220 Analog]
Subdevices: 1/1
Subdevice #0: subdevice #0
card 1: Generic_1 [HD-Audio Generic], device 2: ALC1220 Alt Analog [ALC1220 Alt Analog]
Subdevices: 1/1
Subdevice #0: subdevice #0
Please help.