From: Alex Kost <alezost@gmail.com>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: help-guix@gnu.org
Subject: Re: mumble issues with pulseaudio
Date: Mon, 03 Apr 2017 18:41:58 +0300 [thread overview]
Message-ID: <87k271wla1.fsf@gmail.com> (raw)
In-Reply-To: <87wpb1pzvv.fsf@gnu.org> ("Ludovic \=\?utf-8\?Q\?Court\=C3\=A8s\=22'\?\= \=\?utf-8\?Q\?s\?\= message of "Mon, 03 Apr 2017 12:08:20 +0200")
Ludovic Courtès (2017-04-03 12:08 +0200) wrote:
> Florian Paul Schmidt <mista.tapas@gmx.net> skribis:
>
>> 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..
>
> FWIW I have ~/.asoundrc with:
>
> pcm.!default {
> type pulse
> }
>
> to “reroute” ALSA applications to PulseAudio.
>
> I’m not sure whether we should do that by default, or install this
> .asoundrc for newly-created accounts. I guess some people may not want
> it.
At least I'm one of those people :-) I even have the following in my
.bash_profile to make sure that pulseaudio is never used:
export AUDIODRIVER=alsa
export SDL_AUDIODRIVER=alsa
--
Alex
next prev parent reply other threads:[~2017-04-03 15:42 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
2017-04-03 10:08 ` Ludovic Courtès
2017-04-03 15:41 ` Alex Kost [this message]
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=87k271wla1.fsf@gmail.com \
--to=alezost@gmail.com \
--cc=help-guix@gnu.org \
--cc=ludo@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).