audacity kills rear microphone input on Starship/Matisse HD as soon as it starts
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| audacity (Ubuntu) |
New
|
Undecided
|
Unassigned | ||
Bug Description
Scenario:
=========
1. A mainboard (Asus Prime 570-Pro) with onboard audio:
c:00.4 Audio device [0403]: Advanced Micro Devices, Inc. [AMD] Starship/Matisse HD Audio Controller [1022:1487]
Subsystem: ASUSTeK Computer Inc. Starship/Matisse HD Audio Controller [1043:8733]
2. The device is configured as Analog Stereo Duplex in pavucontrol
3. A microphone is plugged into the pink input jack
4. The VU-meter in the pavucontrol "Input devices" tab displays plausible levels for the mic
5. The mic works in most applications (mumble, teams)
Steps to reproduce:
===================
1. Start audacity
Expected behaviour:
===================
The microphone should continue to work, and Audacity should be able to use it
Observed behaviour:
===================
As soon as audacity starts, the VU-meter in pavucontrol is updated only about once a second, and the displayed levels have no discernible relation to the levels of noise I make as displayed e.g. for the USB Mic in my webcam. If I start to record using the microphone in Audacity, audacity records with a speed of maybe 0.25 recorded seconds per second of wall clock time, recording only weird sounds, if anything at all. The microphone stays unusable for all applications until I restart the computer.
ProblemType: Bug
DistroRelease: Ubuntu 20.10
Package: audacity 2.4.2~dfsg0-3
ProcVersionSign
Uname: Linux 5.8.0-20-lowlatency x86_64
ApportVersion: 2.20.11-0ubuntu48
Architecture: amd64
CasperMD5CheckR
CurrentDesktop: ubuntu:GNOME
Date: Sat Oct 3 13:21:59 2020
InstallationDate: Installed on 2020-05-28 (127 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
SourcePackage: audacity
UpgradeStatus: Upgraded to groovy on 2020-10-03 (0 days ago)
| Florian Hars (hars) wrote | #1 |
| description: | updated |
| Florian Hars (hars) wrote | #2 |
| Luís Gomes (luis-gomes-fcul) wrote | #3 |
Another observation: The microphone input works perfectly fine with jackd, too. But if I start pulseaudio, then start and immediately quit audacity, then stop pulseaudio again and try to start jackd from qjackctl, qjackctl hangs and I have to force quit it.
I also attach the log output from audacity, the lines around the "AlsaOpen ... failed" my be relevant.