On Sat, Apr 5, 2014 at 5:22 PM, Michael Gilbert wrote: > It probably makes sense to change the default to 5 rather than 25.
It appears that this breaks other software such as skype[1], and the workaround would be to actually raise the latency. Quoting from the link: ==== Applications can ask PulseAudio for the latency that they wish to have (the amount of time between writing out a sample and it being played out the speaker/headphones/whatever). 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. ==== Rather than change the default, perhaps wine can set PULSE_LATENCY_MSEC? Applications that are buggy with too high or too low latencies will probably exist always. I don't know what should we do in this case. [1] http://arunraghavan.net/2013/08/pulseaudio-4-0-and-skype/#comment-723074 -- Saludos, Felipe Sateler -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
