On Thu, Sep 29, 2011 at 15:57, Jan Steffens <jan.steff...@gmail.com> wrote:
> On Thu, Sep 29, 2011 at 8:19 AM, Arun Raghavan > <arun.ragha...@collabora.co.uk> wrote: > > On Thu, 2011-09-29 at 02:56 -0300, Spidey / Claudio wrote: > > [...] > >> My bad, hadn't synced yet before that post. I'll test it throughly and > >> tomorrow (today, 29/09) I'll give feedback. > >> Can you reproduce the reported error? I won't file the bug just yet. > > > > Nope -- the mic works just fine for me and a bunch of other people, so I > > suspect a problem on that specific machine. > > Having the same problem using Arch Linux x86_64. Running pulseaudio > 1.0 and skype using lib32-libpulse 0.9.23 seems to be fine, while > skype using lib32-libpulse 1.0 garbles the input. > > Bisecting lib32-libpulse has proven difficult, with me arriving at > seemingly random commits. It appears the issue is not consistently > reproducible. > > So far the earliest commit that reproduced the issue for me seems to > be af18bc8038177a4b83171671daaf771ecf353b8e. > > A colleague running Arch Linux i686 claims he has no issues running > pulseaudio 0.99.4, while sometimes encountering the issue using > pulseaudio 1.0. > _______________________________________________ > pulseaudio-discuss mailing list > pulseaudio-disc...@lists.freedesktop.org > http://lists.freedesktop.org/mailman/listinfo/pulseaudio-discuss > 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. Emerge pavucontrol and check your devices' profiles. Claudio Roberto França Pereira (a.k.a. Spidey) hardMOB - HTForum - @spideybr Engenharia de Computação - UFES 2006/1
