From: Chris Brannon <chris@the-brannons.com>
To: speakup@linux-speakup.org
Subject: Re: you really do not want to upgrade to alsa-lib 1.1.2
Date: Tue, 09 Aug 2016 09:22:38 -0700 [thread overview]
Message-ID: <87oa51di9d.fsf@mushroom.localdomain> (raw)
In-Reply-To: <f8da4f0b-702a-e32f-7eef-9f2b459ef728@raspberryvi.org> (Mike Ray's message of "Tue, 9 Aug 2016 12:12:23 +0100")
Mike Ray <mike@raspberryvi.org> writes:
> Could this be what is causing the sd_espeak module of speech-dispatcher
> to regularly crash and be unloaded when using speech-dispatcher set to
> 'AudioOutputMethod "alsa' ?
Mike,
It might be a similar issue on the Speech Dispatcher side. They're not
directly related, since Speech Dispatcher uses its own audio output
code, rather than letting espeak handle audio output on its own. If you
started noticing new and unexpected sd_espeak crashes after upgrading
your alsa library, then Speech Dispatcher's alsa code may not be playing
well with the new library either.
-- Chris
next prev parent reply other threads:[~ UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
Chris Brannon
` Zachary Kline
` Chris Brannon
` Kyle
` Chris Brannon
` Mike Ray
` Jude DaShiell
` Chris Brannon [this message]
` covici
` Zachary Kline
` covici
` Kirk Reiser
` Jason White
` Chris Brannon
` Jude DaShiell
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87oa51di9d.fsf@mushroom.localdomain \
--to=chris@the-brannons.com \
--cc=speakup@linux-speakup.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).