Microphone not working in Skype-4.3.0.37-r5 (SOLVED)

[Fred Krogh]

Using pavucontrol I can see that the microphone appears to be working. I can hear well on the test call, but silence in the part that is supposed to be playing what I said. The microphone records and plays back just fine when using audacity. Any ideas? Thanks,
Fred

[Fitzcarraldo]

Have you tried disabling the so-called PulseAudio 'glitch-free' mode (oh, the irony)? I find that I have to disable it or I cannot hear nor be heard via Skype. I have to edit the file /etc/pulse/default.pa and change the line:

Code: Select all

load-module module-udev-detect

to:

Code: Select all

load-module module-udev-detect tsched=0

Another thing I would try would be to launch ALSAMixer and check what happens to the microphone and microphone boost channels when Skype is running. It might be worth unticking ‘Allow Skype to automatically adjust my mixer levels’ in Skype if you have it ticked.

[Fred Krogh]

Thanks for the thoughts. I tried your change in /etc/pulse/default.pa. No luck. I don't see any difference in the microphone levels in alsamixer whether or not skype is runnings. The skype automatically adjust mixer levels has been turned off all along.

[MartinB]

I had this problem a few times before.

In my case, it was simply because Capture wasn't set on PulseAudio's audio input. You can change this using alsamixer.

When you run alsamixer, you need to specify the "card number" for PulseAudio so it will show you the controls of PulseAudio instead of your regular sound card. You can specify the card number using -c (e.g. alsamixer -c 2 to select card 2; the cards begin at 0 and I just keep trying different numbers until I get the one for PulseAudio).

When you've got PulseAudio in alsamixer, press F4 to switch to Capture controls. There should only be one Capture control for the PulseAudio "card". If you don't see the word "Capture" in red below this control, then this is your problem. Press space to switch the Capture on for this control, indicate by the word "Capture" in red below the control.

I hope this helps.

[Fred Krogh]

Thanks for the very clear instructions. It seems that I have two microphones that allow capture, the front mic, and one on the webcam. I was configured with just the front mic captured. I've tried all 4 combinations of the capturing on these with no effect on skype. Audacity is a different story. After restoring things to what I had before, it seems that I can record, but the play back just zips through so quickly that no content in the sound can be heard.

[MartinB]

If you've definitely followed the procedure to make sure that PulseAudio's input has Capture enabled, then I'm not sure what else to suggest.

In my case, recording in Audacity was also working, but not with Skype. The reason is that Audacity can capture audio directly from the microphone without going through PulseAudio, so the recording was working even without PulseAudio's input Capture being enabled, whereas Skype requires all audio to go through PulseAudio.

The problem with playback being too fast is also something I encountered recently. In my case, the recording in Audacity moved very slowly, so each second marked on the recording time line would take about eight seconds to record, thus the resulting recording was apparently "fast" when played back. But the recording wasn't just fast; it was also completely distorted, so even slowing it down wouldn't make it sound anything like what I recorded. In this case, the USB device in question was a synthesizer, which can also output audio to its own speakers as well as record. If I selected the USB synthesizer for playback in Audacity instead of my sound card, then it also would play at around 1/8th of the normal playback speed, instead of normal speed.

I'm not exactly sure what the cause of this problem is, but I'm guessing it's a buggy USB audio driver in the kernel. In my case, I was able to solve the problem simply by plugging the synthesizer into a different USB port on my PC. If I remember correctly, there were some clues in dmesg of a problem when plugging the synth into one of the non-working USB ports, so it might be useful to view the dmesg output when you connect your microphone/webcam.

I noticed later that the problem can also be reproduced with my USB webcam, so it's not specific to my synth, but seems to be a problem in general with certain USB chipsets.

[Fred Krogh]

I'm getting this error message which may indicate the source of the problem.

Gtk-Message: Failed to load module "canberra-gtk-module"

As suggested at https://forums.gentoo.org/viewtopic-t-8 ... art-0.html I have the environment variable GTK_MODULE set to /usr/lib64/gtk-2.0/modules/. I have used strace to see that skype is looking for this module in /usr/lib32/gtkl-2.0/modules. I have tried

Code: Select all

ln -s /usr/lib64/gtk-2.0/modules/libcanberra-gtk-module.so libcanberra-gtk-module.so

but that didn't fix anything. Sorry I should have mentioned this error message in the first place, but since skype was working not long ago, I let it slip. For completeness here are the relevent lines from strace

Code: Select all

access("/home/m/.gtk-2.0/2.10.0/i686-pc-linux-gnu/modules/libcanberra-gtk-module.so", F_OK) = -1 ENOENT (No such file or directory)
access("/home/m/.gtk-2.0/2.10.0/i686-pc-linux-gnu/modules/libcanberra-gtk-module.la", F_OK) = -1 ENOENT (No such file or directory)
access("/home/m/.gtk-2.0/2.10.0/modules/libcanberra-gtk-module.so", F_OK) = -1 ENOENT (No such file or directory)
access("/home/m/.gtk-2.0/2.10.0/modules/libcanberra-gtk-module.la", F_OK) = -1 ENOENT (No such file or directory)
access("/home/m/.gtk-2.0/i686-pc-linux-gnu/modules/libcanberra-gtk-module.so", F_OK) = -1 ENOENT (No such file or directory)
access("/home/m/.gtk-2.0/i686-pc-linux-gnu/modules/libcanberra-gtk-module.la", F_OK) = -1 ENOENT (No such file or directory)
access("/home/m/.gtk-2.0/modules/libcanberra-gtk-module.so", F_OK) = -1 ENOENT (No such file or directory)
access("/home/m/.gtk-2.0/modules/libcanberra-gtk-module.la", F_OK) = -1 ENOENT (No such file or directory)
access("/usr/lib32/gtk-2.0/2.10.0/i686-pc-linux-gnu/modules/libcanberra-gtk-module.so", F_OK) = -1 ENOENT (No such file or directory)
access("/usr/lib32/gtk-2.0/2.10.0/i686-pc-linux-gnu/modules/libcanberra-gtk-module.la", F_OK) = -1 ENOENT (No such file or directory)
access("/usr/lib32/gtk-2.0/2.10.0/modules/libcanberra-gtk-module.so", F_OK) = -1 ENOENT (No such file or directory)
access("/usr/lib32/gtk-2.0/2.10.0/modules/libcanberra-gtk-module.la", F_OK) = -1 ENOENT (No such file or directory)
access("/usr/lib32/gtk-2.0/i686-pc-linux-gnu/modules/libcanberra-gtk-module.so", F_OK) = -1 ENOENT (No such file or directory)
access("/usr/lib32/gtk-2.0/i686-pc-linux-gnu/modules/libcanberra-gtk-module.la", F_OK) = -1 ENOENT (No such file or directory)
access("/usr/lib32/gtk-2.0/modules/libcanberra-gtk-module.so", F_OK) = -1 ENOENT (No such file or directory)
access("/usr/lib32/gtk-2.0/modules/libcanberra-gtk-module.la", F_OK) = -1 ENOENT (No such file or directory)
stat64("libcanberra-gtk-module.so", 0xffcb1fa0) = -1 ENOENT (No such file or directory)
stat64("libcanberra-gtk-module.so.so", 0xffcb1fa0) = -1 ENOENT (No such file or directory)
stat64("libcanberra-gtk-module.so.la", 0xffcb1fa0) = -1 ENOENT (No such file or directory)
open("/etc/ld.so.cache", O_RDONLY|O_CLOEXEC) = 8
fstat64(8, {st_mode=S_IFREG|0644, st_size=233711, ...}) = 0
mmap2(NULL, 233711, PROT_READ, MAP_PRIVATE, 8, 0) = 0xfffffffff1c4f000
close(8)                                = 0
open("/lib32/libcanberra-gtk-module.so", O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory)
open("/usr/lib32/libcanberra-gtk-module.so", O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory)
munmap(0xf1c4f000, 233711)              = 0
write(2, "Gtk-Message: Failed to load modu"..., 57Gtk-Message: Failed to load module "canberra-gtk-module"
) = 57

[Fitzcarraldo]

In case it is of help, in my 64-bit multilib installation I have the following:

Code: Select all

$ env | grep MODULE
GTK_MODULES=canberra-gtk-module
$ locate libcanberra-gtk-module.so
/usr/lib64/gtk-2.0/modules/libcanberra-gtk-module.so
/usr/lib64/gtk-3.0/modules/libcanberra-gtk-module.so
$ locate libcanberra-gtk-module.la
$ eix -I libcanberra
[I] media-libs/libcanberra
     Available versions:  0.30-r1 0.30-r4 {alsa gnome gstreamer +gtk +gtk3 oss pulseaudio +sound tdb udev}
     Installed versions:  0.30-r4(11:39:55 12/01/15)(alsa gtk gtk3 pulseaudio sound udev -gnome -gstreamer -oss -tdb)
     Homepage:            http://git.0pointer.net/libcanberra.git/
     Description:         Portable sound event library

BTW, notice the environment variable is GTK_MODULES in my installation.

[Fred Krogh]

I just tried with this setup

Code: Select all

 $ env |grep MODULE
GTK_MODULES=canberra-gtk-module
GTK_MODULE=/usr/lib64/gtk-2.0/modules/
GLADE_MODULE_PATH=:
[quote][/quote][quote]

and get the same error and the same lack of recording. Our setups are very similar. This

Code: Select all

 # eix -I libcanberra 
[?] media-libs/libcanberra
     Available versions:  0.29 0.30-r1 {alsa gnome gstreamer +gtk +gtk3 oss pulseaudio +sound tdb udev}
     Installed versions:  0.30-r4(11:43:55 PM 01/10/2015)(alsa gnome gstreamer gtk gtk3 pulseaudio sound udev -oss -tdb)
     Homepage:            http://0pointer.de/lennart/projects/libcanberra/
     Description:         Portable sound event library

shows the only small differences. I assume that when you start skype you get no complaints about canberra, so somewhere there must be something different in our systems. Anyway, thans for looking at this.

[MartinB]

Are you certain the GTK problem is related to your Skype capture problem? GTK is the API for graphical user interfaces, so I'd guess the two problems are not related.

[Fred Krogh]

Sadly, I'm not sure of anything other than skype is not working. Also, google hangouts, does not ring up those called, and when called from outside google hangouts gives no sign of it here.

[Fred Krogh]

Sorry -- this has been working for awhile. I think the problem was having Digital Stereo Output selected when Analog Stereo Duplex was needed.

[mounty1]

I know it's nearly ten years since the last posting on this thread but here's something to try with KDE 4.14:

System Settings / Multimedia / Audio Recording / Recording

Then make sure your preferred device is at the top of the list on right pane of the System Settings dialog. For example, in my case the PC has a built-in audio card with the usual mic., line and headphone sockets but we use the microphone on the webcam instead. Even though the webcam microphone was enabled (and the built-in disabled) on the Pulseaudio settings, Phonon was still preferring the built-in microphone (even though none was plugged in).

So I changed the setting (clicked on Webcam then on the [Prefer] button), clicked [Apply] and successfully made a Skype test recording.

Then I thought I'll rehearse it again to be sure I was typing this comment correctly so I opened System Settings / Multimedia / Audio Recording / Recording again. The two devices (built-in and webcam) had disappeared and the right pane was now empty, despite having been there only twenty seconds previously. F&*^%#$ KDE again. Anyway, thankfully the settings were preserved and I was able to use Skype.

Oh, another point: I'd changed the backend from VLC to GStreamer. I don't know what if any difference that makes, and now that's it working, I don't intend to experiment any further.

[Efo]

I just had the same problem: mike works in audacity but not in skype

I fixed it by: going to "skype -> Sound Devices", then "Open PulseAudio Volume Control", then I clicked on the "Recording" tab in the PulseAudio window. After that I clicked "Make a test call" in the "Sound Devices" tab in the skype window and looked at the PulseAudio window. As skype begins the call, it pops up in the PulseAudio "Recording" tab. A button appeared with "Monitor of Built-in Audio Analog Stereo", I clicked it and changed to "Built-in Audio Analog Stereo", and that fixed it.

[Ordinateur91]

Thanks for the solution guys:)