<html> <head> <base href="https://bugs.freedesktop.org/" /> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW - When testing a Skype installation (using Skype's Test Call), there is no pavucontrol facility to specify "Use webcam microphone". (default is 'builtin mic')" href="https://bugs.freedesktop.org/show_bug.cgi?id=89158#c4">Comment # 4</a> on <a class="bz_bug_link bz_status_NEW " title="NEW - When testing a Skype installation (using Skype's Test Call), there is no pavucontrol facility to specify "Use webcam microphone". (default is 'builtin mic')" href="https://bugs.freedesktop.org/show_bug.cgi?id=89158">bug 89158</a> from <a class="email" href="mailto:david.henningsson@canonical.com" title="David Henningsson <david.henningsson@canonical.com>"> David Henningsson</a> <pre>> I see here that Mageia's Skype is not the only one affected by pulseaudio's > bizarre handling of webcam microphone input (UBUNTU report): The link you posted is from 2011. The unity-control-center sound rework was released in 2012 (for Ubuntu 12.04). > In a situation when it has found the USB webcam's microphone (it shows its > input strength in Input Devices's 'blue-line' meter), why does pulseaudio > persist in using the PC's unplugged mic input line instead of the webcam's (or > at least offering the choice in a civilised way)? > That's what is wrong here. Yeah. I'm sometimes working on improving the routing so that this (and other problems) would be fixed, but progress is slow as PulseAudio's internal objects aren't really organised in a good way for this type of routing to be easy to do.</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the QA Contact for the bug.</li> <li>You are the assignee for the bug.</li> </ul> </body> </html>