all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: ludo@gnu.org (Ludovic Courtès)
To: help-guix@gnu.org
Subject: Re: mumble issues with pulseaudio
Date: Sat, 01 Apr 2017 15:15:03 +0200	[thread overview]
Message-ID: <87shlsi814.fsf@gnu.org> (raw)
In-Reply-To: <20170331182310.noh3apyuautud73j@abyayala> (ng0's message of "Fri, 31 Mar 2017 18:23:10 +0000")

Hello,

ng0 <contact.ng0@cryptolab.net> skribis:

> The bug is, you have to close every possible open application which
> could make use of sound input/output (webbrowser, IM, etc) then shake
> the random dice pair and hope that Mumble detected your sound devices.
> If it didn't, you have to wait some seconds and restart Mumble and
> repeat it until your sound devices appear to be working.
> This is annoying and can leave you with the impression that it doesn't
> work - but it does work.

Could it be that Mumble does *not* use PulseAudio, but instead attempts
to use ALSA directly?

PulseAudio works best when all the applications on the system use it.
:-)  You can check with ‘pavucontrol’ the list of applications currently
doing audio with PulseAudio.

Note that applications that use PulseAudio, including ‘pavucontrol’,
automatically start the pulseaudio daemon if it’s not already running.

HTH!
Ludo’.

  reply	other threads:[~2017-04-01 13:15 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-31 18:23 mumble issues with pulseaudio ng0
2017-04-01 13:15 ` Ludovic Courtès [this message]
2017-04-01 15:43   ` ng0
2017-04-01 15:46     ` ng0
2017-04-02  9:33       ` Florian Paul Schmidt
2017-04-02  9:38         ` Florian Paul Schmidt
2017-04-03 10:08         ` Ludovic Courtès
2017-04-03 15:41           ` Alex Kost
2017-04-03 15:52             ` ng0
2017-04-03 21:18               ` Ludovic Courtès
2017-04-05  9:45                 ` Alex Kost
2017-04-05  9:57                   ` ng0
2017-04-05 12:47                     ` Florian Paul Schmidt
2017-04-08 20:32                       ` Ludovic Courtès
2017-04-02  9:10     ` Ludovic Courtès
2017-04-02 10:59       ` ng0

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=87shlsi814.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=help-guix@gnu.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.
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/guix.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.