public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Spidey / Claudio" <spideybr@gmail.com>
To: General PulseAudio Discussion
	<pulseaudio-discuss@lists.freedesktop.org>,
	gentoo-user@lists.gentoo.org
Subject: Re: [pulseaudio-discuss] [gentoo-user] PulseAudio 1.0-r1 + Skype ==> Garbled output sound
Date: Fri, 30 Sep 2011 00:09:59 -0300	[thread overview]
Message-ID: <CAGo3WerjXtJV6LixDm60tR7dm-1UitAG=GRbfnj4bNL7Q6khzQ@mail.gmail.com> (raw)
In-Reply-To: <CAMQ-g0cMyKs=kxZqeo78rySx+vg-4tyRCW=1NL4Wr_1bcAzMzw@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1728 bytes --]

On Thu, Sep 29, 2011 at 15:57, Jan Steffens <jan.steffens@gmail.com> wrote:

> On Thu, Sep 29, 2011 at 8:19 AM, Arun Raghavan
> <arun.raghavan@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-discuss@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

[-- Attachment #2: Type: text/html, Size: 2404 bytes --]

  parent reply	other threads:[~2011-09-30  3:12 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-09-29  1:04 [gentoo-user] PulseAudio 1.0-r1 + Skype ==> Garbled output sound Hilco Wijbenga
2011-09-29  3:20 ` Spidey / Claudio
     [not found]   ` <1317267903.6057.33.camel@snowflake>
2011-09-29  5:56     ` [pulseaudio-discuss] " Spidey / Claudio
2011-09-29  6:09       ` Hilco Wijbenga
     [not found]       ` <1317277176.6057.35.camel@snowflake>
     [not found]         ` <CAMQ-g0cMyKs=kxZqeo78rySx+vg-4tyRCW=1NL4Wr_1bcAzMzw@mail.gmail.com>
2011-09-30  3:09           ` Spidey / Claudio [this message]
2011-10-08 22:20             ` Hilco Wijbenga

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='CAGo3WerjXtJV6LixDm60tR7dm-1UitAG=GRbfnj4bNL7Q6khzQ@mail.gmail.com' \
    --to=spideybr@gmail.com \
    --cc=gentoo-user@lists.gentoo.org \
    --cc=pulseaudio-discuss@lists.freedesktop.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox