From: Florian Paul Schmidt <mista.tapas@gmx.net>
To: help-guix@gnu.org
Subject: Re: mumble issues with pulseaudio
Date: Sun, 2 Apr 2017 11:38:15 +0200 [thread overview]
Message-ID: <f3637a8c-4915-1d8b-0d51-375c14a726cb@gmx.net> (raw)
In-Reply-To: <7d1e1ea3-d45f-5942-2bb0-7c41f65dd69b@gmx.net>
On 04/02/2017 11:33 AM, Florian Paul Schmidt wrote:
>> PulseAudio: Starting input alsa_input.pci-0000_00_1b.0.analog-stereo
>> PulseAudio: Starting output: alsa_output.pci-0000_00_1b.0.analog-stereo
>> AudioOutput: Initialized 1 channel 44100 hz mixer
>> AudioInput: Initialized mixer for 1 channel 44100 hz mic and 0 channel
>> 48000 hz echo
Oops and I misread this output. Yes, it seems mumble uses PA natively
here. So the first sentence in my reply below was wrong. The rest of the
reply still standts as being possibly helpful in understanding what can
go wrong in other scenarios.
Note though that I found the native PA support in mumble usually working
worse than using the PA virtual ALSA PCM device.
>
> Yes, this looks like mumble has opened an ALSA |PCM device that's not
> the default device called "default". If it's a PCM device that is going
> directly to a hardware device that does not provide stream mixing, then
> this will make other calls to ALSA to open that device (either directly
> or indirectly through another PCM device) _block_ until mumble has
> released the device again. Also, if the device is used by e.g. PA before
> mumble tries to open it, mumble's call to ALSA will _block_ until PA
> released the device.
>
> This is a longstanding bug in the ALSA API, that the ALSA devs do not
> consider a bug so it will never be fixed. There have been many
> discussions about how the call to ALSA should rather _fail_ than _block_
> in case of the device being busy (there's a sublety here that the
> failing behaviour is available, but nobody uses it, so you get this
> super annoying behaviour of calls to ALSA _blocking_)..
>
> If the PulseAudio installation shipped with GuixSD is "sane" then it
> will provide a virtual ALSA pcm device and will globally route the pcm
> device called "default" to this virtual PCM device. This device will
> provide stream mixing, etc..
>
> So any ALSA application that just uses the "default" PCM device should
> work out of the box with a sane PA installation since this "default" PCM
> device is just a name for the virtual PCM device provided by PA.
>
> Mumble additionally also has "native" PA support which you can build in.
> So to make mumble work on a PA system either
>
> 1] use the PA provided virtual PCM device "default"
>
> or
>
> 2] build mumble with native PA support and enable it in the preferences.
Flo
--
https://fps.io
next prev parent reply other threads:[~2017-04-02 9:38 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
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 [this message]
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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=f3637a8c-4915-1d8b-0d51-375c14a726cb@gmx.net \
--to=mista.tapas@gmx.net \
--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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).