-   Linux - Hardware (
-   -   Mic not recognised by PulseAudio (for Skype) (

gumb 12-25-2012 12:48 PM

Mic not recognised by PulseAudio (for Skype)
I desperately need to put the last piece of a jigsaw in place for the audio setup on my parents' PC before I leave it with them for another few months. I've finally got everything set up the way I've been trying to do it for years but with just one hitch, and most of my Christmas Day has been stolen already fiddling with this.

Scenario: Running openSUSE 12.2, KDE with Gstreamer Phonon backend and PulseAudio enabled. Two sound devices on the system - the on-chip Intel ICH as default for everything and a USB FM transmitter so that when my dad listens to his music collection in Clementine the sound goes to his hifi speakers. The only problem now is that Skype calls are not possible as the microphone isn't recognised anywhere in PulseAudio.

It's the USB webcam microphone, which has a separate audio input in the standard mic jack of the PC. In neither pavucontrol, nor the Veromix KDE plasmoid I'm using as a mixer, nor in the regular KMix mixer panel is the mic visible as an input source. However, it will record if I go into Audacity. Also, if I disable PulseAudio and reboot, the mic works fine including with Skype (problem there is that I can't find a way to channel just music to the hifi speakers without PulseAudio - the Phonon settings don't work and neither does choosing a specific output within Clementine).

I've checked all the Alsamixer levels and reapplied the mic boost and capture volumes each time after enabling/disabling PulseAudio. It appears this problem may be known - this post on the Fedora forums seems related but the fix doesn't work for me. I enabled the following line in the /etc/pulse/ file:

load-module module-alsa-source device=hw:1,0
but on reboot the system starts up using ALSA and not PulseAudio.

I'm lost!

Shadow_7 12-26-2012 08:04 AM

Pulseaudio can be stopped / started at the user level.

$ pulseaudio --kill
$ pulseaudio --start

So no need to reboot. A lot of configurations are set to auto spawn pulseaudio when it is not running. Adding "autospawn = no" (or changing it) in /etc/pulse/client.conf should allow you to selectively not use pulse audio. While still retaining the option from the above user commands.

Pulse is a bit quirky still. I've had to add a number of things for my ice1712 (delta 44) setup. To include a udev entry, /usr/share/pulseaudio/alsa-mixer/profile-sets/ customization, and probably something else I can't recall off the top of my head. Although teamspeak 3 works fine for me with my setup and an odd mic location (input 3). I have yet to use skype, but I'm not a phone person.

With the autospawn disabled, I can stop pulse and run other audio applications that run over jack without the usual performance hit of using pulse over jack. It just takes a bit of user awareness to remember this option and to check ps output when in doubt. I'd recommend using pulse as common things are likely compiled against it like openjdk, with various quirks if you do not use pulse.

gumb 12-26-2012 08:53 AM

Hi. Thanks for responding. Looks like I've just stumbled upon the solution and it was something silly. Put it down to my lack of knowledge with PulseAudio and audio routing. I've always yanked it off every system to date because I don't like the dynamic mixer controls and it used to cause other problems, but now it's doing what I always hoped it would - manage two separate audio outputs and let me channel certain programs to one or the other. It's just not very obvious to non-sound-technicians how to do that.

The fix: I hadn't set the Internal Audio to Analog Stereo Duplex, which can be done from the Input tab of pavucontrol and other places. I'd had it set as Output only, hence the microphone didn't show up anywhere. All seems to be working fine now, including Skype. Just hope all the settings and volume levels stay intact for a few months and a few hundred reboots, until my next visit!

All times are GMT -5. The time now is 04:50 PM.