[Bug 1228057] New: Headset microphone not recognized
https://bugzilla.suse.com/show_bug.cgi?id=1228057 Bug ID: 1228057 Summary: Headset microphone not recognized Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: openSUSE Tumbleweed Status: NEW Severity: Normal Priority: P5 - None Component: Sound Assignee: tiwai@suse.com Reporter: ricardo.mestre@suse.com QA Contact: qa-bugs@suse.de Target Milestone: --- Found By: --- Blocker: --- Running tumbleweed. I have a headset Turtle Beach Stealth Pro. When i plug it in it detects the output, not the mic. pactl looks like this:
~ ❯ pactl list sources | grep "node.name" node.name = "alsa_output.usb-Turtle_Beach_Stealth_Pro_PlayStation_7702FFFF7202-01.analog-stereo"
In the sound system settings I am able to redefine this source profile from "Analog Stereo Output" to "Pro Audio". This makes the input visible in pactl:
~ ❯ pactl list sources | grep "node.name" node.name = "alsa_output.usb-Turtle_Beach_Stealth_Pro_PlayStation_7702FFFF7202-01.pro-output-0" node.name = "alsa_output.usb-Turtle_Beach_Stealth_Pro_PlayStation_7702FFFF7202-01.pro-output-1" node.name = "alsa_input.usb-Turtle_Beach_Stealth_Pro_PlayStation_7702FFFF7202-01.pro-input-0"
Then, i am even able to record directly from the mic (and play) using:
parec -d alsa_input.usb-Turtle_Beach_Stealth_Pro_PlayStation_7702FFFF7202-01.pro-input-0 --file-format=wav output.wav aplay output.wav
However, no application seems to use this as an input device (even apps for recording sound). I wouldn't say its a headset compatibility issue with linux systems in general as ubuntu seems to detect and set up everything as expected just by plugging it in. also:
~ ❯ cat /etc/os-release NAME="openSUSE Tumbleweed" # VERSION="20240503" ID="opensuse-tumbleweed" ID_LIKE="opensuse suse" VERSION_ID="20240503" PRETTY_NAME="openSUSE Tumbleweed" ANSI_COLOR="0;32" # CPE 2.3 format, boo#1217921 CPE_NAME="cpe:2.3:o:opensuse:tumbleweed:20240503:*:*:*:*:*:*:*" #CPE 2.2 format #CPE_NAME="cpe:/o:opensuse:tumbleweed:20240503" BUG_REPORT_URL="https://bugzilla.opensuse.org" SUPPORT_URL="https://bugs.opensuse.org" HOME_URL="https://www.opensuse.org" DOCUMENTATION_URL="https://en.opensuse.org/Portal:Tumbleweed" LOGO="distributor-logo-Tumbleweed" -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1228057 https://bugzilla.suse.com/show_bug.cgi?id=1228057#c1 Takashi Iwai <tiwai@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags| |needinfo?(ricardo.mestre@su | |se.com) CC| |ricardo.mestre@suse.com --- Comment #1 from Takashi Iwai <tiwai@suse.com> --- Could you give alsa-info.sh output? Run with --no-upload option and attach the output file to Bugzilla (don't paste). -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1228057 https://bugzilla.suse.com/show_bug.cgi?id=1228057#c2 --- Comment #2 from Ricardo Mestre <ricardo.mestre@suse.com> --- Created attachment 876096 --> https://bugzilla.suse.com/attachment.cgi?id=876096&action=edit output of > ./alsa-info.sh --no-upload Thanks for the quick reply. Here you go. Let me know if you could use some more info or tests. -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1228057 https://bugzilla.suse.com/show_bug.cgi?id=1228057#c3 --- Comment #3 from Takashi Iwai <tiwai@suse.com> --- Judging from the log, it seems that the device provides two outputs and one input. This might confuse the default setup. Actually, what does the secondary PCM (playback) device work for? When you run like: % aplay -Dplughw:2,0 -vv foo.wav do you hear from the normal output from the headset? And if you run like % aplay -Dplughw:2,1 -vv foo.wav does it sound as well? Also, can you record directly via % arecord -Dplughw:2,0 -fdat -vv bar.wav ? You might need to turn off the wireplumber temporarily while testing the above: % systemctl --user stop wireplumber and restart after testing % systemctl --user start wireplumber -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1228057 https://bugzilla.suse.com/show_bug.cgi?id=1228057#c4 --- Comment #4 from Ricardo Mestre <ricardo.mestre@suse.com> --- Yes, when both commands played on the headset (both on stereo). Even verbose printed the same information (expect the number of the device). Recording like you mentioned worked fine. (Didn't need to turn off wireplumber). -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1228057 https://bugzilla.suse.com/show_bug.cgi?id=1228057#c5 --- Comment #5 from Takashi Iwai <tiwai@suse.com> --- Thanks. So the driver itself looks working. When you run both aplay with -Dplughw:2,0 and -Dplughw:2,1 in parallel, do both play back correctly (i.e. both streams mixed)? Or does it hang or silence? -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1228057 https://bugzilla.suse.com/show_bug.cgi?id=1228057#c6 --- Comment #6 from Ricardo Mestre <ricardo.mestre@suse.com> --- Created attachment 876158 --> https://bugzilla.suse.com/attachment.cgi?id=876158&action=edit aplay in parallel I ran two distinct sounds as:
{ aplay -Dplughw:2,0 -vv foo.wav & aplay -Dplughw:2,1 -vv bar.wav & wait; } > aplay_paralell.out 2>&1 The first sound played in stereo. The other, which was longer (didn't know if it would make any difference) didnt play at all and even yield an error.
I did run another test replacing one of these by the laptop sound card and heard both sounds (from the different speakers) -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1228057 Ricardo Mestre <ricardo.mestre@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Attachment #876158|audio/x-wav |text/plain mime type| | -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1228057 https://bugzilla.suse.com/show_bug.cgi?id=1228057#c7 --- Comment #7 from Takashi Iwai <tiwai@suse.com> --- OK, so it makes little sense to keep both devices available. Could you try to copy (overwrite) the file USB-Audio.conf in below to /usr/share/alsa/cards/USB-Audio.conf, re-login and retry? I'm not sure whether this has any good effect for pipewire, though. If not, we might need to fiddle with alsa-ucm or patching kernel. -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1228057 https://bugzilla.suse.com/show_bug.cgi?id=1228057#c8 --- Comment #8 from Takashi Iwai <tiwai@suse.com> --- Created attachment 876163 --> https://bugzilla.suse.com/attachment.cgi?id=876163&action=edit USB-Audio.conf -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1228057 https://bugzilla.suse.com/show_bug.cgi?id=1228057#c9 --- Comment #9 from Ricardo Mestre <ricardo.mestre@suse.com> --- Unfortunately nothing has changed, even after rebooting and re-plugin it in -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1228057 https://bugzilla.suse.com/show_bug.cgi?id=1228057#c10 --- Comment #10 from Takashi Iwai <tiwai@suse.com> --- Could you give alsa-info.sh output after replacing USB-Audio.conf? Also, could you give the output of "pactl list", too? -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1228057 https://bugzilla.suse.com/show_bug.cgi?id=1228057#c11 --- Comment #11 from Ricardo Mestre <ricardo.mestre@suse.com> --- Created attachment 876181 --> https://bugzilla.suse.com/attachment.cgi?id=876181&action=edit alsa-info.txt.Kur78MIk6q after adjust 1 -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1228057 https://bugzilla.suse.com/show_bug.cgi?id=1228057#c12 --- Comment #12 from Ricardo Mestre <ricardo.mestre@suse.com> --- Created attachment 876182 --> https://bugzilla.suse.com/attachment.cgi?id=876182&action=edit pactl after adjust 1 ofc, here you go. Appreciate your help -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1228057 https://bugzilla.suse.com/show_bug.cgi?id=1228057#c13 Takashi Iwai <tiwai@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |alarrosa@suse.com --- Comment #13 from Takashi Iwai <tiwai@suse.com> --- Thanks. The pactl shows that this headset has no duplex profile by some reason. So it looks rather like a bug in pipewire or wireplumber. Adding Antonio to Cc. Meanwhile, Ricardo, if you haven't tested the latest pipewire 1.2.1 (that should be available in OBS multimedia:libs project), could you try it out? Just to be sure. -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1228057 https://bugzilla.suse.com/show_bug.cgi?id=1228057#c14 --- Comment #14 from Ricardo Mestre <ricardo.mestre@suse.com> --- Created attachment 876242 --> https://bugzilla.suse.com/attachment.cgi?id=876242&action=edit pactl with pipewire 1.2.1 I was able to give it a go with pipewire 1.2.1. Nothing seemed to changed. alsa-info looks the same as before updating. pactl also doesn't look like it changed significantly, but it confirms the pipewire version. -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1228057 https://bugzilla.suse.com/show_bug.cgi?id=1228057#c15 --- Comment #15 from Takashi Iwai <tiwai@suse.com> --- Could you report the issue to the pipewire upstream? https://gitlab.freedesktop.org/pipewire/pipewire/-/issues -- You are receiving this mail because: You are on the CC list for the bug.
participants (1)
-
bugzilla_noreply＠suse.com