unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: ludo@gnu.org (Ludovic Courtès)
To: Ricardo Wurmus <ricardo.wurmus@mdc-berlin.de>
Cc: guix-devel@gnu.org
Subject: Re: [PATCH 2/2] gnu: Add espeak.
Date: Thu, 14 Jan 2016 14:32:11 +0100	[thread overview]
Message-ID: <874megs2w4.fsf@gnu.org> (raw)
In-Reply-To: <idj60ywfjxc.fsf@bimsb-sys02.mdc-berlin.net> (Ricardo Wurmus's message of "Thu, 14 Jan 2016 13:02:39 +0100")

Ricardo Wurmus <ricardo.wurmus@mdc-berlin.de> skribis:

> I’m not using pulseaudio; for me it’s just ALSA for regular software +
> JACK for “professional” audio where sync and timing matters.

That’s what I expected.  ;-)

> I’m not very knowledgeable about pulseaudio, unfortunately.  As
> pulseaudio can manage audio streams using various different backends
> from pulseaudio-agnostic software, what really is to be gained by adding
> pulseaudio to the inputs?  AFAIK using pulseaudio directly is not much
> different from using ALSA and configuring pulseaudio to manage this
> stream.

As you note, the main difference is configuration.  For ALSA-lib to use
PulseAudio, one has to drop the relevant ~/.asoundrc, but it seems that
it does not always work properly.

For instance, my ~/.asoundrc reads this:

--8<---------------cut here---------------start------------->8---
# FIXME: alsamixer & co. from alsa-utils don't support it.

pcm.!default {
    type pulse
}

# ctl.!default {
#     type pulse
# }
--8<---------------cut here---------------end--------------->8---

I don’t recall the details of the FIXME and the commented-out part,
though.

For GuixSD I think it would be best if everything would automatically go
through PulseAudio, without the user having to configure obscure things.

Ludo’.

  reply	other threads:[~2016-01-14 13:32 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-01-12  5:26 [PATCH 0/2] Add eSpeak Leo Famulari
2016-01-12  5:26 ` [PATCH 1/2] gnu: Add sonic Leo Famulari
2016-01-13 14:10   ` Ludovic Courtès
2016-01-14  3:28     ` Leo Famulari
2016-01-12  5:26 ` [PATCH 2/2] gnu: Add espeak Leo Famulari
2016-01-13 14:17   ` Ludovic Courtès
2016-01-14  3:27     ` Leo Famulari
2016-01-15  0:38       ` Leo Famulari
2016-01-15 16:15         ` Ludovic Courtès
2016-01-14 12:02     ` Ricardo Wurmus
2016-01-14 13:32       ` Ludovic Courtès [this message]
2016-01-17 16:09         ` Ricardo Wurmus
2016-01-17 20:30           ` PulseAudio & ALSA Ludovic Courtès
2016-02-09 21:45             ` Ricardo Wurmus
2016-01-12  5:58 ` [PATCH 0/2] Add eSpeak Leo Famulari
2016-01-12  6:01   ` Leo Famulari
2016-01-12 15:48   ` Andreas Enge
2016-01-12 19:30     ` Leo Famulari
2016-01-13  0:09       ` Leo Famulari
2016-01-13 14:01 ` PulseAudio Ludovic Courtès
2016-02-09 21:26   ` PulseAudio Christopher Allan Webber
2016-02-09 21:35     ` PulseAudio Leo Famulari
2016-02-12  9:12       ` PulseAudio Ludovic Courtès
2016-02-12 10:21         ` PulseAudio Ricardo Wurmus
2016-02-12 11:13           ` PulseAudio Alex Sassmannshausen
2016-02-15  7:38             ` PulseAudio Ricardo Wurmus
2016-02-15  8:56               ` PulseAudio Alex Sassmannshausen
2016-02-09 21:43     ` PulseAudio Ricardo Wurmus
2016-02-09 23:36     ` PulseAudio Jookia

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=874megs2w4.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=guix-devel@gnu.org \
    --cc=ricardo.wurmus@mdc-berlin.de \
    /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 public inbox

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

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).