From: ludo@gnu.org (Ludovic Courtès)
To: Florian Paul Schmidt <mista.tapas@gmx.net>
Cc: help-guix@gnu.org
Subject: Re: mumble issues with pulseaudio
Date: Sat, 08 Apr 2017 22:32:57 +0200 [thread overview]
Message-ID: <8760ieprly.fsf@gnu.org> (raw)
In-Reply-To: <7ec5d355-5b0d-fdf7-f63b-3f713bc33908@gmx.net> (Florian Paul Schmidt's message of "Wed, 5 Apr 2017 14:47:58 +0200")
Florian Paul Schmidt <mista.tapas@gmx.net> skribis:
> On 04/05/2017 11:57 AM, ng0 wrote:
>> Aren't we just talking about GuixSD here?
Not only. For some packages it’s a compile-time choice.
> Just as a sidenote: ALSA also has global configuration files,
> e.g. here on ubuntu they live in:
>
> /usr/share/alsa/alsa.conf
>
> and
>
> /usr/share/alsa/alsa.conf.d/
>
> On ubuntu the default ALSA device is routed through PA without a user
> having a ~/.asoundrc. That latter file is used for further
> customization by the user.
Indeed. I just checked on Debian and the situation is similar. It’s
doing something quite sophisticated; from
/usr/share/alsa/alsa.conf.d/pulse.conf:
--8<---------------cut here---------------start------------->8---
# PulseAudio alsa plugin configuration file to set the pulseaudio plugin as
# default output for applications using alsa when pulseaudio is running.
hook_func.pulse_load_if_running {
lib "libasound_module_conf_pulse.so"
func "conf_pulse_hook_load_if_running"
}
@hooks [
{
func pulse_load_if_running
files [
"/usr/share/alsa/pulse-alsa.conf"
"/etc/asound.conf"
"~/.asoundrc"
]
errors false
}
]
--8<---------------cut here---------------end--------------->8---
I tried it on GuixSD and couldn’t get it to work though.
Ludo’.
next prev parent reply other threads:[~2017-04-08 20:33 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
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 [this message]
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=8760ieprly.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=help-guix@gnu.org \
--cc=mista.tapas@gmx.net \
/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).