From: ng0 <contact.ng0@cryptolab.net>
To: "Ludovic Courtès" <ludo@gnu.org>, help-guix@gnu.org
Subject: Re: mumble issues with pulseaudio
Date: Sat, 1 Apr 2017 15:46:13 +0000 [thread overview]
Message-ID: <20170401154613.olv3qzrd72x36edb@abyayala> (raw)
In-Reply-To: <20170401154331.ayicbw46mttkpsle@abyayala>
ng0 transcribed 1.6K bytes:
> Ludovic Courtès transcribed 0.9K bytes:
> > Hello,
> >
> > ng0 <contact.ng0@cryptolab.net> 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?
>
> It was listed as a dependency (if I remember correctly). When I start
> mumble, it appears under 'Applications' and 'All Streams' but not
> 'Virtual Streams'. I avoided getting into pulseaudio for a long time, so
> I can only guess (and read up on the topic).
> A clear sign that it does use pulseaudio would be references in the
> source code, messages in standard output / log with reference to
> pulseaudio, and what else?
This is the output just shortly after boot, ran pavucontrol before it:
[user@abyayala ~]$ mumble
CELT bitstream 8000000b from
/gnu/store/04nqixbnmv29v1nzansp50ppa5gdza4q-mumble-1.2.19/lib/mumble/libcelt0.so.0.7.0
CELT bitstream 80000010 from
/gnu/store/04nqixbnmv29v1nzansp50ppa5gdza4q-mumble-1.2.19/lib/mumble/libcelt0.so.0.11.0
Locale is "en_US" (System: "en_US")
TextToSpeech: Failed to contact speech dispatcher.
Database SQLite: "3.7.7.1"
Overlay: Listening on "/home/user/.MumbleOverlayPipe"
GlobalShortcutX: Using XI2 2.3
AudioInput: 40000 bits/s, 48000 hz, 480 sample
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
warning: The VAD has been replaced by a hack pending a complete rewrite
> > 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.
>
> The problem is that mumble sometimes appears in Applications of
> pavucontrol and sometimes it doesn't.
>
> > Note that applications that use PulseAudio, including ‘pavucontrol’,
> > automatically start the pulseaudio daemon if it’s not already running.
> >
> > HTH!
> > Ludo’.
> >
>
next prev parent reply other threads:[~2017-04-01 14:46 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 [this message]
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
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=20170401154613.olv3qzrd72x36edb@abyayala \
--to=contact.ng0@cryptolab.net \
--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).