We have collected the most relevant information on Skype Pulseaudio Latency. Open the URLs, which are collected below, and you will find all the info you are interested in.
PulseAudio 4.0 and Skype – Arun Raghavan
https://arunraghavan.net/2013/08/pulseaudio-4-0-and-skype/
Skype seemed to have some weird buggy math that only kicked in at low latencies (20-25ms or less) that caused the problem you saw. Setting PULSE_LATENCY_MSEC forces the requested latency (60 is pretty safe across most setups), making sure this bug in Skype is not triggered. Hope that makes some sense.
Chroot 32-bit + Skype + PulseAudio = problems (solved ...
https://bartlomiejb.wordpress.com/2013/12/05/chroot-32-bit-skype-pulseaudio-problems/comment-page-1/
The second line (PULSE_LATENCY_MSEC=60 skype) was/is important to work around the bug in Skype that was adding some “funny” effects, like no sound at all or only some noises. Read this post from PulseAudio developer to learn more. I experienced these problems with PulseAudio 4.0 and Skype 4.2.0.11. This line works like a charm and all works OK.
Pulseaudio bug with skype | Linux.org
https://www.linux.org/threads/pulseaudio-bug-with-skype.10413/
Jul 21, 2014. #4. Skype does not fully support Pulse. And the latest skype for linux has NO alsa support. I think this is a mic problem, caused by latency. This may help: Code: sudo sed -i 's/^Exec=.*/Exec=env PULSE_LATENCY_MSEC=30 skype %U/' /usr/share/applications/skype.desktop. OP.
FS#35690 : [skype] pulseaudio 4.0-1 breaks sound in skype
https://bugs.archlinux.org/task/35690
I confirm adding PULSE_LATENCY_MSEC=30 to the launching script helped. This is the Exec line in the .desktop file: Exec=/usr/bin/env PULSE_LATENCY_MSEC=30 /usr/bin/skype
Now you know Skype Pulseaudio Latency
Now that you know Skype Pulseaudio Latency, we suggest that you familiarize yourself with information on similar questions.
