From: Michael Whapples <mwhapples@aim.com>
To: "Speakup is a screen review system for Linux." <speakup@braille.uwo.ca>
Subject: Re: Speech Dispatcher 0.6.4 beta1 -- request for help with testing
Date: Sun, 15 Jul 2007 17:36:36 +0100 [thread overview]
Message-ID: <1184517396.4130.4.camel@layla.Mshome> (raw)
In-Reply-To: <1184396965.6917.37.camel@chopin>
I have just downloaded it and installed it, seems to be working fine at
the moment, and I am glad that there is now a espeak specific module.
One question about the espeak module, how can I change the voice? I have
tried setting the default voice in speechd.conf to FEMALE1 but it seems
to not have changed anything (even after restarting speech-dispatcher,
and even after a machine restart to make sure it did reload). Is it that
the espeak module doesn't support the different voices?
From
Michael Whapples
On Sat, 2007-07-14 at 00:09 -0700, Hynek Hanke wrote:
> Hello,
>
> the Brailcom organization would like to ask for help with testing
> Speech Dispatcher version 0.6.4 Beta1 for the upcomming release.
>
> You can download the distribution tarball at
> http://www.freebsoft.org/pub/projects/speechd/speech-dispatcher-0.6.4beta1.tar.gz
>
> What is new in 0.6.4?
> - Native output module for eSpeak (thanks to Lukas Loehrer)
> (called espeak, not espeak-generic)
> - Support for punctuation settings in the Generic output module
> (thanks to Steve Holmes)
> - Default audio output for all modules switched to ALSA
> - Support for listing output modules and voices supported by
> a synthesizer
> - Bug fixes (SMP related bugs, bugs in libspeechd and others)
>
> How to report bugs?
>
> Please report bugs at <speechd@bugs.freebsoft.org>. For other
> contact please use <speechd@lists.freebsoft.org>
>
> Thank you,
> Hynek Hanke
>
>
>
>
>
>
>
next prev parent reply other threads:[~ UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
Hynek Hanke
` Michael Whapples [this message]
` Lukas Loehrer
` Michael Whapples
` Lukas Loehrer
` Hynek Hanke
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=1184517396.4130.4.camel@layla.Mshome \
--to=mwhapples@aim.com \
--cc=speakup@braille.uwo.ca \
/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).