| Summary: | Unable to use internal microphone once headset is connected | ||
|---|---|---|---|
| Product: | [Unmaintained] plasma-pa | Reporter: | BOF <bugs_kde_org.5.kuru> |
| Component: | general | Assignee: | Plasma Bugs List <plasma-bugs-null> |
| Status: | RESOLVED NOT A BUG | ||
| Severity: | normal | CC: | isma.af, nate, nicolas.fella, sitter |
| Priority: | NOR | ||
| Version First Reported In: | 6.1.0 | ||
| Target Milestone: | --- | ||
| Platform: | Other | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed/Implemented In: | ||
| Sentry Crash Report: | |||
|
Description
BOF
2024-06-25 19:18:09 UTC
Add 3) I got an audio splitter for headphones/microphone and now i can use the *external* microphone. The internal microphone still does not work. When I switch to it in the setting app there is nothing but silence. While testing I double checked that the system was not using the microphone that is integrated to my laptop. Audio splitter like this one: https://www.amazon.de/Jack-splitter-kabel-Microfoon-Audio/dp/B00JSR5OIE add 4) As my bluetooth headphones also have an integrated microphone, I can use this as audio input. So there wouldn't even be a need for an extra microphone. Yet if I connect an external microphone to the dual-use port of my laptop, I can not switch between them. 6) I had an extra ~5 EUR in-ear headset with included microphone with a 3.5mm audio jack. This one worked fine for both audio and microphone. As in Add 3) I made sure that the system was not using the integrated microphone. 7) It turned out that the headphones I was using uses the plug of a headset (so no wonder the system acts like an external microphone is connected) I used a 3.5mm extension cord (that is headphones only) and connected the same headset. Now I can use the headset and the internal mic. So the main question for me now is question, whether it's KDE or my PC that mutes the internal microphone once an external microphone is connected. Is there any way to find out if the internal microphone is 'connected' to the system or if something else goes wrong inside KDE? We do not have special code that handles this. It'd either be in pipewire or on hardware. I am not sure there is a good way to find out which. |