<div class="gmail_quote">On Thu, Sep 29, 2011 at 15:57, Jan Steffens <span dir="ltr"><<a href="mailto:jan.steffens@gmail.com" target="_blank">jan.steffens@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div>On Thu, Sep 29, 2011 at 8:19 AM, Arun Raghavan<br>
<<a href="mailto:arun.raghavan@collabora.co.uk" target="_blank">arun.raghavan@collabora.co.uk</a>> wrote:<br>
> On Thu, 2011-09-29 at 02:56 -0300, Spidey / Claudio wrote:<br>
> [...]<br>
>> My bad, hadn't synced yet before that post. I'll test it throughly and<br>
>> tomorrow (today, 29/09) I'll give feedback.<br>
>> Can you reproduce the reported error? I won't file the bug just yet.<br>
><br>
> Nope -- the mic works just fine for me and a bunch of other people, so I<br>
> suspect a problem on that specific machine.<br>
<br>
</div>Having the same problem using Arch Linux x86_64. Running pulseaudio<br>
1.0 and skype using lib32-libpulse 0.9.23 seems to be fine, while<br>
skype using lib32-libpulse 1.0 garbles the input.<br>
<br>
Bisecting lib32-libpulse has proven difficult, with me arriving at<br>
seemingly random commits. It appears the issue is not consistently<br>
reproducible.<br>
<br>
So far the earliest commit that reproduced the issue for me seems to<br>
be af18bc8038177a4b83171671daaf771ecf353b8e.<br>
<br>
A colleague running Arch Linux i686 claims he has no issues running<br>
pulseaudio 0.99.4, while sometimes encountering the issue using<br>
pulseaudio 1.0.<br>
<div><div></div><div>_______________________________________________<br>
pulseaudio-discuss mailing list<br>
<a href="mailto:pulseaudio-discuss@lists.freedesktop.org" target="_blank">pulseaudio-discuss@lists.freedesktop.org</a><br>
<a href="http://lists.freedesktop.org/mailman/listinfo/pulseaudio-discuss" target="_blank">http://lists.freedesktop.org/mailman/listinfo/pulseaudio-discuss</a><br>
</div></div></blockquote></div><br>Tested today pulseaudio-1.0-r1 with skype-2.2.0.35-r1 without mic problems. Had to test with echo123, but it worked, anyways.<br>Emerge pavucontrol and check your devices' profiles.<br>
<br clear="all">Claudio Roberto França Pereira (a.k.a. Spidey)<br>
hardMOB - HTForum - @spideybr<br>Engenharia de Computação - UFES 2006/1<br>