[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: mumble issues with pulseaudio
From: |
Ludovic Courtès |
Subject: |
Re: mumble issues with pulseaudio |
Date: |
Sat, 01 Apr 2017 15:15:03 +0200 |
User-agent: |
Gnus/5.13 (Gnus v5.13) Emacs/25.1 (gnu/linux) |
Hello,
ng0 <address@hidden> 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’.
- Re: mumble issues with pulseaudio,
Ludovic Courtès <=
- Re: mumble issues with pulseaudio, ng0, 2017/04/01
- Re: mumble issues with pulseaudio, ng0, 2017/04/01
- Re: mumble issues with pulseaudio, Florian Paul Schmidt, 2017/04/02
- Re: mumble issues with pulseaudio, Florian Paul Schmidt, 2017/04/02
- Re: mumble issues with pulseaudio, Ludovic Courtès, 2017/04/03
- Re: mumble issues with pulseaudio, Alex Kost, 2017/04/03
- Re: mumble issues with pulseaudio, ng0, 2017/04/03
- Re: mumble issues with pulseaudio, Ludovic Courtès, 2017/04/03
- Re: mumble issues with pulseaudio, Alex Kost, 2017/04/05
- Re: mumble issues with pulseaudio, ng0, 2017/04/05